[amdgpu] monitor refresh rates higher than 120 Hz not detected/cannot be set

[Jason T Brockdorf]

using this monitor: https://www.pixiogaming.com/px329
and this video card: https://www.gigabyte.com/us/Graphics-Card/GV-RX580GAMING-4GD-rev-10-11

I am unable to set any refresh rates higher than 120 Hz. The video card and the monitor both support 144 Hz and 165 Hz yet those refresh rates are not available as options to choose in the settings app. I've tried a couple of online guides using xrandr to add and set a custom display resolution/refresh rate but I can't get it to go any higher than 120 Hz. I have the exact same hardware running macOS Mojave 10.14.4 and it allows me to set the refresh rate to 144 Hz and 165 Hz.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-25-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun 29 18:13:05 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Ellesmere [Radeon RX 470/480/570/580] [1458:22fd]
InstallationDate: Installed on 2019-06-28 (1 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=8d1eef58-5823-4ca0-abb0-d2c79b140e40 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/29/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0805
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z390-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd01/29/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: ASUS_MB_CNL
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

[Jason T Brockdorf (apocalysque)]

Sorry, I realize I left out some detail. I can get 144 Hz if I change the resolution to 1920x1080 but that's not the native resolution for the monitor. I'm trying to get 144 Hz / 165 Hz using the monitor's native resolution, 2560x1440.

[Jason T Brockdorf (apocalysque)]

Attached edid output. Notice "Mode 1" is apparently the modeline that specifies 144 Hz native resolution, but I don't see this mode in xorg log.

[Daniel van Vugt (vanvugt)]

Yes, it seems to be an issue either with the amdgpu graphics driver, or with the monitor's own detection data that the supported modes are limited to

[ 3.773] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0
[ 3.773] (II) AMDGPU(0): Modeline "2560x1440"x60.0 241.70 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync (88.9 kHz eP)
[ 3.773] (II) AMDGPU(0): Modeline "2560x1440"x120.0 497.75 2560 2608 2640 2720 1440 1443 1448 1525 +hsync -vsync (183.0 kHz e)
[ 3.773] (II) AMDGPU(0): Modeline "2560x1440"x50.0 201.42 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync (74.1 kHz e)
[ 3.773] (II) AMDGPU(0): Modeline "1920x1200"x59.9 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync (74.6 kHz e)
[ 3.773] (II) AMDGPU(0): Modeline "1920x1080"x144.0 325.04 1920 1944 1976 2056 1080 1084 1089 1098 +hsync -vsync (158.1 kHz e)

and lower...

[Daniel van Vugt (vanvugt)]

I also wonder if Xorg itself is trying to apply sanity checking and ignoring the top mode thinking it can't be true:

 Modeline "Mode 1" 580.08 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync

[Jason T Brockdorf (apocalysque)]

I've tried with a different monitor that also supports 144 Hz and seem to be limited at 120 Hz on this monitor as well. I've attached the xorg log from a boot with that monitor attached instead.

[Jason T Brockdorf (apocalysque)]

I've attached the edid-decode from the asus monitor. parse-edid couldn't properly read the edid from this monitor.

[Jason T Brockdorf (apocalysque)]

Removed the radeon video card and tried using onboard intel graphics. Works fine for pixio monitor but not for asus. I suspect it probably doesn't work for the asus because of bad edid? So it would seem to me that the problem is somewhere in amdgpu? Is there anything else I can do to help resolve?

[Daniel van Vugt (vanvugt)]

Thanks. Testing that second monitor really confirms this is a bug in the amdgpu driver (or Xorg).

[Daniel van Vugt (vanvugt)]

I am not very familiar with amdgpu. It appears much newer versions of the driver are available in Ubuntu 19.04 and later, or just directly from AMD. But I can not find any documentation suggesting issues like this were fixed. Though they might be...

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.