No sound | no output or input devices found for Dell S2721DS | Tiger Lake-H HD Audio Controller

piotrownicki · October 16, 2021, 12:32pm

Hello Geckos,

the issue that I am facing is “no output or input devices found” when headphones are connected to a monitor (Dell S2721DS).

I’m on TW with KDE.

Here’s the output of

/usr/sbin/alsa-info.sh

http://alsa-project.org/db/?f=bef5ea17ccfc0dff37deccbb4b8db1cb0d2b97f4

Yast sound outputs:

Tiger Lake-H HD Audio Controller

Configured as sound card number 0
Driver snd-sof-pci-intel-tgl

When I try to Edit and use quick automatic setup I got “There are no options for this module”

When I delete the entry and then click to edit Tiger Lake-H HD Audio Controller then I got “The kernel module snd-sof-pci-intel-tgl for sound support could not be loaded. This can be caused by incorrect module parameters, including invalid IO or IRQ parameters.”
I was trying to find the solution but seems I can’t fix it alone.

I have [LEFT]sof-firmware already installed. I also installed alsa-firmware.

[/LEFT]
I tried to add following to boot options :
snd_intel_dspcfg.dsp_driver=1
snd_hda_intel.dmic_detect=0
snd_intel_dspcfg.dsp_driver=2
[LEFT][FONT=verdana][LEFT]
Nothing seems to help.
[/LEFT]
[/LEFT]
[/FONT]
The issue is also for me on Fedora 32 with gnome (there I got dummy output instead) and on OpenSuse Leap 15.3.

It works in linux mint 20.2, and in Kubuntu 20.04. Below is a comparison of some of the outputs I got:

|
|pacmd list-sources | grep -e ‘index:’ -e device.string -e ‘name:’
| * index: 0
name: <auto_null.monitor>
|* index: 0
name: <alsa_output.pci-0000_00_1f.3.hdmi-stereo.monitor>
device.string = “0”
|
|aplay -l
|**** List of PLAYBACK Hardware Devices ****
card 1: PCH [HDA Intel PCH], device 0: ALC897 Analog [ALC897 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
|**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC897 Analog [ALC897 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 11: HDMI 5 [HDMI 5]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 12: HDMI 6 [HDMI 6]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 13: HDMI 7 [HDMI 7]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 14: HDMI 8 [HDMI 8]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 15: HDMI 9 [HDMI 9]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 16: HDMI 10 [HDMI 10]
Subdevices: 1/1
Subdevice #0: subdevice #0
|

Happy to provide more. Just let me know what you need to troubleshot.

Regards,
P.

oldcpu · October 16, 2021, 6:19pm

It looks to me that openSUSE Tumbleweed is struggling to identify the code in your PC. I note:


    7.732422] snd_hda_intel 0000:00:1f.3: No response from codec, disabling MSI: last cmd=0x200f0000
...
    8.736506] snd_hda_intel 0000:00:1f.3: Codec #2 probe error; disabling it...
    8.758152] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC897: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line

where it can’t find the code initially, and then later it assesses the codec as ALC897 (whch I note is the same as used by LinuxMint).

Could you provide the alsa-info.sh for those (ie Linux Mint and/or Kbuntu)? I appreciate the info you did provide on LinuxMint, but honestly it doesn’t mean very much to me. The also-info.sh is much more useful, as in provides a list of the kernel modules loaded, lets us know the kernel in use in those distros, plus much more information to compare.

I suspect you could be in bug reporting territory but I am not 100% certain.

piotrownicki · October 16, 2021, 7:31pm

alsa-info output for mint - http://alsa-project.org/db/?f=669abc3a11f7d94dbe601e013e141db64847ed07

oldcpu · October 17, 2021, 2:08am

Comparing the scripts, where sound works on Linux Mint but not on openSUSE I note:

openSUSE has a newer kernel 5.14.9-1-default vs Linux mint’s 5.11.0-37-generic:

openSUSE has pipewire installed and running. Linux mint is only using pulse audio.

Linux mint has a large number of mode probe settings. I confess I am not used to seeing so many … I don’t know what ‘index=-2’ is supposed to do. Also the purpose of “snd_cmipci: mpu_port=0x330 fm_port=0x388” is unknown to me :


snd_pcsp: index=-2
snd_usb_audio: index=-2
snd_atiixp_modem: index=-2
snd_intel8x0m: index=-2
snd_via82xx_modem: index=-2
snd_atiixp_modem: index=-2
snd_intel8x0m: index=-2
snd_via82xx_modem: index=-2
snd_usb_audio: index=-2
snd_usb_caiaq: index=-2
snd_usb_ua101: index=-2
snd_usb_us122l: index=-2
snd_usb_usx2y: index=-2
snd_cmipci: mpu_port=0x330 fm_port=0x388
snd_pcsp: index=-2
snd_usb_audio: index=-2

Linux Mint has many more “ALSA Device modes”. I do not know if that is significant. I do note that in aplay Linux mint lists many HDMI devices, while Tumbleweed lists none.

When I look at the kernel modules loaded for sound I note LinuxMint has these modules loaded and Tumbleweed does not: snd_hda_codec_hdmi, snd_rawmidi, snd_eq, snd_seq_device, snd_seq_midi, snd_seq_midi_event, snd_sof_intel_byt, snd_sof_intel_ipc,

Tumbeweed has these loaded: snd_sof_pci_intel_tgl and Linux Mint does not.

Linux Mint reports various /sys/class/sound/hwC0D2/init_pin_configs settings, and Tumbleweed does not.

The dmesg suggests there may be issues with Tumbleweed in initially recognizing the codec.

I can’t explain the differences. Your Tumbleweed mixer settings look good.

I think you are into bug reporting territory for Tumbleweed. Either their is a regression in the Tumbleweed kernel or those many modeprobe settings in the Linux Mint alsa configuration file made a difference. I you want to play around you could put those Linux mint modprobe options in the Tumbleweed /etc/modprobe.d/50-sound.conf file … reboot and test, … but it might cause your PC to hang upon boot ?? < my speculation - I don’t really know >

If it were me, I would write a bug report.

piotrownicki · October 17, 2021, 3:03pm

I’ve added those Linux mint modprobe options in the Tumbleweed /etc/modprobe.d/50-sound.conf file. I was able to boot but it was not a smooth boot.

Sound from dell is still not working.

Do you know where I should raise this bug?

BTW. It also didn’t worked for me on Fedora 34, and Leap 15.3 (for both Leap’s kernel, and kernel from Backports).
I’m almost sure it didn’t worked on Pop OS 20.04. Which would be strange as it should work as it worked in kubuntu and mint.

piotrownicki · October 17, 2021, 3:31pm

I also found those two reddits:

[LEFT]I tried adding [FONT=&amp]boot options from https://bugzilla.opensuse.org/show_bug.cgi?id=1185693 but those didn’t worked.

[/FONT]I don’t know yet how to revert to alsa-ucm-1.2.4 but might try to see if that will help.

[/LEFT]

oldcpu · October 17, 2021, 5:59pm

There is guidance here for raising bug reports on openSUSE : openSUSE:Submitting bug reports - openSUSE Wiki

The sound driver comes with the kernel, so I recommend you raise the bug report on the kernel : openSUSE:Bugreport kernel - openSUSE Wiki

Attach a text file to the bug report containing the output of the alsa-info.sh diagnostic script.

I think you should be able to use your openSUSE forum username and password when logging on to the bugzilla.

Don’t reference this thread in the bug report as the openSUSE sound driver packager (who is also an alsa sound driver developer) won’t read a forum thread. Try to include all relevant information in your bug report.

Good luck.

piotrownicki · October 23, 2021, 9:46pm

I have raised a bug - https://bugzilla.opensuse.org/show_bug.cgi?id=1191724

My issue was not resolved directly. Seems Leap now supports my hardware hence I will go back to it instead of Tumbleweed.

Thanks for your time and help.

oldcpu · October 24, 2021, 1:33am

Thankyou for sharing the link to the bug report and for working with the openSUSE packager.

As noted, he is a kernel developer and an alsa sound driver developer, and I believe he is one of the best people knowledgeable in GNU/Linux sound aspects on this planet ( !! ) able to help.

Glad to read you have a work around for now even if not ideal.