[MS-7C52, ATI R6xx HDMI, Digital Out, HDMI] No sound at all, second display not working, cpu/agpu performance dropped considerably

Bug #1912773 reported by Hassan Williamson
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Linux Firmware
New
Undecided
Unassigned
Mutter
New
Undecided
Unassigned
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

After a recent update, I now have a system that can no longer play audio (via HDMI), my second monitor (DVI) is no longer being picked up, and CPU/AGPU usage has lost a lot of performance (OBS is basically unusable at this point).

Whatever has happened with the recent updates has caused the AMD drivers (presumably?) to not work correctly - because it is an AMD Ryzen 5 3400g (with no dedicated graphics card).

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu

```
$ lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04
```

2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center

Not sure which package would be the cause, however these were the version that were working prior to the update:

```
libnss-systemd:amd64=245.4-4ubuntu3.3 libudev1:i386=245.4-4ubuntu3.3 libudev1:amd64=245.4-4ubuntu3.3 libudev-dev:amd64=245.4-4ubuntu3.3 udev=245.4-4ubuntu3.3 systemd-timesyncd=245.4-4ubuntu3.3 systemd-sysv=245.4-4ubuntu3.3 libpam-systemd:amd64=245.4-4ubuntu3.3 systemd=245.4-4ubuntu3.3 libsystemd0:amd64=245.4-4ubuntu3.3 libsystemd0:i386=245.4-4ubuntu3.3 libapt-pkg6.0:amd64=2.0.2ubuntu0.2 apt=2.0.2ubuntu0.2 apt-utils=2.0.2ubuntu0.2 ubuntu-release-upgrader-gtk=1:20.04.29 ubuntu-release-upgrader-core=1:20.04.29 update-manager=1:20.04.10.1 update-manager-core=1:20.04.10.1 python3-distupgrade=1:20.04.29 python3-update-manager=1:20.04.10.1 update-notifier=3.192.30.3 update-notifier-common=3.192.30.3 libnetplan0:amd64=0.100-0ubuntu4~20.04.3 netplan.io=0.100-0ubuntu4~20.04.3 mutter-common=3.36.6-1ubuntu0.20.04.2 gir1.2-mutter-6:amd64=3.36.6-1ubuntu0.20.04.2 libmutter-6-0:amd64=3.36.6-1ubuntu0.20.04.2 jq=1.6-1 libjq1:amd64=1.6-1 linux-firmware=1.187.7 linux-generic-hwe-20.04=5.8.0.38.43~20.04.23 linux-image-generic-hwe-20.04=5.8.0.38.43~20.04.23 linux-headers-generic-hwe-20.04=5.8.0.38.43~20.04.23 linux-headers-generic=5.4.0.62.65 linux-libc-dev:amd64=5.4.0-62.70 mutter=3.36.6-1ubuntu0.20.04.2
```

This list was generated with the command:

`awk 'BEGIN{ start="0" } { if($0 ~ /Log started: 2021-01-20/) { start="1"} if ( start == "1" && $0 ~ /Unpacking.*over/) {gsub(/[\s\t)( ]+/,"",$5); printf("%s=%s ", $2 , $5)}}' /var/log/apt/term.log`

3) What you expected to happen

Sound and video working via HDMI on primary monitor, second monitor displaying (extended) video via DVI. CPU and AGPU being able to render via OBS.

4) What happened instead

No sound. No second display. Any CPU or AGPU tasks running slower than normal.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC3: hazrpg 3344 F.... pulseaudio
 /dev/snd/controlC2: hazrpg 3344 F.... pulseaudio
 /dev/snd/controlC0: hazrpg 3344 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 22 11:51:14 2021
InstallationDate: Installed on 2020-05-22 (244 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
Symptom_Card: Raven/Raven2/Fenghuang HDMI/DP Audio Controller - HD-Audio Generic
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [MS-7C52, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.20
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A320M-A PRO MAX (MS-7C52)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.20:bd09/18/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnA320M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C52
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

Revision history for this message
Hassan Williamson (hazrpg) wrote :
summary: - [MS-7C52, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
+ [MS-7C52, ATI R6xx HDMI, Digital Out, HDMI] No sound at all, second
+ display not working, cpu/agpu performance dropped considerably
Revision history for this message
Hassan Williamson (hazrpg) wrote :

Forgot to mention in the original post, but trying to revert all updates that caused the problem (as per the versions listed above) but that didn't work because they no longer exist in the repo (and the system had already cleared the cache). So I always get the error that the package(s) were not found:

E: Version '245.4-4ubuntu3.3' for 'libnss-systemd' was not found
E: Version '245.4-4ubuntu3.3' for 'libudev1:i386' was not found
E: Version '245.4-4ubuntu3.3' for 'libudev1' was not found
E: Version '245.4-4ubuntu3.3' for 'libudev-dev' was not found
E: Version '245.4-4ubuntu3.3' for 'udev' was not found
E: Version '245.4-4ubuntu3.3' for 'systemd-timesyncd' was not found
E: Version '245.4-4ubuntu3.3' for 'systemd-sysv' was not found
E: Version '245.4-4ubuntu3.3' for 'libpam-systemd' was not found
E: Version '245.4-4ubuntu3.3' for 'systemd' was not found
E: Version '245.4-4ubuntu3.3' for 'libsystemd0' was not found
E: Version '245.4-4ubuntu3.3' for 'libsystemd0:i386' was not found
E: Version '1:20.04.29' for 'ubuntu-release-upgrader-gtk' was not found
E: Version '1:20.04.29' for 'ubuntu-release-upgrader-core' was not found
E: Version '1:20.04.10.1' for 'update-manager' was not found
E: Version '1:20.04.10.1' for 'update-manager-core' was not found
E: Version '1:20.04.29' for 'python3-distupgrade' was not found
E: Version '1:20.04.10.1' for 'python3-update-manager' was not found
E: Version '3.192.30.3' for 'update-notifier' was not found
E: Version '3.192.30.3' for 'update-notifier-common' was not found
E: Version '0.100-0ubuntu4~20.04.3' for 'libnetplan0' was not found
E: Version '0.100-0ubuntu4~20.04.3' for 'netplan.io' was not found
E: Version '3.36.6-1ubuntu0.20.04.2' for 'mutter-common' was not found
E: Version '3.36.6-1ubuntu0.20.04.2' for 'gir1.2-mutter-6' was not found
E: Version '3.36.6-1ubuntu0.20.04.2' for 'libmutter-6-0' was not found
E: Version '3.36.6-1ubuntu0.20.04.2' for 'mutter' was not found

Revision history for this message
Hassan Williamson (hazrpg) wrote :
Download full text (7.1 KiB)

I've done more digging and I think the regressing happened sooner, but I only rebooted it on the day I noticed it wasn't working. I decided to see when the system was actually last rebooted by using:

$ last reboot | less

reboot system boot 5.8.0-40-generic Fri Jan 22 11:44 still running
reboot system boot 5.8.0-40-generic Fri Jan 22 10:15 - 11:44 (01:28)
reboot system boot 5.4.0-64-generic Fri Jan 22 10:06 - 10:14 (00:07)
reboot system boot 5.8.0-40-generic Fri Jan 22 10:03 - 10:14 (00:11)
reboot system boot 5.8.0-40-generic Fri Jan 22 08:23 - 10:02 (01:39)
reboot system boot 5.8.0-40-generic Fri Jan 22 08:10 - 08:23 (00:13)
reboot system boot 5.4.0-64-generic Fri Jan 22 08:06 - 08:09 (00:03)
reboot system boot 5.8.0-36-generic Fri Jan 22 07:59 - 08:05 (00:06)
reboot system boot 5.8.0-38-generic Fri Jan 22 07:53 - 07:58 (00:05)
reboot system boot 5.8.0-40-generic Fri Jan 22 07:45 - 07:52 (00:07)
reboot system boot 5.8.0-40-generic Fri Jan 22 07:39 - 07:40 (00:00)
reboot system boot 5.8.0-40-generic Fri Jan 22 07:35 - 07:38 (00:03)
reboot system boot 5.8.0-36-generic Sun Jan 10 03:43 - 07:34 (12+03:51)
reboot system boot 5.4.0-58-generic Mon Jan 4 10:00 - 03:42 (5+17:42)

You'll see everything was fine on the 10 Jan 2021 and 4 Jan 2021. That means the regression happened on or after these dates. I've rerun the awk command to see what packages were changed in that time and I have:

$ awk 'BEGIN{ start="0" } { if($0 ~ /Log started: 2021-01-05/) { start="1"} if ( start == "1" && $0 ~ /Unpacking.*over/) {gsub(/[\s\t)( ]+/,"",$5); printf("%s=%s ", $2 , $5)}}' /var/log/apt/term.log

libproxy1-plugin-gsettings:amd64=0.4.15-10ubuntu1.1 libproxy1-plugin-networkmanager:amd64=0.4.15-10ubuntu1.1 libproxy1v5:amd64=0.4.15-10ubuntu1.1 libproxy1v5:i386=0.4.15-10ubuntu1.1 python-apt-common=2.0.0ubuntu0.20.04.2 libproxy-tools=0.4.15-10ubuntu1.1 python3-apt=2.0.0ubuntu0.20.04.2 p11-kit-modules:amd64=0.23.20-1build1 libp11-kit0:amd64=0.23.20-1build1 libp11-kit0:i386=0.23.20-1build1 firefox-locale-en=84.0+build3-0ubuntu0.20.04.1 libopenexr-dev=2.3.0-6ubuntu0.2 libopenexr24:amd64=2.3.0-6ubuntu0.2 linux-generic-hwe-20.04=5.4.0.58.61 linux-image-generic-hwe-20.04=5.4.0.58.61 linux-headers-generic-hwe-20.04=5.4.0.58.61 linux-headers-generic=5.4.0.58.61 firefox=84.0+build3-0ubuntu0.20.04.1 linux-libc-dev:amd64=5.4.0-58.64 p11-kit=0.23.20-1build1 libwavpack1:i386=5.2.0-1 libwavpack1:amd64=5.2.0-1 linux-generic-hwe-20.04=5.4.0.59.62 linux-image-generic-hwe-20.04=5.4.0.59.62 linux-headers-generic-hwe-20.04=5.4.0.59.62 libatopology2:amd64=1.2.2-2.1ubuntu2.2 libasound2:i386=1.2.2-2.1ubuntu2.2 libasound2:amd64=1.2.2-2.1ubuntu2.2 libasound2-dev:amd64=1.2.2-2.1ubuntu2.2 libasound2-data=1.2.2-2.1ubuntu2.2 libdrm-common=2.4.101-2 libdrm2:amd64=2.4.101-2 libdrm2:i386=2.4.101-2 xserver-common=2:1.20.8-2ubuntu2.6 xserver-xorg-legacy=2:1.20.8-2ubuntu2.6 libegl-dev:amd64=1.3.1-1ubuntu0.20.04.1 libegl1:amd64=1.3.1-1ubuntu0.20.04.1 libopengl-dev:amd64=1.3.1-1ubuntu0.20.04.1 libopengl0:amd64=1.3.1-1ubuntu0.20.04.1 libglx-dev:amd64=1.3.1-1ubuntu0.20.04.1 libgl-dev:amd64=1.3.1-1ubuntu0.20.04.1 libgl1:amd64=1.3.1-1ubuntu0.20.04.1 li...

Read more...

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Is linux-modules-extra installed?

Revision history for this message
Hassan Williamson (hazrpg) wrote :

Hi @kaihengfeng thank you very much for commenting, much appreciated.

Yes, linux-modules-extra is installed:

$ uname -r
5.8.0-36-generic

$ sudo apt install linux-modules-extra-5.8.0-36-generic
[sudo] password for hazrpg:
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-modules-extra-5.8.0-36-generic is already the newest version (5.8.0-36.40~20.04.1).
linux-modules-extra-5.8.0-36-generic set to manually installed.
The following packages were automatically installed and are no longer required:
  libllvm10 libllvm10:i386 libomxil-bellagio-bin libomxil-bellagio0 libwayland-server0:i386 linux-headers-5.4.0-62 linux-headers-5.4.0-62-generic
Use 'sudo apt autoremove' to remove them.
0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.

I've also tried installing it for all the others:

$ sudo apt install linux-modules-extra-5.8.0-40-generic linux-modules-extra-5.8.0-38-generic linux-modules-extra-5.8.0-36-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-modules-extra-5.8.0-36-generic is already the newest version (5.8.0-36.40~20.04.1).
linux-modules-extra-5.8.0-38-generic is already the newest version (5.8.0-38.43~20.04.1).
linux-modules-extra-5.8.0-38-generic set to manually installed.
linux-modules-extra-5.8.0-40-generic is already the newest version (5.8.0-40.45~20.04.1).
linux-modules-extra-5.8.0-40-generic set to manually installed.

affects: alsa-driver (Ubuntu) → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1912773

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Hassan Williamson (hazrpg) wrote :

Fixed it! However I'm not sure why the file was created when I'm running on AMD hardware and requiring the use of the APU.

The bug is that a blacklist file was created in:

/etc/modprobe.d/blacklist-amdgpu.conf

With the following line:

blacklist amdgpu

That obviously prevented the APU drivers to load up, so the HDMI audio sink could be initialised and prevented GPU rendering.

This problem could likely affect multiple people and are unaware if they are on a single display and using speakers connected to the motherboard instead of via other means such as the 3.5mm output, optical, or even via Bluetooth. Since the system worked otherwise. The only symptom people on single displays and not using HDMI audio people would experience is when doing anything CPU or GPU intensive, since I can only presume the CPU is doing all the legwork to render the display instead of the APU.

For reference the CPU is a AMD Ryzen 5 3400g with Vega 11 APU, and no dedicated graphics card.

If anyone needs any additional information, logs, or anything let me know and I'll be happy to help out where I can. I'm just glad that I got this resolved, but I'd hate for others to experience the same issues while updates trickle down (it could also be months before anyone notices on single display and no HDMI audio setups).

Changed in linux (Ubuntu):
status: Incomplete → Invalid
no longer affects: amd
Revision history for this message
Hassan Williamson (hazrpg) wrote :

This issue still exists, when trying to figure out why bug #1962308 was happening, this exact same problem still happens on 5.8.0-63 (originally reported on 5.8.0-40).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.