sudo modprobe snd_soc_sst_bytcr_rt5640 If that fails, try:
snd_intel_sst.acpi_path=80860F14 Or for newer kernels using SOF (Sound Open Firmware): Acpi 80860f14
Open a terminal and run:
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: Symptom 2: Linux dmesg Errors On Linux, the
For ACPI 80860F14 , SOF handles the device much more elegantly. On Linux kernel 5.4+, you can enable SOF with: sudo modprobe snd_soc_sst_bytcr_rt5640 If that fails
The machine driver tells the SST core how to talk to 80860F14 . For most Bay Trail devices:
sudo modprobe snd_soc_sst_bytcr_rt5651 sudo modprobe snd_soc_sst_cht_bsw_rt5672 Add the following to your bootloader (GRUB) kernel command line: