Recent update appears imcompatible with audio firmware. Some but not all audio devices do not work

Hello all,

I discovered after updating today that my built in speakers on my laptop no longer work, but my 3.5mm audio jack headphones still do. I usually keep my speakers muted, so the problem may have happened earlier without me realizing it.

Here is my bug report printout: 51f04d3

To save you some reading, my audio card is an Intel Alder Lake PCH-P High Definition Audio card.

When I search for audio sinks, they all appear to be suspended, including my headphones, which work. The headphones and built-in speaker seem to be mutually exclusive, so this is the printout with the headphones not plugged in:

base ❯ pactl list short sinks                                                                                (base) 
1178    alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__HDMI3__sink     PipeWire        s24-32le 2ch 48000Hz        SUSPENDED
1179    alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__HDMI2__sink     PipeWire        s24-32le 2ch 48000Hz        SUSPENDED
1180    alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__HDMI1__sink     PipeWire        s24-32le 2ch 48000Hz        SUSPENDED
1181    alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__Speaker__sink   PipeWire        s32le 2ch 48000Hz   SUSPENDED

Running speaker-test produces no output whatsoever, even on maximum volume.

I have checked that my speakers are not muted in alsamixer.

I tried restarting pipewire, pipewire-pulse, and wireplumber.

I reinstalled sof-firmware, since only one version appears on pacman.

Launching in lts mode makes no difference.

Running dmseg produces, among other things, the following:

sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware info: version 2:2:0-57864
sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:1

Which I believe indicates that the Kernel and Firmware ABIs do not align.

For now, I’m just using my headphones, since they work for some reason. Please let me know if you have any recommendations and I apologize for not following the template. I looked around a little but I couldn’t find it.

For anyone who was interested in this thread, I installed another recent update and the problem seems to be corrected.

I never did find the actual source of the issue, however.