http://bugzilla.opensuse.org/show_bug.cgi?id=1205887 http://bugzilla.opensuse.org/show_bug.cgi?id=1205887#c1 Mathias Homann <Mathias.Homann@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Mathias.Homann@opensuse.org Flags| |needinfo?(Mathias.Homann@op | |ensuse.org) --- Comment #1 from Mathias Homann <Mathias.Homann@opensuse.org> --- I just now installed nvidia-g06 525.60.11 and so far the problem seems to be gone, but i'd like the bug to stay open for some time to keep it under observation. I'll put myself in NEEDINFO. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1205887 http://bugzilla.opensuse.org/show_bug.cgi?id=1205887#c3 --- Comment #3 from Mathias Homann <Mathias.Homann@opensuse.org> --- (In reply to Takashi Iwai from comment #2)

Please give alsa-info.sh output. Run the script with --no-upload option and attach the output.

The error message "cannot find the slot for index 0 (range 0-0), error: -16" usually implies that you specify the module option index=0 for this driver while the given slot (0) has been already occupied by another sound card (e.g. USB-audio). In that case, it's more about a configuration failure.

Since I've updated the nvidia drivers the issue has not yet happened again, do you want the output from alsa-info when it happens or when everything is working, or both? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1205887 http://bugzilla.opensuse.org/show_bug.cgi?id=1205887#c5 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #5 from Takashi Iwai <tiwai@suse.com> --- In the log, you can find the following: !!Modprobe options (Sound related) !!-------------------------------- snd_hda_intel: id=PCH index=1 snd_hda_intel: id=HDMI index=0 ... and that's the configuration failure. You are defining twice for the same driver in different ways, conflicting with each other. If you must apply those slot swapping, it should be applicable like options snd_hda_intel index=1,0 id=PCH,HDMI and additionally, reserve two slots by options snd slots=snd_hda_intel,snd_hda_intel I close the bug for now. If the setup above still shows the problem, please reopen. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1205887 http://bugzilla.opensuse.org/show_bug.cgi?id=1205887#c7 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |WONTFIX Flags|needinfo?(tiwai@suse.com) | --- Comment #7 from Takashi Iwai <tiwai@suse.com> --- (In reply to Mathias Homann from comment #6)

(In reply to Takashi Iwai from comment #5)

...

In the log, you can find the following:

!!Modprobe options (Sound related) !!--------------------------------

snd_hda_intel: id=PCH index=1 snd_hda_intel: id=HDMI index=0

... and that's the configuration failure. You are defining twice for the same driver in different ways, conflicting with each other.

If you must apply those slot swapping, it should be applicable like

options snd_hda_intel index=1,0 id=PCH,HDMI

and additionally, reserve two slots by

options snd slots=snd_hda_intel,snd_hda_intel

I close the bug for now. If the setup above still shows the problem, please reopen.

Well, here's the thing, I didn't do that. In actual fact, I haven't done *any* manual configuration on sound, it's all yast.

But you must have explicitly configured the sound setup via YaST in the past, and that was the result. YaST won't write such options unless user requests it.

Also, that actually *is* my hardware. Onboard intel chip that can play through the analog sockets or through the HDMI port of my GPU. Has worked fine for 10+ years, now it's suddenly a misconfiguration?

You were just lucky, and the luck was gone when you change some hardware configuration or plug another device like USB-audio.

Then how else is that supposed to be set up, and why has it just now started to fall apart on me, and why does it only sometimes fail? Like I said in the comment on the attachment - that alsa-info output is from when everything *works*.

It works for now because the hardware configuration casually matches with the old setup. At best, drop those old configurations. With the modern sound backend like pipewire or PulseAudio, such static configurations make little sense and rather confusing. If any static configuration is needed, it's at user's own risk. IMO, YaST sound module should be dropped. But it's a bit different story. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1205887 http://bugzilla.opensuse.org/show_bug.cgi?id=1205887#c9 --- Comment #9 from Takashi Iwai <tiwai@suse.com> --- There are the files defining those options in /etc/modprobe.d/*. Take a look at the files there and delete the corresponding files. Of course, if you are *not* using piepwire or PulseAudio but access directly to the ALSA devices, those setups have a meaning. Otherwise, those configs are superfluous and should be dropped. -- You are receiving this mail because: You are on the CC list for the bug.