LinuxQuestions.org - [SOLVED] Can't get 144hz on my main Monitor with nvidia drivers

- Manjaro (https://www.linuxquestions.org/questions/manjaro-119/)

- - Can't get 144hz on my main Monitor with nvidia drivers (https://www.linuxquestions.org/questions/manjaro-119/cant-get-144hz-on-my-main-monitor-with-nvidia-drivers-4175694791/)

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

inxi -SGx:

Code:

$ inxi -SGx

System:    Host: xxxx Kernel: 5.10.32-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: KDE Plasma 5.21.4 

          Distro: Manjaro Linux base: Arch Linux 

Graphics:  Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] driver: nvidia v: 460.73.01 bus-ID: 20:00.0 

          Display: x11 server: X.Org 1.20.11 driver: loaded: nvidia resolution: 1: 2560x1440~60Hz 2: 1920x1080~60Hz 

          OpenGL: renderer: GeForce GTX 1060 6GB/PCIe/SSE2 v: 4.6.0 NVIDIA 460.73.01 direct render: Yes

Current xorg.conf:

Code:

# nvidia-settings: X configuration file generated by nvidia-settings

# nvidia-settings:  version 460.73.01



Section "ServerLayout"

    Identifier    "Layout0"

    Screen      0  "Screen0" 0 0

    InputDevice    "Keyboard0" "CoreKeyboard"

    InputDevice    "Mouse0" "CorePointer"

    Option        "Xinerama" "0"

EndSection



Section "Files"

EndSection



Section "InputDevice"

    # generated from default

    Identifier    "Mouse0"

    Driver        "mouse"

    Option        "Protocol" "auto"

    Option        "Device" "/dev/psaux"

    Option        "Emulate3Buttons" "no"

    Option        "ZAxisMapping" "4 5"

EndSection



Section "InputDevice"

    # generated from default

    Identifier    "Keyboard0"

    Driver        "kbd"

EndSection



Section "Monitor"

    # HorizSync source: edid, VertRefresh source: edid

    Identifier    "Monitor0"

    VendorName    "Unknown"

    ModelName      "Acer XF270HU"

    HorizSync      31.0 - 90.0

    VertRefresh    56.0 - 76.0

    Option        "DPMS"

EndSection



Section "Device"

    Identifier    "Device0"

    Driver        "nvidia"

    VendorName    "NVIDIA Corporation"

    BoardName      "GeForce GTX 1060 6GB"

EndSection



Section "Screen"

    Identifier    "Screen0"

    Device        "Device0"

    Monitor        "Monitor0"

    DefaultDepth    24

    Option        "Stereo" "0"

    Option        "nvidiaXineramaInfoOrder" "DFP-0"

    Option        "metamodes" "DVI-D-0: 2560x1440 +1920+0, DP-2: nvidia-auto-select +0+0"

    Option        "SLI" "Off"

    Option        "MultiGPU" "Off"

    Option        "BaseMosaic" "off"

    SubSection    "Display"

        Depth      24

    EndSubSection

EndSection

I also found this line in /var/log/Xorg.0.log:

Code:

[ 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:

Code:

[ 4302.028] (--) NVIDIA(GPU-0): Acer XF270HU (DFP-0): 330.0 MHz maximum pixel clock

I did some research already but I couldn't find anything that fixed my issue, maybe some of you know what's wrong... Thanks in advance!

Welcome to LQ, jlongcheck. What follows may sound

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.

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 (Post 6248493)

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

Quote:

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):

Code:

$ echo -n /sys/class/drm/card*-* | xargs -d ' ' -I {} -exec bash -c 'edid-decode {}/edid ; true'

xargs: warning: the -E option has no effect if -0 or -d is used.



EDID of '/sys/class/drm/card0-DP-1/edid' was empty.

edid-decode (hex):



00 ff ff ff ff ff ff 00 04 69 fd 22 de 82 01 00

25 19 01 03 68 30 1b 78 2a 2a c5 a4 56 4f 9e 28

0f 50 54 b7 ef 00 d1 c0 81 40 81 80 95 00 b3 00

71 4f 81 c0 81 00 02 3a 80 18 71 38 2d 40 58 2c

45 00 dc 0c 11 00 00 1e 00 00 00 ff 00 46 39 4c

4d 54 46 30 39 39 30 33 38 0a 00 00 00 fd 00 32

4b 18 53 11 00 0a 20 20 20 20 20 20 00 00 00 fc

00 41 53 55 53 20 56 53 32 32 38 0a 20 20 00 a5



----------------



Block 0, Base EDID:

  EDID Structure Version & Revision: 1.3

  Vendor & Product Identification:

    Manufacturer: ACI

    Model: 8957

    Serial Number: 99038

    Made in: week 37 of 2015

  Basic Display Parameters & Features:

    Analog display

    Input voltage level: 0.7/0.7 V

    Blank level equals black level

    Sync: Separate

    Maximum image size: 48 cm x 27 cm

    Gamma: 2.20

    DPMS levels: Off

    RGB color display

    First detailed timing is the preferred timing

  Color Characteristics:

    Red  : 0.6406, 0.3378

    Green: 0.3105, 0.6191

    Blue : 0.1591, 0.0585

    White: 0.3134, 0.3291

  Established Timings I & II:

    IBM    :  720x400    70.082 Hz  9:5    31.467 kHz  28.320 MHz

    DMT 0x04:  640x480    59.940 Hz  4:3    31.469 kHz  25.175 MHz

    Apple  :  640x480    66.667 Hz  4:3    35.000 kHz  30.240 MHz

    DMT 0x06:  640x480    75.000 Hz  4:3    37.500 kHz  31.500 MHz

    DMT 0x08:  800x600    56.250 Hz  4:3    35.156 kHz  36.000 MHz

    DMT 0x09:  800x600    60.317 Hz  4:3    37.879 kHz  40.000 MHz

    DMT 0x0a:  800x600    72.188 Hz  4:3    48.077 kHz  50.000 MHz

    DMT 0x0b:  800x600    75.000 Hz  4:3    46.875 kHz  49.500 MHz

    Apple  :  832x624    74.551 Hz  4:3    49.726 kHz  57.284 MHz

    DMT 0x10:  1024x768    60.004 Hz  4:3    48.363 kHz  65.000 MHz

    DMT 0x11:  1024x768    70.069 Hz  4:3    56.476 kHz  75.000 MHz

    DMT 0x12:  1024x768    75.029 Hz  4:3    60.023 kHz  78.750 MHz

    DMT 0x24:  1280x1024  75.025 Hz  5:4    79.976 kHz  135.000 MHz

  Standard Timings:

    DMT 0x52:  1920x1080  60.000 Hz  16:9    67.500 kHz  148.500 MHz

    DMT 0x20:  1280x960    60.000 Hz  4:3    60.000 kHz  108.000 MHz

    DMT 0x23:  1280x1024  60.020 Hz  5:4    63.981 kHz  108.000 MHz

    DMT 0x2f:  1440x900    59.887 Hz  16:10  55.935 kHz  106.500 MHz

    DMT 0x3a:  1680x1050  59.954 Hz  16:10  65.290 kHz  146.250 MHz

    DMT 0x15:  1152x864    75.000 Hz  4:3    67.500 kHz  108.000 MHz

    DMT 0x55:  1280x720    60.000 Hz  16:9    45.000 kHz  74.250 MHz

    DMT 0x1c:  1280x800    59.810 Hz  16:10  49.702 kHz  83.500 MHz

  Detailed Timing Descriptors:

    DTD 1:  1920x1080  60.000 Hz  16:9    67.500 kHz  148.500 MHz (476 mm x 268 mm)

                Hfront  88 Hsync  44 Hback 148 Hpol P

                Vfront    4 Vsync  5 Vback  36 Vpol P

    Display Product Serial Number: 'F9LMTF099038'

  Display Range Limits:

    Monitor ranges (GTF): 50-75 Hz V, 24-83 kHz H, max dotclock 170 MHz

    Display Product Name: 'ASUS VS228'

Checksum: 0xa5

EDID of '/sys/class/drm/card0-DP-3/edid' was empty.

edid-decode (hex):



00 ff ff ff ff ff ff 00 04 72 49 05 b3 23 81 90

08 1d 01 03 80 3c 22 78 2e 3c 90 ab 54 4c a0 24

0d 50 54 bf ef 80 71 4f 81 40 81 80 81 c0 81 00

95 00 b3 00 d1 c0 56 5e 00 a0 a0 a0 29 50 30 20

35 00 55 50 21 00 00 1a 00 00 00 fd 00 38 4c 1f

5a 19 00 0a 20 20 20 20 20 20 00 00 00 fc 00 58

46 32 37 30 48 55 0a 20 20 20 20 20 00 00 00 ff

00 54 37 38 45 45 30 30 34 38 35 32 31 0a 00 54



----------------



Block 0, Base EDID:

  EDID Structure Version & Revision: 1.3

  Vendor & Product Identification:

    Manufacturer: ACR

    Model: 1353

    Serial Number: 2424382387

    Made in: week 8 of 2019

  Basic Display Parameters & Features:

    Digital display

    Maximum image size: 60 cm x 34 cm

    Gamma: 2.20

    DPMS levels: Off

    RGB color display

    Default (sRGB) color space is primary color space

    First detailed timing is the preferred timing

  Color Characteristics:

    Red  : 0.6679, 0.3310

    Green: 0.2998, 0.6250

    Blue : 0.1425, 0.0517

    White: 0.3125, 0.3281

  Established Timings I & II:

    IBM    :  720x400    70.082 Hz  9:5    31.467 kHz  28.320 MHz

    DMT 0x04:  640x480    59.940 Hz  4:3    31.469 kHz  25.175 MHz

    Apple  :  640x480    66.667 Hz  4:3    35.000 kHz  30.240 MHz

    DMT 0x05:  640x480    72.809 Hz  4:3    37.861 kHz  31.500 MHz

    DMT 0x06:  640x480    75.000 Hz  4:3    37.500 kHz  31.500 MHz

    DMT 0x08:  800x600    56.250 Hz  4:3    35.156 kHz  36.000 MHz

    DMT 0x09:  800x600    60.317 Hz  4:3    37.879 kHz  40.000 MHz

    DMT 0x0a:  800x600    72.188 Hz  4:3    48.077 kHz  50.000 MHz

    DMT 0x0b:  800x600    75.000 Hz  4:3    46.875 kHz  49.500 MHz

    Apple  :  832x624    74.551 Hz  4:3    49.726 kHz  57.284 MHz

    DMT 0x10:  1024x768    60.004 Hz  4:3    48.363 kHz  65.000 MHz

    DMT 0x11:  1024x768    70.069 Hz  4:3    56.476 kHz  75.000 MHz

    DMT 0x12:  1024x768    75.029 Hz  4:3    60.023 kHz  78.750 MHz

    DMT 0x24:  1280x1024  75.025 Hz  5:4    79.976 kHz  135.000 MHz

    Apple  :  1152x870    75.062 Hz 192:145  68.681 kHz  100.000 MHz

  Standard Timings:

    DMT 0x15:  1152x864    75.000 Hz  4:3    67.500 kHz  108.000 MHz

    DMT 0x20:  1280x960    60.000 Hz  4:3    60.000 kHz  108.000 MHz

    DMT 0x23:  1280x1024  60.020 Hz  5:4    63.981 kHz  108.000 MHz

    DMT 0x55:  1280x720    60.000 Hz  16:9    45.000 kHz  74.250 MHz

    DMT 0x1c:  1280x800    59.810 Hz  16:10  49.702 kHz  83.500 MHz

    DMT 0x2f:  1440x900    59.887 Hz  16:10  55.935 kHz  106.500 MHz

    DMT 0x3a:  1680x1050  59.954 Hz  16:10  65.290 kHz  146.250 MHz

    DMT 0x52:  1920x1080  60.000 Hz  16:9    67.500 kHz  148.500 MHz

  Detailed Timing Descriptors:

    DTD 1:  2560x1440  59.951 Hz  16:9    88.787 kHz  241.500 MHz (597 mm x 336 mm)

                Hfront  48 Hsync  32 Hback  80 Hpol P

                Vfront    3 Vsync  5 Vback  33 Vpol N

  Display Range Limits:

    Monitor ranges (GTF): 56-76 Hz V, 31-90 kHz H, max dotclock 250 MHz

    Display Product Name: 'XF270HU'

    Display Product Serial Number: 'T78EE0048521'

Checksum: 0x54

EDID of '/sys/class/drm/card0-HDMI-A-1/edid' was empty.

I've also tried various different modelines, overriding/ignoring the EDID, all leading to the same error.

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.

I have no first hand help to offer; here's another search for you: https://duckduckgo.com/?q=linux+cann...h+NVIDIA+GP106

If you want to solve this, concentrate on that and not on discussing off topic remarks.

Hi, the problem has been solved, please see my solution here: https://forum.manjaro.org/t/cant-get...1?u=jlongcheck

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").

I explained the details I used to solve it here:

https://www.linuxquestions.org/quest...nv-4175695291/

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.