Why isn't my monitor's native resolution not recognised under Linux?
I own a ViewSonic VA1931wa-LED monitor which has a native resolution of 1366x768 pixels with a refresh rate of 60Hz. The problem is that no matter what I do, it works just fine on Windows but on any Linux distribution it can't work properly. I have experimented both with the proprietary nvidia driver (my GPU is an nvidia GeForce 210) and with the nouveau driver and the resolutions I get which are closest to the native one are 1368x768 and 1360x768.
I have also tried typing gtf 1366 768 60 in the terminal and the output is the following:
# 1368x768 @ 60.00 Hz (GTF) hsync: 47.70 kHz; pclk: 85.86 MHz
Modeline "1368x768_60.00" 85.86 1368 1440 1584 1800 768 769 772 795 -HSync +Vsync
As you can clearly see even though I type in 1366 horizontal pixels I get 1368 as an output. So, is there a way to force my monitor to display its native resolution? If not then what else can be done?
linux drivers graphics-card resolution
add a comment |
I own a ViewSonic VA1931wa-LED monitor which has a native resolution of 1366x768 pixels with a refresh rate of 60Hz. The problem is that no matter what I do, it works just fine on Windows but on any Linux distribution it can't work properly. I have experimented both with the proprietary nvidia driver (my GPU is an nvidia GeForce 210) and with the nouveau driver and the resolutions I get which are closest to the native one are 1368x768 and 1360x768.
I have also tried typing gtf 1366 768 60 in the terminal and the output is the following:
# 1368x768 @ 60.00 Hz (GTF) hsync: 47.70 kHz; pclk: 85.86 MHz
Modeline "1368x768_60.00" 85.86 1368 1440 1584 1800 768 769 772 795 -HSync +Vsync
As you can clearly see even though I type in 1366 horizontal pixels I get 1368 as an output. So, is there a way to force my monitor to display its native resolution? If not then what else can be done?
linux drivers graphics-card resolution
See if this helps superuser.com/questions/1323967/… askubuntu.com/questions/377937/how-to-set-a-custom-resolutioncvt 1366 768 60
thenxrandr --newmode
thenxrandr --addmode
. This works in VirtualBox with non-standard resolutions, but with real monitors I think it depends on the video driver.
– Paulo
Nov 22 at 19:14
Possible duplicate of My computer doesn't recognize the monitor's resolution on some VGA cables, what's going on?
– phuclv
Nov 24 at 14:32
try a different cable VGA resolution with Sony Bravia TV, VGA cable causing resolution issue, Resolution 1920 x 1080 is not available for external monitor...
– phuclv
Nov 24 at 14:34
add a comment |
I own a ViewSonic VA1931wa-LED monitor which has a native resolution of 1366x768 pixels with a refresh rate of 60Hz. The problem is that no matter what I do, it works just fine on Windows but on any Linux distribution it can't work properly. I have experimented both with the proprietary nvidia driver (my GPU is an nvidia GeForce 210) and with the nouveau driver and the resolutions I get which are closest to the native one are 1368x768 and 1360x768.
I have also tried typing gtf 1366 768 60 in the terminal and the output is the following:
# 1368x768 @ 60.00 Hz (GTF) hsync: 47.70 kHz; pclk: 85.86 MHz
Modeline "1368x768_60.00" 85.86 1368 1440 1584 1800 768 769 772 795 -HSync +Vsync
As you can clearly see even though I type in 1366 horizontal pixels I get 1368 as an output. So, is there a way to force my monitor to display its native resolution? If not then what else can be done?
linux drivers graphics-card resolution
I own a ViewSonic VA1931wa-LED monitor which has a native resolution of 1366x768 pixels with a refresh rate of 60Hz. The problem is that no matter what I do, it works just fine on Windows but on any Linux distribution it can't work properly. I have experimented both with the proprietary nvidia driver (my GPU is an nvidia GeForce 210) and with the nouveau driver and the resolutions I get which are closest to the native one are 1368x768 and 1360x768.
I have also tried typing gtf 1366 768 60 in the terminal and the output is the following:
# 1368x768 @ 60.00 Hz (GTF) hsync: 47.70 kHz; pclk: 85.86 MHz
Modeline "1368x768_60.00" 85.86 1368 1440 1584 1800 768 769 772 795 -HSync +Vsync
As you can clearly see even though I type in 1366 horizontal pixels I get 1368 as an output. So, is there a way to force my monitor to display its native resolution? If not then what else can be done?
linux drivers graphics-card resolution
linux drivers graphics-card resolution
asked Nov 22 at 18:51
Evangelos
1
1
See if this helps superuser.com/questions/1323967/… askubuntu.com/questions/377937/how-to-set-a-custom-resolutioncvt 1366 768 60
thenxrandr --newmode
thenxrandr --addmode
. This works in VirtualBox with non-standard resolutions, but with real monitors I think it depends on the video driver.
– Paulo
Nov 22 at 19:14
Possible duplicate of My computer doesn't recognize the monitor's resolution on some VGA cables, what's going on?
– phuclv
Nov 24 at 14:32
try a different cable VGA resolution with Sony Bravia TV, VGA cable causing resolution issue, Resolution 1920 x 1080 is not available for external monitor...
– phuclv
Nov 24 at 14:34
add a comment |
See if this helps superuser.com/questions/1323967/… askubuntu.com/questions/377937/how-to-set-a-custom-resolutioncvt 1366 768 60
thenxrandr --newmode
thenxrandr --addmode
. This works in VirtualBox with non-standard resolutions, but with real monitors I think it depends on the video driver.
– Paulo
Nov 22 at 19:14
Possible duplicate of My computer doesn't recognize the monitor's resolution on some VGA cables, what's going on?
– phuclv
Nov 24 at 14:32
try a different cable VGA resolution with Sony Bravia TV, VGA cable causing resolution issue, Resolution 1920 x 1080 is not available for external monitor...
– phuclv
Nov 24 at 14:34
See if this helps superuser.com/questions/1323967/… askubuntu.com/questions/377937/how-to-set-a-custom-resolution
cvt 1366 768 60
then xrandr --newmode
then xrandr --addmode
. This works in VirtualBox with non-standard resolutions, but with real monitors I think it depends on the video driver.– Paulo
Nov 22 at 19:14
See if this helps superuser.com/questions/1323967/… askubuntu.com/questions/377937/how-to-set-a-custom-resolution
cvt 1366 768 60
then xrandr --newmode
then xrandr --addmode
. This works in VirtualBox with non-standard resolutions, but with real monitors I think it depends on the video driver.– Paulo
Nov 22 at 19:14
Possible duplicate of My computer doesn't recognize the monitor's resolution on some VGA cables, what's going on?
– phuclv
Nov 24 at 14:32
Possible duplicate of My computer doesn't recognize the monitor's resolution on some VGA cables, what's going on?
– phuclv
Nov 24 at 14:32
try a different cable VGA resolution with Sony Bravia TV, VGA cable causing resolution issue, Resolution 1920 x 1080 is not available for external monitor...
– phuclv
Nov 24 at 14:34
try a different cable VGA resolution with Sony Bravia TV, VGA cable causing resolution issue, Resolution 1920 x 1080 is not available for external monitor...
– phuclv
Nov 24 at 14:34
add a comment |
1 Answer
1
active
oldest
votes
Due to the way the legacy CRTC hardware works on Nvidia graphics cards, you can only set horizontal resolutions which are multiples of 8. 1360 and 1368 are multiples of 8, 1366 isn't.
You didn't say how your monitor is connected to your graphics card (VGA, DisplayPort, HDMI/DVI, ...). The details are a bit complicated, but again for legacy reasons, some of those connections include a horizontal and vertical phase where only blank pixels are sent. For your given modeline, you'd e.g. have 1368 framebuffer pixels out of 1584 horizontal pixels in total.
That means it doesn't really matter that the last two pixels of the 1368 range are not displayed, the card will send an additional 216 blank pixels that are also ignored by the monitor, anyway.
So in your case, I'd just choose to the 1368 horizontal resolution. It means your desktop will have two pixels at the right that are not visible (and I don't know any way to convince X that the actual framebuffer is smaller). Possibly you can configure your window manager to always ignore this area.
Edit
VGA uses analog transmission, so an LCD connected to VGA has a A/D converter to convert the pixel information back to digital. I'm not completely sured what you mean by "some vertical parts of the display are blurred", but if you mean vertical areas or stripes in equal distance, the reason is that the A/D conversion doesn't happen on the pixel boundary, and the reason for that is that the total horizontal width (1584 in your modeline) isn't what the monitor needs: This total width will stretch or shrink the pixels, so at regular times the sampling will happen at a boundary between pixels.
So you can play around with the total width (and/or the sync values, to shift the image) of your modeline.
Also, please have a look at your /var/log/Xorg.0.log
, it should contain the modelines the monitor suggests via EDID. Or read the EDID data using other tools. If you don't know how to interpret the log, please upload it in a pastebin etc., and edit your question with a link.
Another thing you can try is to look up which modeline Windows uses (though I'm not sure where to find this information under Windows).
The monitor is connected to the GPU through VGA, which is the only interface available on this monitor. The problem is that even though I can set my resolution to 1368x768 and the picture is just fine, some vertical parts of the display are blurred and can't be fixed even when adjusting the settings manually. But what's even more puzzling is that under Windows, both the GPU and the monitor's native resolution are instantly recognised and applied once the driver is installed and it works flawlessly.
– Evangelos
Nov 23 at 18:37
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1377658%2fwhy-isnt-my-monitors-native-resolution-not-recognised-under-linux%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Due to the way the legacy CRTC hardware works on Nvidia graphics cards, you can only set horizontal resolutions which are multiples of 8. 1360 and 1368 are multiples of 8, 1366 isn't.
You didn't say how your monitor is connected to your graphics card (VGA, DisplayPort, HDMI/DVI, ...). The details are a bit complicated, but again for legacy reasons, some of those connections include a horizontal and vertical phase where only blank pixels are sent. For your given modeline, you'd e.g. have 1368 framebuffer pixels out of 1584 horizontal pixels in total.
That means it doesn't really matter that the last two pixels of the 1368 range are not displayed, the card will send an additional 216 blank pixels that are also ignored by the monitor, anyway.
So in your case, I'd just choose to the 1368 horizontal resolution. It means your desktop will have two pixels at the right that are not visible (and I don't know any way to convince X that the actual framebuffer is smaller). Possibly you can configure your window manager to always ignore this area.
Edit
VGA uses analog transmission, so an LCD connected to VGA has a A/D converter to convert the pixel information back to digital. I'm not completely sured what you mean by "some vertical parts of the display are blurred", but if you mean vertical areas or stripes in equal distance, the reason is that the A/D conversion doesn't happen on the pixel boundary, and the reason for that is that the total horizontal width (1584 in your modeline) isn't what the monitor needs: This total width will stretch or shrink the pixels, so at regular times the sampling will happen at a boundary between pixels.
So you can play around with the total width (and/or the sync values, to shift the image) of your modeline.
Also, please have a look at your /var/log/Xorg.0.log
, it should contain the modelines the monitor suggests via EDID. Or read the EDID data using other tools. If you don't know how to interpret the log, please upload it in a pastebin etc., and edit your question with a link.
Another thing you can try is to look up which modeline Windows uses (though I'm not sure where to find this information under Windows).
The monitor is connected to the GPU through VGA, which is the only interface available on this monitor. The problem is that even though I can set my resolution to 1368x768 and the picture is just fine, some vertical parts of the display are blurred and can't be fixed even when adjusting the settings manually. But what's even more puzzling is that under Windows, both the GPU and the monitor's native resolution are instantly recognised and applied once the driver is installed and it works flawlessly.
– Evangelos
Nov 23 at 18:37
add a comment |
Due to the way the legacy CRTC hardware works on Nvidia graphics cards, you can only set horizontal resolutions which are multiples of 8. 1360 and 1368 are multiples of 8, 1366 isn't.
You didn't say how your monitor is connected to your graphics card (VGA, DisplayPort, HDMI/DVI, ...). The details are a bit complicated, but again for legacy reasons, some of those connections include a horizontal and vertical phase where only blank pixels are sent. For your given modeline, you'd e.g. have 1368 framebuffer pixels out of 1584 horizontal pixels in total.
That means it doesn't really matter that the last two pixels of the 1368 range are not displayed, the card will send an additional 216 blank pixels that are also ignored by the monitor, anyway.
So in your case, I'd just choose to the 1368 horizontal resolution. It means your desktop will have two pixels at the right that are not visible (and I don't know any way to convince X that the actual framebuffer is smaller). Possibly you can configure your window manager to always ignore this area.
Edit
VGA uses analog transmission, so an LCD connected to VGA has a A/D converter to convert the pixel information back to digital. I'm not completely sured what you mean by "some vertical parts of the display are blurred", but if you mean vertical areas or stripes in equal distance, the reason is that the A/D conversion doesn't happen on the pixel boundary, and the reason for that is that the total horizontal width (1584 in your modeline) isn't what the monitor needs: This total width will stretch or shrink the pixels, so at regular times the sampling will happen at a boundary between pixels.
So you can play around with the total width (and/or the sync values, to shift the image) of your modeline.
Also, please have a look at your /var/log/Xorg.0.log
, it should contain the modelines the monitor suggests via EDID. Or read the EDID data using other tools. If you don't know how to interpret the log, please upload it in a pastebin etc., and edit your question with a link.
Another thing you can try is to look up which modeline Windows uses (though I'm not sure where to find this information under Windows).
The monitor is connected to the GPU through VGA, which is the only interface available on this monitor. The problem is that even though I can set my resolution to 1368x768 and the picture is just fine, some vertical parts of the display are blurred and can't be fixed even when adjusting the settings manually. But what's even more puzzling is that under Windows, both the GPU and the monitor's native resolution are instantly recognised and applied once the driver is installed and it works flawlessly.
– Evangelos
Nov 23 at 18:37
add a comment |
Due to the way the legacy CRTC hardware works on Nvidia graphics cards, you can only set horizontal resolutions which are multiples of 8. 1360 and 1368 are multiples of 8, 1366 isn't.
You didn't say how your monitor is connected to your graphics card (VGA, DisplayPort, HDMI/DVI, ...). The details are a bit complicated, but again for legacy reasons, some of those connections include a horizontal and vertical phase where only blank pixels are sent. For your given modeline, you'd e.g. have 1368 framebuffer pixels out of 1584 horizontal pixels in total.
That means it doesn't really matter that the last two pixels of the 1368 range are not displayed, the card will send an additional 216 blank pixels that are also ignored by the monitor, anyway.
So in your case, I'd just choose to the 1368 horizontal resolution. It means your desktop will have two pixels at the right that are not visible (and I don't know any way to convince X that the actual framebuffer is smaller). Possibly you can configure your window manager to always ignore this area.
Edit
VGA uses analog transmission, so an LCD connected to VGA has a A/D converter to convert the pixel information back to digital. I'm not completely sured what you mean by "some vertical parts of the display are blurred", but if you mean vertical areas or stripes in equal distance, the reason is that the A/D conversion doesn't happen on the pixel boundary, and the reason for that is that the total horizontal width (1584 in your modeline) isn't what the monitor needs: This total width will stretch or shrink the pixels, so at regular times the sampling will happen at a boundary between pixels.
So you can play around with the total width (and/or the sync values, to shift the image) of your modeline.
Also, please have a look at your /var/log/Xorg.0.log
, it should contain the modelines the monitor suggests via EDID. Or read the EDID data using other tools. If you don't know how to interpret the log, please upload it in a pastebin etc., and edit your question with a link.
Another thing you can try is to look up which modeline Windows uses (though I'm not sure where to find this information under Windows).
Due to the way the legacy CRTC hardware works on Nvidia graphics cards, you can only set horizontal resolutions which are multiples of 8. 1360 and 1368 are multiples of 8, 1366 isn't.
You didn't say how your monitor is connected to your graphics card (VGA, DisplayPort, HDMI/DVI, ...). The details are a bit complicated, but again for legacy reasons, some of those connections include a horizontal and vertical phase where only blank pixels are sent. For your given modeline, you'd e.g. have 1368 framebuffer pixels out of 1584 horizontal pixels in total.
That means it doesn't really matter that the last two pixels of the 1368 range are not displayed, the card will send an additional 216 blank pixels that are also ignored by the monitor, anyway.
So in your case, I'd just choose to the 1368 horizontal resolution. It means your desktop will have two pixels at the right that are not visible (and I don't know any way to convince X that the actual framebuffer is smaller). Possibly you can configure your window manager to always ignore this area.
Edit
VGA uses analog transmission, so an LCD connected to VGA has a A/D converter to convert the pixel information back to digital. I'm not completely sured what you mean by "some vertical parts of the display are blurred", but if you mean vertical areas or stripes in equal distance, the reason is that the A/D conversion doesn't happen on the pixel boundary, and the reason for that is that the total horizontal width (1584 in your modeline) isn't what the monitor needs: This total width will stretch or shrink the pixels, so at regular times the sampling will happen at a boundary between pixels.
So you can play around with the total width (and/or the sync values, to shift the image) of your modeline.
Also, please have a look at your /var/log/Xorg.0.log
, it should contain the modelines the monitor suggests via EDID. Or read the EDID data using other tools. If you don't know how to interpret the log, please upload it in a pastebin etc., and edit your question with a link.
Another thing you can try is to look up which modeline Windows uses (though I'm not sure where to find this information under Windows).
edited Nov 24 at 12:01
answered Nov 23 at 8:30
dirkt
9,04231121
9,04231121
The monitor is connected to the GPU through VGA, which is the only interface available on this monitor. The problem is that even though I can set my resolution to 1368x768 and the picture is just fine, some vertical parts of the display are blurred and can't be fixed even when adjusting the settings manually. But what's even more puzzling is that under Windows, both the GPU and the monitor's native resolution are instantly recognised and applied once the driver is installed and it works flawlessly.
– Evangelos
Nov 23 at 18:37
add a comment |
The monitor is connected to the GPU through VGA, which is the only interface available on this monitor. The problem is that even though I can set my resolution to 1368x768 and the picture is just fine, some vertical parts of the display are blurred and can't be fixed even when adjusting the settings manually. But what's even more puzzling is that under Windows, both the GPU and the monitor's native resolution are instantly recognised and applied once the driver is installed and it works flawlessly.
– Evangelos
Nov 23 at 18:37
The monitor is connected to the GPU through VGA, which is the only interface available on this monitor. The problem is that even though I can set my resolution to 1368x768 and the picture is just fine, some vertical parts of the display are blurred and can't be fixed even when adjusting the settings manually. But what's even more puzzling is that under Windows, both the GPU and the monitor's native resolution are instantly recognised and applied once the driver is installed and it works flawlessly.
– Evangelos
Nov 23 at 18:37
The monitor is connected to the GPU through VGA, which is the only interface available on this monitor. The problem is that even though I can set my resolution to 1368x768 and the picture is just fine, some vertical parts of the display are blurred and can't be fixed even when adjusting the settings manually. But what's even more puzzling is that under Windows, both the GPU and the monitor's native resolution are instantly recognised and applied once the driver is installed and it works flawlessly.
– Evangelos
Nov 23 at 18:37
add a comment |
Thanks for contributing an answer to Super User!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1377658%2fwhy-isnt-my-monitors-native-resolution-not-recognised-under-linux%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
See if this helps superuser.com/questions/1323967/… askubuntu.com/questions/377937/how-to-set-a-custom-resolution
cvt 1366 768 60
thenxrandr --newmode
thenxrandr --addmode
. This works in VirtualBox with non-standard resolutions, but with real monitors I think it depends on the video driver.– Paulo
Nov 22 at 19:14
Possible duplicate of My computer doesn't recognize the monitor's resolution on some VGA cables, what's going on?
– phuclv
Nov 24 at 14:32
try a different cable VGA resolution with Sony Bravia TV, VGA cable causing resolution issue, Resolution 1920 x 1080 is not available for external monitor...
– phuclv
Nov 24 at 14:34