[kernel-bugs] [Bug 1176351] New: Audio device: Intel Corporation Device 02c8: not detected
https://bugzilla.suse.com/show_bug.cgi?id=1176351 Bug ID: 1176351 Summary: Audio device: Intel Corporation Device 02c8: not detected Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: gp@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I've got a new notebook, Intel chipsets only, where everythings works - except for audio. It appears the audio chip/sound card are not detected by the kernel or initialized. lspci -v has: 00:1f.3 Audio device: Intel Corporation Device 02c8 (prog-if 80) Subsystem: Lenovo Device 22be Flags: fast devsel, IRQ 16, IOMMU group 13 Memory at ea33c000 (64-bit, non-prefetchable) [size=16K] Memory at ea000000 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 <?> Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ Kernel modules: snd_hda_intel, snd_soc_skl, snd_sof_pci # lsmod | grep snd snd 114688 1 thinkpad_acpi soundcore 16384 1 snd # cat /proc/asound/cards --- no soundcards --- # dmesg | grep audio [ 18.072024] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 [ 18.072026] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 18.072036] sof-audio-pci 0000:00:1f.3: enabling device (0004 -> 0006) [ 18.072179] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [ 18.072267] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 18.078993] sof-audio-pci 0000:00:1f.3: use msi interrupt mode [ 18.109492] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 5 [ 18.109493] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 18.109497] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 4 [ 18.109521] sof-audio-pci 0000:00:1f.3: Direct firmware load for intel/sof/sof-cml.ri failed with error -2 [ 18.109522] sof-audio-pci 0000:00:1f.3: error: request firmware intel/sof/sof-cml.ri failed err: -2 [ 18.109524] sof-audio-pci 0000:00:1f.3: error: failed to load DSP firmware -2 [ 18.110449] sof-audio-pci 0000:00:1f.3: error: sof_probe_work failed err: -2 [ 220.595600] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 [ 220.595605] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 220.595786] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [ 220.595899] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 220.601386] sof-audio-pci 0000:00:1f.3: use msi interrupt mode [ 220.630638] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 5 [ 220.630640] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 220.630644] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 4 [ 220.630664] sof-audio-pci 0000:00:1f.3: Direct firmware load for intel/sof/sof-cml.ri failed with error -2 [ 220.630666] sof-audio-pci 0000:00:1f.3: error: request firmware intel/sof/sof-cml.ri failed err: -2 [ 220.630669] sof-audio-pci 0000:00:1f.3: error: failed to load DSP firmware -2 [ 220.631004] sof-audio-pci 0000:00:1f.3: error: sof_probe_work failed err: -2 -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1176351 https://bugzilla.suse.com/show_bug.cgi?id=1176351#c1 Gerald Pfeifer <gp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Audio device: Intel |Audio device: Intel |Corporation Device 02c8: |Corporation Device 02c8: |not detected |not detected | |(snd_hda_intel.dmic_detect= | |0 works around) --- Comment #1 from Gerald Pfeifer <gp@suse.com> --- Adding snd_hda_intel.dmic_detect=0 to the GRUB_CMDLINE_LINUX_DEFAULT entry in /etc/default/grub, running update-bootloader, and rebooting appears to work around this issue. That's a bit tricky and took me a fair bit to find. Can the kernel somehow handle this itself? (Found online at https://askubuntu.com/questions/1256825/no-sound-on-ubuntu-20-04-dell-xps-73... ) -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1176351 https://bugzilla.suse.com/show_bug.cgi?id=1176351#c2 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai@suse.com --- Comment #2 from Takashi Iwai <tiwai@suse.com> --- Did you install sof-firmware package as well as alsa-ucm-conf package? The error message indicates at least the lack of the former. The SOF should work once after installing those missing pieces. The workaround skips the SOF, and directly driving the HD-audio legacy stuff. The drawback is that you have no built-in mic, as the digital mic isn't handled via HD-audio bus. BTW, your suggested workaround was a deprecated option for old kernels. For the recent kernels, it's snd-intel-dspcfg.dsp_driver=1. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1176351 https://bugzilla.suse.com/show_bug.cgi?id=1176351#c3 --- Comment #3 from Gerald Pfeifer <gp@suse.com> --- Thank you, Takashi! Indeed the sof-firmware package was missing. Once I installed that (and removed the kernel command-line hack) audio was up and running fine from what I can tell. Now, how can we improve the situation for new users? My notebook (installed from scratch) has 31 kernel-firmware packages installed, including kernel-firmware-nvidia and kernel-firmware-mellanox (where neither hardware is present). I take it sof-firmware is somehow, hmm, different? Is there a way to pull in sof-firmware when needed? Or install by default, like the others? -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1176351 https://bugzilla.suse.com/show_bug.cgi?id=1176351#c4 --- Comment #4 from Takashi Iwai <tiwai@suse.com> --- The sof-firmware package has the hardware supplements rpm tags, and it should have been installed if the PCI chip was detected. Maybe the entry is missing for your device. The update candidate of sof-firmware is found in OBS home:tiwai:test:sdw/sof-firmware repo, and this contains the supplements for your device (8086:02c8), and this should fix the issue. Please check the package there (sof-firmware-1.5.1, and best with alsa-ucm-conf there, too) to check whether anything goes south. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1176351 https://bugzilla.suse.com/show_bug.cgi?id=1176351#c5 --- Comment #5 from Gerald Pfeifer <gp@suse.com> --- I installed those two packages (sof-firmware and alsa-ucm-conf) from https://build.opensuse.org/project/show/home:tiwai:test:sdw and audio works fine. Later today I'll have some video conferences, where I can test the full setup, and will report if there's any special findings. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1176351 https://bugzilla.suse.com/show_bug.cgi?id=1176351#c6 --- Comment #6 from Gerald Pfeifer <gp@suse.com> --- Created attachment 841586 --> https://bugzilla.suse.com/attachment.cgi?id=841586&action=edit This is how pavucontrol looks like on the Input tab Just did a call with Teams: sound worked fine, alas people couldn't hear me. I fiddled a bit with pavucontrol, and with the setting per the attached screenshot another test call actually worked. (Interesting observation: The low bar, that I thought was to represent microphone input in fact appears to show *output* as well?) % cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.8.4-1-default root=/dev/mapper/cr_system-root splash=silent resume=/dev/system/swap mitigations=auto quiet % rpm -qa alsa* sof* | sort alsa-1.2.3.2-1.2.x86_64 alsa-plugins-1.2.2-2.4.x86_64 alsa-plugins-pulse-1.2.2-2.4.x86_64 alsa-plugins-speexrate-1.2.2-2.4.x86_64 alsa-plugins-upmix-1.2.2-2.4.x86_64 alsa-ucm-conf-1.2.3-20.1.noarch alsa-utils-1.2.3-1.3.x86_64 sof-firmware-1.5.1-14.1.noarch -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1176351 https://bugzilla.suse.com/show_bug.cgi?id=1176351#c7 --- Comment #7 from Gerald Pfeifer <gp@suse.com> --- The successful call was with a headset. When I unplugged that "Stereo Input" became unavailable and only "Multichannel Input" was and input did not work any more. Trying to switch back to the headset on the next call caused a massive interference for the other attendees. (Right now the "mute" button on the keyboard, on the <F4> key, is stuck and always lights up, i.e., I cannot toggle mute any more. That changes when I plug in the head set, and changes back again when I unplug that.) Do I assume correctly that for calls "Stereo Input+Output" and a headset are best for the time being? If there is any way I can help (test or otherwise), please let me know. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1176351 https://bugzilla.suse.com/show_bug.cgi?id=1176351#c8 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gp@suse.com Flags| |needinfo?(gp@suse.com) --- Comment #8 from Takashi Iwai <tiwai@suse.com> --- Now I'm back from vacation and catching up. It seems that some discrepancy is present between UCM profile and the actual implementation. Could you try to boot with snd-intel-dspcfg.dsp_driver=1 option and check whether the headset mic mess persists? This will switch to the legacy driver, and the headset should be dealt there as is. Note that the built-in mic doesn't work in this mode. It's supported only with SOF driver. In anyway, please give alsa-info.sh outputs from the sessions both with and without the option above. Run the script with --no-upload option and attach to Bugzilla. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1176351 https://bugzilla.suse.com/show_bug.cgi?id=1176351#c9 --- Comment #9 from Gerald Pfeifer <gp@suse.com> --- Created attachment 841812 --> https://bugzilla.suse.com/attachment.cgi?id=841812&action=edit alsa-info.txt when booting with default options Sharing alsa-info.txt for the default case for now. As in important note: I believe I never got the built-in microphone to actually ever record anything! That's reason I started using a head-set. And a test I just conducted, where I plugged the head-set in, spoke a few words (pavu-control showed activity on the input, which automatically switched to stereo input), plugged it out, spoke a few words (pavu-control showed no activity on the input, which automatically switched to multi-channel input), seems to confirm that. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1176351 https://bugzilla.suse.com/show_bug.cgi?id=1176351#c10 Gerald Pfeifer <gp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(gp@suse.com) | --- Comment #10 from Gerald Pfeifer <gp@suse.com> --- Created attachment 842343 --> https://bugzilla.suse.com/attachment.cgi?id=842343&action=edit alsa-info.txt when booting with snd-intel-dspcfg.dsp_driver=1 Now I've been on vacation, hence the delay. Here is the output of alsa-info.sh with the snd-intel-dspcfg.dsp_driver=1 option set (and after a zypper dup bringing a few updates). The more I thought about this issue, the more I started to wonder whether the mike not working (from what I could see) in default mode points towards a, if not the, key issue? -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1176351 https://bugzilla.suse.com/show_bug.cgi?id=1176351#c11 --- Comment #11 from Takashi Iwai <tiwai@suse.com> --- For the TW, the original issue (the missing sof-firmware) should have been already fixed. The mic problems (both built-in and headset) are the second issues, and this needs to be addressed, of course. Now sof-firmware and alsa-* packages are updated for TW as well, and those should make the built-in mic working with SOF driver (i.e. without dsp_driver=1 workaround). And, the headset mic problem is yet different from this. The step to check the headset mic functionality to get alsa-info.sh output with and without the headset plugged. If the driver could detect the headset, it's one step forward. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1176351 https://bugzilla.suse.com/show_bug.cgi?id=1176351#c12 --- Comment #12 from Gerald Pfeifer <gp@suse.com> --- (In reply to Takashi Iwai from comment #11)
For the TW, the original issue (the missing sof-firmware) should have been already fixed. The mic problems (both built-in and headset) are the second issues, and this needs to be addressed, of course.
Now sof-firmware and alsa-* packages are updated for TW as well, and those should make the built-in mic working with SOF driver (i.e. without dsp_driver=1 workaround). And, the headset mic problem is yet different from this.
Good news! I'm back from vacation and updated to latest Tumbleweed (and also the alsa-* packages, after having done sof-firmware already while out) and the built-in mic worked fine in my first tests. In fact, I managed to use the built-in, switch to a headset, back to built-in and each of those three tests worked. Plus I ran another test where I unplugged the headset and continued to talk, and that worked, too.
The step to check the headset mic functionality to get alsa-info.sh output with and without the headset plugged. If the driver could detect the headset, it's one step forward.
I ran alsa-info.sh with the headset unplugged and then plugged in, and will attach the results in a second.
From my perspective I cannot get anything to fail right now. Admittedly I have not been using the system extensively (suspend, calls,... over multiple days) yet. Do you want to mark this as RESOLVED and I'll report (or reopen, as you prefer) anything new?
In any case, thank you for your help! -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1176351 https://bugzilla.suse.com/show_bug.cgi?id=1176351#c13 --- Comment #13 from Gerald Pfeifer <gp@suse.com> --- Created attachment 842520 --> https://bugzilla.suse.com/attachment.cgi?id=842520&action=edit alsa-info.txt, booted without special options, without headset -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1176351 https://bugzilla.suse.com/show_bug.cgi?id=1176351#c14 --- Comment #14 from Gerald Pfeifer <gp@suse.com> --- Created attachment 842521 --> https://bugzilla.suse.com/attachment.cgi?id=842521&action=edit alsa-info.txt, booted without special options, headset plugged in -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1176351 https://bugzilla.suse.com/show_bug.cgi?id=1176351#c18 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #18 from Takashi Iwai <tiwai@suse.com> --- The bug about alsa-lib breakage was already addressed. Let's close. -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply＠suse.com