Acpi — 80860f14

The trouble begins when you install , FreeBSD , or even an unmodified Windows PE environment. Symptom 1: The Unknown Device In Windows Device Manager, you may see an entry under “Other devices” labeled “Unknown device” with the Hardware ID ACPI 80860F14 . No driver is loaded, and consequently, there is no audio. Symptom 2: Linux dmesg Errors On Linux, the kernel’s ACPI subsystem will parse the tables and attempt to match the ID to a driver. Without the proper kernel modules or firmware, you will see errors like:

The machine driver tells the SST core how to talk to 80860F14 . For most Bay Trail devices: Acpi 80860f14

On Bay Trail tablets and embedded boards, OEMs hardcode the audio codec and its connections into the ACPI DSDT using custom methods. While Windows drivers are tolerant and use a fallback mechanism, the Linux snd_soc_sst driver requires exact matching between the ACPI ID and a known machine driver (e.g., bytcr_rt5640 , bytcr_rt5651 ). The trouble begins when you install , FreeBSD

acpi 80860F14: failed to add I2C device for audio codec snd_soc_sst_bytcr_rt5640: probe of 80860F14 failed with error -22 bytcr_rt5640: ACPI HID 80860F14 not found Even if the main HDA Intel driver loads (for HDMI audio), the internal speakers and headphone jack remain silent. aplay -l or cat /proc/asound/cards will show only HDMI or no card at all. Technical Deep Dive: Why Linux Struggles The Linux kernel has supported Intel SST since version 3.14, but Bay Trail support has been notoriously finicky. The problem is rarely the kernel itself—it is the ACPI BIOS . Symptom 2: Linux dmesg Errors On Linux, the

Sometimes the legacy snd_hda_intel grabs the PCI slot. Blacklist it in /etc/modprobe.d/blacklist.conf :