Skip to content

Higher refresh rates not working on kernels >5.9

Brief summary of the problem:

Starting graphical env (GDM in my case) results in a screen that does turn on, but goes back in standby after 20s (default for my screen). Switching TTY is not possible, as if there is no video output.

Setting the screen at 120Hz also results in the same issue. Only 60Hz is possible, and does correctly load. This was not the case on linux58, this was working perfectly under wayland at 240hz. Changing DP-port on gpu does not do anything.

Hardware description:

  • CPU: AMD 3700X
  • GPU:MSI 5700XT
  • System Memory:32GB
  • Display(s): 1 - Samsung Odyssey G9 - 5120x1440 @240hz
  • Type of Diplay Connection: DP 1.4

System infomration:

  • Distro name and Version: Linux 5.10.2-2-MANJARO x86_64 20.2 Nibia
  • AMD package version: mesa 20.3.1-1

How to reproduce the issue:

Set display at 240Hz or 120Hz in On-screen-display. Start system.

Attached files:

edit 07-jan: I have tested this as well on an archiso202101. grub does show with 240hz, but as soon it leaves the bootloader, the monitor goes blank and in standby. Adaptive-sync/freesync also does not help. Neither on 120Hz.

edit 11-feb: I have tested on 5.10.15, something did change now. Instead of full on EDID errors, i'm now working in some default resolution (800x600 or something).

What catches my eye is:

feb 11 20:16:55 hostname gnome-shell[1696]: Boot VGA GPU /dev/dri/card0 selected as primary
feb 11 20:16:57 hostname gnome-shell[1696]: Failed to use stored monitor configuration: Invalid mode 5120x1440 (119,999702) for monitor 'SAM LC49G95T'
feb 11 20:16:57 hostname gnome-shell[1696]: Disabling DMA buffer screen sharing for driver 'amdgpu'.

I've set my screen now at 120Hz, as i still do have issues on 5.4 with 240Hz. This is in wayland.

journal -xeb ; https://pastebin.com/VanT55yz dmesg -ek ; https://pastebin.com/akJZjzK6

Edited by David