No sound after update on Lenovo X9-15

Ask Fedora
, ,
1

After updating and rebooting my system, a Lenovo X9-15 with Intel Lunar Lake running Fedora 43 KDE Desktop Edition, the internal speakers are no longer detected.
The kernel was updated to Linux fedora 6.17.8-300.fc43.x86_64.

lspci -k shows the audio hardware:

00:1f.3 Multimedia audio controller: Intel Corporation Lunar Lake-M HD Audio Controller (rev 10)
        Subsystem: Lenovo Device 233b
        Kernel driver in use: sof-audio-pci-intel-lnl
        Kernel modules: snd_sof_pci_intel_lnl, snd_hda_intel

There are bug reports on Ubuntu with the Lenovo X9-14. I don’t know if these issues are related:

I have found a workaround: Booting the old kernel Linux fedora 6.17.7-300.fc43.x86_64 brings back the audio device.

2 Likes
3

same issue. can rollback to Linux fedora 6.17.7-300.fc43.x86_64 however that kernel has its own stability issues.

4

Same on my Thinkpad X9 15 - booting 6.17.7-300 solves it for now.

5

Same here, Dell 14 Pro Premium. Rolled back to 6.17.7 for now.

6

Same on Lenovo Yoga Aura 7i (Lunar Lake). Not only do the interal speakers not show as a device (neither do the hdmi speakers show as a device), but worse: The usb-dock audio out does show as a device, but no audible sound output comes out when selecting this device. All of this is working on 6.17.7. I didn’t bother testing mic-input devices this time, but mic input was also gone in the late Fedora 42 updates, when the audio output was also broken.

7

Likewise. 9i audio stopped working and it keeps trying to connect to nearby airplay devices for audio. I’ll just get a pop up for “blah’s Macbook volume 0%” on my screen.

Edit: The strikethrough section is a separate bug, though still from pipewire.

8

Following the steps on this page didn’t work sadly. I think it’s a bug

9

People in Arch are having the same issue. I think it’s upstream and we just have to wait or use 6.17.7

1 Like
10

6.17.9, which I installed today, has the same issue.
I downgraded to 6.17.7 again.

1 Like
11

Same here, sadly.

12

6.17.10 from updates-testing fixes it.

2 Likes