Can't set Monitor to 160hz

DoomSlinger · 2023-04-01 06:11:02

Ok, So I just got a new monitor, specifically the Cooler Master Tempest gp27u. It is a 160hz monitor, but 160hz doesn't show up as a refresh rate option when trying to set it. The max shown is 144hz. I tested the monitor in windows, and 160hz does work there. This does not work in Xorg or Wayland.

GPU/CPU:
RTX 3070
Ryzen 7 5800x

Kernal: 6.2.8-arch1-1
Graphics drivers: nvidia 530.41.03-1
Desktop Version: plasma-desktop 5.27.3-1
Xorg version: 21.1.8-1
Wayland version: 1.21.0-2

I don't know how useful this information will be, but here is the results of xrandr, the decoded edid file for the monitor, and a copy of my xorg.conf

xrandr results:

https://pastebin.com/ePFy2iPN

edid-decode results:

https://pastebin.com/L0xCJ1a9

xorg.conf:

https://pastebin.com/YY8ca6Z4

if there is anything else you need to help me out, just let me know. I have no idea where else to look to be honest.

Last edited by DoomSlinger (2023-04-01 06:19:00)

seth · 2023-04-01 07:15:18

xorg.conf

Anything in there but

Section "Screen"
    Identifier     "Screen0"
    Option         "CustomEDID" "HDMI-1:/etc/X11/modified-edid.bin"
    Option         "nvidiaXineramaInfoOrder" "DFP-0"
    Option         "metamodes" "HDMI-0: nvidia-auto-select +5440+600, DP-0: nvidia-auto-select +1600+0, HDMI-1: 1600x1200_65 +0+480"
EndSection

is cruft.

Please post the xorg log - the mode is in the same block as the 144Hz one, so detectable. Maybe the driver says why it's filtered.
You could also try to https://wiki.archlinux.org/title/Xrandr … esolutions

DoomSlinger · 2023-04-01 07:33:18

Ok, I deleted and regenerated my xorg.conf while troubleshooting, i'll post the new one here:

https://pastebin.com/E115Z3gC

also, the option for customEDID I put manually for a different monitor, as I have a multi-monitor setup. I've tested without that setting, doesn't change anything

Here is the xorg.0.log file:

https://pastebin.com/PDhZJQE3

Edit: forgot to mention, I have gone through the xrandr page, any time I use the --addmode parameter, I get the following error:

$ cvt 3840 2160 160
# 3840x2160 159.98 Hz (CVT) hsync: 379.47 kHz; pclk: 2058.25 MHz
Modeline "3840x2160_160.00" 2058.25 3840 4200 4632 5424 2160 2163 2168 2372 -hsync +vsync
$ xrandr --newmode "3840x2160_160.00" 2058.25 3840 4200 4632 5424 2160 2163 2168 2372 -hsync +vsync
$ xrandr --addmode DP-0 3840x2160_160.00
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 18 (RRAddOutputMode)
Serial number of failed request: 47
Current serial number in output stream: 48

Last edited by DoomSlinger (2023-04-01 07:41:55)

seth · 2023-04-01 07:53:37

I meant "everything"

[   207.896] (==) ServerLayout "Layout0"
[   207.896] (**) |-->Screen "Screen0" (0)
[   207.896] (**) |   |-->Monitor "Monitor0"
[   207.896] (**) |   |-->Device "Device0"
[   207.896] (**) |-->Input Device "Keyboard0"
[   207.896] (**) |-->Input Device "Mouse0"

This is all garbage

[   207.896] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[   207.896] (WW) Disabling Keyboard0
[   207.896] (WW) Disabling Mouse0

plus the drivers don't exist since ages.
Don't use nvidia-settings to generate a static server layout; this is however unrelated to the topic at hand.

[   207.904] (--) NVIDIA(GPU-0): CMT GP27-FUS (DFP-0): 2670.0 MHz maximum pixel clock

You're not hitting any signal limits.

X Error of failed request: BadMatch (invalid parameter attributes)

Option "ModeValidation" "DFP-0:AllowNonEdidModes,AllowNonHDMI3DModes,NoEdidHDMI2Check,NoTotalSizeCheck,NoVertRefreshCheck,NoHorizSyncCheck,NoEdidMaxPClkCheck"

But the modeline you used is wrong anyway

Modeline "3840x2160_160.00" 1398.400  3840 3888 3920 4000  2160 2163 2168 2185  +HSync -VSync

("edid-decode -X" can also print them for you)

DoomSlinger · 2023-04-01 08:55:09

Ok, I tried the mode validation option with the modeline from using edid-decode, and it didn't fix the BadMatch error.

As for the log files, did I miss some log files that would help? The only xorg log file I know of is the Xorg.0.log file, and I posted all the contents of that in my previous post. So what specific files should I post that will help, as well as their usual file paths? I'm a complete noob when it comes to going through linux log files and the journalctl, so if there is a good spot on the wiki that breaks all that down really well, I'd love to see it.

seth · 2023-04-01 13:04:46

Is the mode validation option picked up according to the xorg log?

The xorg log is the most relevant here.
Add

Option "ModeDebug" "True"

to make it a bit more chatty.

DoomSlinger · 2023-04-01 17:33:10

Ok, I added ModeDebug to the xorg config:
(First Half): https://pastebin.com/9ceh4E3y
(Second Half): https://pastebin.com/YdJHhcA8

I also looked through it for a bit and found this:

[     7.278] (WW) NVIDIA(GPU-0):   Validating Mode "3840x2160_160":
[     7.278] (WW) NVIDIA(GPU-0):     Mode Source: EDID
[     7.278] (WW) NVIDIA(GPU-0):     3840 x 2160 @ 160 Hz
[     7.278] (WW) NVIDIA(GPU-0):       Pixel Clock      : 1398.40 MHz
[     7.278] (WW) NVIDIA(GPU-0):       HRes, HSyncStart : 3840, 3888
[     7.278] (WW) NVIDIA(GPU-0):       HSyncEnd, HTotal : 3920, 4000
[     7.278] (WW) NVIDIA(GPU-0):       VRes, VSyncStart : 2160, 2163
[     7.278] (WW) NVIDIA(GPU-0):       VSyncEnd, VTotal : 2168, 2185
[     7.278] (WW) NVIDIA(GPU-0):       Sync Polarity    : +H -V 
[     7.278] (WW) NVIDIA(GPU-0):     ViewPort 3840x2160 exceeds hardware capabilities.
[     7.278] (WW) NVIDIA(GPU-0):     Mode is rejected: GPU extended capability check failed.
[     7.278] (WW) NVIDIA(GPU-0):     GPU extended capability check failed.
[     7.278] (WW) NVIDIA(GPU-0):     Mode "3840x2160_160" is invalid.

Edit: I added "Option "ModeValidation" "NoExtendedGpuCapabilitiesCheck" to my xorg conf, and now it actually is showing 160hz as an option in nvidia-settings and in KDE display settings. However, when I try to apply it, it fails. I got this error doing it in Nvidia:

Failed to set MetaMode (1) 'DPY-0:3840x2160_160 +1600+0, DPY-2: nvidia-auto-select +5440+540, DPY-5: nvidia-auto-select +0+480' (Mode 7360x2160,id: -1) on X screen 0

This was at the end of the xorg log as well:

[    33.812] (WW) NVIDIA(0): Failed to validate MetaMode:
[    33.812] (WW) NVIDIA(0):  - Setting a mode on display 0 failed: The extended GPU
[    33.812] (WW) NVIDIA(0):     capabilities check failed
[    33.812] (WW) NVIDIA(0): 
[    33.812] (WW) NVIDIA(0): No valid modes for "DP-0: 3840x2160_144 @3840x2160 +1600+0
[    33.812] (WW) NVIDIA(0):     {ViewPortIn=3840x2160, ViewPortOut=3840x2160+0+0}, HDMI-0:
[    33.812] (WW) NVIDIA(0):     nvidia-auto-select @1920x1080 +5440+540
[    33.812] (WW) NVIDIA(0):     {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, HDMI-1:
[    33.812] (WW) NVIDIA(0):     nvidia-auto-select @1600x1200 +0+480
[    33.812] (WW) NVIDIA(0):     {ViewPortIn=1600x1200, ViewPortOut=1600x1200+0+0}";
[    33.812] (WW) NVIDIA(0):     removing.
[   241.370] (WW) NVIDIA(0): Failed to validate MetaMode:
[   241.370] (WW) NVIDIA(0):  - Setting a mode on display 0 failed: The extended GPU
[   241.370] (WW) NVIDIA(0):     capabilities check failed
[   241.370] (WW) NVIDIA(0): 
[   241.370] (WW) NVIDIA(0): No valid modes for
[   241.370] (WW) NVIDIA(0):     "DPY-0:3840x2160_160+1600+0,DPY-2:nvidia-auto-select+5440+540,DPY-5:nvidia-auto-select+0+480";
[   241.370] (WW) NVIDIA(0):     removing.
[   241.494] (WW) NVIDIA(0): Failed to validate MetaMode:
[   241.494] (WW) NVIDIA(0):  - Setting a mode on display 0 failed: The extended GPU
[   241.494] (WW) NVIDIA(0):     capabilities check failed
[   241.494] (WW) NVIDIA(0): 
[   241.494] (WW) NVIDIA(0): No valid modes for
[   241.494] (WW) NVIDIA(0):     "DPY-0:3840x2160_160+1600+0,DPY-2:nvidia-auto-select+5440+540,DPY-5:nvidia-auto-select+0+480";
[   241.494] (WW) NVIDIA(0):     removing.

Last edited by DoomSlinger (2023-04-01 18:12:01)

seth · 2023-04-01 18:42:35

Does the mode work if you remove the other outputs?

DoomSlinger · 2023-04-01 19:21:57

If by outputs, you mean my other monitors, doing that results in a black screen if I try to apply 160hz, though, in my monitors menu it does report that it is running at 160hz.

EDIT: Ok, found something out, I realised I had the NoExtendedGpuCapabilitiesCheck set with the DFP-0: setting, after changing that, I can apply the 160hz setting to without only having that monitor pluged in. However, every monitor goes black when I do that. Looking at the previous log shows this:

[    37.193] (II) NVIDIA(0): Setting mode "DP-0: 3840x2160_160 @3840x2160 +1600+0 {ViewPortIn=3840x2160, ViewPortOut=3840x2160+0+0}, HDMI-0: nvidia-auto-select @1920x1080 +5440+417 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, HDMI-1: nvidia-auto-select @1600x1200 +0+357 {ViewPortIn=1600x1200, ViewPortOut=1600x1200+0+0}"
[    44.305] (WW) NVIDIA: Wait for channel idle timed out.

So now linux is recognizing the other refresh rate, however it doesn't like it and seems to crash xorg when I apply it, or at least that's my guess.

Last edited by DoomSlinger (2023-04-01 22:31:10)

Arch Linux

#1 2023-04-01 06:11:02

Can't set Monitor to 160hz

#2 2023-04-01 07:15:18

Re: Can't set Monitor to 160hz

#3 2023-04-01 07:33:18

Re: Can't set Monitor to 160hz

#4 2023-04-01 07:53:37

Re: Can't set Monitor to 160hz

#5 2023-04-01 08:55:09

Re: Can't set Monitor to 160hz

#6 2023-04-01 13:04:46

Re: Can't set Monitor to 160hz

#7 2023-04-01 17:33:10

Re: Can't set Monitor to 160hz

#8 2023-04-01 18:42:35

Re: Can't set Monitor to 160hz

#9 2023-04-01 19:21:57

Re: Can't set Monitor to 160hz

Board footer