Right-click the device in Device Manager and select .
You need to tell the kernel to ignore the broken ACPI entry or to use a specific quirk.
When a device shows a yellow warning triangle labeled "Unknown Device" or "Multimedia Audio Controller" in Device Manager, the OS is failing to map the hardware ID to a functional software architecture. Acpi Essx8336 1
ACPI is the standard that allows an operating system to discover hardware components, manage power states (sleep, hibernate), and control peripherals. When Linux boots, it parses the ACPI tables from the BIOS/UEFI. If a device is defined in ACPI but the OS cannot find a proper driver or configuration, it throws an "ACPI Error."
While Windows generally has mature driver support, users with generic or off-brand laptops often find themselves with a "missing driver" for the Everest I2S Codec Audio Device . The shows a yellow exclamation mark next to the entry for ACPI\ESSX8336\1 . Right-click the device in Device Manager and select
Right-click the problem device showing the ESSX8336 ID and select .
Select from the dropdown. If you see ACPI\VEN_ESSX&DEV_8336 , you have found the culprit. 2. Install Intel Smart Sound Technology (SST) First ACPI is the standard that allows an operating
Download and install the and the Intel Management Engine . Restart your computer. 3. Manual Driver Installation
Encountering in your logs is a rite of passage for Linux users on modern Intel hardware. While frustrating, it is not a hardware defect. It is a software handshake failure between the BIOS’s ACPI table and the Linux audio stack.
For Linux enthusiasts, this chip was a "dealbreaker" for years. While recent kernel updates (v6.x and newer) and the Sound Open Firmware (SOF) project have made strides, many distributions still require manual tinkering with HiFi.conf or UCM (Use Case Manager) files to get internal microphones or speakers to trigger correctly.
options snd_soc_sof_es8336 quirk=0x1