Advanced setup of Dual Monitors with different resolutions












0















I have a 4k and an FHD monitor and would like to set them up appropriately. By default the FHD monitor is kind of OK but everything on the 4k is too small.



I'm on Ubuntu 18.04, running an nVIDIA Titan V GPU with the 410.48 drivers. I also have no xorg.conf file in /etc/X11.



So, following some answers from across StackExchange and the Arch Wiki, I was using the following method to set up my screens up till today:




  1. Go to Activities -> Displays -> Set Scaling to 200%


  2. Run the following script every time I log in:



    #!/bin/bash
    xrandr --output DP-0 --primary --scale 1.4x1.4 --pos 3840x0
    xrandr --output HDMI-0 --scale 2x2 --pos 0x432


    (Using .xprofile didn't work for me, though that's slightly beside the point.)




DP-0 is my main (4k) monitor, HDMI-0 is my side (FHD) monitor.



This solution worked fine so far, but today xrandr --scale started resetting my Display Scaling to 100%. And what's worse, I cannot change it back to 200% until I reboot. I've also tried changing it back from the terminal but the command



gsettings set org.gnome.desktop.interface scaling-factor 2


again does nothing, and neither does changing that value through dconf.editor.



I rarely reboot my machine (since I need it to be accessible at all times) and I've unfortunately installed quite a bit of software since the last reboot but I don't think any of it had much to do with the X server. How do I find out what's suddenly causing my Display Scaling to reset when I run xrandr? Is there some log file I can look at for xrandr?





Additionally, I tried an alternative solution outlined in this answer, but I received an error:



xxx@yyy:~$ cvt 5376 3024 60
# 5376x3024 59.98 Hz (CVT 16.26M9) hsync: 187.80 kHz; pclk: 1409.25 MHz
Modeline "5376x3024_60.00" 1409.25 5376 5848 6440 7504 3024 3027 3032 3131 -hsync +vsync
xxx@yyy:~$ xrandr --newmode "5376x3024_60.00" 1409.25 5376 5848 6440 7504 3024 3027 3032 3131 -hsync +vsync
xxx@yyy:~$ xrandr --addmode DP-0 5376x3024_60.00
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: 43
Current serial number in output stream: 44


Any idea what's causing this BadMatch?










share|improve this question























  • Did you try setting visually with arandr? you can setup resolution and position easily.

    – bistoco
    Feb 6 at 18:01











  • Unfortunately, arandr doesn't seem to allow adding custom resolutions, so it doesn't really fix my problem.

    – Mate de Vita
    Feb 7 at 10:02


















0















I have a 4k and an FHD monitor and would like to set them up appropriately. By default the FHD monitor is kind of OK but everything on the 4k is too small.



I'm on Ubuntu 18.04, running an nVIDIA Titan V GPU with the 410.48 drivers. I also have no xorg.conf file in /etc/X11.



So, following some answers from across StackExchange and the Arch Wiki, I was using the following method to set up my screens up till today:




  1. Go to Activities -> Displays -> Set Scaling to 200%


  2. Run the following script every time I log in:



    #!/bin/bash
    xrandr --output DP-0 --primary --scale 1.4x1.4 --pos 3840x0
    xrandr --output HDMI-0 --scale 2x2 --pos 0x432


    (Using .xprofile didn't work for me, though that's slightly beside the point.)




DP-0 is my main (4k) monitor, HDMI-0 is my side (FHD) monitor.



This solution worked fine so far, but today xrandr --scale started resetting my Display Scaling to 100%. And what's worse, I cannot change it back to 200% until I reboot. I've also tried changing it back from the terminal but the command



gsettings set org.gnome.desktop.interface scaling-factor 2


again does nothing, and neither does changing that value through dconf.editor.



I rarely reboot my machine (since I need it to be accessible at all times) and I've unfortunately installed quite a bit of software since the last reboot but I don't think any of it had much to do with the X server. How do I find out what's suddenly causing my Display Scaling to reset when I run xrandr? Is there some log file I can look at for xrandr?





Additionally, I tried an alternative solution outlined in this answer, but I received an error:



xxx@yyy:~$ cvt 5376 3024 60
# 5376x3024 59.98 Hz (CVT 16.26M9) hsync: 187.80 kHz; pclk: 1409.25 MHz
Modeline "5376x3024_60.00" 1409.25 5376 5848 6440 7504 3024 3027 3032 3131 -hsync +vsync
xxx@yyy:~$ xrandr --newmode "5376x3024_60.00" 1409.25 5376 5848 6440 7504 3024 3027 3032 3131 -hsync +vsync
xxx@yyy:~$ xrandr --addmode DP-0 5376x3024_60.00
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: 43
Current serial number in output stream: 44


Any idea what's causing this BadMatch?










share|improve this question























  • Did you try setting visually with arandr? you can setup resolution and position easily.

    – bistoco
    Feb 6 at 18:01











  • Unfortunately, arandr doesn't seem to allow adding custom resolutions, so it doesn't really fix my problem.

    – Mate de Vita
    Feb 7 at 10:02
















0












0








0








I have a 4k and an FHD monitor and would like to set them up appropriately. By default the FHD monitor is kind of OK but everything on the 4k is too small.



I'm on Ubuntu 18.04, running an nVIDIA Titan V GPU with the 410.48 drivers. I also have no xorg.conf file in /etc/X11.



So, following some answers from across StackExchange and the Arch Wiki, I was using the following method to set up my screens up till today:




  1. Go to Activities -> Displays -> Set Scaling to 200%


  2. Run the following script every time I log in:



    #!/bin/bash
    xrandr --output DP-0 --primary --scale 1.4x1.4 --pos 3840x0
    xrandr --output HDMI-0 --scale 2x2 --pos 0x432


    (Using .xprofile didn't work for me, though that's slightly beside the point.)




DP-0 is my main (4k) monitor, HDMI-0 is my side (FHD) monitor.



This solution worked fine so far, but today xrandr --scale started resetting my Display Scaling to 100%. And what's worse, I cannot change it back to 200% until I reboot. I've also tried changing it back from the terminal but the command



gsettings set org.gnome.desktop.interface scaling-factor 2


again does nothing, and neither does changing that value through dconf.editor.



I rarely reboot my machine (since I need it to be accessible at all times) and I've unfortunately installed quite a bit of software since the last reboot but I don't think any of it had much to do with the X server. How do I find out what's suddenly causing my Display Scaling to reset when I run xrandr? Is there some log file I can look at for xrandr?





Additionally, I tried an alternative solution outlined in this answer, but I received an error:



xxx@yyy:~$ cvt 5376 3024 60
# 5376x3024 59.98 Hz (CVT 16.26M9) hsync: 187.80 kHz; pclk: 1409.25 MHz
Modeline "5376x3024_60.00" 1409.25 5376 5848 6440 7504 3024 3027 3032 3131 -hsync +vsync
xxx@yyy:~$ xrandr --newmode "5376x3024_60.00" 1409.25 5376 5848 6440 7504 3024 3027 3032 3131 -hsync +vsync
xxx@yyy:~$ xrandr --addmode DP-0 5376x3024_60.00
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: 43
Current serial number in output stream: 44


Any idea what's causing this BadMatch?










share|improve this question














I have a 4k and an FHD monitor and would like to set them up appropriately. By default the FHD monitor is kind of OK but everything on the 4k is too small.



I'm on Ubuntu 18.04, running an nVIDIA Titan V GPU with the 410.48 drivers. I also have no xorg.conf file in /etc/X11.



So, following some answers from across StackExchange and the Arch Wiki, I was using the following method to set up my screens up till today:




  1. Go to Activities -> Displays -> Set Scaling to 200%


  2. Run the following script every time I log in:



    #!/bin/bash
    xrandr --output DP-0 --primary --scale 1.4x1.4 --pos 3840x0
    xrandr --output HDMI-0 --scale 2x2 --pos 0x432


    (Using .xprofile didn't work for me, though that's slightly beside the point.)




DP-0 is my main (4k) monitor, HDMI-0 is my side (FHD) monitor.



This solution worked fine so far, but today xrandr --scale started resetting my Display Scaling to 100%. And what's worse, I cannot change it back to 200% until I reboot. I've also tried changing it back from the terminal but the command



gsettings set org.gnome.desktop.interface scaling-factor 2


again does nothing, and neither does changing that value through dconf.editor.



I rarely reboot my machine (since I need it to be accessible at all times) and I've unfortunately installed quite a bit of software since the last reboot but I don't think any of it had much to do with the X server. How do I find out what's suddenly causing my Display Scaling to reset when I run xrandr? Is there some log file I can look at for xrandr?





Additionally, I tried an alternative solution outlined in this answer, but I received an error:



xxx@yyy:~$ cvt 5376 3024 60
# 5376x3024 59.98 Hz (CVT 16.26M9) hsync: 187.80 kHz; pclk: 1409.25 MHz
Modeline "5376x3024_60.00" 1409.25 5376 5848 6440 7504 3024 3027 3032 3131 -hsync +vsync
xxx@yyy:~$ xrandr --newmode "5376x3024_60.00" 1409.25 5376 5848 6440 7504 3024 3027 3032 3131 -hsync +vsync
xxx@yyy:~$ xrandr --addmode DP-0 5376x3024_60.00
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: 43
Current serial number in output stream: 44


Any idea what's causing this BadMatch?







18.04 xorg multiple-monitors display-resolution xrandr






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 6 at 17:12









Mate de VitaMate de Vita

1




1













  • Did you try setting visually with arandr? you can setup resolution and position easily.

    – bistoco
    Feb 6 at 18:01











  • Unfortunately, arandr doesn't seem to allow adding custom resolutions, so it doesn't really fix my problem.

    – Mate de Vita
    Feb 7 at 10:02





















  • Did you try setting visually with arandr? you can setup resolution and position easily.

    – bistoco
    Feb 6 at 18:01











  • Unfortunately, arandr doesn't seem to allow adding custom resolutions, so it doesn't really fix my problem.

    – Mate de Vita
    Feb 7 at 10:02



















Did you try setting visually with arandr? you can setup resolution and position easily.

– bistoco
Feb 6 at 18:01





Did you try setting visually with arandr? you can setup resolution and position easily.

– bistoco
Feb 6 at 18:01













Unfortunately, arandr doesn't seem to allow adding custom resolutions, so it doesn't really fix my problem.

– Mate de Vita
Feb 7 at 10:02







Unfortunately, arandr doesn't seem to allow adding custom resolutions, so it doesn't really fix my problem.

– Mate de Vita
Feb 7 at 10:02












0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1116157%2fadvanced-setup-of-dual-monitors-with-different-resolutions%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1116157%2fadvanced-setup-of-dual-monitors-with-different-resolutions%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

 ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕