[SOLVED] Can't get 144hz on my main Monitor with nvidia drivers
ManjaroThis forum is for the discussion of Manjaro Linux. Note: This forum does not have any official participation.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Can't get 144hz on my main Monitor with nvidia drivers
Hi, I just installed Manjaro and I'm struggling to get my main monitor to work at 1440p 144hz. Here's my xrandr -q output:
Code:
$ xrandr -q
Screen 0: minimum 8 x 8, current 4480 x 1440, maximum 32767 x 32767
DVI-D-0 connected primary 2560x1440+1920+0 (normal left inverted right x axis y axis) 597mm x 336mm
2560x1440 59.95*+
1920x1080 60.00
1680x1050 59.95
1440x900 59.89
1280x1024 75.02 60.02
1280x960 60.00
1280x800 59.81
1280x720 60.00
1152x864 75.00
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32 56.25
640x480 75.00 72.81 59.94
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 476mm x 268mm
1920x1080 60.00*+
1680x1050 59.95
1440x900 59.89
1280x1024 75.02 60.02
1280x960 60.00
1280x800 59.81
1280x720 60.00
1152x864 75.00
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32 56.25
640x480 75.00 59.94
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)
DP-5 disconnected (normal left inverted right x axis y axis)
2560x1440_144.00_gtf (0x22d) 807.690MHz -HSync +VSync
h: width 2560 start 2784 end 3072 total 3584 skew 0 clock 225.36KHz
v: height 1440 start 1441 end 1444 total 1565 clock 144.00Hz
2560x1440_144.00_cvt (0x22e) 808.750MHz -HSync +VSync
h: width 2560 start 2792 end 3072 total 3584 skew 0 clock 225.66KHz
v: height 1440 start 1443 end 1448 total 1568 clock 143.91Hz
As you can see, I tried to create custom resolutions using gtf and cvt but adding either of them using xrandr results in this error:
Code:
$ xrandr --addmode DVI-D-0 "2560x1440_144.00_gtf"
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: 45
Current serial number in output stream: 46
[ 4396.038] (--) NVIDIA(GPU-0): Ancor Communications Inc ASUS VS228 (DFP-4): 1440.0 MHz maximum pixel clock
The monitor it mentions here is actually my 60hz 1080p monitor, I don't know if or how this could be relevant. The "corresponding" line for the 1440p144hz monitor looks like this:
Personally, I think even trying for 144hz is ridiculous, and I'm amazed that folks bother.
Here's the logic: Everyone is ok watching tv, which is 50Hz or 60Hz depending on where you watch it. Our eyes merge in minor differences, a fact proved by both the PAL & SECAM tv colour decoding systems. Nobody complained about the tv refresh, because most can't see it. Even double that (120Hz) and that's been done by some. My advice would be not to push your video card to those high refresh speeds, because they just overload the system. 4K is 4 times the work of ordinary hdmi. You have hit a processing or bandwidth limit.
Last edited by business_kid; 05-07-2021 at 01:12 PM.
Somebody on the 'net wrote they were able to se the refresh rate through nvidia's settings UI.
Elsewise, you need to research where and why this went wrong:
Quote:
Originally Posted by jlongcheck
Code:
$ xrandr --addmode DVI-D-0 "2560x1440_144.00_gtf"
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: 45
Current serial number in output stream: 46
Personally, I think even trying for 144hz is ridiculous, and I'm amazed that folks bother.
You've clearly never tried 144hz and I don't know how this is supposed to contribute to finding a solution.
Quote:
You have hit a processing or bandwidth limit.
No, I have not, everything is working fine on windows and linux with open source drivers.
Quote:
Elsewise, you need to research where and why this went wrong
I did my research and it seems to be an issue with the nvidia driver since nouveau drivers are working perfectly fine. However, I don't understand why the EDID doesn't even show 144hz being available and why nouveau permits to add new modes and nvidia doesn't (second EDID is the one of interest):
When I started with X, a lot of folks were running 640x480@60hz. The product was (640×480×60)18,432,000 Mb/S per colour. Now there was overscan for Analogue Monitors (+~10%), synch pulses for horizontal & vertical, and things were messy. So let's give it 20MB/Sper channel (x3) and we get a ballpark figure of 7.5MB/S.
You're attempting 3840×2080×144×3= 3,450,470,400Gb/S = 431,308,300Mhz/S (before corrections) which is an amazing amount of throughput to require from your system. Personally, I don't buy the
Quote:
Originally Posted by jlongcheck
You've clearly never tried 144hz
line much like I don't buy the line "If it costs more it has to be better" line. Research the frequency response of the eye to understand why. You clearly won't believe me https://www.healthline.com/health/hu...est-fps-vision
For the record,144 Hz = 6.9 milliseconds.
None of this takes into consideration that the GPU (whose frequency is usually much lower than CPU only updates portion of the picture each time, as there are bandwidth limits in GPU power. We're talking processed GPU output.
But you clearly want 144Hz, so don't listen to me if you don't want to. Knock yourself out.
Interesting. I had a similar problem trying to get 3840x2160 60Hz on my Sceptre 4K TV (the EDID would only report capability up to 30Hz). My solution was similar, but I created an xorg.conf with "X -configure" (and it had some issues because it put "nouveau" as the Driver instead of "nvidia").
That isn't solved that is a . That is how your distro packed it. at any time with a full install of your nvidia driver you just do as the Nvidia has built the driver to do. nvidia-xconfig . It readers your monitor and sets it up. if you have 2 it will do that also.
On some TV's used as monitors many can do 144hz but do not send that info out to the driver.
up to manufactures.
I have a 55 inch TV I use it runs at 60 hz. but can be clocked to 120 hz.
That would mean editing your xconfig.
Quote:
it had some issues because it put "nouveau" as the Driver instead of "nvidia").
I had to install Manjaro's latest the other day to make sure project runs on it.
No it didn't I found the system rather lacking.
That said it is good for surfing the internet out of the box.
I did finally install all the devel stuff build my own latest drivers.
Then figured out what it would take to get the stuff to run on Wayland and xorg.
Then immediately formatted that hard drive off to another distro.
Manjaro has a cool history i started out with mandrake in 1998.
The Arch factor and pacman is a huge turn off. And praying some packager wrote the install script right.
Quote:
The answer is the install script on pacman did not run nvidia-xconfig for your system.
My install (Debian) had neither xorg.conf nor 20-nvidia.conf, and the first advice for generating either that I got was "X -configure" to generate xorg.conf. So that's what I tried first and I got it to work.
I did NOT actually want to generate a conf file specifying the monitors that are currently attached to my computer. I mean, it's fine for as long as these specific monitors are attached to this computer, but I often switch things up, especially with a laptop that is sometimes attached to a second monitor and is sometimes free so I can use it in another room or out and about (in the before times).
All I wanted from xorg.conf was to specify a list of options so I could add (and use) a non-EDID modeline.
The bottom line is that xorg.conf definitely works with the nvidia driver. Maybe it's not the most elegant solution, but it is a solution which works fine.
IsaacKuo I did see that. Debian latest is using wayland out of the box as default.
Like you said I checked it as useful.
Installed built installed my project got it to run.
The main issue I have is the installs all lacked development. and or many of the libraries.so
have been renamed so not to interfere with making 3 packages out of one program.
I found Debian latest was easier to set up.
than.
The rpm guys and the pacman guys.
SUSE Tumble weed was much more prepared than the latest debian out of the box.
Why?
The latest debian still is working on the complete install script for all the dev stuff.
I think Manjaro is a fine distro. I would run the long term Arch repo.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
