ASUS PG279QM 27" 240 hz monitor only showing up to 143.91hz in KDE Plasma Wayland

Help
, ,
1

I have been working on this issue for a bit, if i type xrandr, i get the following output -

DP-1 connected primary 2560x1440+1920+0 (normal left inverted right x axis y axis) 596mm x 335mm
2560x1440 143.91*+
1920x1440 143.90
1600x1200 143.89
1440x1080 143.80
1400x1050 143.89
1280x1024 143.79
1280x960 143.86
1152x864 143.92
1024x768 143.87
800x600 143.83
640x480 143.85
320x240 142.05
1920x1200 143.89
1680x1050 143.88
1440x900 143.86
1280x800 143.84
1152x720 143.77
960x600 143.72
928x580 143.50
800x500 143.68
768x480 143.69
720x480 143.85
640x400 143.37
320x200 141.40
2048x1152 143.88
1920x1080 143.88
1600x900 143.93
1368x768 143.77
1280x720 143.67
1024x576 143.91
864x486 143.63
720x400 143.88
640x350 143.57

i’ve tried creating custom modes to allow me to get 240hz, but it only ever seems to want to go to 140hz. I do get 240hz in hyprland and X11, so i know the hardware and cables are perfectly capable, but some configuration is off in my machine. I’ve also tried setting using kscreendoctor and that didn’t work either. Any help would be greatly appreciated.

according to xorg, it does detect 240 from my monitor, and i’m using the new NVIDIA 560 driver, but it was doing this on the previous 550 driver as well. NVIDIA card is a Geforce RTX 4070

here is my edid file -

Block 2, DisplayID Extension Block:
Version: 1.3
Extension Count: 0
Display Product Type: Standalone display device
Display Interface Data Block:
Interface Type: DisplayPort
Number of Links: 4
Interface Standard Version: 1.4
Supported bpc for RGB encoding: 8, 10, 12
Supported bpc for YCbCr 4:4:4 encoding: 8, 10, 12
Supported bpc for YCbCr 4:2:2 encoding: 8, 10, 12
Supported Content Protection: HDCP 2.0
Spread Spectrum: Down Spread 0.5%
Color Characteristics Data Block:
Uses spatial color
Uses 1931 CIE (x, y) coordinates
Primary #0: (0.6873, 0.3054)
Primary #1: (0.1914, 0.7251)
Primary #2: (0.1470, 0.0615)
White point #0: (0.3127, 0.3291)
Video Timing Modes Type 1 - Detailed Timings Data Block:
DTD: 2560x1440 199.992119 Hz 16:9 317.188 kHz 862.750000 MHz (aspect 16:9, no 3D stereo)
Hfront 48 Hsync 32 Hback 80 Hpol P
Vfront 138 Vsync 5 Vback 3 Vpol N
DTD: 2560x1440 239.969753 Hz 16:9 388.511 kHz 1056.750000 MHz (aspect 16:9, no 3D stereo)
Hfront 48 Hsync 32 Hback 80 Hpol P
Vfront 171 Vsync 5 Vback 3 Vpol N
Checksum: 0x7f
Checksum: 0x90

also kscreen output shows the following -

{
“id”: “f135870a2532e90c9a62e23e65b42e72”,
“metadata”: {
“fullname”: “xrandr-ASUSTek COMPUTER INC-ROG PG279QM-#GTIYMxgwAA1O”,
“name”: “DP-0”
},
“mode”: {
“refresh”: 239.96975708007812,
“size”: {
“height”: 1440,
“width”: 2560
}
},
“overscan”: 0,
“rgbrange”: 0,
“rotation”: 1,
“scale”: 1,
“vrrpolicy”: 2
}

which i’m not sure why it’s called DP-0 here but everywhere else including xrandr it’s called DP-1

2

Could get the output of kscreen-doctor -o
and drm_info.

This will allow to find out where the issue originates from.

What is your distro and versions (beside Nvidia driver) ?

3

kscreen-doctor -o outputs - Output: 1 HDMI-A-1
enabled
connected
priority 2
HDMI
Modes: 0:1920x1080@60*! 1:1920x1080@60 2:1920x1080@50 3:1680x1050@60 4:1400x1050@60 5:1600x900@60 6:1280x1024@75 7:1280x1024@60 8:1440x900@60 9:1280x800@60 10:1152x864@75 11:1280x720@60 12:1280x720@60 13:1280x720@50 14:1024x768@75 15:1024x768@60 16:800x600@75 17:800x600@60 18:720x576@50 19:720x480@60 20:640x480@75 21:640x480@60 22:640x480@60
Geometry: 0,0 1920x1080
Scale: 1
Rotation: 1
Overscan: 0
Vrr: incapable
RgbRange: unknown
HDR: incapable
Wide Color Gamut: incapable
ICC profile: none
Color profile source: sRGB
Output: 2 DP-1
enabled
connected
priority 1
DisplayPort
Modes: 0:2560x1440@60! 1:2560x1440@240 2:2560x1440@200 3:2560x1440@144* 4:2560x1440@120 5:2560x1440@100 6:1024x768@60 7:800x600@60 8:640x480@60
Geometry: 1920,0 2560x1440
Scale: 1
Rotation: 1
Overscan: 0
Vrr: Automatic
RgbRange: unknown
HDR: enabled
SDR brightness: 200 nits
SDR gamut wideness: 20%
Peak brightness: 446 nits
Max average brightness: 351 nits
Min brightness: 0.099 nits Brightness factor: 100%
Wide Color Gamut: enabled
ICC profile: none
Color profile source: sRGB

distro is arch linux but using cachyos repositories

uname -r kernel is 6.11.0-rc3-2-cachyos-rc-lto

4

Since you tried kscreen-doctor previously you might have tried already:
kscreen-doctor output.DP-1.mode.2560x1440@240

What is the output of the command ?

Is the frequency visible then in systemsettings screen settings ?

5

it gives me this output - kscreen.doctor: setop exec returned KScreen::Config(
KScreen::Output(1, “HDMI-A-1”, connected enabled priority 2, pos: QPoint(0,0), res: QSize(1920, 1080), modeId: “0”, scale: 1, clone: no, rotation: KScreen::Output::None, followPreferredMode: false)
KScreen::Output(2, “DP-1”, connected enabled priority 1, pos: QPoint(1920,0), res: QSize(2560, 1440), modeId: “1”, scale: 1, clone: no, rotation: KScreen::Output::None, followPreferredMode: false) )

the 240 hz has always been visible in system settings, but if i set it to 240 and leave and come back, it sets it back to 144. It’s always getting stuck on 144 and not sure why. almost like something is setting it to that

6

If you set KWIN_DRM_PREFER_COLOR_DEPTH=24 in /etc/environment and reboot, do you get 240Hz then?

7

Unfortunately if i go to system settings and set it to 240 after setting the KWIN_DRM_PREFER_COLOR_DEPTH=24, and come back, it sets it back to 144 again.

and if i do kscreen-doctor -o it sets it back to 144 again

8

I did previously have a 180 hz monitor that i replaced with the 240, not sure if that’s causing an issue or not

9

Anything else I can try?

10

I am not sure you did exactly what @Zamundaaa suggested.
The KWIN_DRM_PREFER_COLOR_DEPTH=24 needs to be set for KWin, that is the entire session, you can put it in ~/.bash_profile (if you use bash) or /etc/environment.
Then reboot or restart KWin (kwin_wayland --replace, it will kill your non-Qt application) and test again.

11

Ok so here is what I did, I had the variable in /etc/environment, and i screenshotted to show that the variable does hold the value 24. This did not resolve my issue. I still can’t set my monitor to 240 hz

image
image1920Ă—993 104 KB

12

Okay, then we need to figure out why the driver rejects the configuration. https://invent.kde.org/plasma/kwin/-/wikis/Debugging-DRM-issues shows how to get the log for that. Just start dmesg before you change the setting, then try to do it, and then stop dmesg again.

1 Like
13

I have the same issue also on a asus desktop monitor