http://bugzilla.opensuse.org/show_bug.cgi?id=1163046 http://bugzilla.opensuse.org/show_bug.cgi?id=1163046#c2 --- Comment #2 from Felix Miata --- This may have nothing to do with the Raven/Raven2/Fenghuang possibly being too new. In the past several hours I've tried, using YaST2 and among other things setup-pulseaudio --enable and to test aplay -vv /usr/share/sounds/alsa/test.wav to get HDMI and/or DisplayPort audio out of 15.1 on several PCs, and/or from 15.2 and/or Debian 10. On one it was already and remains working (host gb250, only as normal user, and only in Debian 10/TDE; Device 8086:a2f0; DP & HDMI). All others tried in recent hours, all using Intel CPUs, fail: 1: host gb250 15.1/TDE as root or normal user; onboard Device 8086:a2f0; HDMI 2: host gx78b 15.1/KDE3 and 15.2/KDE3 using the HD from the comment 0 PC as root or normal user; onboard Device 8086:3a6e; DP & DP-HDMI adapter; has internal speaker that makes sound instead of DP 3: host ab250 15.1/TDE or IceWM as root or normal user; onboard Device 8086:a2f0; HDMI; analog pin jack also tried and fails 4: host vostro 15.1/Plasma 5 as root user (no normal users on the fresh installation pending BTRFS /home recovery from old SSD); PCIe Device 10de:0be9; DP; analog pin jack tried also fails 5: host gx760 15.1/TDE as root or normal user, also failing in 13.1/Plasma 4, 42.3/TDE and TW/Plasma 5; onboard Device 8086:3a6e; DP-HDMI adapter 6: host gx780 15.1/KDE3 as normal user; onboard Device 8086:3a6e; DP; has internal speaker that makes sound instead of DP 7: host ta790 15.1/Plasma 5 as root & normal user; onboard devices 1002:4383 & 1002:960f; HDMI In most of these, aplay -vv displays as if it was actually getting something to the speakers, with ...###... scrolling across the bottom of the output, but instead on gb250 "aplay: main:828: audio open error: No such file or directory" results. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1163046 http://bugzilla.opensuse.org/show_bug.cgi?id=1163046#c4 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(mrmazda@earthlink | |.net) --- Comment #4 from Takashi Iwai --- Please check the latest upstream 5.5.y kernel in OBS Kernel:stable. If it still shows the problem, try 5.4.y kernel in OBS home:tiwai:kernel:5.4, too. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1163046 http://bugzilla.opensuse.org/show_bug.cgi?id=1163046#c6 Felix Miata changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|no AMD |undue difficulty enabling |Raven/Raven2/Fenghuang |HDMI/DisplayPort audio |(HDMI) sound in Leap 15.2 |output |Alpha chip IDs: 1002:15de | |1002:15e3 | Flags|needinfo?(mrmazda@earthlink | |.net) | Severity|Normal |Enhancement --- Comment #6 from Felix Miata --- Note that comment #3 and attachment 829714 apply to attempted use of pavucontrol by admin user root. It appears the problem is is basically there is no working automagic for HDMI audio support, and lacking documentation explaining the means to make it work manually. Thus -> new summary. I was finally able to make HDMI sound work on multiple 15.1, 15.2 & TW installations with each respective default kernel via pavucontrol, by totally disabling analog video output, which means no headphone output is possible while HDMI is kept enabled. Pavucontrol is non-functional at the system admin/maintainer (root) level, because pavucontrol is purposely and secretly disabled for root, or at least no method is available based upon discoverable documentation for whatever other method of configuration might exist. https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.1/index.html lacks the strings audio, sound and HDMI. Googling "site:docs.opensuse.org hdmi displayport audio sound" also comes up blank. Googling "site:doc.opensuse.org hdmi" only produces hits for 8 years old 12.1. Googling "hdmi audio" did produce several nebulous pointers to pavucontrol, but none anywhere on opensuse.org on the first hit page, if anywhere at all. If a pure alsa system is unable to produce HDMI audio output, that fact needs discoverable documentation. If YaST cannot be made to perform this configuration, there should at least be discoverable documentation for an alternative configuration means. (In reply to Takashi Iwai from comment #5)

You can try to run "/usr/sbin/alsactl monitor" and plug/unplug the monitor. If this shows the event, and either "HDMI/DP,pcm=3 Jack" or "HDMI/DP,pcm=7 Jack" shows true in alsa-info.sh output, the hotplug was done properly. The rest would be either the remaining audio setup (that is specific to AMD/ATI) or GPU driver problem.

@user> /usr/sbin/alsactl monitor card 0, #12 (3,7,0,ELD,0) VALUE INFO card 0, #7 (0,0,0,HDMI/DP,pcm=7 Jack,0) VALUE card 0, #12 (3,7,0,ELD,0) VALUE INFO card 0, #7 (0,0,0,HDMI/DP,pcm=7 Jack,0) VALUE card 0, #12 (3,7,0,ELD,0) VALUE INFO Comment #0 PC is being delivered to owner in coming minutes now that for it a solution is in place. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1163046 http://bugzilla.opensuse.org/show_bug.cgi?id=1163046#c8 --- Comment #8 from Felix Miata --- Created attachment 829919 --> http://bugzilla.opensuse.org/attachment.cgi?id=829919&action=edit alsa-info.txt from TW host big31 with non-working Oland Radeon HDMI audio Here is another host that YaST sound setup doesn't make work for Plasma ("Unable to start the sound server to retrieve possible sound I/O methods. Only automatic detection will be available.", and system settings test sound produces no sound), and Youtube in Newmoon and SeaMonkey don't work, but on which aplay -Dhdmi:1,0 does work: # aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Intel [HDA Intel], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 1: ALC662 rev1 Digital [ALC662 rev1 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 # inxi -AGSxx System: Host: big31 Kernel: 5.4.7-1-default x86_64 bits: 64 compiler: gcc v: 9.2.1 Desktop: KDE Plasma 5.17.4 tk: Qt 5.13.1 wm: kwin_x11 dm: startx Distro: openSUSE Tumbleweed 20200110 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] vendor: Dell driver: amdgpu v: kernel bus ID: 01:00.0 chip ID: 1002:6611 Display: server: X.Org 1.20.6 driver: amdgpu unloaded: fbdev,modesetting,vesa alternate: ati compositor: kwin_x11 resolution: 2560x1440~60Hz OpenGL: renderer: AMD Radeon HD 8500 Series (OLAND DRM 3.35.0 5.4.7-1-default LLVM 9.0.1) v: 4.5 Mesa 19.3.1 direct render: Yes Audio: Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: Biostar Microtech Intl Corp driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:27d8 Device-2: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series] vendor: Dell driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 1002:aab0 Sound Server: ALSA v: k5.4.7-1-default # alsamixer ALSA lib pulse.c:242:(pulse_connect) PulseAudio: Unable to connect: Connection refused cannot open mixer: Connection refused -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1163046 http://bugzilla.opensuse.org/show_bug.cgi?id=1163046#c10 --- Comment #10 from Takashi Iwai --- Don't use YaST sound setup for such modern systems. It's a thing to be dropped in future in anyway, just like X setup. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1163046 http://bugzilla.opensuse.org/show_bug.cgi?id=1163046#c12 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #12 from Takashi Iwai --- You mixed up too many different things. Some reports are really about bugs that are seen in the recent updates (e.g. Carbon X1 requiring the new UCM stuff with the latest PA git version), some are invalid usage, and some are misunderstanding. In your case, it's rather about the misunderstanding. - In general, PA is recommended for HDMI access on a desktop system -- if available - The auto-start of PA is disabled for root as default due to the system security matters - If non-PA access is required, the special PCM device (hdmi:xxx) must be used for accessing to HDMI or DP. The direct access with hw:xxx or plughw:xxx, and with default:xxx wouldn't work. - Also for non-PA access, the card indexing may require manual adjustment; it's nothing new, rather the system setup issue. - YaST sound module may help setting up the system configuration with the module options, but nothing more than that. It cannot know about the above things, and it's rather an obsoleted feature to be dropped in future. So, if you found any other real bug to be fixed in openSUSE *packaging*, please open another bug. For other issues, please report to upstream. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1163046 http://bugzilla.opensuse.org/show_bug.cgi?id=1163046#c14 --- Comment #14 from Takashi Iwai --- Felix, bugzilla is no user forum. If there is a bug to be fixed in the package, please let me know. Other than that, there is another more appropriate place to discuss that. If you want more documentation, feel free to contribute there. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1163046 http://bugzilla.opensuse.org/show_bug.cgi?id=1163046#c17 Felix Miata changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |tiwai@suse.com Resolution|INVALID |--- Flags| |needinfo?(tiwai@suse.com) --- Comment #17 from Felix Miata --- https://en.opensuse.org/SDB:Audio_troubleshooting or anything else on the wiki only attempts to make up for what's absent from official documentation. Lack of adequate, or even any, official documentation, is the problem. If official documentation actually exists, it needs to be readily discoverable. Coaxing Takashi's instructional bits out of Bugzilla is too difficult, and shouldn't count as official anyway. Where do SLE clients find sound configuration docs? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1163046 http://bugzilla.opensuse.org/show_bug.cgi?id=1163046#c22 --- Comment #22 from Felix Miata --- Moving this to https://trello.com/c/fG1yBNlO/ makes it unfollowable, even though logged in there: [quote] Card not found. This card may be on a private board. If someone gave you this link, they may need to invite you to one of their boards or teams. [/quote] -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1163046 http://bugzilla.opensuse.org/show_bug.cgi?id=1163046#c26 Felix Miata changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Version|Leap 15.2 |Leap 15.5 Resolution|NORESPONSE |--- --- Comment #26 from Felix Miata --- That nothing has changed doesn't mean problem solved. It hasn't been. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1163046 http://bugzilla.opensuse.org/show_bug.cgi?id=1163046#c28 Tom���� Ba��ant changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(mrmazda@earthlink | |.net) --- Comment #28 from Tom���� Ba��ant --- Is it okay to add a note the the current docs with the information that Takashi provided? -- You are receiving this mail because: You are on the CC list for the bug.