Video / audio troubles with RX 570 / stretch

Everything about X, Gnome, KDE, ... and everything running on it

Video / audio troubles with RX 570 / stretch

Postby oddhack » 2018-12-16 03:15

I just installed stretch on a new machine (Ryzen 5 2600 / AMD RX 570 GPU / AsRock B450-M Pro / Samsung 43NU6950 display), and am having various display driver-related (I think) difficulties with appropriate modelines and with having no sound (over HDMI or otherwise):

* Initially X ran at a max resolution of 1920x1080, and refused explicit modelines suitable for the 4K monitor. AFAICT by inspecting Xorg.0.log, it tried running the radeon driver, which apparently doesn't support the Polaris 12 GPU in my RX 570, and fell back to the VESA driver.
* To get around this I installed the AMDGPU driver, e.g. just installed linux-firmware. This did succeed in running at 4K, but the system has no sound. Apparently AMDGPU doesn't support sound over HDMI until the DC improvements consequent to kernel 4.15 and later, but that aside, I wasn't even getting sound out of the onboard analog audio ports, and no audio device showed in the audio controls other than "Simultaneous Audio" without any underlying physical devices.
* This seemed odd because the snd_hda_intel module was loaded, and there were no obvious audio-related errors in syslog. All I see is:
Code: Select all
Dec 14 23:33:38 celly kernel: [147930.102594] snd_hda_intel 0000:23:00.1: Handle vga_switcheroo audio client
Dec 14 23:33:38 celly kernel: [147930.102600] snd_hda_intel 0000:23:00.1: Force to non-snoop mode
Dec 14 23:33:38 celly kernel: [147930.110024] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.1/0000:23:00.1/sound/card0/input20
Dec 14 23:33:38 celly kernel: [147930.110148] input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.1/0000:23:00.1/sound/card0/input21
Dec 14 23:33:38 celly kernel: [147930.110261] input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.1/0000:23:00.1/sound/card0/input22
Dec 14 23:33:38 celly kernel: [147930.110377] input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.1/0000:23:00.1/sound/card0/input23
Dec 14 23:33:38 celly kernel: [147930.110491] input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:03.1/0000:23:00.1/sound/card0/input24
Dec 14 23:33:38 celly kernel: [147930.110601] input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci0000:00/0000:00:03.1/0000:23:00.1/sound/card0/input25
Dec 14 23:33:38 celly systemd[1]: Reached target Sound Card.
Dec 14 23:33:38 celly kernel: [147930.116426] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC892: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
Dec 14 23:33:38 celly kernel: [147930.116433] snd_hda_codec_realtek hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Dec 14 23:33:38 celly kernel: [147930.116437] snd_hda_codec_realtek hdaudioC1D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
Dec 14 23:33:38 celly kernel: [147930.116440] snd_hda_codec_realtek hdaudioC1D0:    mono: mono_out=0x0
Dec 14 23:33:38 celly kernel: [147930.116444] snd_hda_codec_realtek hdaudioC1D0:    inputs:
Dec 14 23:33:38 celly kernel: [147930.116448] snd_hda_codec_realtek hdaudioC1D0:      Front Mic=0x19
Dec 14 23:33:38 celly kernel: [147930.116452] snd_hda_codec_realtek hdaudioC1D0:      Rear Mic=0x18
Dec 14 23:33:38 celly kernel: [147930.116455] snd_hda_codec_realtek hdaudioC1D0:      Line=0x1a
Dec 14 23:33:38 celly systemd-udevd[4669]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99.


That's where matters stand. If I could get analog audio out, that would be something, but I'd like audio over HDMI. Advice welcome; possible paths forward I see right now are:

* Try the AMDGPU-PRO driver, which supposedly doesn't have the audio-over-HDMI issue (whether this would address the underlying complete lack of audio problem is not clear to me).
* Update to testing, which supports a kernel recent enough that it might support the DC layer improvements needed for AMDGPU audio-over-HDMI (again, whether this has any bearing on the lack of analog audio is unclear). I'm averse to doing this since this is intended to be my primary desktop / production system.
oddhack
 
Posts: 13
Joined: 2018-07-21 23:35

Re: Video / audio troubles with RX 570 / stretch

Postby llivv » 2018-12-16 04:35

stable backports is another option
current stable backports kernel is 4.18

check for other backported packages
https://packages.debian.org/stretch-backports/

see howto add backports
https://backports.debian.org/Instructions/
In memory of Ian Ashley Murdock (1973 - 2015) founder of the Debian project.
User avatar
llivv
 
Posts: 5488
Joined: 2007-02-14 18:10
Location: cold storage

Re: Video / audio troubles with RX 570 / stretch

Postby oddhack » 2018-12-16 09:04

llivv wrote:stable backports is another option
current stable backports kernel is 4.18

check for other backported packages
https://packages.debian.org/stretch-backports/

see howto add backports
https://backports.debian.org/Instructions/


Thanks! Very helpful suggestion :-)
oddhack
 
Posts: 13
Joined: 2018-07-21 23:35

Re: Video / audio troubles with RX 570 / stretch

Postby oddhack » 2018-12-16 13:00

llivv wrote:stable backports is another option
current stable backports kernel is 4.18


Installing the 4.18 kernel from stretch-backports was straightforward, but I wasn't getting video on the text console, and only the VESA driver in X. It turned out that I had to enable stretch-backports non-free too:

Code: Select all
deb http://ftp.debian.org/debian stretch-backports main non-free


Once that was done, video was normal and X ran under amdgpu again (bonus, it appears to be running 4k@60, while I was only getting 4k@30 under the stretch kernel / firmware). So that's good news.

Unfortunately, I'm still getting no audio, HDMI or otherwise. Now the device listed is "Dummy Output" instead of "Simultaneous Output", but it's just as useless. This feels like a problem purely with the audio driver(s) so perhaps I should bring that up separately.
oddhack
 
Posts: 13
Joined: 2018-07-21 23:35

Re: Video / audio troubles with RX 570 / stretch

Postby bw123 » 2018-12-16 13:46

oddhack wrote:
...
* This seemed odd because the snd_hda_intel module was loaded, and there were no obvious audio-related errors in syslog. All I see is:
Code: Select all
...
Dec 14 23:33:38 celly systemd-udevd[4669]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99.


?
User avatar
bw123
 
Posts: 3787
Joined: 2011-05-09 06:02

Re: Video / audio troubles with RX 570 / stretch

Postby llivv » 2018-12-16 18:55

oddhack wrote:Unfortunately, I'm still getting no audio, HDMI or otherwise. Now the device listed is "Dummy Output" instead of "Simultaneous Output", but it's just as useless.

what other backports did you install so far (if any other than the kernel)?

https://wiki.debian.org/AtiHowTo

man amdgpu #(HDMI options)
In memory of Ian Ashley Murdock (1973 - 2015) founder of the Debian project.
User avatar
llivv
 
Posts: 5488
Joined: 2007-02-14 18:10
Location: cold storage

Re: Video / audio troubles with RX 570 / stretch

Postby oddhack » 2018-12-17 01:44

bw123 wrote:
oddhack wrote:
...
* This seemed odd because the snd_hda_intel module was loaded, and there were no obvious audio-related errors in syslog. All I see is:
Code: Select all
...
Dec 14 23:33:38 celly systemd-udevd[4669]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99.


?


Thanks for noticing that. After updating to the 4.18.0 backports kernel I'm still seeing something like this in syslog, but now it's:

Code: Select all
/var/log/syslog:Dec 16 05:52:21 celly systemd-udevd[13501]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 2' failed with exit code 99.


According to 'aplay -l' I do have two audio devices:

Code: Select all
**** List of PLAYBACK Hardware Devices ****
card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 11: HDMI 5 [HDMI 5]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Generic [HD-Audio Generic], device 0: ALC892 Analog [ALC892 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0


And I can successfully use alsactl to init or restore devices 0 and 1. However, I still don't get any sound, and can't adjust the volume above 0 in alsamixer. Delving more into alsa now, but I'd appreciate pointers on diagnosing alsa issues as I'm pretty unfamiliar with this stuff.
oddhack
 
Posts: 13
Joined: 2018-07-21 23:35

Re: Video / audio troubles with RX 570 / stretch

Postby oddhack » 2018-12-17 01:55

llivv wrote:
oddhack wrote:Unfortunately, I'm still getting no audio, HDMI or otherwise. Now the device listed is "Dummy Output" instead of "Simultaneous Output", but it's just as useless.

what other backports did you install so far (if any other than the kernel)?


Quite a few, since I did some 'apt-get -t stretch-backports upgrade' operations which pulled in a bunch of other stuff besides the linux-image-4.18.0-0.bpo.1-amd64 and firmware-amd-graphics updates. Here's what's in the APT log:

Code: Select all
Start-Date: 2018-12-16  04:47:35
Commandline: apt-get -t stretch-backports upgrade
Upgrade: manpages:amd64 (4.10-2, 4.16-1~bpo9+1), hplip-data:amd64 (3.16.11+repack0-3, 3.18.10+dfsg0-3~bpo9+1), libservlet3.1-java:amd64 (8.5.14-1+deb9u3, 8.5.35-2~bpo9+1), iptables:amd64 (1.6.0+snapshot20161117-6, 1.6.2-1.1~bpo9+1), linux-libc-dev:amd64 (4.9.130-2, 4.18.6-1~bpo9+1), libldap-2.4-2:amd64 (2.4.44+dfsg-5+deb9u2, 2.4.46+dfsg-5~bpo9+1), libxapian30:amd64 (1.4.3-2+deb9u2, 1.4.9-1~bpo9+1), printer-driver-hpcups:amd64 (3.16.11+repack0-3, 3.18.10+dfsg0-3~bpo9+1), rake:amd64 (10.5.0-2, 12.3.1-1~bpo9+1), libsqlite3-dev:amd64 (3.16.2-5+deb9u1, 3.25.3-2~bpo9+1), git-man:amd64 (1:2.11.0-3+deb9u4, 1:2.19.2-1~bpo9+1), libgwenhywfar60:amd64 (4.15.3-5+b1, 4.20.0-1~bpo9+1), libsystemd0:amd64 (232-25+deb9u6, 239-12~bpo9+1), ant:amd64 (1.9.9-1+deb9u1, 1.9.12-1~bpo9+1), libsqlite3-0:amd64 (3.16.2-5+deb9u1, 3.25.3-2~bpo9+1), printer-driver-postscript-hp:amd64 (3.16.11+repack0-3, 3.18.10+dfsg0-3~bpo9+1), libatspi2.0-dev:amd64 (2.22.0-6+deb9u1, 2.30.0-2~bpo9+1), gir1.2-atk-1.0:amd64 (2.22.0-1, 2.30.0-1~bpo9+1), wayland-protocols:amd64 (1.7-1, 1.13-1~bpo9+1), dh-autoreconf:amd64 (14, 17~bpo9+1), geoip-database:amd64 (20170512-1, 20181108-1~bpo9+1), at-spi2-core:amd64 (2.22.0-6+deb9u1, 2.30.0-2~bpo9+1), liblognorm5:amd64 (2.0.1-1.1+b1, 2.0.3-1~bpo9+1), python3-brlapi:amd64 (5.4-7+deb9u1, 5.6-5~bpo9+1), git:amd64 (1:2.11.0-3+deb9u4, 1:2.19.2-1~bpo9+1), python3-pyatspi:amd64 (2.20.3+dfsg-1, 2.30.0+dfsg-1~bpo9+1), libbrlapi0.6:amd64 (5.4-7+deb9u1, 5.6-5~bpo9+1), libgwenhywfar-data:amd64 (4.15.3-5, 4.20.0-1~bpo9+1), python3-idna:amd64 (2.2-1, 2.6-1~bpo9+1), xbrlapi:amd64 (5.4-7+deb9u1, 5.6-5~bpo9+1), libip6tc0:amd64 (1.6.0+snapshot20161117-6, 1.6.2-1.1~bpo9+1), udev:amd64 (232-25+deb9u6, 239-12~bpo9+1), python-chardet:amd64 (2.3.0-2, 3.0.4-1~bpo9+1), libfastjson4:amd64 (0.99.4-1, 0.99.8-1~bpo9+1), libnm0:amd64 (1.6.2-3+deb9u2, 1.14.4-2~bpo9+1), network-manager-gnome:amd64 (1.4.4-1+deb9u1, 1.8.18-2~bpo9+1), linux-compiler-gcc-6-x86:amd64 (4.9.130-2, 4.18.6-1~bpo9+1), libassuan0:amd64 (2.4.3-2, 2.5.1-2~bpo9+2), network-manager:amd64 (1.6.2-3+deb9u2, 1.14.4-2~bpo9+1), python-lxml:amd64 (3.7.1-1, 4.2.5-1~bpo9+1), libatk-adaptor:amd64 (2.22.0-2, 2.30.0-2~bpo9+1), libwxgtk3.0-0v5:amd64 (3.0.2+dfsg-4, 3.0.4+dfsg-4~bpo9+1), libudev1:amd64 (232-25+deb9u6, 239-12~bpo9+1), rsyslog:amd64 (8.24.0-1, 8.40.0-1~bpo9+1), libtalloc2:amd64 (2.1.8-1, 2.1.9-2~bpo9+1), python-talloc:amd64 (2.1.8-1, 2.1.9-2~bpo9+1), hoichess:amd64 (0.19.0-5+b1, 0.22.0-1~bpo9+1), libiptc0:amd64 (1.6.0+snapshot20161117-6, 1.6.2-1.1~bpo9+1), libatk1.0-0:amd64 (2.22.0-1, 2.30.0-1~bpo9+1), libimobiledevice6:amd64 (1.2.0+dfsg-3.1, 1.2.1~git20180302.3a37a4e-1~bpo9+1), libatspi2.0-0:amd64 (2.22.0-6+deb9u1, 2.30.0-2~bpo9+1), hplip:amd64 (3.16.11+repack0-3, 3.18.10+dfsg0-3~bpo9+1), libnss-myhostname:amd64 (232-25+deb9u6, 239-12~bpo9+1), libhpmud0:amd64 (3.16.11+repack0-3, 3.18.10+dfsg0-3~bpo9+1), libldap-common:amd64 (2.4.44+dfsg-5+deb9u2, 2.4.46+dfsg-5~bpo9+1), gpgv:amd64 (2.1.18-8~deb9u3, 2.2.10-3~bpo9+1), libpam-systemd:amd64 (232-25+deb9u6, 239-12~bpo9+1), distro-info-data:amd64 (0.36, 0.39~bpo9+1), libnma0:amd64 (1.4.4-1+deb9u1, 1.8.18-2~bpo9+1), python-bs4:amd64 (4.5.3-1, 4.6.3-1~bpo9+1), systemd:amd64 (232-25+deb9u6, 239-12~bpo9+1), libwxbase3.0-0v5:amd64 (3.0.2+dfsg-4, 3.0.4+dfsg-4~bpo9+1), dh-python:amd64 (2.20170125, 3.20180723~bpo9+1), libssh-gcrypt-4:amd64 (0.7.3-2+deb9u1, 0.8.1-1~bpo9+1), gir1.2-atspi-2.0:amd64 (2.22.0-6+deb9u1, 2.30.0-2~bpo9+1), iproute2:amd64 (4.9.0-1+deb9u1, 4.18.0-2~bpo9+1), printer-driver-hpijs:amd64 (3.16.11+repack0-3, 3.18.10+dfsg0-3~bpo9+1), manpages-dev:amd64 (4.10-2, 4.16-1~bpo9+1), libsane-hpaio:amd64 (3.16.11+repack0-3, 3.18.10+dfsg0-3~bpo9+1), libxtables12:amd64 (1.6.0+snapshot20161117-6, 1.6.2-1.1~bpo9+1), libatk-bridge2.0-0:amd64 (2.22.0-2, 2.30.0-2~bpo9+1), fonts-opensymbol:amd64 (2:102.7+LibO5.2.7-1+deb9u4, 2:102.10+LibO6.1.3-1~bpo9+2), python-idna:amd64 (2.2-1, 2.6-1~bpo9+1), libatk1.0-data:amd64 (2.22.0-1, 2.30.0-1~bpo9+1), python3-lxml:amd64 (3.7.1-1, 4.2.5-1~bpo9+1), libip4tc0:amd64 (1.6.0+snapshot20161117-6, 1.6.2-1.1~bpo9+1), libatk1.0-dev:amd64 (2.22.0-1, 2.30.0-1~bpo9+1), python3-chardet:amd64 (2.3.0-2, 3.0.4-1~bpo9+1), ant-optional:amd64 (1.9.9-1+deb9u1, 1.9.12-1~bpo9+1), libatk-bridge2.0-dev:amd64 (2.22.0-2, 2.30.0-2~bpo9+1), libidn2-0:amd64 (0.16-1+deb9u1, 2.0.5-1~bpo9+1), libgwengui-gtk2-0:amd64 (4.15.3-5+b1, 4.20.0-1~bpo9+1), python3-bs4:amd64 (4.5.3-1, 4.6.3-1~bpo9+1)
End-Date: 2018-12-16  04:49:04

Start-Date: 2018-12-16  04:51:24
Commandline: apt -t stretch-backports install linux-image-4.18.0-0.bpo.1-amd64
Requested-By: jon (34316)
Install: irqbalance:amd64 (1.1.0-2.3, automatic), linux-image-4.18.0-0.bpo.1-amd64:amd64 (4.18.6-1~bpo9+1), libapparmor-perl:amd64 (2.11.0-3+deb9u2, automatic), apparmor:amd64 (2.11.0-3+deb9u2, automatic)
End-Date: 2018-12-16  04:51:37

Start-Date: 2018-12-16  05:12:31
Commandline: apt install xserver-xorg-legacy
Requested-By: jon (34316)
Install: xserver-xorg-legacy:amd64 (2:1.19.2-1+deb9u5)
End-Date: 2018-12-16  05:12:32

Start-Date: 2018-12-16  05:33:14
Commandline: apt -t stretch-backports upgrade
Requested-By: jon (34316)
Install: libqpdf21:amd64 (8.0.2-2~bpo9+1, automatic), linux-headers-4.18.0-0.bpo.1-amd64:amd64 (4.18.6-1~bpo9+1, automatic), e2fsprogs-l10n:amd64 (1.44.4-2~bpo9+1, automatic), libcom-err2:amd64 (1.44.4-2~bpo9+1), libisccfg160:amd64 (1:9.11.4.P2+dfsg-3~bpo9+1, automatic), libwayland-egl1:amd64 (1.16.0-1~bpo9+1, automatic), gnupg-utils:amd64 (2.2.10-3~bpo9+1, automatic), gpg-wks-client:amd64 (2.2.10-3~bpo9+1, automatic), libegl1:amd64 (1.1.0-1~bpo9+1, automatic), libfstrm0:amd64 (0.3.0-1, automatic), gnupg-l10n:amd64 (2.2.10-3~bpo9+1, automatic), libegl-mesa0:amd64 (18.1.9-1~bpo9+1, automatic), libgl1:amd64 (1.1.0-1~bpo9+1, automatic), python3-asn1crypto:amd64 (0.24.0-1~bpo9+1, automatic), dwz:amd64 (0.12-1+b1, automatic), libopengl0:amd64 (1.1.0-1~bpo9+1, automatic), gpg-wks-server:amd64 (2.2.10-3~bpo9+1, automatic), gpg:amd64 (2.2.10-3~bpo9+1, automatic), libisc169:amd64 (1:9.11.4.P2+dfsg-3~bpo9+1, automatic), python-certifi:amd64 (2016.2.28-1, automatic), libgles1:amd64 (1.1.0-1~bpo9+1, automatic), libgles2:amd64 (1.1.0-1~bpo9+1, automatic), orca:amd64 (3.30.1-1~bpo9+1), linux-headers-4.18.0-0.bpo.1-common:amd64 (4.18.6-1~bpo9+1, automatic), libstring-shellquote-perl:amd64 (1.03-1.2, automatic), python3-unidiff:amd64 (0.5.2-1, automatic), liblmdb0:amd64 (0.9.18-5, automatic), libext2fs2:amd64 (1.44.4-2~bpo9+1, automatic), libllvm6.0:amd64 (1:6.0-1~bpo9+1, automatic), libglvnd-dev:amd64 (1.1.0-1~bpo9+1, automatic), liblwres160:amd64 (1:9.11.4.P2+dfsg-3~bpo9+1, automatic), libprotobuf-c1:amd64 (1.2.1-2, automatic), libglx0:amd64 (1.1.0-1~bpo9+1, automatic), libglvnd-core-dev:amd64 (1.1.0-1~bpo9+1, automatic), python3-gst-1.0:amd64 (1.10.4-1, automatic), libnss-systemd:amd64 (239-12~bpo9+1, automatic), libisccc160:amd64 (1:9.11.4.P2+dfsg-3~bpo9+1, automatic), linux-kbuild-4.18:amd64 (4.18.6-1~bpo9+1, automatic), libbind9-160:amd64 (1:9.11.4.P2+dfsg-3~bpo9+1, automatic), libjson-c3:amd64 (0.12.1-1.1, automatic), libdns1102:amd64 (1:9.11.4.P2+dfsg-3~bpo9+1, automatic), python3-certifi:amd64 (2016.2.28-1, automatic), gpg-agent:amd64 (2.2.10-3~bpo9+1), libgpg-error-l10n:amd64 (1.32-3~bpo9+2, automatic), python-asn1crypto:amd64 (0.24.0-1~bpo9+1, automatic), gpgconf:amd64 (2.2.10-3~bpo9+1, automatic), gpgsm:amd64 (2.2.10-3~bpo9+1, automatic), libglx-mesa0:amd64 (18.1.9-1~bpo9+1, automatic), libglvnd0:amd64 (1.1.0-1~bpo9+1, automatic), libdrm-common:amd64 (2.4.95-1~bpo9+1, automatic), libxml-simple-perl:amd64 (2.22-1, automatic)
Upgrade: libcomerr2:amd64 (1.43.4-2, 1.44.4-2~bpo9+1), libgles2-mesa:amd64 (13.0.6-1+b2, 18.1.9-1~bpo9+1), intel-microcode:amd64 (3.20180807a.1~deb9u1, 3.20180807a.2~bpo9+1), libdrm-nouveau2:amd64 (2.4.74-1, 2.4.95-1~bpo9+1), gnupg-agent:amd64 (2.1.18-8~deb9u3, 2.2.10-3~bpo9+1), libegl1-mesa-dev:amd64 (13.0.6-1+b2, 18.1.9-1~bpo9+1), python-requests:amd64 (2.12.4-1, 2.20.0-2~bpo9+1), libglapi-mesa:amd64 (13.0.6-1+b2, 18.1.9-1~bpo9+1), mesa-common-dev:amd64 (13.0.6-1+b2, 18.1.9-1~bpo9+1), python3-urllib3:amd64 (1.19.1-1, 1.24-1~bpo9+1), libgpgme11:amd64 (1.8.0-3+b2, 1.12.0-4~bpo9+1), libgpg-error0:amd64 (1.26-2, 1.32-3~bpo9+2), bind9-host:amd64 (1:9.10.3.dfsg.P4-12.3+deb9u4, 1:9.11.4.P2+dfsg-3~bpo9+1), e2fsprogs:amd64 (1.43.4-2, 1.44.4-2~bpo9+1), firmware-amd-graphics:amd64 (20161130-4, 20180825+dfsg-1~bpo9+1), gnome-orca:amd64 (3.22.2-3, 3.30.1-1~bpo9+1), libxatracker2:amd64 (13.0.6-1+b2, 18.1.9-1~bpo9+1), libegl1-mesa:amd64 (13.0.6-1+b2, 18.1.9-1~bpo9+1), e2fslibs:amd64 (1.43.4-2, 1.44.4-2~bpo9+1), amd64-microcode:amd64 (3.20160316.3, 3.20180524.1~bpo9+1), python3-requests:amd64 (2.12.4-1, 2.20.0-2~bpo9+1), libgbm1:amd64 (13.0.6-1+b2, 18.1.9-1~bpo9+1), dirmngr:amd64 (2.1.18-8~deb9u3, 2.2.10-3~bpo9+1), libss2:amd64 (1.43.4-2, 1.44.4-2~bpo9+1), libwayland-client0:amd64 (1.12.0-1, 1.16.0-1~bpo9+1), python-cryptography:amd64 (1.7.1-3, 2.3-1~bpo9+1), libwayland-bin:amd64 (1.12.0-1, 1.16.0-1~bpo9+1), libdrm-amdgpu1:amd64 (2.4.74-1, 2.4.95-1~bpo9+1), libwayland-dev:amd64 (1.12.0-1, 1.16.0-1~bpo9+1), python3-cryptography:amd64 (1.7.1-3, 2.3-1~bpo9+1), firmware-linux-nonfree:amd64 (20161130-4, 20180825+dfsg-1~bpo9+1), linux-image-amd64:amd64 (4.9+80+deb9u6, 4.18+98~bpo9+1), systemd-sysv:amd64 (232-25+deb9u6, 239-12~bpo9+1), libwayland-egl1-mesa:amd64 (13.0.6-1+b2, 18.1.9-1~bpo9+1), lintian:amd64 (2.5.50.4, 2.5.116~bpo9+1), python-urllib3:amd64 (1.19.1-1, 1.24-1~bpo9+1), libdrm2:amd64 (2.4.74-1, 2.4.95-1~bpo9+1), linux-headers-amd64:amd64 (4.9+80+deb9u6, 4.18+98~bpo9+1), debhelper:amd64 (10.2.5, 11.3.5~bpo9+1), libgl1-mesa-dev:amd64 (13.0.6-1+b2, 18.1.9-1~bpo9+1), libgl1-mesa-dri:amd64 (13.0.6-1+b2, 18.1.9-1~bpo9+1), firmware-misc-nonfree:amd64 (20161130-4, 20180825+dfsg-1~bpo9+1), qpdf:amd64 (6.0.0-2, 8.0.2-2~bpo9+1), python-gpg:amd64 (1.8.0-3+b2, 1.12.0-4~bpo9+1), libgl1-mesa-glx:amd64 (13.0.6-1+b2, 18.1.9-1~bpo9+1), libdrm-intel1:amd64 (2.4.74-1, 2.4.95-1~bpo9+1), libdrm-radeon1:amd64 (2.4.74-1, 2.4.95-1~bpo9+1), mesa-vdpau-drivers:amd64 (13.0.6-1+b2, 18.1.9-1~bpo9+1), gnupg:amd64 (2.1.18-8~deb9u3, 2.2.10-3~bpo9+1), firmware-linux:amd64 (20161130-4, 20180825+dfsg-1~bpo9+1), libdrm-dev:amd64 (2.4.74-1, 2.4.95-1~bpo9+1), devscripts:amd64 (2.17.6+deb9u2, 2.18.10~bpo9+1), libwayland-server0:amd64 (1.12.0-1, 1.16.0-1~bpo9+1), mesa-va-drivers:amd64 (13.0.6-1+b2, 18.1.9-1~bpo9+1), libwayland-cursor0:amd64 (1.12.0-1, 1.16.0-1~bpo9+1)
End-Date: 2018-12-16  05:33:46


AFAICT at this point, my video problems are solved. I'm getting 4K@60 with the amdgpu driver and the right firmware appears to be getting loaded. The remaining problem, which possibly? has nothing at all to do with the AMD driver, is the complete lack of audio despite there being two ALSA devices on the system (ATI HDMI and Realtek motherboard audio).
oddhack
 
Posts: 13
Joined: 2018-07-21 23:35

Re: Video / audio troubles with RX 570 / stretch

Postby llivv » 2018-12-17 06:11

Lucky for me I read the post in the other forum before I read your last post here.

after upgrading to
Code: Select all
apt -t stretch-backports install linux-image-4.18.0-0.bpo.1-amd64

did you see any missing firmware warnings while the new kernels ram disk image finished building?
I see you later installed xserver-xorg-video-legacy than upgraded again
which pulled in these firmware packages
    firmware-linux-nonfree
    firmware-misc-nonfree
    firmware-linux

did apt show missing firmware while rebuilding the ram disk image /boot/initrd.img-4.18.0-0.bpo.1-amd64

from the other forum
oddhack wrote:There are two alsa devices for the ATI HDMI and Realtek,

7.1 CH HD Audio (Realtek ALC892 Audio Codec), ELNA Audio Caps
just double checking myself
Code: Select all
firmware-realtek
from backports

The mobo is pretty new so keep your fingers crossed that the firmware for the alc892 is included in the backports firmware package.
In memory of Ian Ashley Murdock (1973 - 2015) founder of the Debian project.
User avatar
llivv
 
Posts: 5488
Joined: 2007-02-14 18:10
Location: cold storage

Re: Video / audio troubles with RX 570 / stretch

Postby oddhack » 2018-12-17 08:01

llivv wrote:Lucky for me I read the post in the other forum before I read your last post here.

after upgrading to
Code: Select all
apt -t stretch-backports install linux-image-4.18.0-0.bpo.1-amd64

did you see any missing firmware warnings while the new kernels ram disk image finished building?


Only for the rtl8169 module, which is AFAIK the Ethernet adapter (which works fine, in any event).

I see you later installed xserver-xorg-video-legacy than upgraded again
which pulled in these firmware packages
    firmware-linux-nonfree
    firmware-misc-nonfree
    firmware-linux

did apt show missing firmware while rebuilding the ram disk image /boot/initrd.img-4.18.0-0.bpo.1-amd64


Again only for the r8169 module - I did a reinstall to double-check on this, log follows:

Code: Select all
# apt -t stretch-backports install --reinstall linux-image-4.18.0-0.bpo.1-amd64
Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
  gnome-orca gnupg-agent iputils-arping libbind9-140 libdns162
  libgconfmm-2.6-1v5 libglademm-2.4-1v5 libisc160 libisccc140 libisccfg140
  liblwres141 libtxc-dxtn-s2tc python-pyasn1 python3-pyasn1
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 32 not upgraded.
Need to get 45.4 MB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ftp.debian.org/debian stretch-backports/main amd64 linux-image-4.18.0-0.bpo.1-amd64 amd64 4.18.6-1~bpo9+1 [45.4 MB]
Fetched 45.4 MB in 4s (10.0 MB/s)
(Reading database ... 267065 files and directories currently installed.)
Preparing to unpack .../linux-image-4.18.0-0.bpo.1-amd64_4.18.6-1~bpo9+1_amd64.deb ...
Unpacking linux-image-4.18.0-0.bpo.1-amd64 (4.18.6-1~bpo9+1) over (4.18.6-1~bpo9+1) ...
Setting up linux-image-4.18.0-0.bpo.1-amd64 (4.18.6-1~bpo9+1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.18.0-0.bpo.1-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-4.18.0-0.bpo.1-amd64
Found initrd image: /boot/initrd.img-4.18.0-0.bpo.1-amd64
Found linux image: /boot/vmlinuz-4.9.0-8-amd64
Found initrd image: /boot/initrd.img-4.9.0-8-amd64
done


just double checking myself
Code: Select all
firmware-realtek
from backports

The mobo is pretty new so keep your fingers crossed that the firmware for the alc892 is included in the backports firmware package.


The ALC892 itself is quite old though, isn't it? I see forum posts about it dating back to 2010. But after you posted this I figured out that I didn't have firmware-realtek installed - will be trying that momentarily and report back.
oddhack
 
Posts: 13
Joined: 2018-07-21 23:35

Re: Video / audio troubles with RX 570 / stretch

Postby oddhack » 2018-12-17 08:41

Installing firmware-realtek did get some progress. The alsactl error in the boot log is no longer present, and I now see two devices in the pulseaudio sound controls: "HDMI / DisplayPort 4 - Ellesmere [Radeon RX 580]" and "Line Out - Family 17h (Models 00h-0fh) HD Audio Controller".

Unfortunately, I'm still getting no actual sound out of the analog ports or the HDMI monitor, and there aren't any errors showing up in syslog when I try to play audio (or run the speaker test). I'm also seeing a periodic syslog panic report which appears? to be related to systemd-udevd, though I have no idea if that's related to the audio problems:

Code: Select all

Dec 17 01:21:59 celly kernel: [ 1330.141147] INFO: task systemd-udevd:393 blocked for more than 120 seconds.
Dec 17 01:21:59 celly kernel: [ 1330.141154]       Tainted: G           O      4.18.0-0.bpo.1-amd64 #1 Debian 4.18.6-1~bpo9+1
Dec 17 01:21:59 celly kernel: [ 1330.141156] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 17 01:21:59 celly kernel: [ 1330.141159] systemd-udevd   D    0   393    386 0x80000124
Dec 17 01:21:59 celly kernel: [ 1330.141164] Call Trace:
Dec 17 01:21:59 celly kernel: [ 1330.141175]  ? __schedule+0x3f5/0x880
Dec 17 01:21:59 celly kernel: [ 1330.141179]  schedule+0x32/0x80
Dec 17 01:21:59 celly kernel: [ 1330.141192]  __sev_do_cmd_locked+0x1bd/0x270 [ccp]
Dec 17 01:21:59 celly kernel: [ 1330.141198]  ? remove_wait_queue+0x60/0x60
Dec 17 01:21:59 celly kernel: [ 1330.141207]  sev_do_cmd+0x2a/0x40 [ccp]
Dec 17 01:21:59 celly kernel: [ 1330.141216]  sev_get_api_version+0x34/0xa0 [ccp]
Dec 17 01:21:59 celly kernel: [ 1330.141224]  ? sp_get_psp_master_device+0x63/0x80 [ccp]
Dec 17 01:21:59 celly kernel: [ 1330.141232]  psp_pci_init+0x43/0x230 [ccp]
Dec 17 01:21:59 celly kernel: [ 1330.141240]  sp_mod_init+0x16/0x1000 [ccp]
Dec 17 01:21:59 celly kernel: [ 1330.141244]  ? 0xffffffffc062c000
Dec 17 01:21:59 celly kernel: [ 1330.141248]  do_one_initcall+0x4d/0x1c5
Dec 17 01:21:59 celly kernel: [ 1330.141253]  ? free_unref_page_commit+0x95/0x120
Dec 17 01:21:59 celly kernel: [ 1330.141256]  ? _cond_resched+0x16/0x40
Dec 17 01:21:59 celly kernel: [ 1330.141260]  ? kmem_cache_alloc_trace+0xb5/0x1c0
Dec 17 01:21:59 celly kernel: [ 1330.141264]  ? do_init_module+0x22/0x218
Dec 17 01:21:59 celly kernel: [ 1330.141267]  do_init_module+0x5b/0x218
Dec 17 01:21:59 celly kernel: [ 1330.141271]  load_module.constprop.55+0x2545/0x2d50
Dec 17 01:21:59 celly kernel: [ 1330.141275]  ? vfs_read+0x119/0x130
Dec 17 01:21:59 celly kernel: [ 1330.141279]  ? __do_sys_finit_module+0xd2/0x100
Dec 17 01:21:59 celly kernel: [ 1330.141282]  __do_sys_finit_module+0xd2/0x100
Dec 17 01:21:59 celly kernel: [ 1330.141287]  do_syscall_64+0x55/0x110
Dec 17 01:21:59 celly kernel: [ 1330.141291]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Dec 17 01:21:59 celly kernel: [ 1330.141295] RIP: 0033:0x7f2e6048c229
Dec 17 01:21:59 celly kernel: [ 1330.141296] Code: Bad RIP value.
Dec 17 01:21:59 celly kernel: [ 1330.141305] RSP: 002b:00007ffd659b2088 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
Dec 17 01:21:59 celly kernel: [ 1330.141309] RAX: ffffffffffffffda RBX: 0000559a148fd0b0 RCX: 00007f2e6048c229
Dec 17 01:21:59 celly kernel: [ 1330.141311] RDX: 0000000000000000 RSI: 00007f2e601a2265 RDI: 000000000000000f
Dec 17 01:21:59 celly kernel: [ 1330.141313] RBP: 00007f2e601a2265 R08: 0000000000000000 R09: 00007ffd659b2600
Dec 17 01:21:59 celly kernel: [ 1330.141315] R10: 000000000000000f R11: 0000000000000246 R12: 0000000000000000
Dec 17 01:21:59 celly kernel: [ 1330.141317] R13: 0000559a14938480 R14: 0000000000020000 R15: 0000559a14021a9a
oddhack
 
Posts: 13
Joined: 2018-07-21 23:35

Re: Video / audio troubles with RX 570 / stretch

Postby llivv » 2018-12-17 13:32

as user post output of
Code: Select all
user@host:~$ groups


did you post all of the Call Trace?
if you got all of it in the post above disregard my request below.

[[[[ if you can repost the kernel log starting 10 lines above
1330.141147] INFO: task systemd-udevd:393 blocked for more than 120 seconds.

to the end of the Call Trace:
where normal boot messages resume
(if not sure just do your best - call traces are usually 30 to 60 lines of the kernal log) sometimes longer if it was a kernel panic.
]]]


If your boot is hanging with a 120 second timeout you can disable the timeout
see the line in the log you posted above:
"Dec 17 01:21:59 celly kernel: [ 1330.141156] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

This line below informs kernel devs that there is a blob of some kind ( in your case the blob is nvidia ) that is not a native module released with the kernel.
also known as an out of tree module IIRC
Code: Select all
Dec 17 01:21:59 celly kernel: [ 1330.141154]       Tainted: G           O      4.18.0-0.bpo.1-amd64 #1 Debian 4.18.6-1~bpo9+1
In memory of Ian Ashley Murdock (1973 - 2015) founder of the Debian project.
User avatar
llivv
 
Posts: 5488
Joined: 2007-02-14 18:10
Location: cold storage

Re: Video / audio troubles with RX 570 / stretch

Postby oddhack » 2018-12-18 11:07

llivv wrote:as user post output of
Code: Select all
user@host:~$ groups


did you post all of the Call Trace?
if you got all of it in the post above disregard my request below.


(Edit: the call trace problem is almost certainly unrelated to my audio issues - it looks like a BIOS problem with this motherboard vs. my Ryzen 2600, see https://bugzilla.redhat.com/show_bug.cgi?id=1608242)

I pasted the complete syslog here: https://pastebin.com/JaEAJwms . The first panic/call trace is around line 1351. I notice it does stop recurring after a while.

If your boot is hanging with a 120 second timeout you can disable the timeout
see the line in the log you posted above:


Boot actually isn't hanging, but shutdowns hang for several minutes with the messages:

Code: Select all
systemd-udevd[386]: giving up waiting for workers to finish
systemd-udevd[386]: event loop failed: Connection timed out
(several minute wait)
systemd-shutdown[1]: Sending SIGKILL to remaining processes...
systemd-shutdown[1]: Sending SIGKILL to PID 393 (systemd-udevd)


I suspect this is a bit of a red herring and could be unrelated to audio issues, though. After several reboot cycles, I'm still seeing these panic messages in syslog, but now I'm actually getting audio over HDMI and can control it with pulseaudio control apps. This is mystifying since nothing changed in the system configuration between reboots. If it persists, the only remaining problem will be that the realtek driver isn't showing up in pulseaudio (cross fingers).
oddhack
 
Posts: 13
Joined: 2018-07-21 23:35

Re: Video / audio troubles with RX 570 / stretch

Postby llivv » 2018-12-18 13:57

oddhack wrote:
llivv wrote:as user post output of
Code: Select all
user@host:~$ groups
I'll assume !! -- your user is a member of the audio group.....? What groups is your user a member of ? /quote
oddhack wrote:
llivv wrote:did you post all of the Call Trace?
if you got all of it in the post above disregard my request below.

(Edit: the call trace problem is almost certainly unrelated to my audio issues - it looks like a BIOS problem with this motherboard vs. my Ryzen 2600, see https://bugzilla.redhat.com/show_bug.cgi?id=1608242)
I'm looking at what you are posting and doing my best to interpret.
oddhack wrote:I pasted the complete syslog here: https://pastebin.com/JaEAJwms . The first panic/call trace is around line 1351. I notice it does stop recurring after a while.
scanning syslog, thanks for posting (dmesg is preferred) it's a lot easier for me to read, especially if I'm drowsy, which happens occasionally ....

oddhack wrote:
llivv wrote:If your boot is hanging with a 120 second timeout you can disable the timeout
see the line in the log you posted above:
Boot actually isn't hanging, but shutdowns hang for several minutes with the messages:
Code: Select all
systemd-udevd[386]: giving up waiting for workers to finish
systemd-udevd[386]: event loop failed: Connection timed out
(several minute wait)
systemd-shutdown[1]: Sending SIGKILL to remaining processes...
systemd-shutdown[1]: Sending SIGKILL to PID 393 (systemd-udevd)
way ahead of me here.... I can't keep up at this pace.....

oddhack wrote:I suspect this is a bit of a red herring and could be unrelated to audio issues, though. After several reboot cycles, I'm still seeing these panic messages in syslog,
does it say panic in the logs? It looks like a kernel oops to me- but I haven't scanned the full log you posted yet.
oddhack wrote:but now I'm actually getting audio over HDMI and can control it with pulseaudio control apps. This is mystifying since nothing changed in the system configuration between reboots. If it persists, the only remaining problem will be that the realtek driver isn't showing up in pulseaudio (cross fingers).

fingers crossed for sure - here too....
6: what devices show in alsamixer
7: post what's in /proc/asound/devices
8: do you have 2 cards in /proc/asound
take a look around asound and see if you can match up /proc entries with pulseaudio and alsa devices.

I'll finish scanning the log now, thanks for pasting it up ! :wink:

edit: I'll post a saved dmesg on my box with an oops at the KMS framebuffer switch.
starting at pastebin line# 606 [ 8.366116] [drm] Replacing VGA console driver
ending and pastebin line# 687 [ 8.376581] systemd-udevd[391]: worker [432] failed while handling '/devices/pci0000:00/0000:00:02.0'
The oops caused a blank screen after the KMS switch. I've seen it happen in the last of the 2,6 kernels on older chipsets way back years ago. There are about 10 Bug reports on this issue and it was already fixed in the kernel available in experimental....... 4.19.5-1~exp1 .......
My mobo is an intel DG41RQ / Xeon X3350 / 2GB PC2-6400 DDR2 800MHz
Most of the specs are identified in the log.
https://pastebin.com/BVRiSCuR
if your interested, there are quite a few similarities between yours and mine.

edit2 don't ask me what I was thinking about in my post saying " the nvida blob was tainting the kernel " I see which module is the out of tree module now.......
In memory of Ian Ashley Murdock (1973 - 2015) founder of the Debian project.
User avatar
llivv
 
Posts: 5488
Joined: 2007-02-14 18:10
Location: cold storage

Re: Video / audio troubles with RX 570 / stretch

Postby oddhack » 2018-12-18 20:25

llivv wrote:I'll assume !! -- your user is a member of the audio group.....? What groups is your user a member of ?


Code: Select all
users root adm mail cdrom sudo audio dip plugdev games netdev lpadmin sambashare vboxusers


I did have to explicitly add 'audio' after noticing alsamixer was getting different results as root and my user, but that preceded these problems.

llivv wrote:
oddhack wrote:I suspect this is a bit of a red herring and could be unrelated to audio issues, though. After several reboot cycles, I'm still seeing these panic messages in syslog,
does it say panic in the logs? It looks like a kernel oops to me- but I haven't scanned the full log you posted yet.


You're right. It's not an actual kernel panic that brings the system down. I am not clear on where the traceback is being logged from, but it looks like the cause is system-udevd failing.

oddhack wrote:but now I'm actually getting audio over HDMI and can control it with pulseaudio control apps. This is mystifying since nothing changed in the system configuration between reboots. If it persists, the only remaining problem will be that the realtek driver isn't showing up in pulseaudio (cross fingers).


fingers crossed for sure - here too....
6: what devices show in alsamixer


Run as root, it shows 'Card: HDA ATI HDMI'. F6 says 'Select sound card' but doesn't show anything. alsamixer shows 6 S/PDIF channels but doesn't let me actually adjust the volume on any of them.

Run as my user, it shows 'Card: PulseAudio'. F6 shows two options, '0: HDA ATI HDMI' and '1: HD-Audio Generic'. I am unable to toggle between them because of what looks like some weird ncurses UI bug - hitting F6 shows the menu very very briefly and then returns to the channel control UI before I can select anything.

7: post what's in /proc/asound/devices


Code: Select all
  2: [ 0- 3]: digital audio playback
  3: [ 0- 7]: digital audio playback
  4: [ 0- 8]: digital audio playback
  5: [ 0- 9]: digital audio playback
  6: [ 0-10]: digital audio playback
  7: [ 0-11]: digital audio playback
  8: [ 0- 0]: hardware dependent
  9: [ 0]   : control
 10: [ 1- 0]: digital audio playback
 11: [ 1- 0]: digital audio capture
 12: [ 1- 2]: digital audio capture
 13: [ 1- 0]: hardware dependent
 14: [ 1]   : control
 33:        : timer


8: do you have 2 cards in /proc/asound


Yes:

Code: Select all
/proc/asound
/proc/asound/oss
/proc/asound/oss/devices
/proc/asound/oss/sndstat
/proc/asound/pcm
/proc/asound/seq
/proc/asound/HDMI
/proc/asound/card0
/proc/asound/card0/id
/proc/asound/card0/pcm3p
/proc/asound/card0/pcm3p/info
/proc/asound/card0/pcm3p/sub0
/proc/asound/card0/pcm3p/sub0/info
/proc/asound/card0/pcm3p/sub0/status
/proc/asound/card0/pcm3p/sub0/prealloc
/proc/asound/card0/pcm3p/sub0/hw_params
/proc/asound/card0/pcm3p/sub0/sw_params
/proc/asound/card0/pcm3p/sub0/prealloc_max
/proc/asound/card0/pcm7p
/proc/asound/card0/pcm7p/info
/proc/asound/card0/pcm7p/sub0
/proc/asound/card0/pcm7p/sub0/info
/proc/asound/card0/pcm7p/sub0/status
/proc/asound/card0/pcm7p/sub0/prealloc
/proc/asound/card0/pcm7p/sub0/hw_params
/proc/asound/card0/pcm7p/sub0/sw_params
/proc/asound/card0/pcm7p/sub0/prealloc_max
/proc/asound/card0/pcm8p
/proc/asound/card0/pcm8p/info
/proc/asound/card0/pcm8p/sub0
/proc/asound/card0/pcm8p/sub0/info
/proc/asound/card0/pcm8p/sub0/status
/proc/asound/card0/pcm8p/sub0/prealloc
/proc/asound/card0/pcm8p/sub0/hw_params
/proc/asound/card0/pcm8p/sub0/sw_params
/proc/asound/card0/pcm8p/sub0/prealloc_max
/proc/asound/card0/pcm9p
/proc/asound/card0/pcm9p/info
/proc/asound/card0/pcm9p/sub0
/proc/asound/card0/pcm9p/sub0/info
/proc/asound/card0/pcm9p/sub0/status
/proc/asound/card0/pcm9p/sub0/prealloc
/proc/asound/card0/pcm9p/sub0/hw_params
/proc/asound/card0/pcm9p/sub0/sw_params
/proc/asound/card0/pcm9p/sub0/prealloc_max
/proc/asound/card0/pcm10p
/proc/asound/card0/pcm10p/info
/proc/asound/card0/pcm10p/sub0
/proc/asound/card0/pcm10p/sub0/info
/proc/asound/card0/pcm10p/sub0/status
/proc/asound/card0/pcm10p/sub0/prealloc
/proc/asound/card0/pcm10p/sub0/hw_params
/proc/asound/card0/pcm10p/sub0/sw_params
/proc/asound/card0/pcm10p/sub0/prealloc_max
/proc/asound/card0/pcm11p
/proc/asound/card0/pcm11p/info
/proc/asound/card0/pcm11p/sub0
/proc/asound/card0/pcm11p/sub0/info
/proc/asound/card0/pcm11p/sub0/status
/proc/asound/card0/pcm11p/sub0/prealloc
/proc/asound/card0/pcm11p/sub0/hw_params
/proc/asound/card0/pcm11p/sub0/sw_params
/proc/asound/card0/pcm11p/sub0/prealloc_max
/proc/asound/card0/codec#0
/proc/asound/card0/eld#0.0
/proc/asound/card0/eld#0.1
/proc/asound/card0/eld#0.2
/proc/asound/card0/eld#0.3
/proc/asound/card0/eld#0.4
/proc/asound/card0/eld#0.5
/proc/asound/card0/oss_mixer
/proc/asound/card1
/proc/asound/card1/id
/proc/asound/card1/pcm0c
/proc/asound/card1/pcm0c/oss
/proc/asound/card1/pcm0c/info
/proc/asound/card1/pcm0c/sub0
/proc/asound/card1/pcm0c/sub0/info
/proc/asound/card1/pcm0c/sub0/status
/proc/asound/card1/pcm0c/sub0/prealloc
/proc/asound/card1/pcm0c/sub0/hw_params
/proc/asound/card1/pcm0c/sub0/sw_params
/proc/asound/card1/pcm0c/sub0/prealloc_max
/proc/asound/card1/pcm0p
/proc/asound/card1/pcm0p/oss
/proc/asound/card1/pcm0p/info
/proc/asound/card1/pcm0p/sub0
/proc/asound/card1/pcm0p/sub0/info
/proc/asound/card1/pcm0p/sub0/status
/proc/asound/card1/pcm0p/sub0/prealloc
/proc/asound/card1/pcm0p/sub0/hw_params
/proc/asound/card1/pcm0p/sub0/sw_params
/proc/asound/card1/pcm0p/sub0/prealloc_max
/proc/asound/card1/pcm2c
/proc/asound/card1/pcm2c/info
/proc/asound/card1/pcm2c/sub0
/proc/asound/card1/pcm2c/sub0/info
/proc/asound/card1/pcm2c/sub0/status
/proc/asound/card1/pcm2c/sub0/prealloc
/proc/asound/card1/pcm2c/sub0/hw_params
/proc/asound/card1/pcm2c/sub0/sw_params
/proc/asound/card1/pcm2c/sub0/prealloc_max
/proc/asound/card1/codec#0
/proc/asound/card1/oss_mixer
/proc/asound/cards
/proc/asound/hwdep
/proc/asound/timers
/proc/asound/Generic
/proc/asound/devices
/proc/asound/modules
/proc/asound/version


take a look around asound and see if you can match up /proc entries with pulseaudio and alsa devices.


It seems like /proc/asound/card0 maps onto the 'HDA ATI HDMI' device and /proc/asound/card1 onto the 'HD-Audio Generic'. It is peculiar that pulseaudio only shows the first device, though. I've tried to look for errors from pulseaudio but don't see anything relevant in syslog/user.log. N.b. where does pulseaudio even get started? I don't see anything under /etc/systemd or /etc/init.d that appears to fire off the daemon.

Most of the specs are identified in the log.
https://pastebin.com/BVRiSCuR
if your interested, there are quite a few similarities between yours and mine.


I think there's a known BIOS issue that's causing my timeouts - checking with AsRock to see if the latest BIOS might address this, I'd rather not do a BIOS upgrade just on the off chance it might help. Apologies for misleading you with this! If a BIOS upgrade magically fixes audio, of course that would be great, too.
oddhack
 
Posts: 13
Joined: 2018-07-21 23:35

Next

Return to Desktop & Multimedia

Who is online

Users browsing this forum: No registered users and 3 guests

fashionable