Sometimes the legacy snd_hda_intel grabs the PCI slot. Blacklist it in /etc/modprobe.d/blacklist.conf :
Fortunately, the open-source community—specifically the Linux kernel and SOF teams—has made vast strides. With the right kernel modules, firmware files, and a bit of persistence, the mute can be lifted. For the average Windows user, it is a simple driver hunt. For the Linux enthusiast, it is a rite of passage into the world of ACPI debugging. Acpi 80860f14
snd_intel_sst.acpi_path=80860F14 Or for newer kernels using SOF (Sound Open Firmware): Sometimes the legacy snd_hda_intel grabs the PCI slot
sudo dmesg | grep -i "sst" sudo i2cdetect -l (if i2c-tools installed) Look for references to "byt" or "cht" and a codec ID like RT5640, RT5651, or ES8316. For the average Windows user, it is a simple driver hunt
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 .
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: