Audio stopped working after update

jojomodding · 2024-01-08 17:50:03

Hi guys,

Recently, I updated my OS and then (after the next reboot), audio stopped working. I have ThinkPad with a Raptor Lake Intel CPU (i7-1370P) and am using PipeWire.
Concretely, when booting, the mute LED turns on immediately (before I even log in, it did not do this before), and nothing I do can make sound come out of the speakers.

What might cause this?

seth · 2024-01-08 21:51:24

Kernel update?
Tried LTS kernel?

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

jojomodding · 2024-01-09 00:42:14

Kernel update? Yes
Tried LTS Kernel? Yes, to no effect.

Log: http://0x0.st/HINZ.txt

This is with the LTS kernel, but the error messages look similar with the latest (I can post that, if wanted).
Note that I changed the device status from "Off" to "On" in `pavucontrol" after a few seconds. This had no obviously observable effect, as it switched back to "Off" almost immediately.

seth · 2024-01-09 08:09:49

Jan 09 01:38:54 JosETHLaptop kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: ------------[ DSP dump start ]------------
Jan 09 01:38:54 JosETHLaptop kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: DSP panic!
Jan 09 01:38:54 JosETHLaptop kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: fw_state: SOF_FW_BOOT_COMPLETE (6)
Jan 09 01:38:54 JosETHLaptop kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: 0x00000005: module: ROM, state: FW_ENTERED, running
Jan 09 01:38:54 JosETHLaptop kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: status code: 0xdead006 (unknown)

and we're off to the races.

Since the kernel doesn't matter, did you also update https://archlinux.org/packages/extra/x8 … -firmware/ and does it help to downgrade that?

jojomodding · 2024-01-09 20:49:15

Yes I updated the entire system (as one should do), which might have included sof-firmware. I downgraded it to 2023.09.1-1, but that did not help.

Last edited by jojomodding (2024-01-09 20:49:48)

seth · 2024-01-09 21:19:07

which might have included sof-firmware

=> /var/log/pacman.log

1. check what was actually in the ciritical udpate
2. check your older journals (eg. "… -b -5" for 5 boots ago) whether you had the same DSP panics there.

jojomodding · 2024-01-09 21:39:47

As for 2: These crashes do not come up regularly. Often, there is only

Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,0p: Channels doesn't match (requested 64, got 2)
Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,0c: Channels doesn't match (requested 64, got 2)
Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,3p: Channels doesn't match (requested 64, got 2)
Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,4p: Channels doesn't match (requested 64, got 2)
Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,5p: Channels doesn't match (requested 64, got 2)
Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,6c: Channels doesn't match (requested 64, got 4)
Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,7c: Channels doesn't match (requested 64, got 4)
Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,31p: Channels doesn't match (requested 64, got 2)
Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,0p: Channels doesn't match (requested 64, got 2)
Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,0p: Channels doesn't match (requested 64, got 2)
Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,0c: Channels doesn't match (requested 64, got 2)
Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,0c: Channels doesn't match (requested 64, got 2)
Jan 09 21:47:18 JosETHLaptop wireplumber[1286]: <WpSiAudioAdapter:0x56528d6933c0> Object activation aborted: proxy destroyed
Jan 09 21:47:18 JosETHLaptop wireplumber[1286]: <WpSiAudioAdapter:0x56528d6933c0> failed to activate item: Object activation aborted: proxy destroyed
Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,3p: Channels doesn't match (requested 64, got 2)
Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,3p: Channels doesn't match (requested 64, got 2)
Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,4p: Channels doesn't match (requested 64, got 2)
Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,4p: Channels doesn't match (requested 64, got 2)
Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,5p: Channels doesn't match (requested 64, got 2)
Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,5p: Channels doesn't match (requested 64, got 2)
Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,6c: Channels doesn't match (requested 64, got 4)
Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,6c: Channels doesn't match (requested 64, got 4)
Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,7c: Channels doesn't match (requested 64, got 4)
Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,7c: Channels doesn't match (requested 64, got 4)
Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,31p: Channels doesn't match (requested 64, got 2)
Jan 09 21:47:18 JosETHLaptop pipewire[1285]: spa.alsa: hw:0,31p: Channels doesn't match (requested 64, got 2)

There are quite a few DSP dumps in my log, though, and the earliest is a few days after I first installed Linux. And indeed, I've had intermittent sound issues (see https://bbs.archlinux.org/viewtopic.php?id=290477) which might have been related, but at least I heard something *sometimes*..

seth · 2024-01-09 21:54:13

Can you right now "mpv -ao alsa thunderstruck.mp3"?

jojomodding · 2024-01-09 22:10:41

It is shown as playing, but no sound comes out (although `pavucontrol` shows there should be some, and bluetooth headphones work)

seth · 2024-01-09 22:25:04

seth wrote:

1. check what was actually in the ciritical udpate

Do non-bluetooth headphones work as well (ie. such using a phone jack)?

jojomodding · 2024-01-09 22:26:47

Good question.. I'll test as soon as I find some

seth · 2024-01-09 22:29:08

x-ref: https://bbs.archlinux.org/viewtopic.php … 2#p2142222

devourer · 2024-01-12 01:41:45

jojomodding wrote:

Hi guys,
Recently, I updated my OS and then (after the next reboot), audio stopped working. I have ThinkPad with a Raptor Lake Intel CPU (i7-1370P) and am using PipeWire.
Concretely, when booting, the mute LED turns on immediately (before I even log in, it did not do this before), and nothing I do can make sound come out of the speakers.
What might cause this?

I don't know what's causing the problem, but I have a similar machine as you and what you are describing happened to me yesterday after a system update/reboot. I was able to get sound in Chrome and Firefox, but not in VLC or mpv. I remembered the exact same thing had happened many months ago and, after a lot of googling, I found a solution that fixed the problem, which I applied once again: I simply renamed/backed up the folder ~/.local/state/wireplumber to ~/.local/state/wireplumber.bak. Then, after rebooting, the wireplumber folder and its configuration files were recreated and the sound was working perfectly again in all applications.

I hope this helps.

samA29 · 2024-01-13 03:21:19

devourer wrote:

jojomodding wrote:
Hi guys,
Recently, I updated my OS and then (after the next reboot), audio stopped working. I have ThinkPad with a Raptor Lake Intel CPU (i7-1370P) and am using PipeWire.
Concretely, when booting, the mute LED turns on immediately (before I even log in, it did not do this before), and nothing I do can make sound come out of the speakers.
What might cause this?
I don't know what's causing the problem, but I have a similar machine as you and what you are describing happened to me yesterday after a system update/reboot. I was able to get sound in Chrome and Firefox, but not in VLC or mpv. I remembered the exact same thing had happened many months ago and, after a lot of googling, I found a solution that fixed the problem, which I applied once again: I simply renamed/backed up the folder ~/.local/state/wireplumber to ~/.local/state/wireplumber.bak. Then, after rebooting, the wireplumber folder and its configuration files were recreated and the sound was working perfectly again in all applications.
I hope this helps.

Yup this fixes it.

sam

JBG7 · 2024-05-03 19:32:42

devourer wrote:

jojomodding wrote:
Hi guys,
Recently, I updated my OS and then (after the next reboot), audio stopped working. I have ThinkPad with a Raptor Lake Intel CPU (i7-1370P) and am using PipeWire.
Concretely, when booting, the mute LED turns on immediately (before I even log in, it did not do this before), and nothing I do can make sound come out of the speakers.
What might cause this?
I don't know what's causing the problem, but I have a similar machine as you and what you are describing happened to me yesterday after a system update/reboot. I was able to get sound in Chrome and Firefox, but not in VLC or mpv. I remembered the exact same thing had happened many months ago and, after a lot of googling, I found a solution that fixed the problem, which I applied once again: I simply renamed/backed up the folder ~/.local/state/wireplumber to ~/.local/state/wireplumber.bak. Then, after rebooting, the wireplumber folder and its configuration files were recreated and the sound was working perfectly again in all applications.
I hope this helps.

I don't know how to thank you enough, I'd never find this without your forum post and it really helps. My configuration:

Lenovo Legion Pro 7 16IRX9H (2024 model)

devourer · 2024-05-03 19:58:03

You're most welcome.

eXpies · 2024-09-30 11:45:51

Just wanted to say THANKS!

devourer wrote:

jojomodding wrote:
Hi guys,
Recently, I updated my OS and then (after the next reboot), audio stopped working. I have ThinkPad with a Raptor Lake Intel CPU (i7-1370P) and am using PipeWire.
Concretely, when booting, the mute LED turns on immediately (before I even log in, it did not do this before), and nothing I do can make sound come out of the speakers.
What might cause this?
I don't know what's causing the problem, but I have a similar machine as you and what you are describing happened to me yesterday after a system update/reboot. I was able to get sound in Chrome and Firefox, but not in VLC or mpv. I remembered the exact same thing had happened many months ago and, after a lot of googling, I found a solution that fixed the problem, which I applied once again: I simply renamed/backed up the folder ~/.local/state/wireplumber to ~/.local/state/wireplumber.bak. Then, after rebooting, the wireplumber folder and its configuration files were recreated and the sound was working perfectly again in all applications.
I hope this helps.

Arch Linux

#1 2024-01-08 17:50:03

Audio stopped working after update

#2 2024-01-08 21:51:24

Re: Audio stopped working after update

#3 2024-01-09 00:42:14

Re: Audio stopped working after update

#4 2024-01-09 08:09:49

Re: Audio stopped working after update

#5 2024-01-09 20:49:15

Re: Audio stopped working after update

#6 2024-01-09 21:19:07

Re: Audio stopped working after update

#7 2024-01-09 21:39:47

Re: Audio stopped working after update

#8 2024-01-09 21:54:13

Re: Audio stopped working after update

#9 2024-01-09 22:10:41

Re: Audio stopped working after update

#10 2024-01-09 22:25:04

Re: Audio stopped working after update

#11 2024-01-09 22:26:47

Re: Audio stopped working after update

#12 2024-01-09 22:29:08

Re: Audio stopped working after update

#13 2024-01-12 01:41:45

Re: Audio stopped working after update

#14 2024-01-13 03:21:19

Re: Audio stopped working after update

#15 2024-05-03 19:32:42

Re: Audio stopped working after update

#16 2024-05-03 19:58:03

Re: Audio stopped working after update

#17 2024-09-30 11:45:51

Re: Audio stopped working after update

Board footer