2160p at 144hz issue, using new AMD hardware

Develon5543 · 2020-09-17 10:50:43

Hiya guys. I'm wanting to reach 3840x2160p @ 144hz with my current setup, but no matter what I try, I just end up with a black screen or an error message.

Specs:
CPU: AMD Ryzen 9 3900XT
GPU: AMD Radeon RX 5700 XT
Monitor: Nixeus NX-EDG274K

Driver: mesa-git (20.3.0) or mesa (20.1.7)
Kernel: 5.8.9-arch2-1

I'm currently running cinnamon. When I try to change the refresh rate to 144hz using the system settings, I sometimes get this error.

GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gnome_2drr_2derror_2dquark.Code2: could not set the configuration for CRTC 79

When using xrandr, I get this error instead.

[develon@FoatOS ~]$ xrandr --output DisplayPort-0 --mode 3840x2160 --rate 144
xrandr: Configure crtc 0 failed

Here is my Xorg.0.log.

Last edited by Develon5543 (2020-09-17 10:51:10)

solskog · 2020-09-17 11:15:19

This old thread was dealing with a nvidia gpu, but it may give a hint.
https://bbs.archlinux.org/viewtopic.php?id=242149

Last edited by solskog (2020-09-17 11:16:53)

Develon5543 · 2020-09-17 11:29:54

Yeah, I did try to read through that post. I'm not sure I really understand a lot of the things they're saying in it though. I should mention that I did try adding a custom modeline temporarily, but it just caused my monitor to say "Unsupported" (It does support 2160p @ 144hz though. Something about the modeline must've confused it)

seth · 2020-09-17 14:52:50

Output of "xrandr -q" and what modeline exactly did you try to exactly add how?
The maximum pixelclock in the xorg log matches

# 3840x2160 @ 60.000 Hz Reduced Blank (CVT) field rate 59.997 Hz; hsync: 133.312 kHz; pclk: 533.25 MHz
Modeline "3840x2160_60.00_rb1"  533.25  3840 3888 3920 4000  2160 2163 2168 2222 +hsync -vsync

and DisplayPort 1.2, you need a 1.4 chain (or up) to get into the desired resolution/frequency.

I assume the monitor is good, so consult the manual of your GPU and in doubt: #1 it's always the cable ;-)

Develon5543 · 2020-09-17 18:28:27

Output of "xrandr -q"

Screen 0: minimum 320 x 200, current 3840 x 2160, maximum 16384 x 16384
DisplayPort-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 596mm x 335mm
   3840x2160     59.98*+ 144.00   120.00   100.00    90.00    80.00    60.00    50.00    59.94    30.00    25.00    24.00    29.97    23.98  
   4096x2160     30.00    25.00    24.00    29.97    23.98  
   1920x1200     59.98  
   1920x1080    119.96    99.92    60.00    60.00    50.00    59.94    30.00    25.00    24.00    29.97    23.98  
   1600x1200     59.98  
   1680x1050     59.98  
   1400x1050     59.98  
   1280x1024     75.02    60.02  
   1440x900      59.89  
   1280x960      60.00  
   1280x800      59.98  
   1152x864      75.00  
   1280x720      60.00    50.00    59.94  
   1024x768      75.03    70.07    60.00  
   832x624       74.55  
   800x600       72.19    75.00    60.32    56.25  
   640x480       75.00    72.81    66.67    60.00    59.94  
   720x400       70.08  
DisplayPort-1 disconnected (normal left inverted right x axis y axis)
HDMI-A-0 disconnected (normal left inverted right x axis y axis)
HDMI-A-1 disconnected (normal left inverted right x axis y axis)

What modeline I generated

[develon@FoatOS ~]$ cvt 3840 2160 144
# 3840x2160 143.94 Hz (CVT) hsync: 338.25 kHz; pclk: 1829.25 MHz
Modeline "3840x2160_144.00"  1829.25  3840 4200 4624 5408  2160 2163 2168 2350 -hsync +vsync

Here's how I added that modeline.

xrandr --newmode "3840x2160_144.00"  1829.25  3840 4200 4624 5408  2160 2163 2168 2350 -hsync +vsync
xrandr --addmode DisplayPort-0 3840x2160_144.00
xrandr --output DisplayPort-0 --mode 3840x2160_144.00

Setting the resolution/frequency this way causes my monitor to say "Not Supported" after the last command. I have to log into tty2 in order to go back to 60hz.

seth wrote:

...and DisplayPort 1.2, you need a 1.4 chain (or up) to get into the desired resolution/frequency.

Ah this is strange because my displayport cable claims that it's displayport 1.4. I'd assume the RX 5700 XT would support displayport 1.4 as well, along with my monitor. I'm not really sure where the problem lies, but it may be the cable like you stated earlier.

seth · 2020-09-17 19:19:55

Try

% cvt12 3840 2160 144 -b
# 3840x2160 @ 144.000 Hz Reduced Blank (CVT) field rate 144.000 Hz; hsync: 333.216 kHz; pclk: 1306.21 MHz
Modeline "3840x2160_144.00_rb2"  1306.21  3840 3848 3880 3920  2160 2300 2308 2314 +hsync -vsync

About the GPU: don't assume, check - the actual vendor/brand of the board might matter (I'm less concerned about the GPU itself and more about the output)

Develon5543 · 2020-09-17 20:25:53

Alright so I checked the box to be sure, and yes, it says it supports displayport 1.4. (It says this on the box exactly: Display Port 1.4 (HBR3) / DSC)
When adding that new mode, my monitor doesn't say "Not Supported" anymore, but it stays at 60hz and I get this error again.

xrandr: Configure crtc 0 failed

If it matters, here is a link to a new Xorg.0.log, after trying to add the reduced blanking modeline. (I also tested cvt12 without reduced blanking right before that because the output was different than cvt. So you have logs of both here.)

I also want to thank you for your time, as you've been really helpful.

Last edited by Develon5543 (2020-09-17 20:28:39)

seth · 2020-09-17 20:57:42

[     5.531] (II) AMDGPU(0): Ranges: V min: 48 V max: 144 Hz, H min: 134 H max: 134 kHz, PixClock max 1305 MHz

Apparently it means "1305"…

Does an interlaced signal work?

% cvt12 3840 2160 144 -i
# 3840x2160 @ 144.000 Hz Interlaced (CVT) field rate 143.900 Hz; hsync: 169.442 kHz; pclk: 905.50 MHz
Modeline "3840x2160_144.00i"  905.50  3840 4168 4592 5344  2160 2163 2168 2257 Interlace  -hsync +vsync

143.865Hz could get you below that clock as well…

% cvt12 3840 2160 143.865 -b
# 3840x2160 @ 143.865 Hz Reduced Blank (CVT) field rate 143.865 Hz; hsync: 332.904 kHz; pclk: 1304.98 MHz
Modeline "3840x2160_143.87_rb2"  1304.98  3840 3848 3880 3920  2160 2300 2308 2314 +hsync -vsync

Develon5543 · 2020-09-17 21:14:24

Ah so the other reduced blanking mode just resulted in the previous error, but the interlaced option actually set my monitor to 3840x1080 @ 150.5hz. The screen looks like it's being squished from the left and right sides.
Are these issues caused by the monitor or graphics card? Is there any way to tell? Maybe it's the cable I'm using, but honestly I have no idea. If you have a suspicion that it's the cable, I'll probably head to the store today and pick one up.

Last edited by Develon5543 (2020-09-17 21:15:10)

seth · 2020-09-17 21:28:31

The monitor likely misinterprets the interlaced signal (3840x1080 @ 150.5hz is not what you generate and 1080 is only half of 2160)
You could try whether passing "amdgpu.audio=0" to the kernel clears enough bandwidth to run the 3840x2160_144.00_rb2 modeline or otherwise smaller frequencies (w/ reduced blanking) - eg. 143Hz "only" requires 1296.58 MHz
https://wiki.archlinux.org/index.php/Kernel_parameters

Develon5543 · 2020-09-17 21:46:03

Here's what it looks like with amdgpu.audio set to 0. Also maybe off topic, but would freesync somehow mess with this stuff? It's turned on in the monitor and on my xorg configuration. I'm not sure if that would somehow limit the bandwidth or anything.

seth · 2020-09-17 21:50:27

Yes: https://wiki.archlinux.org/index.php/Va … nc_Monitor

Develon5543 · 2020-09-17 22:14:44

Okay so I disabled the xorg configuration and also turned off freesync in the monitor. However, it doesn't really help.
Logs for that
I don't really want to overclock the monitor as that sounds like a pretty bad idea, but even disabling freesync isn't helping. I suppose the last thing I could possibly try is showing you my monitor settings that I don't understand, and maybe one of them will get it to work.

"Over Drive" 63/127 (No visible effect)
"DDCCI" on (No visible effect)
"Ultra Vivid" off. off/low/medium/high (No visible effect, maybe has something to do with color.)
"DCR" off (Causes the backlight to automatically change)
"DP Option" -- (Allows setting Display Port versions per monitor plugin. Everything's set to 1.4 and changing the setting reverts it back to 1.4.)
"DSC" off. off/auto (Causes a black screen when changed. I'm not sure what it does as I had to change where the display cable was plugged in after that. Might be important though.)
"Free Sync" off (Freesync)

"HDR" auto. off/auto/force ST.2084 (Does nothing when set to off or auto. Using the force option opens up more hdr options, but the colors of the display look completely wrong with this mode active.

seth · 2020-09-18 07:09:36

that sounds like a pretty bad idea

Yes. The link was only meant to point out that VRR does tend to limit your maximum refresh rate.

The EDID provides you w/

Modeline "3840x2160"x144.0  1235.08  3840 3848 3880 3920  2160 2165 2173 2188 +hsync -vsync (315.1 kHz e)

which should be well inside the maximum clock.
Does this mode also (still) fail w/o VRR and audio?
What about the 120Hz mode?

Develon5543 · 2020-09-18 10:06:00

Alright, tried that modeline you suggested. Here's the log for that. This was taken with amdgpu.audio set to 0, and with freesync turned off. I also did try 120hz before, but that fails as well.

Arch Linux

#1 2020-09-17 10:50:43

2160p at 144hz issue, using new AMD hardware

#2 2020-09-17 11:15:19

Re: 2160p at 144hz issue, using new AMD hardware

#3 2020-09-17 11:29:54

Re: 2160p at 144hz issue, using new AMD hardware

#4 2020-09-17 14:52:50

Re: 2160p at 144hz issue, using new AMD hardware

#5 2020-09-17 18:28:27

Re: 2160p at 144hz issue, using new AMD hardware

#6 2020-09-17 19:19:55

Re: 2160p at 144hz issue, using new AMD hardware

#7 2020-09-17 20:25:53

Re: 2160p at 144hz issue, using new AMD hardware

#8 2020-09-17 20:57:42

Re: 2160p at 144hz issue, using new AMD hardware

#9 2020-09-17 21:14:24

Re: 2160p at 144hz issue, using new AMD hardware

#10 2020-09-17 21:28:31

Re: 2160p at 144hz issue, using new AMD hardware

#11 2020-09-17 21:46:03

Re: 2160p at 144hz issue, using new AMD hardware

#12 2020-09-17 21:50:27

Re: 2160p at 144hz issue, using new AMD hardware

#13 2020-09-17 22:14:44

Re: 2160p at 144hz issue, using new AMD hardware

#14 2020-09-18 07:09:36

Re: 2160p at 144hz issue, using new AMD hardware

#15 2020-09-18 10:06:00

Re: 2160p at 144hz issue, using new AMD hardware

Board footer