How to make monitor's refresh rate 144Hz at startup?

I got this nice 144Hz monitor. For some reason everything just wants to default to 60Hz on boot. This is what my 20-Nvidia.conf looks like:

Section “Device” Identifier “Device0”
Driver “nvidia”
VendorName “NVIDIA Corporation”
BoardName “GeForce GTX 770”
Option “Coolbits” “12”
Option “RegistryDwords” “OGL_MaxFramesAllowed=0x0; EnableBrightnessControl=1”
Option “ModeValidation” “AllowNon60HzDFPModes”
Option “ModeDebug” “True”
Option “FlatPanelProperties” “Scaling=Native”
Option “UseEvents” “True”
EndSection

Section “Screen”
Identifier “Screen0”
Device “Device0”
Monitor “Monitor0”
DefaultDepth 24
Option “Stereo” “0”
Option “nvidiaXineramaInfoOrder” “DFP-4”
Option “metamodes” “1920x1080_144 +0+0”
Option “SLI” “Off”
Option “MultiGPU” “Off”
Option “BaseMosaic” “off”
Option “DynamicTwinView” “false”
SubSection “Display”
Depth 24
Modes “1920x1080_144”
EndSubSection
EndSection

And this is my 50-monitor.conf:

Section “Monitor” # HorizSync source: edid, VertRefresh source: edid
Identifier “Monitor0”
VendorName “Unknown”
ModelName “Idek Iiyama PLG2488H”
HorizSync 30.0 - 160.0
VertRefresh 55.0 - 145.0
Modeline “1920x1080_144.00” 452.50 1920 2088 2296 2672 1080 1083 1088 1177 -hsync +vsync
Option “PreferredMode” “1920x1080_144.00”
Option “DPMS”
UseModes “Modes[0]”
EndSection

Section “Modes”
Identifier “Modes[0]”
Modeline “1920x1080_144.00” 452.50 1920 2088 2296 2672 1080 1083 1088 1177 -hsync +vsync
EndSection

Some parts may seem like dublicates, and that’s because I’ve tried all the tricks in the book.

One option would be to run shell command “xrandr --output DP-1 --mode 1920x1080 --rate 144” at startup, but no matter how much I google, I can’t find a way to do this. (I’m using Gnome btw). The closest thing to success was that it would run this command everytime I open terminal.

1920x1080@144Hz is above 160kHz hsync, /var/log/Xorg.0.log should state that the resolution is above the allowed parameters.

Such thing doesn’t exist with Systemd, but here’s my “journalctl -e /usr/bin/Xorg” output:

joulu 24 12:22:30 linux-f9d1 gdm-Xorg-:0[851]: () evdev: Eee PC WMI hotkeys: Device: "/dev/input/event13"joulu 24 12:22:30 linux-f9d1 gdm-Xorg-:0[851]: (–) evdev: Eee PC WMI hotkeys: Vendor 0 Product 0
joulu 24 12:22:30 linux-f9d1 gdm-Xorg-:0[851]: (–) evdev: Eee PC WMI hotkeys: Found keys
joulu 24 12:22:30 linux-f9d1 gdm-Xorg-:0[851]: (II) evdev: Eee PC WMI hotkeys: Configuring as keyboard
joulu 24 12:22:30 linux-f9d1 gdm-Xorg-:0[851]: (
) Option “config_info” “udev:/sys/devices/platform/eeepc-wmi/input/input16/event13”
joulu 24 12:22:30 linux-f9d1 gdm-Xorg-:0[851]: (II) XINPUT: Adding extended input device “Eee PC WMI hotkeys” (type: KEYBOARD, id 11)
joulu 24 12:22:30 linux-f9d1 gdm-Xorg-:0[851]: () Option “xkb_rules” “evdev”
joulu 24 12:22:30 linux-f9d1 gdm-Xorg-:0[851]: (
) Option “xkb_model” “pc104”
joulu 24 12:22:30 linux-f9d1 gdm-Xorg-:0[851]: () Option “xkb_layout” “us,fi”
joulu 24 12:22:30 linux-f9d1 gdm-Xorg-:0[851]: (
) Option “xkb_variant” “,”
joulu 24 12:22:30 linux-f9d1 gdm-Xorg-:0[851]: (II) config/udev: Adding input device PC Speaker (/dev/input/event4)
joulu 24 12:22:30 linux-f9d1 gdm-Xorg-:0[851]: (II) No input driver specified, ignoring this device.
joulu 24 12:22:30 linux-f9d1 gdm-Xorg-:0[851]: (II) This device may have been added with another device file.
joulu 24 12:22:31 linux-f9d1 gdm-Xorg-:0[851]: (II) NVIDIA(0): Setting mode “DP-1: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}”
joulu 24 12:22:38 linux-f9d1 gdm-Xorg-:0[851]: The XKEYBOARD keymap compiler (xkbcomp) reports:
joulu 24 12:22:38 linux-f9d1 gdm-Xorg-:0[851]: > Warning: Type “ONE_LEVEL” has 1 levels, but <RALT> has 2 symbols
joulu 24 12:22:38 linux-f9d1 gdm-Xorg-:0[851]: > Ignoring extra symbols
joulu 24 12:22:38 linux-f9d1 gdm-Xorg-:0[851]: Errors from xkbcomp are not fatal to the X server
joulu 24 12:22:39 linux-f9d1 gdm-Xorg-:0[851]: The XKEYBOARD keymap compiler (xkbcomp) reports:
joulu 24 12:22:39 linux-f9d1 gdm-Xorg-:0[851]: > Warning: Type “ONE_LEVEL” has 1 levels, but <RALT> has 2 symbols
joulu 24 12:22:39 linux-f9d1 gdm-Xorg-:0[851]: > Ignoring extra symbols
joulu 24 12:22:39 linux-f9d1 gdm-Xorg-:0[851]: Errors from xkbcomp are not fatal to the X server
joulu 24 12:22:57 linux-f9d1 gdm-Xorg-:0[851]: (II) NVIDIA(0): Setting mode “DPY-5:1920x1080_144+0+0”

Last entry is where I put 144Hz mode manually through nvidia-settings.

Well your monitors maximum horizontal sync is not able to do 1920x1080x144Hz because it’s 169.35kHz hsync according to a quick calculation.

You should try 120Hz as a starting point.

Such thing doesn’t exist with Systemd,

ls -l /var/log/ | grep Xorg
-rw-r--r-- 1 root    root               54672 24. Dez 11:25 Xorg.0.log
-rw-r--r-- 1 root    root               25726 22. Dez 21:21 Xorg.0.log.old

It is there.

Are you telling me that my 144Hz monitor - which states “144Hz” with bold letters on it - isn’t able to do 144Hz? And when I put it to 144Hz mode through nvidia-settings, it works just fine.

I get nothing. Well mine is a very fresh OpenSUSE 13.2 install.

I’m saying your xorg.conf says the upper limit is 160kHz if what you posted is right and 1920x1080x144Hz is 169kHz.

cvt 1920 1080 144# 1920x1080 143.88 Hz (CVT) hsync: 169.35 kHz; pclk: 452.50 MHz
Modeline "1920x1080_144.00"  452.50  1920 2088 2296 2672  1080 1083 1088 1177 -hsync +vsync

Unless you are gaming, the whole 144Hz thing is pretty much pointless anyway - you could just go for 120Hz and that’s that. Perhaps nVidia settings sets a different modeline for it, I can’t really say because I don’t have a 144Hz display to test this on.

That’s totally unrelated to systemd. That’s a GNOME thing.

gdm redirects all X logs (also ~/.xsession-errors) to the journal.

If you’d use a different display manager, you would have an Xorg.0.log even with current systemd… :wink:

Iiyama ProLite gb2488hsu is the name of my monitor. It’s for competitive gaming and I didn’t come across any review saying, that it couldn’t 1920x1080x144Hz. That would be really absurd, since 144Hz is really the point of this monitor. Although I must say, that I’m not familiar with any of this hsync stuff.

Well, I do play CS:GO competitively. :stuck_out_tongue: (Yes, on Linux!)

Does GNOME have their own display settings too? To be honest, I haven’t looked at it in ages - perhaps it forces the Hz somewhere else as well.

No no, I believe that it can do 144Hz but the HorizSync setting in your xorg.conf says it cannot do it - perhaps it’s below what the capabilities of the monitor are and is set incorrectly or then the 144Hz mode is below the 169kHz normal modeline that I get out of all my calculators.

Do you have the tech specs somewhere where they list maximum hsync and vsync values?

On 2014-12-24 13:06, Blodoffer wrote:
>
> Miuku;2684971 Wrote:
>> I’m saying your xorg.conf says the upper limit is 160kHz if what you
>> posted is right and 1920x1080x144Hz is 169kHz.
>
> Iiyama ProLite gb2488hsu is the name of my monitor. It’s for competitive
> gaming and I didn’t come across any review saying, that it couldn’t
> 1920x1080x144Hz. That would be really absurd, since 144Hz is really the
> point of this monitor. Although I must say, that I’m not familiar with
> any of this hsync stuff.

Notice that Miuku is talking about this other limit - not of the real
limit, but the limit written into your config file that you posted:

HorizSync 30.0 - 160.0 <===
VertRefresh 55.0 - 145.0


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

From manufacturers site:
Horizontal sync DVI/DP: 30 - 160 KHz
Vertical sync DVI/DP: 55 - 144 Hz
Synchronization Separate Sync

Gnome does have their own monitor settings, but you can only change resolution from there.

I wish “~/.config/monitors.xml” would even exist, so I could edit that.

And when I put it to 144Hz mode through nvidia-settings, it works just fine.

If I understand you correctly, you can get the desired display mode manually using nvidia-settings, is the right? If so, then it should be possible to set the display mode via a startup script using

nvidia-settings --load-config-only

which will locad a config file from ~/.nvidia-settings-rc

Described here

Adding the script to startup in Gnome DE:
https://tr.opensuse.org/SDB:Applications_autostart_in_GNOME

This manual seems a little outdated. When I go to gnome-tweak-tool I can find an option to set startup apps, but only apps, not scripts or anything. I’ve tried putting a file called “rr.sh” (marked as executable) to …/.config/autostart. It’s supposed to run a shell command

"xrandr --output DP-1 --mode 1920x1080 --rate 144"

but I can’t make it work. Any help here?

The ~/.config/autostart/ directory only works with .desktop files as defiined by the freedesktop.org standard

http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s05.html

A minimal .desktop file to run your script might look like

[Desktop Entry]
Type=Application
Name=Display mode configuration
Exec=/path/to/rr.sh

The second thing to consider is that the xrandr display mode must be detected/supported for it to work.

So, for example, assuming the following generated modeline is supported (can be trial and error process to find a working modeline in itself)

cvt 1920 1080 144# 1920x1080 143.88 Hz (CVT) hsync: 169.35 kHz; pclk: 452.50 MHz
Modeline "1920x1080_144.00"  452.50  1920 2088 2296 2672  1080 1083 1088 1177 -hsync +vsync

Then, you would do

xrandr --newmode "1920x1080_144.00"  452.50  1920 2088 2296 2672  1080 1083 1088 1177 -hsync +vsync
xrandr --addmode DP-1 "1920x1080_144.00"

and set it with

xrandr --output DP-1 --mode "1920x1080_144.00"

Hope that helps a little.