The ES8336 needs Use Case Manager (UCM) configuration files to define how the hardware switches between speakers and headphones. If the distro does not play sound, manually place the Es8336.conf files into /usr/share/alsa/ucm2/conf.d/sof-ess8336/ . This often resolves the issue. Why is this hardware so difficult?
The solution usually involves a multi-step driver installation if this hardware ID appears in Windows Device Manager. Standard Windows Updates often do not find the correct driver for this specific hardware ID. 1. Driver Signature Problem Acpi Essx8336 1
Device Manager shows an "Unknown Device" or "Multimedia Audio Controller" with a yellow exclamation mark. The hardware ID is ACPI\VEN_ESSX&DEV_8336 . The ES8336 needs Use Case Manager (UCM) configuration
Ensure alsa-ucm-conf and sof-firmware are installed through the package manager. Why is this hardware so difficult
The "ACPI ESSX8336 1" device ID refers to the Everest Semiconductor ES8336 audio codec. This component is common in budget laptops and 2-in-1 devices. These devices often use Intel Gemini Lake, Jasper Lake, and Tiger Lake processors. The ES8336 is known for efficient power use in portable devices. However, users often report "No Output Device Found" errors, particularly after a new Windows installation or when switching to Linux.
The ES8336 needs the Intel SST driver to function. Before installing the Everest driver, ensure the "Intel(R) Smart Sound Technology (Intel(R) SST) OED" and "Intel(R) Smart Sound Technology (Intel(R) SST) Audio Controller" are installed under System Devices. 3. Manual Update via "Have Disk"
Many ES8336 drivers from smaller OEMs are not digitally signed. To install them, temporarily disable Driver Signature Enforcement. Go to and select the option to disable signature requirements upon reboot. 2. Intel Smart Sound Technology (SST) Dependency