Arch linux system upgrade killed my audio

System Details

  • Device: ezkinil
  • OS: arch linux
  • Firmware Type: UEFI Full ROM
  • Firmware Version: MrChromebox-2606.1
  • Internal storage type: SSD M2

Summary of the Issue

hello. i did pacman -Syu in the morning and it upgraded a few important packages (wireplumber, libwireplumber, and both linux/linux-zen kernels). turned off the laptop a couple hours after that because i went out. now i come home and i realise audio is dead. only output device listed in pavucontrol is a dummy output, not the “acp3xalc5682m98 Speakers” and “acp3xalc5682m98 Headphones” that existed before the update. (these two were created by the chromebook audio script by weirdtreething)

reran the weirdtreething audio script and it did nothing to solve the issue. tried to manually enable wireplumber again by running “systemctl --user --now enable wireplumber” in terminal but it did nothing either. “wpctl status” doesn’t even show the acp3xalc5682m98 devices.

debugging script output

Steps to Reproduce

  1. do pacman -Syu

  2. ???

  3. lose your audio

Expected Behavior

nothing shouldn’t have happened. audio should have stayed the same after the upgrade.

EDIT:

refer to this thread i made in the arch linux’s forums. seems like the issue is kernel regression: audio works in the linux-lts kernel (which uses the 6.18 kernel). now: idk if the faulty detection of the output devices should be a fix to the script by weirdtreething, or if we should wait for a new kernel update that fixes this?

this is not unexpected when you live on the bleeding edge and use a rolling release distro

1 Like

its just 2 weeks since i installed arch for the first time, didnt know itd be like this! u.u

where should i report the issue? is this something that concerns the kernel devs or the arch devs? or does the audio script need to be fixed so it works with the new kernel?

Having the same issue. Lantis (HP 14a-na1014ns) i just reinstalled CachyOS (Arch distro) and the audio setup script doesnt work.

PD: Nevermind, my issue was for having Intel ME disabled