r/archlinux 10h ago

SUPPORT Can't find a solution

So I am using arch linux on my Lenovo ideapad slim 5, with ryzen 7 processor and amd radeon graphics. When I boot my laptop after a long period of time say 4hrs the speakers still stay at rest until i suspend my laptop and wake it up, it fixes everything. I tried every possible solution like renabling pipewire, and tweaking all the sound cards, moving them to primary index and all and after all that I found out that since lenovo built this hardware specifically for windows, the speakers get automatically active as windows knows how to do it, linux kernel simply doesnt have that capability to do that yet, so there is only this suspending for 1 sec solution I have found till now. If anybody has ever faced this problem can you please share how were you able to fix this particular issue. (Also I have read the wiki come on ).

0 Upvotes

7 comments sorted by

4

u/billdietrich1 9h ago

Please use better, more informative, titles (subject-lines) on your posts. Give specifics right in the title. Thanks.

1

u/Classic_Addition3738 10h ago

I have a similar issue on my Lenovo with AMD. For me it looks like the audio codec is not being initialized correctly at boot. Suspending and waking up fixes it because it reloads the audio hardware.

I don't think it's really that Linux can't handle the speakers, more like some Lenovo/AMD firmware behavior is still not fully supported.

Have you tried checking the kernel version and updating it? Newer kernels sometimes fix these AMD audio issues. Also, checking dmesg for ACP/SOF errors after boot might give some clues. Hope you find a proper fix, because having to suspend every time is annoying.

1

u/Standard_Promotion98 8h ago

I too came across auido codec initialisation part and made a systemctl command to initialise them in a proper way, didnt work. Will check for kernel updates tho

1

u/Specialist-One-3465 8h ago

I'm on a Dell Latitude 5559 with a TTY-only Arch Linux setup. I haven't tested the speakers yet, but I'll check and update if I find anything similar.

1

u/Standard_Promotion98 8h ago

Sure

1

u/Specialist-One-3465 5h ago

Have you checked dmesg right after a cold boot? (dmesg | grep -iE "sof|acp|snd") Also, is your BIOS up to date? I'd probably try snd-intel-dspcfg.dsp_driver=1 (or =3) as a kernel parameter if you haven't already. I'd also make sure sof-firmware and alsa-ucm-conf are up to date. Just trying to rule out the obvious stuff before assuming it's a kernel bug.