video corruption with amd RX560 and 2k display

Bug #1740484 reported by Antonio Díaz Rebaque on 2017-12-29
This bug affects 2 people
Affects Status Importance Assigned to Milestone
mutter (Fedora)
mutter (Ubuntu)

Bug Description

When using wayland, I get a lot of video corruption on my 2k display. It usually shows up as bands of the background image or gnome-shell status bar flickering across the display at different vertical positions. There is a Fedora bug with a similar problem and video:

WORKAROUND: Select 'Gnome under X.Org' from the login screen instead of wayland.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 29 11:06:18 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus: bcmwl,, 4.13.0-21-generic, x86_64: installed
ExtraDebuggingInterest: No
 Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller])
   Subsystem: Sapphire Technology Limited Baffin [Radeon RX 560] [1da2:e348]
MachineType: System manufacturer System Product Name
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed root=UUID=2452d0da-14e9-4f88-9660-5a86aee79ff4 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install) 12/04/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3401
dmi.board.asset.tag: Default string PRIME B350M-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3401:bd12/04/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: To be filled by O.E.M. System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

Luke McKee (hojuruku-s) wrote :
Download full text (6.6 KiB)

This may be EFI bios related / amdgpu.ko kernel driver dpm powerplay related.

The dmesg.txt attached seems to confirm this in this ticket.

The problem is not software, it's overheating / hardware related. It's affecting AMI EFI bios code + AMD GPU SBIOS powerplay voltage tables.

See this thread.

Here is an email I just sent to msi support about this saga, as they are trying to replicate this defect as it's no good when fans either don't spin up on some cards, or stay locked at 1000rpm out of 3000rpm. No good = the card crashing corruption etc software issues. This user needs to monitor his fan speed / temperature when using the GPU. I have emails about how to that as well if he wants.

I'm using Linux out of the box to reproduce the error. Latest version I think 18.02 or 17.xx from memory.

╠ @@ Package: sys-kernel/linux-sabayon-4.14.12-r1 branch: 5, [sabayon-weekly]
╠ Available: version: 4.14.12-r1 ~ tag: NoTag ~ revision: 0
╠ Installed: version: 4.14.12-r1 ~ tag: NoTag ~ revision: 0
╠ Slot: 4.14
╠ Homepage:
╠ Description: Official Sabayon Linux Standard
╠ kernel image

But i'm moving to pure custom compiled everything. Right now whilst i'm transitioning I"m using an out of the box kernel.

All it matters is if upstream Linux is broken then many linux distributions by default are broken. And this admgpu driver not handling modified voltage tables is going to kill cards running linux.

Ubuntu's kernel may have a custom patch to fix this already, that's why you can't replicate it now. let me look at the sources / patches for ubuntu kernel now.

See the original post I put up, that's other people getting it.

Someone else on the internet with the bug in Ubuntu:

RX 580 Ubuntu Driver Problems
Wed, 05/31/2017 - 00:40 — Anonymous

I just got a pair of XFX RX 580 card and am having some trouble with the amdgpu-pro drivers.

On a fresh install of Ubuntu 16.04.2, after updating packages, updating the kernel to 4.8, installing the AMDGPU-PRO 17.10 drivers, and rebooting, I see these messages in the log

Maybe it's been patched in more recent ubuntu versions.

The goal is to work around the bug in firmware so people who run older linuxes / unpatched don't get hit. Anything to mitigate this overheating issue either at the linux kernel or firmware is a good move.

He used 16.04.2 without a kernel update from the CD.

But Ubuntu 16.04.2 has other problems....
znmeb commented on 2017-12-04 23:05

This software doesn't even work on Ubuntu 16.04.3 LTS, which AMD supposedly supports!! See

I couldn't even make it work on 16.04.2. I've pretty much given up on AMD.
But could be that.... Maybe they are putting the spin on the powerplay issue as something else. Remember AMDGPU-Pro isn...


description: updated
affects: xorg (Ubuntu) → wayland (Ubuntu)
Daniel van Vugt (vanvugt) wrote :

If the bug is specific to "Wayland" sessions then this is a bug in the 'eglnative' backend of package 'mutter' (used by gnome-shell).

Please help by reporting the problem directly to the mutter developers here:

And when done, please tell us the ID of your newly-created bug.

affects: wayland (Ubuntu) → mutter (Ubuntu)
Changed in mutter (Ubuntu):
status: New → Incomplete
Changed in mutter (Fedora):
importance: Unknown → Undecided
status: Unknown → Confirmed
Jan Vlug (jan-vlug) wrote :

I'm a bit in doubt where to provide updates for this bug, as it is also reported for:


For now I will post comments in Gnomes GitLab, as the issue seems not to be distribution specific.

But, is Gnomes GitLab the best place, as this seems to be a driver issue? If not please let me know where this issue should be reported.

Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

Changed in mutter (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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