Comment # 6 on bug 1205887 from Mathias Homann

(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.

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?

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*.