Bug 1212941

Summary: No sound on Chromebook Snow
Product: [openSUSE] openSUSE Tumbleweed Reporter: Holger Sickenberg <holgi>
Component: SoundAssignee: Takashi Iwai <tiwai>
Status: RESOLVED WORKSFORME QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: holgi
Version: Current   
Target Milestone: ---   
Hardware: armv7   
OS: openSUSE Tumbleweed   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: dmesg.txt
hwinfo.txt
dmesg-with-lines.txt

Description Holger Sickenberg 2023-07-03 09:28:32 UTC
Created attachment 867936 [details]
dmesg.txt

On Chromebook Snow there is no sound module loaded.
dmesg and HWINFO file attached

Kernel:
Linux localhost.localdomain 6.3.9-1-lpae #1 SMP Thu Jun 22 03:53:43 UTC 2023 (0df701d) armv7l armv7l armv7l GNU/Linux

(Obviously same behavior on Leap 15.4)
Comment 1 Holger Sickenberg 2023-07-03 09:29:35 UTC
Created attachment 867937 [details]
hwinfo.txt

Hardware specs also on https://en.opensuse.org/HCL:ARMChromebook
Comment 2 Takashi Iwai 2023-07-04 07:16:37 UTC
It seems trying to bind, but it didn't reach to the final state, as it seems.
At first, it gives an error:

[   38.785336] snow-audio sound: Failed parsing codec node

But this might be OK.  The driver tries to rebind afterwards, too.

Then, it continues with samsung-i2s:

[   38.810098] samsung-i2s 3830000.i2s-sec: DMA channels sourced from device 3830000.i2s

So far, so good.  And found the codec:

[   39.100569] max98095 7-0011: Hardware revision: C

Then a warning:

[   39.111577] snow-audio sound: ASoC: driver name too long 'Snow-I2S-MAX98095' -> 'Snow-I2S-MAX980'
[   39.113056] max98095 7-0011: ASoC: mux External MIC has no paths
[   39.113077] max98095 7-0011: ASoC: mux Linein Mux has no paths

Those are more or less expected.  And that's all, no clear indication of fatal errors.

Could you try to boot with snd_soc_core.dyndbg=+p boot option and get dmesg?

BTW, the dmesg contains more serious problem: the crash from parport_pc.
Please try to add blacklist of parport_pc module.
Comment 3 Holger Sickenberg 2023-07-13 13:05:27 UTC
Created attachment 868182 [details]
dmesg-with-lines.txt

New dmesg with further cmdline options added.
Comment 4 Takashi Iwai 2023-07-17 09:03:52 UTC
The log doesn't indicate any error, and it means that the kernel seems working as expected.  The driver got loaded and set up.

Do you have alsa-ucm-conf package installed?  The device needs special initialization sequences and the UCM profile does it.

Also, which sound backend are you using?  PulseAudio or pipewire?
Comment 5 Holger Sickenberg 2023-07-25 11:16:35 UTC
You are right, it's working now.
Comment 6 Holger Sickenberg 2023-07-25 11:17:06 UTC
No longer an issue