You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Lenovo Yoga Slim 7 15ILL9 - No sound coming from speakers #9720
Describe the bug
Despite a topology in place, the Lenovo machine doesn't produce sound from the speakers.
To Reproduce
Install Ubuntu 24.10 on the laptop, build & install 6.12.0-rc7+ kernel, then boot the laptop. With sof topology updated, sound is not being made from the speakers.
Reproduction Rate
Always
Expected behavior
Sound should be heard from the speakers.
Impact
No audio, results in an annoyance, but doesn't stop the system from functioning.
Environment
Branch name and commit hash of the 2 repositories: sof (firmware/topology) and linux (kernel driver).
It's a tangent, but I'd be extremely interested in the contents of the /sys/firmware/efi/efivars/CirrusSmart* files - when you get a chance could you drop them here or on the new ticket we use to further investigate this system?
@simontrimmer , here are the contents of the directory, as requested from #9663:
/sys/firmware/efi/efivars$ ls | grep "CirrusSmart*"
CirrusSmartAmpCalibrationData-02f9af02-7734-4233-b43d-93fe5aa35db3
CirrusSmartCalInfo-ea064247-46bd-433b-9249-e31b63a64172
@cgbowman - Great they are both there - could you attach them and laser etched underneath is the date of manufacture "mfg date" could you grab that too please?
I'm assuming it looks to you like it is playing back and not like sox's play tool that doesn't show progress if the data isn't flowing?
Could you attach the output of alsa-info and maybe "wpctl status" as I don't think that is included yet...
Cheers
-Simon
@cgbowman Thanks! I'm out of the workshop now but will compare with the one I have tomorrow, but I'm 99% certain that I have more Sinks than you see in your wpctl output - I wonder if this is one of those ucm problems?
(The unit I have will almost certainly have had all the files updated to the latest from https://github.com/alsa-project/alsa-ucm-conf as I'd recently had some fun with another product and this Lenovo would have been installed off a live USB image I'd made for the one that needed the updated ucm configuration)
@simontrimmer, I updated the files, rebooted, and the Settings menu's 'output device' shows as "Dummy Output". Specifically, adding the change to the sof-soundwire.conf file causes the change.
I've also tried changing the entire ucm2 folder and replacing it with the latest dir available in the alsa-ucm-conf repo and I observe the same issue.
@cgbowman Interesting - I suspect we're in the right area .... Is there an error message from the UCM?
Looking at the one I have here:
...
│
├─ Sinks:
│ 56. Lunar Lake-M HD Audio Controller HDMI / DisplayPort 3 Output [vol: 1.00]
│ 57. Lunar Lake-M HD Audio Controller HDMI / DisplayPort 2 Output [vol: 1.00]
│ 58. Lunar Lake-M HD Audio Controller HDMI / DisplayPort 1 Output [vol: 1.00]
│ * 59. Lunar Lake-M HD Audio Controller Headphones + Speaker [vol: 0.37]
│
...
which mirrors the outputs to HDMI and the cs42l43/cs35l56 pair, and it looks like when I upgraded the alsa-ucm-conf files they were matched with similarly dated alsa-lib and alsa-utils, I think a new file syntax (7) was introduced that might be confusing it, this was important to make a different system I was using work, but it could also apply here too.
@cgbowman just checking, was your alsa-info data above produced with active playback (if not, pls run again with music as speaker test is quite fast/short) ? Just want to rule out userspace isn't incorrectly modifying mixer values when a stream is started/stopped.
@cgbowman just checking, was your alsa-info data above produced with active playback (if not, pls run again with music as speaker test is quite fast/short) ? Just want to rule out userspace isn't incorrectly modifying mixer values when a stream is started/stopped.
Apologies, it was not produced with active playback. I will upload more info when I have the chance.
@charleskeepax would not having a headset plugged in be the most likely reason for the Jack Override returning -EBUSY?
I was saying earlier today I should come back to this - I do think that something in the alsa-ucm-conf / alsa-utils / alsa-lib isn't happy and that is just snowballing, but the only way I could think of reproducing the problem and then working out what was happening was to sacrifice my working system running Debian12+updates and basically starting again with a clean Ubuntu noble install and working through the problems. I did that recently on a different product and whilst I got to do what I needed in the sound domain, the UI experience was less than enjoyable and put me off rushing into it 😁 Might be a good week for it.
@cgbowman - just checking, did you update the alsa-utils & alsa-lib when you updated the UCM files? (thinking about syntax 7)
There was a UEFI update about a week ago, but sound isn't working yet. The system recognizes seven different output devices which are all non-functional, plus the dummy output. I would like to help diagnose and hopefully solve this problem, but I don't know where to begin - SOF and sound in general are new to me.
Can confirm I am seeing the same behaviour as @Scharkenberg . Using EndeavourOS, with the default kernel 6.13.2 shows Dummy Output. Upgrading to 6.14-rc3 now at least detects Lunar Lake-M HD Audio Controller, but still no audio and 7 different audio output options. Happy to provide any logs to get this addressed.
Unrelated, but for anyone reading this, I found my laptop fans weren't working on kernel 6.13.2. 6.14 has resolved this.
I just updated my test unit to the public bios release "DMI: LENOVO 83HM/LNVNB161216, BIOS NYCN66WW 01/15/2025" and early indications are extremely positive - I used a kernel built the head of Linus' branch and even the annoying "it hangs at some point, probably power management related" has gone.
I have an early ubuntu 25.04 build on here at the moment, but the key feature for people is to make sure that they have the latest alsa components (some of the alsa-ucm-conf files now have file format dependencies on the newer alsa-lib/alsa-utils).
The distro has:
ii alsa-ucm-conf 1.2.12-1ubuntu1 all ALSA Use Case Manager configuration files
ii alsa-utils 1.2.13-1ubuntu1 amd64 Utilities for configuring and using ALSA
and wpctl status was only showing the Dummy Output, updating my alsa-ucm-conf files to the head solved that problem.
Depending on your distribution, you might need to get update the linux-firmware repository - I published the initial tuning files a long time ago now but that's not very long when considering Linux distribution cadences. The files I booted up with were the ones I published yesterday but the originals will produce sound.
Merge tag 'sound-6.14-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound
Pull sound fixes from Takashi Iwai:
"A slightly large collection of fixes, spread over various drivers.
Almost all are small and device-specific fixes and quirks in ASoC SOF
Intel and AMD, Renesas, Cirrus, HD-audio, in addition to a small fix
for MIDI 2.0"
* tag 'sound-6.14-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound: (41 commits)
ALSA: seq: Drop UMP events when no UMP-conversion is set
ALSA: hda/conexant: Add quirk for HP ProBook 450 G4 mute LED
ALSA: hda/cirrus: Reduce codec resume time
ALSA: hda/cirrus: Correct the full scale volume set logic
virtio_snd.h: clarify that `controls` depends on VIRTIO_SND_F_CTLS
ALSA: hda: Add error check for snd_ctl_rename_id() in snd_hda_create_dig_out_ctls()
ALSA: hda/tas2781: Fix index issue in tas2781 hda SPI driver
ASoC: imx-audmix: remove cpu_mclk which is from cpu dai device
ALSA: hda/realtek: Fixup ALC225 depop procedure
ALSA: hda/tas2781: Update tas2781 hda SPI driver
ASoC: cs35l41: Fix acpi_device_hid() not found
ASoC: SOF: amd: Add branch prediction hint in ACP IRQ handler
ASoC: SOF: amd: Handle IPC replies before FW_BOOT_COMPLETE
ASoC: SOF: amd: Drop unused includes from Vangogh driver
ASoC: SOF: amd: Add post_fw_run_delay ACP quirk
ASoC: Intel: soc-acpi-intel-ptl-match: revise typo of rt713_vb_l2_rt1320_l13
ASoC: Intel: soc-acpi-intel-ptl-match: revise typo of rt712_vb + rt1320 support
ALSA: Switch to use hrtimer_setup()
ALSA: hda: hda-intel: add Panther Lake-H support
ASoC: SOF: Intel: pci-ptl: Add support for PTL-H
...
Just thought I'd pipe in to also confirm that I now have audio working!
Steps I took:
Update alsa-libs and alsa-utils to latest from git
Update alsa-ucm-conf to latest from git
Install latest linux-firmware from git (suggest using yay to install linux-firmware-git, arch packages aren't latest)
I also updated my linux kernel to latest commit. However, after I got sound working I reverted back to the default for arch which is 6.13.3 and found sound was still working. So seems as though 6.13 kernel should be sufficient, the main culprits are grabbing latest linux-firmware and alsa components.
I can confirm that on my Manjaro installation I only needed the newest linux-firmware (specifically the cs42l* and cs35l56 goodies) and the newest alsa-ucm-conf from the master branch.
There is a very small delay at the beginning of a playback session (and perhaps dropped buffers?) but I can live with it for now.
Can confirm too that update linux-firmware and alsa-ucm-conf from master works for my Yoga 7 Aura.
I've tried it with Fedora 41, but it did not work because of the kernel version (6.12). After update to 6.14.rc4 it works!
Experienced missing ucm2 profiles when I upgraded my 15ILL9 from Ubuntu 25.04 plucky to 25.10 questing (no sound coming from built-in speakers, only dummy output displayed in settings). Internal speakers were working fine before in 25.04.
Fixed it by overwriting the current ucm2 files with the files from the newest version.
After that, sound devices were recognized properly again and sound output from internal speakers was working again.
For the next looker, I'm using Lenovo x9-15 without sound in 24.04. Had a bit of joy as the sound worked in 25.04 before losing it again after upgrading to 25.10. Patching with that latest version v1.2.14 works.
This probably needs to be filed as an Ubuntu/canonical ticket, it sounds like they have back ported some UCM stuff to 25.04 but lost it again on 25.10.
I had the same issue on Ubuntu 25.10 with Intel Lunar Lake-M HD Audio (only “Dummy Output” showing and aplay -l returning no soundcards). What fixed it for me was forcing the Intel DSP driver and reinstalling the SOF firmware.
After reboot, the real audio device appeared instead of “Dummy Output”.
It seems Ubuntu defaults to the wrong DSP mode for Lunar Lake in some cases, and forcing dsp_driver=3 along with reinstalling the SOF firmware resolves detection.
Activity
cgbowman commentedon Dec 11, 2024
@simontrimmer , here are the contents of the directory, as requested from #9663:
simontrimmer commentedon Dec 11, 2024
@cgbowman - Great they are both there - could you attach them and laser etched underneath is the date of manufacture "mfg date" could you grab that too please?
I'm assuming it looks to you like it is playing back and not like sox's play tool that doesn't show progress if the data isn't flowing?
Could you attach the output of alsa-info and maybe "wpctl status" as I don't think that is included yet...
Cheers
-Simon
cgbowman commentedon Dec 11, 2024
Certainly!
Cirrus Firmware: cirrus-smart-firmware.zip
alsa-info output: lenovo-yoga-slim-alsa-info.txt
wpctl status output: lenovo-yoga-slim-wpctl-status.txt
Mfg date: 2024/09/02
Correct, if I simply attempt to 'test' the speaker in the settings UI, it will show a graphic of a bar above the output device, resembling playback:

simontrimmer commentedon Dec 11, 2024
@cgbowman Thanks! I'm out of the workshop now but will compare with the one I have tomorrow, but I'm 99% certain that I have more Sinks than you see in your wpctl output - I wonder if this is one of those ucm problems?
(The unit I have will almost certainly have had all the files updated to the latest from https://github.com/alsa-project/alsa-ucm-conf as I'd recently had some fun with another product and this Lenovo would have been installed off a live USB image I'd made for the one that needed the updated ucm configuration)
simontrimmer commentedon Dec 11, 2024
@cgbowman - Actually perhaps 24.10 is missing this?
alsa-project/alsa-ucm-conf@e4277a2
cgbowman commentedon Dec 11, 2024
@simontrimmer, I updated the files, rebooted, and the Settings menu's 'output device' shows as "Dummy Output". Specifically, adding the change to the sof-soundwire.conf file causes the change.
I've also tried changing the entire ucm2 folder and replacing it with the latest dir available in the alsa-ucm-conf repo and I observe the same issue.
simontrimmer commentedon Dec 12, 2024
@cgbowman Interesting - I suspect we're in the right area .... Is there an error message from the UCM?
Looking at the one I have here:
...
│
├─ Sinks:
│ 56. Lunar Lake-M HD Audio Controller HDMI / DisplayPort 3 Output [vol: 1.00]
│ 57. Lunar Lake-M HD Audio Controller HDMI / DisplayPort 2 Output [vol: 1.00]
│ 58. Lunar Lake-M HD Audio Controller HDMI / DisplayPort 1 Output [vol: 1.00]
│ * 59. Lunar Lake-M HD Audio Controller Headphones + Speaker [vol: 0.37]
│
...
which mirrors the outputs to HDMI and the cs42l43/cs35l56 pair, and it looks like when I upgraded the alsa-ucm-conf files they were matched with similarly dated alsa-lib and alsa-utils, I think a new file syntax (7) was introduced that might be confusing it, this was important to make a different system I was using work, but it could also apply here too.
-Simon
lgirdwood commentedon Dec 12, 2024
@cgbowman just checking, was your alsa-info data above produced with active playback (if not, pls run again with music as speaker test is quite fast/short) ? Just want to rule out userspace isn't incorrectly modifying mixer values when a stream is started/stopped.
cgbowman commentedon Dec 12, 2024
Apologies, it was not produced with active playback. I will upload more info when I have the chance.
cgbowman commentedon Dec 13, 2024
Attached full journalctl output after updating ucm2 directory:
lenovo-yoga-slim-updated-ucm-journalctl.txt
Some notable entries from alsactl:
Updated alsa-info output with music playing in Rhythmbox:
lenovo-yoga-slim-alsa-info-music-playing.txt
lgirdwood commentedon Dec 16, 2024
@simontrimmer any ideas why the codec jack kcontrol would be -EBUSY above ?
simontrimmer commentedon Dec 16, 2024
Er,
@charleskeepax would not having a headset plugged in be the most likely reason for the Jack Override returning -EBUSY?
I was saying earlier today I should come back to this - I do think that something in the alsa-ucm-conf / alsa-utils / alsa-lib isn't happy and that is just snowballing, but the only way I could think of reproducing the problem and then working out what was happening was to sacrifice my working system running Debian12+updates and basically starting again with a clean Ubuntu noble install and working through the problems. I did that recently on a different product and whilst I got to do what I needed in the sound domain, the UI experience was less than enjoyable and put me off rushing into it 😁 Might be a good week for it.
@cgbowman - just checking, did you update the alsa-utils & alsa-lib when you updated the UCM files? (thinking about syntax 7)
-Simon
5 remaining items
Scharkenberg commentedon Feb 18, 2025
There was a UEFI update about a week ago, but sound isn't working yet. The system recognizes seven different output devices which are all non-functional, plus the dummy output. I would like to help diagnose and hopefully solve this problem, but I don't know where to begin - SOF and sound in general are new to me.
bfog commentedon Feb 18, 2025
Can confirm I am seeing the same behaviour as @Scharkenberg . Using EndeavourOS, with the default kernel 6.13.2 shows Dummy Output. Upgrading to 6.14-rc3 now at least detects Lunar Lake-M HD Audio Controller, but still no audio and 7 different audio output options. Happy to provide any logs to get this addressed.
Unrelated, but for anyone reading this, I found my laptop fans weren't working on kernel 6.13.2. 6.14 has resolved this.
simontrimmer commentedon Feb 19, 2025
Random tagging of potentially interested parties - @Scharkenberg @bfog @cgbowman
I just updated my test unit to the public bios release "DMI: LENOVO 83HM/LNVNB161216, BIOS NYCN66WW 01/15/2025" and early indications are extremely positive - I used a kernel built the head of Linus' branch and even the annoying "it hangs at some point, probably power management related" has gone.
I have an early ubuntu 25.04 build on here at the moment, but the key feature for people is to make sure that they have the latest alsa components (some of the alsa-ucm-conf files now have file format dependencies on the newer alsa-lib/alsa-utils).
The distro has:
and wpctl status was only showing the Dummy Output, updating my alsa-ucm-conf files to the head solved that problem.
Depending on your distribution, you might need to get update the linux-firmware repository - I published the initial tuning files a long time ago now but that's not very long when considering Linux distribution cadences. The files I booted up with were the ones I published yesterday but the originals will produce sound.
alsa-ucm-conf
Kernel
cgbowman commentedon Feb 19, 2025
Awesome! I've updated my device as of yesterday for firmware, kernel, & other bits. I'll update the alsa components and report my observations.
cgbowman commentedon Feb 19, 2025
Can confirm, after updating linux-firmware & alsa-ucm-conf (whilst using an updated drm-tip kernel) and rebooting, I'm greeted with working audio!
Thanks @simontrimmer and others for all your work! If you think there's no other work to do here, I think we can close this issue as fixed.
simontrimmer commentedon Feb 19, 2025
@cgbowman - Great!
bfog commentedon Feb 20, 2025
Just thought I'd pipe in to also confirm that I now have audio working!
Steps I took:
I also updated my linux kernel to latest commit. However, after I got sound working I reverted back to the default for arch which is 6.13.3 and found sound was still working. So seems as though 6.13 kernel should be sufficient, the main culprits are grabbing latest linux-firmware and alsa components.
Scharkenberg commentedon Feb 21, 2025
I can confirm that on my Manjaro installation I only needed the newest linux-firmware (specifically the cs42l* and cs35l56 goodies) and the newest alsa-ucm-conf from the master branch.
There is a very small delay at the beginning of a playback session (and perhaps dropped buffers?) but I can live with it for now.
pavelToman commentedon Mar 3, 2025
Can confirm too that update linux-firmware and alsa-ucm-conf from master works for my Yoga 7 Aura.
I've tried it with Fedora 41, but it did not work because of the kernel version (6.12). After update to 6.14.rc4 it works!
t7tran commentedon Oct 31, 2025
For the next looker, I'm using Lenovo x9-15 without sound in 24.04. Had a bit of joy as the sound worked in 25.04 before losing it again after upgrading to 25.10. Patching with that latest version v1.2.14 works.
charleskeepax commentedon Nov 1, 2025
This probably needs to be filed as an Ubuntu/canonical ticket, it sounds like they have back ported some UCM stuff to 25.04 but lost it again on 25.10.
arabhossain commentedon Mar 3, 2026
I had the same issue on Ubuntu 25.10 with Intel Lunar Lake-M HD Audio (only “Dummy Output” showing and
aplay -lreturning no soundcards). What fixed it for me was forcing the Intel DSP driver and reinstalling the SOF firmware.These were the exact steps:
After reboot, the real audio device appeared instead of “Dummy Output”.
It seems Ubuntu defaults to the wrong DSP mode for Lunar Lake in some cases, and forcing
dsp_driver=3along with reinstalling the SOF firmware resolves detection.simontrimmer commentedon Mar 11, 2026
FYI Ubuntu 25.10 did have a UCM issue that regressed support for a number of products, this was chased through and there is an updated package https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2130874