Mutter on Wayland detecting incorrect default refresh rate. Refresh rate set in Gnome not applying to GDM
I used Fedora 34 Beta with Gnome 40 to test the following issue. I tested in Wayland. I have also experienced this behavior with 3.38.
- My monitor is a HP Omen 27i (1440p, 165hz, gsync compatible freesync, nano ips)
- Video card is a AMD 6900XT
Mutter isn't detecting the correct refresh rate of my monitor. It's defaulting to 60hz, when it should be 165hz. I know my monitor default is 165hz because its 165hz in my motherboards bios, a Linux TTY console without any graphical interface, Windows 10 installer and inside Windows 10 without any GPU drivers, and Xorg detects 165hz by default.
Another problem is GDM does not obey the refresh rate set inside of Gnome. If I set 165hz in Gnomes display properties, GDM defaults to 60hz regardless. When logging in, Mutter resets back to 165hz.
Negative impact of running at 60hz is the awful lag. Monitor is designed for 165hz with its response time. The latency increase of 60hz is noticeable.
Steps to reproduce
- Boot into a fresh install of Gnome, incorrect refresh rate.
- Manually set correct refresh rate, GDM does not obey it.
Incorrect default refresh rate followed by GDM not obeying manually set refresh rate.
What did you expect to happen
Correct refresh rate detected followed by GDM obeying manually set refresh rate.
Relevant logs, screenshots, screencasts etc.
- xrandr output after fresh boot up of Gnome 40 on Fedora 34 showing 60hz: https://i.imgur.com/cugUkVX.png
- xrandr and Gnome display properties showing manually set 165hz: https://i.imgur.com/FrMaT90.png
- photo showing GDM after logging out and my monitors OSD showing 60hz: https://i.imgur.com/ZkgxYlJ.jpg
- photo after logging back into Gnome with my monitor showing 165hz after Mutter resetting back: https://i.imgur.com/fvQLhpf.jpg
- xrandr output on my main system (Xfce, Xorg, Arch Linux) showing correct detection values: https://i.imgur.com/DpmzHXk.png