Repository navigation
Internal speakers not working - Lenovo Yoga Slim 7 15ILL9 (83HM), Lunar Lake, CS35L56 left amp SPI probe failure #5685
Description
System Information
| Field | Value |
|---|---|
| Machine | Lenovo Yoga Slim 7 15ILL9 |
| DMI Product | 83HM |
| BIOS | NYCN75WW (12/26/2025) |
| CPU | Intel Core Ultra (Lunar Lake) |
| Audio controller | Intel Lunar Lake-M HD Audio (00:1f.3, rev 10) |
| Audio chips | CS42L43 (SoundWire codec) + CS35L56 x2 (SPI amplifiers) |
| Kernel | 6.18.13-200.fc43.x86_64 |
| Distro | Fedora 43 |
Symptom
No internal speakers detected at all. aplay -l reports "no soundcards found". The right CS35L56 amp probes successfully but the left fails, preventing sof_sdw from registering the sound card entirely.
Bluetooth audio works. The issue persists across multiple distros (Fedora 43, Manjaro including kernel 6.12 LTS) and fresh installs, confirming this is not a userspace configuration issue.
Relationship to existing issue
This may be related to #5621 (HP Elitebook 8 G1i, same chipset). Both show identical left amp failure with HALO_STATE=0x0. However, this Lenovo has different ACPI errors (PMAP type mismatch returning Package instead of Buffer) which may indicate a distinct but related root cause.
Key errors
The left CS35L56 never communicates over SPI:
cs35l56 spi-cs35l56-left: Firmware boot timed out(0): HALO_STATE=0x0
cs35l56 spi-cs35l56-left: probe with driver cs35l56 failed with error -5
The right amp probes fine but lacks calibration data:
cs35l56 spi-cs35l56-right: Cirrus Logic CS35L56 Rev B0 OTP3 fw:3.4.4 (patched=0)
cs35l56 spi-cs35l56-right: No calibration for silicon ID 0x1da272567ba61
Sound card never registers:
platform sof_sdw: deferred probe pending: sof_sdw: snd_soc_register_card failed -517
ACPI PMAP errors at boot (repeated ~9 times):
ACPI Error: Incorrect return type from \_SB_.PC00.HDAS.IDA_.SNDW.SWD6.AF01.PMAP - received [Package], requested [Buffer]
ACPI: \_SB_.PC00.HDAS.IDA_.SNDW.SWD6.AF01: can't evaluate "PMAP" as buffer
Full relevant dmesg
[ 0.197102] ACPI Error: Incorrect return type from \_SB_.PC00.HDAS.IDA_.SNDW.SWD6.AF01.PMAP - received [Package], requested [Buffer] (20250807/nsxfeval-114)
[ 0.197104] ACPI: \_SB_.PC00.HDAS.IDA_.SNDW.SWD6.AF01: can't evaluate "PMAP" as buffer
[ 0.197149] ACPI Error: Incorrect return type from \_SB_.PC00.HDAS.IDA_.SNDW.SWD6.AF01.PMAP - received [Package], requested [Buffer] (20250807/nsxfeval-114)
[ 0.197150] ACPI: \_SB_.PC00.HDAS.IDA_.SNDW.SWD6.AF01: can't evaluate "PMAP" as buffer
[ 0.197217] ACPI Error: Incorrect return type from \_SB_.PC00.HDAS.IDA_.SNDW.SWD6.AF01.PMAP - received [Package], requested [Buffer] (20250807/nsxfeval-114)
[ 0.197219] ACPI: \_SB_.PC00.HDAS.IDA_.SNDW.SWD6.AF01: can't evaluate "PMAP" as buffer
[ 0.197272] ACPI Error: Incorrect return type from \_SB_.PC00.HDAS.IDA_.SNDW.SWD6.AF01.PMAP - received [Package], requested [Buffer] (20250807/nsxfeval-114)
[ 0.197273] ACPI: \_SB_.PC00.HDAS.IDA_.SNDW.SWD6.AF01: can't evaluate "PMAP" as buffer
[ 0.197323] ACPI Error: Incorrect return type from \_SB_.PC00.HDAS.IDA_.SNDW.SWD6.AF01.PMAP - received [Package], requested [Buffer] (20250807/nsxfeval-114)
[ 0.197324] ACPI: \_SB_.PC00.HDAS.IDA_.SNDW.SWD6.AF01: can't evaluate "PMAP" as buffer
[ 0.197384] ACPI Error: Incorrect return type from \_SB_.PC00.HDAS.IDA_.SNDW.SWD6.AF01.PMAP - received [Package], requested [Buffer] (20250807/nsxfeval-114)
[ 0.197385] ACPI: \_SB_.PC00.HDAS.IDA_.SNDW.SWD6.AF01: can't evaluate "PMAP" as buffer
[ 0.197416] ACPI Error: Incorrect return type from \_SB_.PC00.HDAS.IDA_.SNDW.SWD6.AF01.PMAP - received [Package], requested [Buffer] (20250807/nsxfeval-114)
[ 0.197417] ACPI: \_SB_.PC00.HDAS.IDA_.SNDW.SWD6.AF01: can't evaluate "PMAP" as buffer
[ 0.197466] ACPI Error: Incorrect return type from \_SB_.PC00.HDAS.IDA_.SNDW.SWD6.AF01.PMAP - received [Package], requested [Buffer] (20250807/nsxfeval-114)
[ 0.197467] ACPI: \_SB_.PC00.HDAS.IDA_.SNDW.SWD6.AF01: can't evaluate "PMAP" as buffer
[ 0.197538] ACPI Error: Incorrect return type from \_SB_.PC00.HDAS.IDA_.SNDW.SWD6.AF01.PMAP - received [Package], requested [Buffer] (20250807/nsxfeval-114)
[ 0.197539] ACPI: \_SB_.PC00.HDAS.IDA_.SNDW.SWD6.AF01: can't evaluate "PMAP" as buffer
[ 5.571996] sof-audio-pci-intel-lnl 0000:00:1f.3: SoundWire enabled on CannonLake+ platform, using SOF driver
[ 5.636014] sof-audio-pci-intel-lnl 0000:00:1f.3: Topology file: intel/sof-ipc4-tplg/sof-lnl-cs42l43-l0-4ch.tplg
[ 5.698385] cs42l43 sdw:0:0:01fa:4243:01: supply vdd-p not found, using dummy regulator
[ 5.698416] cs42l43 sdw:0:0:01fa:4243:01: supply vdd-d not found, using dummy regulator
[ 5.698426] cs42l43 sdw:0:0:01fa:4243:01: supply vdd-a not found, using dummy regulator
[ 5.698437] cs42l43 sdw:0:0:01fa:4243:01: supply vdd-io not found, using dummy regulator
[ 5.698443] cs42l43 sdw:0:0:01fa:4243:01: supply vdd-cp not found, using dummy regulator
[ 5.701229] cs42l43 sdw:0:0:01fa:4243:01: devid: 0x042a43, rev: 0xa1, otp: 0x03
[ 5.722054] cs42l43 sdw:0:0:01fa:4243:01: Slave 6 state check1: UNATTACHED, status was 1
[ 5.780536] cs35l56 spi-cs35l56-left: supply VDD_P not found, using dummy regulator
[ 5.780562] cs35l56 spi-cs35l56-left: supply VDD_IO not found, using dummy regulator
[ 5.780568] cs35l56 spi-cs35l56-left: supply VDD_A not found, using dummy regulator
[ 6.052378] cs35l56 spi-cs35l56-left: Firmware boot timed out(0): HALO_STATE=0x0
[ 6.052402] cs35l56 spi-cs35l56-left: probe with driver cs35l56 failed with error -5
[ 6.052485] cs35l56 spi-cs35l56-right: supply VDD_P not found, using dummy regulator
[ 6.052503] cs35l56 spi-cs35l56-right: supply VDD_IO not found, using dummy regulator
[ 6.052511] cs35l56 spi-cs35l56-right: supply VDD_A not found, using dummy regulator
[ 6.118176] cs35l56 spi-cs35l56-right: Cirrus Logic CS35L56 Rev B0 OTP3 fw:3.4.4 (patched=0)
[ 6.252092] cs35l56 spi-cs35l56-right: No calibration for silicon ID 0x1da272567ba61
[ 16.456904] platform sof_sdw: deferred probe pending: sof_sdw: snd_soc_register_card failed -517
Activity
ujfalusi commentedon Mar 10, 2026
@rfvirgil, can you take a look at this?
rfvirgil commentedon Mar 10, 2026
@drewbstew Looks like you have several BIOS problems with that laptop. Also possibly your kernel is missing some bugfixes.
It is not related to #5621.
Can you please attach:
lspci -nnvsudo acpidump(in acpica-tools)tar -cf efivars.tar /sys/firmware/efi/efivars/Cirrus*drewbstew commentedon Mar 10, 2026
Thanks for taking a look.
efivars.tar.gz
acpidump-full.txt
dmesg-full.txt
output of lspci -nnv
rfvirgil commentedon Mar 11, 2026
@drewbstew Does sound work with Windows?
We've previously had confirmation that sound works correctly on this model with Linux:
thesofproject/sof#9720 (comment)
simontrimmer commentedon Mar 11, 2026
I have just updated the bios on my test system to
DMI: LENOVO 83HM/LNVNB161216, BIOS NYCN75WW 12/26/2025
and the audio drivers start up correctly with an updated Ubuntu 25.10 (6.17.0-14-generic) and also with a 7.0rc2 kernel.
drewbstew commentedon Mar 11, 2026
Tested on 6.17.1-300.fc43.x86_64 — audio still not working, aplay -l reports no soundcards found.
dmesg errors are essentially identical to 6.18 (same PMAP type mismatch, same cs35l56-left firmware timeout, same sof_sdw -517).
@rfvirgil Regarding Windows: I only used Windows briefly during initial setup to update the BIOS, so I can't confirm audio state there. I believe audio was working on Fedora at some point shortly after setup, but I can't be certain — it's possible I'm confusing it with headphone use. I no longer have a Windows environment to test with.
Happy to provide any additional diagnostics that would help narrow down why your test system works with this BIOS but mine doesn't.
drewbstew commentedon Mar 11, 2026
Found two Cirrus-related EFI variables:
CirrusSmartAmpCalibrationData
CirrusSmartCalInfo
The calibration data appears partial — only one amp has valid data, the left amp section is zeroed. This may explain why my unit differs from your test system. Could corrupted or incomplete EFI calibration data be preventing the left CS35L56 from initializing? Is there a way to reset or regenerate this calibration data without a working Windows environment?
simontrimmer commentedon Mar 11, 2026
Hi @drewbstew,
The calibration data would come into play at a later point in time, the driver will still initialise the amplifiers without it.
At the moment there is a communication problem between the amplifiers and the codec - where @rfvirgil was asking whether Windows worked was a diagnostic as to whether it was a hardware issue.
The test system I have is a retail unit, I also had to reinstall windows on this to perform a bios update and to do that I needed to use the Lenovo pcsupport web site to generate recovery media
-Simon
drewbstew commentedon Mar 16, 2026
@simontrimmer I've done some more investigating on Windows and found that one of the three Cirrus Logic XU devices shows "requires further installation" in Device Manager. Running Get-PnpDevice on that device shows Service is blank and Manufacturer is Microsoft — meaning no Cirrus-specific driver is bound to it, just a generic Microsoft SoundWire class driver with no active service.
The device ID is SOUNDWIRE\SDCA_06&MAN_01FA&FUNC_4243&TYPE_01&VER_01&ADR_01&LID_00&UID_00&SUBSYS_380E17AA&DynamicEnumSpeaker0
Could you run the following on your working unit and share the output, specifically the Service and Manufacturer fields?
Get-PnpDevice -InstanceId (Get-PnpDevice | Where-Object {$_.FriendlyName -like "Cirrus"} | Select-Object -ExpandProperty InstanceId) | Format-List Name, Status, Problem, Service, Manufacturer
If your unit has a populated Service field where mine has blank, that would confirm the issue is a missing or non-matching driver binding rather than dead hardware.
If you're still running Ubuntu, could you run
ls -la /sys/bus/soundwire/devices/*/driver
or
sudo dmesg | grep -i "cs35l56|4243|spi-cs35l56"
and share the output?
Much thanks for the help.
simontrimmer commentedon Mar 17, 2026
Hi @drewbstew,
I'll include some debug from our system, but as this system has problems in both Windows and Linux it is more weight to a connectivity problem between the codec and the amps.
I have not been inside this laptop, but looking at some photos I suspect it may be a solution with the codec and the amps on different boards - might be worth getting a service centre involved to check that they are properly connected (or if it's new get it swapped).
-Simon
charleskeepax commentedon Jun 9, 2026
Going to close this as it looks like probably a hardware issue, please re-open if more is needed here.