On Thu, Sep 05, 2024 at 08:52:26PM +0200, Franco Martelli wrote: > > I am running debian testing, updated daily. > I'm on stable, so I can't help much > > > > > After yesterday's update, the kernel module snd_hda_intel is being > > loaded with the wrong (default) parameters. > Have you verified this by running the following commands: > > ~$ cat /sys/module/snd_hda_intel/parameters/id > ~$ cat /sys/module/snd_hda_intel/parameters/index
Thanks for the suggestion. No I hadn't checked there, and the results are peculiar: it is looking like an obscure bug in the snd_hda_intel driver. The parameter that matters is "index". Checking /sys/module/snd_hda_intel/parameters/index gives 1,0,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 which is "correct" as if the options have been correctly set. BUT sound is still connected to the HDMI port (index 0,1) !! As usual, manually removing and restoring snd_hda_intel fixes the problem: sound is then connected to PCH (index 1,0): # modprobe -r snd_hda_intel # modprobe snd_hda_intel /sys/module/snd_hda_intel/parameters/index does not change, but is now reflecting the truth. This is now a debian bug against modprobe, although it is probably not modprobe at fault: 1080...@bugs.debian.org As noted there, bug=663436 many years ago had something similar going on with snd_hda_intel. I will copy this reply to that the current bug because it adds significant information. I am wondering whether to contact the maintainer for snd_hda_intel, but I wnatto be sure that I am not overlooking something silly. > > I have /etc/modprobe.d/snd-hda.conf > > which specifies: > > options snd_hda_intel id=[HDMI,PCH] index=1,0 > > > > The details are very unlikely to be important, but if you are > > interested, the snd_hda_intel module defaults to emitting sound on the > > HDMI port instead of the PCH port connected to the speakers and > > headphone. > as workaround try to specify those parameters in the kernel-line in the boot > loader. See: Yes, I know about the kernel command line possibility, but I already have a workaround. Rather I wnat to nail this bug. But thanks for the suggestion. ael
