[Bug 1159962] New: No sound with two snd_hda_intel devices on old MSI MS-16GN notebook
http://bugzilla.opensuse.org/show_bug.cgi?id=1159962 Bug ID: 1159962 Summary: No sound with two snd_hda_intel devices on old MSI MS-16GN notebook Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai@suse.com Reporter: hpj@urpla.net QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 826806 --> http://bugzilla.opensuse.org/attachment.cgi?id=826806&action=edit full alsa info of this device Hi Takashi, here's a pathologic case of non working sound with an old notebook, that my son discovered and insists to use. The primary problem seems to be, that snd_hda_intel is assigned to both sound devices: 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler HDMI Audio 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) (rev 40) I've tried to setup both in yast, but the former (HDMI) fails with an unspecific error, while the latter results in: [ 29.843918] snd_hda_intel 0000:00:14.2: no codecs found! It looks like it is trying to setup the former, although yast shows it as not configured: cat /proc/asound/card*/codec* | grep Codec Codec: ATI R6xx HDMI For completeness, hwinfo --sound: 23: PCI 01.1: 0403 Audio device [Created at pci.386] Unique ID: mnDB.SblQee99PEF SysFS ID: /devices/pci0000:00/0000:00:01.1 SysFS BusID: 0000:00:01.1 Hardware Class: sound Model: "ATI Wrestler HDMI Audio" Vendor: pci 0x1002 "ATI Technologies Inc" Device: pci 0x1314 "Wrestler HDMI Audio" SubVendor: pci 0x1462 "Micro-Star International Co., Ltd. [MSI]" SubDevice: pci 0x109a Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xfeb44000-0xfeb47fff (rw,non-prefetchable) IRQ: 28 (862 events) Module Alias: "pci:v00001002d00001314sv00001462sd0000109Abc04sc03i00" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=no, avail=yes, need=no, active=unknown 27: PCI 14.2: 0403 Audio device [Created at pci.386] Unique ID: 5Dex.Ra8MFFdEW23 SysFS ID: /devices/pci0000:00/0000:00:14.2 SysFS BusID: 0000:00:14.2 Hardware Class: sound Model: "ATI SBx00 Azalia (Intel HDA)" Vendor: pci 0x1002 "ATI Technologies Inc" Device: pci 0x4383 "SBx00 Azalia (Intel HDA)" SubVendor: pci 0x1462 "Micro-Star International Co., Ltd. [MSI]" SubDevice: pci 0x109a Revision: 0x40 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xfeb40000-0xfeb43fff (rw,non-prefetchable) IRQ: 16 (no events) Module Alias: "pci:v00001002d00004383sv00001462sd0000109Abc04sc03i00" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=yes, avail=yes, need=no, active=unknown I've tried several settings already in /etc/modprobe.d/50-sound.conf, but none was successful. Some rudiments appear in the attached alsa-info file. The net isn't very fruitfully, when it comes to ATI R6xx devices, and even SBx00 Azalia reveals the standard procedures only. Any idea, how to disable the Wrestler device, while keeping Azalia, would be a good start, I guess? Let me know, if you need anything else. Thanks and a happy new year, Pete -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1159962
http://bugzilla.opensuse.org/show_bug.cgi?id=1159962#c1
--- Comment #1 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=1159962
http://bugzilla.opensuse.org/show_bug.cgi?id=1159962#c2
--- Comment #2 from Hans-Peter Jansen
Actually, it's other way round: the error at probe happens for the secondary device, i.e. the onboard audio, while the first device, HDMI, was probed correctly, judging from alsa-info.sh output.
Yes, you're right. yast is confused about two devices, that are handled from the same driver, and consequently doesn't manage these two devices correctly. If I remove the former setup and start with Azalia, it creates: /etc/modprobe.d/50-sound.conf: options snd slots=snd-hda-intel # 5Dex.Ra8MFFdEW23:SBx00 Azalia (Intel HDA) and if I remove this again, and start with HDMI, it creates: options snd slots=snd-hda-intel # mnDB.SblQee99PEF:Wrestler HDMI Audio alias snd-card-0 snd-hda-intel Hence, it differs in the comments only. :-( No matter, what yast thinks, the system always sets up the HDMI device, according to alsa: cat /proc/asound/card0/codec#0: Codec: ATI R6xx HDMI Address: 0 AFG Function Id: 0x1 (unsol 0) Vendor Id: 0x1002aa01 Subsystem Id: 0x00aa0100 Revision Id: 0x100200 No Modem Function Group found Default PCM: rates [0x70]: 32000 44100 48000 bits [0x2]: 16 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D3 Power: setting=D0, actual=D0 GPIO: io=0, o=0, i=0, unsolicited=0, wake=0 Node 0x02 [Audio Output] wcaps 0x201: Stereo Digital Converter: stream=0, channel=0 Digital: Digital category: 0x0 IEC Coding Type: 0x0 Node 0x03 [Pin Complex] wcaps 0x400381: Stereo Digital Control: name="IEC958 Playback Con Mask", index=0, device=0 Control: name="IEC958 Playback Pro Mask", index=0, device=0 Control: name="IEC958 Playback Default", index=0, device=0 Control: name="IEC958 Playback Switch", index=0, device=0 Pincap 0x00000094: OUT Detect HDMI Pin Default 0x18560010: [Jack] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0x1, Sequence = 0x0 Pin-ctls: 0x40: OUT Unsolicited: tag=01, enabled=1 Connection: 1 0x02 Manually appending this doesn't change the picture: alias snd-card-1 snd-hda-intel
I have no idea why it failed, so far, so let's try the following at first:
- Please try to remove the extra configuration for sound drivers in /etc/modprobe.d/*.conf. enable_msi=0 should be superfluous, at least. Done, see above. - Try the 5.4.y kernel in OBS Kernel:stable repo. It should be the same result, but who knows... Done, see above.
Other than that, I'd check BIOS setup. You might have some item allowing to disable the onboard audio.
I've upgraded to the latest BIOS version already: 119. Unfortunately, the BIOS doesn't provide *any* audio related switches, and is very sparse at any controls. See Page 96ff, if you like: https://download.msi.com/archive/mnu_exe/CR650_English.zip Our main objective is getting the onboard sound (Azalia) to work. The HDMI sound is a rarely used (if at all) nice to have option, while the onboard sound is *essential*. I've no good way to test HDMI output at the moment without some fuzz, but yes, it looks, like HDMI is working correctly, independently from what yast thinks, it is controlling. Interestingly, the only snd related kernel message is: dmesg | grep snd [ 29.887885] snd_hda_intel 0000:00:14.2: no codecs found! which means, that setting up HDMI doesn't trigger any kernel messages: 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler HDMI Audio Subsystem: Micro-Star International Co., Ltd. [MSI] Device 109a Flags: bus master, fast devsel, latency 0, IRQ 28 Memory at feb44000 (32-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel only this one: 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) (rev 40) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 109a Flags: bus master, slow devsel, latency 32, IRQ 16 Memory at feb40000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel so I'm certain, that the Codec problem is in charge of Azalia not working. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1159962
http://bugzilla.opensuse.org/show_bug.cgi?id=1159962#c9
Hans-Peter Jansen
Did any pci boot option help?
Not exactly. My son deals with this "the windows way": if it fails, he has leaned to reboot properly: shut down and switch on manually. While I'm able to reproduce the issue with the current kernel, it seems to survive a suspend often enough with the reboot=warm option and adhering to the procedure above. To be honest, I've lost interest since the system takes ages to boot up, even running on a ssd and with mitigations switched off.. Let's file this as one of the "rare" pc firmware curiosities. Following the kernel development for more than two decades, I recognize you as one of the hidden champions. Sound has gained so much since you got involved. Thank you very much, Takashi, always a pleasure to read you in the changelogs. ;-) Cheers from the middle Rhine valley. Pete -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com