Bug 1213052

Please don't use YaST sound module.  For modern systems, it rather often breaks things.  Check /etc/modprobe.d/*, and remove a file if it's created by YaST sound module.

Then boot again.  Run alsa-info.sh script with --no-upload option as root, and attach the output to Bugzilla (don't paste).

Created attachment 868042 [details]
output from alas-info

Please find attached the output of alsa-info.sh

The kernel log shows:
[    1.227909] snd_hda_intel 0000:0a:00.1: Cannot probe codecs, giving up

Is it something to do with the default setup of SUSE-prime?
  https://github.com/openSUSE/SUSEPrime

Check the section "HDMI audio support does not work".

Hi,

There is no 90-nvidia-udev-pm-G05.rules script under /usr/lib/udev/rules.d on my system.

So I cannot do what is suggested under "HDMI audio support does not work" that is being mention in "https://github.com/openSUSE/SUSEPrime".

Also prime-select is not being install on my system.

Best Regards
Chris

OK, but it still smells like a setup problem of Nvidia driver.
Adding Stefan to Cc.

I see only one graphics card, so there is no need to have suse-prime package installed. Therefore there is no /usr/lib/udev/rules.d/90-nvidia-udev-pm-G05.rules installed, which would disable HDMI audio by default. So this issue needs to have a different reason.

NVIDIA's driver README refers to 

https://download.nvidia.com/XFree86/gpu-hdmi-audio-document/

Not sure whether this is useful. It's obviously old information from 2014.

Created attachment 868218 [details]
output from nvidia-bug-report.sh

Hi,

I had found a workaround after boot as follow

  1. YaST delete current GM204 audio
  2. YaST re-initialise GM204 audio
  3. systemctl --user restart pipewire.service

Best Regards
Chris

Then this might be related with the power management of Nvidia chip.

Could you try to add a file /etc/modprobe.d/60-hda-softdep.conf containing the line:
  softdep snd-hda-intel pre: nvidia

then reboot/retest?

Hi 

No change after reboot with the new script in /etc/modprobe.d, below is the output of wpctl

wpctl status
PipeWire 'pipewire-0' [0.3.64, chris@VikingSrvNew, cookie:1613439557]
 └─ Clients:
        31. pipewire-pulse                      [0.3.64, chris@VikingSrvNew, pid:3688]
        33. PulseAudio systray                  [0.3.64, chris@VikingSrvNew, pid:3395]
        34. WirePlumber                         [0.3.64, chris@VikingSrvNew, pid:3687]
        35. WirePlumber [export]                [0.3.64, chris@VikingSrvNew, pid:3687]
        53. Firefox                             [0.3.64, chris@VikingSrvNew, pid:3296]
        54. wpctl                               [0.3.64, chris@VikingSrvNew, pid:5487]

Audio
 ├─ Devices:
 │      44. Full HD webcam                      [alsa]
 │  
 ├─ Sinks:
 │  *   32. Dummy Output                        [vol: 1.00]
 │  
 ├─ Sink endpoints:
 │  
 ├─ Sources:
 │  *   51. Full HD webcam Mono                 [vol: 1.00]
 │  
 ├─ Source endpoints:
 │  
 └─ Streams:

Video
 ├─ Devices:
 │      41. Full HD webcam                      [v4l2]
 │      42. Full HD webcam                      [v4l2]
 │      43. OBS Virtual Camera                  [v4l2]
 │  
 ├─ Sinks:
 │  
 ├─ Sink endpoints:
 │  
 ├─ Sources:
 │  *   45. Full HD webcam (V4L2)              
 │  
 ├─ Source endpoints:
 │  
 └─ Streams:

Settings
 └─ Default Configured Node Names:
         0. Audio/Sink    alsa_output.pci-0000_0a_00.1.hdmi-stereo
         1. Audio/Source  alsa_input.usb-Sunplus_IT_Co_Full_HD_webcam_AN20200618001-02.mono-fallback

Best Regards
Chris

Please give the dmesg output, at best from both the boot with the modprobe.d hack and another boot without the hack.

Created attachment 868271 [details]
dmesg without modprobe.d script

dmesg output with no modprobe.d script applied.

Created attachment 868272 [details]
dmesg with script applied

dmesg output with modprobe.d script hack

Thanks.  So nvidia module itself gets loaded before snd-hda-intel module.  But this still might be some timing issue.

Remove the previous modprobe.d entry, and create another one containing the following line:

install snd-hda-intel sleep 3; /sbin/modprobe --ignore-install snd-hda-intel $CMDLINE_OPTS

This hackish workaround will delay the load of HD-audio module forcibly for 3 seconds.  Let's see whether this helps or not.

Hi,

Do you mean create a new script in /etc/modprobe.d ?
What will be the "number" use to start the script name ?

Best Regards
Chris

The file name doesn't matter much as long as it contains ".conf" extension.
You can keep the same file or create a new one as you like.

Created attachment 868374 [details]
lastest dmesg output

Hi,

Please find attached is the latest dmesg output with new hack script.
Same as before wirepipe do not recognise the Nvidia audio.

Best Regards
Chris

Hm, the whole process seemed just shifted instead of only this one.
What if you add the previous softdep config in addition?

Also, when you change the sleep 3 to a longer value, e.g. sleep 10, how is the effect?

Last but not least, drop all those modprobe.d configs again, add the following instead:
  blacklist snd-hda-intel

This will disable HD-audio loading.  Then load the module manually after the boot.  Does it work?  If yes, it means the problem is the timing of the device initialization.

Created attachment 868378 [details]
dmesg output with latest hack scripts

Delay install and softdep does not work.
But blacklist snd_hda_intel then reload it after boot finish work, so I will write a script to do "modprobe snd_hda_intel" for workaround.

Best Regards
Chris