I have found that a custom reslolution at 75 or 80hz is great for gaming, its a good balance between a frame rate you can maintain, while being significantly more smooth compared to 60hz. This is ideal for games that have questionable gsync or freesync
My problem is that: the xrandr goes to the distorted vga screen when I run xrandr and not the main screen at my laptop. Therefore, I cannot see and change the resolution of the vga output.
when i put xrandr --newmode "1920x1080_76.00" 224.00 1920 2064 2264 2608 1080 1083 1088 1131 -hsync +vsync i get X Error of failed request: BadName (named color or font does not exist) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 16 (RRCreateMode) Serial number of failed request: 43 Current serial number in output stream: 43 why is that? my monitor is 60hz and i want to overclock it to 76hz as i have done in windows.
So frustrating. I used to play CS2 with 4:3 1280x960 @ 165hz on Windows, but since switching to linux (lubuntu), I only have 60hz as an option in my monitor settings, and when I use xrandr to add my custom 1280x960 @ 165hz, it just gives me BadName (named color or font does not exist) and some other stuff. Really, REALLY annoying.
For some reason my new Asus monitor doesn't display 75hz as an option in Manjaro, but it does in Winblows. I was able to get 75hz working via this method. I just hope it holds on reboot. Thanks! 😀
Your comment just reminded me that a lot of 75 hz monitors will set the recommended mode as 60 hz for compatibility. When you run 'xrandr', is there a 75 hz option listed at all? In xrandr, you can see the optimal and current modes with the + and * icons beside the mode. If it's listed, you can change it much more easily with xrandr --output [name] --mode [resolution] --rate [refresh rate]! If not, and you need the manual method from the video to persist on reboot, you can always add it to the initialization of X11 through an xinit file to it applies on system startup.
@@TonyTascioglu Thanks for the reply. Unfortunately, 75Hz isn't listed when running xrandr, even though it's officially a 75Hz monitor (Windows is somehow able to detect it properly). xrandr gives me this '1920x1080 60.00*+ 50.00 59.94'. As I said, your method works beautifully, however, it doesn't persist. Not quite sure how to xinit this thing. You wouldn't happen to have a follow video showing how to make these changes persist, would you? 😁
@@TonyTascioglu I created a bash script with the following and it works perfectly when I run it. I also created a crontab with @reboot sleep 20 && absolutePath/fix-rate.sh >/dev/null 2>&1 but it doesn't work: xrandr --newmode '1920x1080_75.00' 220.75 1920 2064 2264 2608 1080 1083 1088 1130 -hsync +vsync && xrandr --addmode HDMI-A-0 '1920x1080_75.00' && xrandr --addmode HDMI-A-0 '1920x1080_75.00' && xrandr --output HDMI-A-0 --mode '1920x1080_75.00'
After rebooting the system erases the changes. Ubuntu 20.0x Is there a fix or another app to do that? It only works here while the computer is turned on, and then doesn't save.
I just made all the commands. I have the mode when i make xrandr, but i need to activate it also, So i made xrandr --output XWAYLAND52 --mode "3440x1440_60.00", but it seems that nothing happened :/ I have capped the second monitor to 49hz, using extension mode..
This assumes your display can handle the resolution and scale it. There are 2 ways to do scaling: Scale internally, have your GPU resample and send to the display at it's native resolution. That is similar to --scale in xrandr, and changes the input/output scaling. The way in this video is to change the MODE you send your display. So if you go to a resolution or refresh rate not supported by your tv/display/projector, you'll hit a black screen. Note that some displays also might use special timings or require more tweaking than the CVT modeline.
after 4 years of trying out linux every now and again, and having to switch back to windows (I have on my other SSD), cuz something is allways broken and I get tired of it, I decided to try it again, only to find my second monitor to be stuck at 24hz, been looking for a solution for hours, there is no one with this problem apparently, people just saying " must be the cable or smth", but at last!!!! something that works!!!!! but, just one question, this is permanent, right?
When I apply the custom resolution to my screen uxing `xrandr --output` (Overclocked from 60 to 75Hz), 3/4 of my screen just goes on crazy. I know my screen can handle 75Hz, I have tested it on a Windows machine and it works just fine. Any ideas where this issue might come from ? Thanks!
I can definitely see the 15Hz difference, I wouldn't go through the hassle of overclocking if it wasn't the case (': Btw, the issue is fixed, for some reason I can get to 75Hz using a custom EDID but only up to 73Hz without bugging with xrandr.
Interesting - it's likely the sub timings. When you run cvt, the line it gives you has timings beyond resolution and vsync, and one of those is probably not what the display is expecting. How you can further optimize that without trial and error - I'm not too sure. Dumping the EDID modes might give some more parameters.
Has someone a idea why my screen becomes black after selecting the new resolution. I'm currently using Ubuntu 22 and I have a the default ATI amd drivers. I used to be on windows and there it worked in VirtualBox, but now it doesn't work anymore. The Problem is I have a 3:2 2k monitor and everything is so tiny. Ps: my selected screen is called eDP and my display manager is Xorg or X11 I can't find a difference between them
eDP screens are typically built-in screens on laptops, and usually only support their native resolution. Forcing a manual resolution/refresh rate as I show in this video only work if the display knows how to deal with and use those timings. In this case, your laptop screen likely doesn't not support the timings you're trying to send. Since VirtualBox is 'emulating' the hardware, whether your timings worked there just depends on how their virtual display was programmed (likely supporting a wider range of configurations as opposed to a real display). As for the Xorg vs X11, "X" is the protocol. Xorg is the open source group/project that implements the X protocol (x11 being the 11th version).
Hm. I haven't run into this. Have you tried the advice with changing a grub parameter as mentioned in: askubuntu.com/questions/441040/failed-to-get-size-of-gamma-for-output-default-when-trying-to-add-new-screen-res or a kernel parameter like with stackoverflow.com/questions/47391669/xrandr-displaying-failed-to-get-size-of-gamma-for-output-default (do backup your grub.cfg before changing these!!!)
I just get "X Error of failed request: BadMatch (invalid parameter attributes)" when I try to add 3840x2160_60.00 Looks like getting a new DP cable worked. Weird because on Windows the existing cable supported 4k 60hz. But I think Gnome sends 4:4:4 chroma subsmpling vs Windows only sending 4:2:0, so it can handle the bandwidth from Windows but not Linux
It likely could have been a limitation then - 4:4:4 is basically double the bandwidth of 4:2:0. Though I always thought that was more of an issue on HDMI as DisplayPort typically has had higher bandwidth in a given generation. xrandr is a little hard to debug (bonus points for CRTC errors) so it can be hard to tell.
I have found that a custom reslolution at 75 or 80hz is great for gaming, its a good balance between a frame rate you can maintain, while being significantly more smooth compared to 60hz. This is ideal for games that have questionable gsync or freesync
My problem is that: the xrandr goes to the distorted vga screen when I run xrandr and not the main screen at my laptop. Therefore, I cannot see and change the resolution of the vga output.
thanks, i used this to play the new CS2 at a different resolution and refresh rate
The lengths CS players will go to in order to play in 4:3 ;) Just kidding obviously, glad I could help.
That information helped me to set up higher refresh rate on my monitor. From 60 to 75 Ghz. Thanks a lot!
Glad it helped!
holy crap, you managed to overclock your monitor to 75,000,000,000Hz? wow that's one hell of a smooth monitor
@@reyynerp we both know that it was a mistake but it was needed haha
thanks tony you seem nerdy smart
when i put xrandr --newmode "1920x1080_76.00" 224.00 1920 2064 2264 2608 1080 1083 1088 1131 -hsync +vsync i get
X Error of failed request: BadName (named color or font does not exist)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 16 (RRCreateMode)
Serial number of failed request: 43
Current serial number in output stream: 43
why is that?
my monitor is 60hz and i want to overclock it to 76hz as i have done in windows.
So frustrating. I used to play CS2 with 4:3 1280x960 @ 165hz on Windows, but since switching to linux (lubuntu), I only have 60hz as an option in my monitor settings, and when I use xrandr to add my custom 1280x960 @ 165hz, it just gives me BadName (named color or font does not exist) and some other stuff. Really, REALLY annoying.
For some reason my new Asus monitor doesn't display 75hz as an option in Manjaro, but it does in Winblows. I was able to get 75hz working via this method. I just hope it holds on reboot. Thanks! 😀
Your comment just reminded me that a lot of 75 hz monitors will set the recommended mode as 60 hz for compatibility. When you run 'xrandr', is there a 75 hz option listed at all? In xrandr, you can see the optimal and current modes with the + and * icons beside the mode.
If it's listed, you can change it much more easily with xrandr --output [name] --mode [resolution] --rate [refresh rate]!
If not, and you need the manual method from the video to persist on reboot, you can always add it to the initialization of X11 through an xinit file to it applies on system startup.
@@TonyTascioglu Thanks for the reply. Unfortunately, 75Hz isn't listed when running xrandr, even though it's officially a 75Hz monitor (Windows is somehow able to detect it properly). xrandr gives me this '1920x1080 60.00*+ 50.00 59.94'.
As I said, your method works beautifully, however, it doesn't persist. Not quite sure how to xinit this thing. You wouldn't happen to have a follow video showing how to make these changes persist, would you? 😁
@@TonyTascioglu I created a bash script with the following and it works perfectly when I run it. I also created a crontab with @reboot sleep 20 && absolutePath/fix-rate.sh >/dev/null 2>&1 but it doesn't work:
xrandr --newmode '1920x1080_75.00' 220.75 1920 2064 2264 2608 1080 1083 1088 1130 -hsync +vsync && xrandr --addmode HDMI-A-0 '1920x1080_75.00' && xrandr --addmode HDMI-A-0 '1920x1080_75.00' && xrandr --output HDMI-A-0 --mode '1920x1080_75.00'
@@bassam.2023 ur the best!!!
After rebooting the system erases the changes. Ubuntu 20.0x
Is there a fix or another app to do that?
It only works here while the computer is turned on, and then doesn't save.
I just have it in my startup scripts to just switch it on power-on, but I'm sure there is a better way to set it as well.
how can i set my new resolution to my monitor?
Thanks!
I just made all the commands. I have the mode when i make xrandr, but i need to activate it also,
So i made xrandr --output XWAYLAND52 --mode "3440x1440_60.00", but it seems that nothing happened :/ I have capped the second monitor to 49hz, using extension mode..
so i did the hole thing with 800x600 and the screen just stays black
This assumes your display can handle the resolution and scale it.
There are 2 ways to do scaling: Scale internally, have your GPU resample and send to the display at it's native resolution. That is similar to --scale in xrandr, and changes the input/output scaling.
The way in this video is to change the MODE you send your display. So if you go to a resolution or refresh rate not supported by your tv/display/projector, you'll hit a black screen.
Note that some displays also might use special timings or require more tweaking than the CVT modeline.
after 4 years of trying out linux every now and again, and having to switch back to windows (I have on my other SSD), cuz something is allways broken and I get tired of it, I decided to try it again, only to find my second monitor to be stuck at 24hz, been looking for a solution for hours, there is no one with this problem apparently, people just saying " must be the cable or smth", but at last!!!! something that works!!!!! but, just one question, this is permanent, right?
how can i remove it now, i cant change on arandr
When I apply the custom resolution to my screen uxing `xrandr --output` (Overclocked from 60 to 75Hz), 3/4 of my screen just goes on crazy.
I know my screen can handle 75Hz, I have tested it on a Windows machine and it works just fine.
Any ideas where this issue might come from ?
Thanks!
I don't think 75hz is worth all the trouble to be honest.
I can definitely see the 15Hz difference, I wouldn't go through the hassle of overclocking if it wasn't the case (':
Btw, the issue is fixed, for some reason I can get to 75Hz using a custom EDID but only up to 73Hz without bugging with xrandr.
Interesting - it's likely the sub timings. When you run cvt, the line it gives you has timings beyond resolution and vsync, and one of those is probably not what the display is expecting.
How you can further optimize that without trial and error - I'm not too sure. Dumping the EDID modes might give some more parameters.
Has someone a idea why my screen becomes black after selecting the new resolution. I'm currently using Ubuntu 22 and I have a the default ATI amd drivers. I used to be on windows and there it worked in VirtualBox, but now it doesn't work anymore. The Problem is I have a 3:2 2k monitor and everything is so tiny.
Ps: my selected screen is called eDP
and my display manager is Xorg or X11 I can't find a difference between them
eDP screens are typically built-in screens on laptops, and usually only support their native resolution.
Forcing a manual resolution/refresh rate as I show in this video only work if the display knows how to deal with and use those timings. In this case, your laptop screen likely doesn't not support the timings you're trying to send. Since VirtualBox is 'emulating' the hardware, whether your timings worked there just depends on how their virtual display was programmed (likely supporting a wider range of configurations as opposed to a real display).
As for the Xorg vs X11, "X" is the protocol. Xorg is the open source group/project that implements the X protocol (x11 being the 11th version).
It says failed to get size of gamma for output device
Hm. I haven't run into this. Have you tried the advice with changing a grub parameter as mentioned in:
askubuntu.com/questions/441040/failed-to-get-size-of-gamma-for-output-default-when-trying-to-add-new-screen-res
or a kernel parameter like with stackoverflow.com/questions/47391669/xrandr-displaying-failed-to-get-size-of-gamma-for-output-default
(do backup your grub.cfg before changing these!!!)
is it possible to add a new res like 960x540
Yes, that is what this does, it creates a new mode and adds it to the modelist of supported resolution/clock rates.
Thanks x10000000000000
I just get "X Error of failed request: BadMatch (invalid parameter attributes)" when I try to add 3840x2160_60.00
Looks like getting a new DP cable worked. Weird because on Windows the existing cable supported 4k 60hz. But I think Gnome sends 4:4:4 chroma subsmpling vs Windows only sending 4:2:0, so it can handle the bandwidth from Windows but not Linux
It likely could have been a limitation then - 4:4:4 is basically double the bandwidth of 4:2:0. Though I always thought that was more of an issue on HDMI as DisplayPort typically has had higher bandwidth in a given generation. xrandr is a little hard to debug (bonus points for CRTC errors) so it can be hard to tell.