Skip to content

[BUG] #10989

Description

@BeepPlayz

Audio Issues with sof-essx8336 (Everest ES8336) on Kali Linux - UCM cset error

Hardware & System Information

  • Laptop Model: Infinix X2 Slim Intel Core i3 11th Gen 1115G4
  • OS: Kali Linux (Rolling)
  • Kernel Version: 6.19.14+kali-amd64
  • Audio Server: PipeWire (WirePlumber)

Problem Description

I am unable to get any audio output from my internal laptop speakers. The audio card is detected by the kernel and appears in aplay -l, but no sound is produced. Bluetooth audio works perfectly fine, confirming that the audio server layer is operational.

Diagnostic Outputs

  1. Output of aplay -l:
    card 0: sofessx8336 [sof-essx8336], device 0: ES8336 () []
    Subdevices: 1/1
    Subdevice #0: subdevice #0
    card 0: sofessx8336 [sof-essx8336], device 5: HDMI 1 (
    ) [HDMI 1]
    card 0: sofessx8336 [sof-essx8336], device 6: HDMI 2 () [HDMI 2]
    card 0: sofessx8336 [sof-essx8336], device 7: HDMI 3 (
    ) [HDMI 3]

  2. Error during sudo alsactl init:
    When attempting to initialize ALSA, the system throws the following UCM sequence execution error, indicating a control-name mismatch or missing routing bits in the UCM configuration:

Steps Already Tried

  • Attempted overriding options using snd_soc_sof_8336 quirk=0x01 and 0xf0 via modprobe configuration, but with no success.
  • Cleaned user-level PipeWire state directories (~/.config/pulse and ~/.local/state/wireplumber).
  • Restoring asound.state from the official community repository failed to match the control switches.

The hardware works flawlessly on Windows, indicating this is purely a Linux pin-routing/UCM mapping issue for this specific motherboard topology.

Could anyone guide me on how to supply the correct quirk parameters or patch the

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working as expected

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions