GNOME prevents high resolution VGA without EDID info over VGA
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I recently bought a KVM switch, consisting of a VGA switcher and switchable USB hub. This switch however, does not pass EDID info from the connected display to either of the two connected computers.
I am using it to switch between a dockable laptop running Arch (Antergos) and a Windows PC. The Windows PC handles the lack of EDID info. The laptop does not. This problem does not occur when the laptop is directly connected to the monitor.
The laptop will limit the maximum resolution on the switched monitor to 1024x768. The GNOME settings menu and xrandr also accept 800x600 as a working option. The native resolution of this screen is 1280x1024@75Hz. Attempting to switch to this resolution manually with xrandr, or by GNOME settings after adding it through xrandr, results in it to instantly switching back to 1024x768. This does not happen when running outside a gnome session (startx /usr/bin/xterm) and the system will happily switch to whatever resolution. Even when gnome-session is started manually from xterm after fixing the resolution, it will revert back to 1024x768 and remain that way until gnome-session ends.
System: Lenovo Thinkpad x230 Tablet (Wacom ISD is not the cause of the problem)
OS: Arch (Antergos) with default configuration for everything display related.
Monitor: AOC LM721A
KVM switch: FJ-2UK
Relevent Xorg.0.log lines:
[ 201.470] (II) intel(0): switch to mode 1280x1024@75.0 on VGA1 using pipe 1, position (0, 0), rotation normal, reflection none
[ 201.572] (II) intel(0): switch to mode 1024x768@60.0 on VGA1 using pipe 1, position (0, 0), rotation normal, reflection none
arch-linux xorg gnome monitors edid
edited 18 mins ago
Rui F Ribeiro
37.4k1374118
asked Feb 15 '15 at 11:16
KaelanDuck
814
add a comment |Â
up vote
1
down vote
favorite
I recently bought a KVM switch, consisting of a VGA switcher and switchable USB hub. This switch however, does not pass EDID info from the connected display to either of the two connected computers.
I am using it to switch between a dockable laptop running Arch (Antergos) and a Windows PC. The Windows PC handles the lack of EDID info. The laptop does not. This problem does not occur when the laptop is directly connected to the monitor.
The laptop will limit the maximum resolution on the switched monitor to 1024x768. The GNOME settings menu and xrandr also accept 800x600 as a working option. The native resolution of this screen is 1280x1024@75Hz. Attempting to switch to this resolution manually with xrandr, or by GNOME settings after adding it through xrandr, results in it to instantly switching back to 1024x768. This does not happen when running outside a gnome session (startx /usr/bin/xterm) and the system will happily switch to whatever resolution. Even when gnome-session is started manually from xterm after fixing the resolution, it will revert back to 1024x768 and remain that way until gnome-session ends.
System: Lenovo Thinkpad x230 Tablet (Wacom ISD is not the cause of the problem)
OS: Arch (Antergos) with default configuration for everything display related.
Monitor: AOC LM721A
KVM switch: FJ-2UK
Relevent Xorg.0.log lines:
[ 201.470] (II) intel(0): switch to mode 1280x1024@75.0 on VGA1 using pipe 1, position (0, 0), rotation normal, reflection none
[ 201.572] (II) intel(0): switch to mode 1024x768@60.0 on VGA1 using pipe 1, position (0, 0), rotation normal, reflection none
arch-linux xorg gnome monitors edid
edited 18 mins ago
Rui F Ribeiro
37.4k1374118
asked Feb 15 '15 at 11:16
KaelanDuck
814
Try removing themonitors.xmlfile in~/.config/, rebooting, and setting the desired resolution withxrandr.
– drs
Feb 15 '15 at 17:20
@drs That works, now it switches to the right resolution. It even works through reboot so long as the mode is added to xrandr. If you added this as a solution I would accept it.
– KaelanDuck
Feb 16 '15 at 0:49
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I recently bought a KVM switch, consisting of a VGA switcher and switchable USB hub. This switch however, does not pass EDID info from the connected display to either of the two connected computers.
I am using it to switch between a dockable laptop running Arch (Antergos) and a Windows PC. The Windows PC handles the lack of EDID info. The laptop does not. This problem does not occur when the laptop is directly connected to the monitor.
The laptop will limit the maximum resolution on the switched monitor to 1024x768. The GNOME settings menu and xrandr also accept 800x600 as a working option. The native resolution of this screen is 1280x1024@75Hz. Attempting to switch to this resolution manually with xrandr, or by GNOME settings after adding it through xrandr, results in it to instantly switching back to 1024x768. This does not happen when running outside a gnome session (startx /usr/bin/xterm) and the system will happily switch to whatever resolution. Even when gnome-session is started manually from xterm after fixing the resolution, it will revert back to 1024x768 and remain that way until gnome-session ends.
System: Lenovo Thinkpad x230 Tablet (Wacom ISD is not the cause of the problem)
OS: Arch (Antergos) with default configuration for everything display related.
Monitor: AOC LM721A
KVM switch: FJ-2UK
Relevent Xorg.0.log lines:
[ 201.470] (II) intel(0): switch to mode 1280x1024@75.0 on VGA1 using pipe 1, position (0, 0), rotation normal, reflection none
[ 201.572] (II) intel(0): switch to mode 1024x768@60.0 on VGA1 using pipe 1, position (0, 0), rotation normal, reflection none
arch-linux xorg gnome monitors edid
edited 18 mins ago
Rui F Ribeiro
37.4k1374118
asked Feb 15 '15 at 11:16
KaelanDuck
814
I recently bought a KVM switch, consisting of a VGA switcher and switchable USB hub. This switch however, does not pass EDID info from the connected display to either of the two connected computers.
I am using it to switch between a dockable laptop running Arch (Antergos) and a Windows PC. The Windows PC handles the lack of EDID info. The laptop does not. This problem does not occur when the laptop is directly connected to the monitor.
The laptop will limit the maximum resolution on the switched monitor to 1024x768. The GNOME settings menu and xrandr also accept 800x600 as a working option. The native resolution of this screen is 1280x1024@75Hz. Attempting to switch to this resolution manually with xrandr, or by GNOME settings after adding it through xrandr, results in it to instantly switching back to 1024x768. This does not happen when running outside a gnome session (startx /usr/bin/xterm) and the system will happily switch to whatever resolution. Even when gnome-session is started manually from xterm after fixing the resolution, it will revert back to 1024x768 and remain that way until gnome-session ends.
System: Lenovo Thinkpad x230 Tablet (Wacom ISD is not the cause of the problem)
OS: Arch (Antergos) with default configuration for everything display related.
Monitor: AOC LM721A
KVM switch: FJ-2UK
Relevent Xorg.0.log lines:
[ 201.470] (II) intel(0): switch to mode 1280x1024@75.0 on VGA1 using pipe 1, position (0, 0), rotation normal, reflection none
[ 201.572] (II) intel(0): switch to mode 1024x768@60.0 on VGA1 using pipe 1, position (0, 0), rotation normal, reflection none
arch-linux xorg gnome monitors edid
arch-linux xorg gnome monitors edid
edited 18 mins ago
Rui F Ribeiro
37.4k1374118
asked Feb 15 '15 at 11:16
KaelanDuck
814
edited 18 mins ago
Rui F Ribeiro
37.4k1374118
asked Feb 15 '15 at 11:16
KaelanDuck
814
edited 18 mins ago
Rui F Ribeiro
37.4k1374118
edited 18 mins ago
Rui F Ribeiro
37.4k1374118
edited 18 mins ago
Rui F Ribeiro
37.4k1374118
37.4k1374118
asked Feb 15 '15 at 11:16
KaelanDuck
814
asked Feb 15 '15 at 11:16
KaelanDuck
814
asked Feb 15 '15 at 11:16
KaelanDuck
814
814
Try removing themonitors.xmlfile in~/.config/, rebooting, and setting the desired resolution withxrandr.
– drs
Feb 15 '15 at 17:20
@drs That works, now it switches to the right resolution. It even works through reboot so long as the mode is added to xrandr. If you added this as a solution I would accept it.
– KaelanDuck
Feb 16 '15 at 0:49
add a comment |Â
Try removing themonitors.xmlfile in~/.config/, rebooting, and setting the desired resolution withxrandr.
– drs
Feb 15 '15 at 17:20
@drs That works, now it switches to the right resolution. It even works through reboot so long as the mode is added to xrandr. If you added this as a solution I would accept it.
– KaelanDuck
Feb 16 '15 at 0:49
Try removing the
monitors.xml file in ~/.config/, rebooting, and setting the desired resolution with xrandr.– drs
Feb 15 '15 at 17:20
Try removing the
monitors.xml file in ~/.config/, rebooting, and setting the desired resolution with xrandr.– drs
Feb 15 '15 at 17:20
@drs That works, now it switches to the right resolution. It even works through reboot so long as the mode is added to xrandr. If you added this as a solution I would accept it.
– KaelanDuck
Feb 16 '15 at 0:49
@drs That works, now it switches to the right resolution. It even works through reboot so long as the mode is added to xrandr. If you added this as a solution I would accept it.
– KaelanDuck
Feb 16 '15 at 0:49
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
Somewhere around version 3.14 gnome added a feature where it remembers the configurations of previously plugged-in monitors. Unfortunately, this feature sometimes prevents gnome from allowing a monitor's proper resolution to be set. Common symptoms are xrandr failing to change the resolution and providing no error as to why, as well as monitors exhibiting the correct resolution at a tty console, but not in gnome.
The configurations are stored in an undocumented file in ~/.config/monitors.xml. You can poke through this file to see if you can identify the offending entry and remove it. Or you can regain control over your monitors entirely and delete this file altogether.
After changing the file, you may need to reboot or restart gnome before you can set the correct resolution with xrandr.
answered Feb 16 '15 at 1:59
drs
3,27342758
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
Somewhere around version 3.14 gnome added a feature where it remembers the configurations of previously plugged-in monitors. Unfortunately, this feature sometimes prevents gnome from allowing a monitor's proper resolution to be set. Common symptoms are xrandr failing to change the resolution and providing no error as to why, as well as monitors exhibiting the correct resolution at a tty console, but not in gnome.
The configurations are stored in an undocumented file in ~/.config/monitors.xml. You can poke through this file to see if you can identify the offending entry and remove it. Or you can regain control over your monitors entirely and delete this file altogether.
After changing the file, you may need to reboot or restart gnome before you can set the correct resolution with xrandr.
answered Feb 16 '15 at 1:59
drs
3,27342758
add a comment |Â
up vote
2
down vote
accepted
Somewhere around version 3.14 gnome added a feature where it remembers the configurations of previously plugged-in monitors. Unfortunately, this feature sometimes prevents gnome from allowing a monitor's proper resolution to be set. Common symptoms are xrandr failing to change the resolution and providing no error as to why, as well as monitors exhibiting the correct resolution at a tty console, but not in gnome.
The configurations are stored in an undocumented file in ~/.config/monitors.xml. You can poke through this file to see if you can identify the offending entry and remove it. Or you can regain control over your monitors entirely and delete this file altogether.
After changing the file, you may need to reboot or restart gnome before you can set the correct resolution with xrandr.
answered Feb 16 '15 at 1:59
drs
3,27342758
add a comment |Â
up vote
2
down vote
accepted
up vote
2
down vote
accepted
Somewhere around version 3.14 gnome added a feature where it remembers the configurations of previously plugged-in monitors. Unfortunately, this feature sometimes prevents gnome from allowing a monitor's proper resolution to be set. Common symptoms are xrandr failing to change the resolution and providing no error as to why, as well as monitors exhibiting the correct resolution at a tty console, but not in gnome.
The configurations are stored in an undocumented file in ~/.config/monitors.xml. You can poke through this file to see if you can identify the offending entry and remove it. Or you can regain control over your monitors entirely and delete this file altogether.
After changing the file, you may need to reboot or restart gnome before you can set the correct resolution with xrandr.
answered Feb 16 '15 at 1:59
drs
3,27342758
Somewhere around version 3.14 gnome added a feature where it remembers the configurations of previously plugged-in monitors. Unfortunately, this feature sometimes prevents gnome from allowing a monitor's proper resolution to be set. Common symptoms are xrandr failing to change the resolution and providing no error as to why, as well as monitors exhibiting the correct resolution at a tty console, but not in gnome.
The configurations are stored in an undocumented file in ~/.config/monitors.xml. You can poke through this file to see if you can identify the offending entry and remove it. Or you can regain control over your monitors entirely and delete this file altogether.
After changing the file, you may need to reboot or restart gnome before you can set the correct resolution with xrandr.
answered Feb 16 '15 at 1:59
drs
3,27342758
answered Feb 16 '15 at 1:59
drs
3,27342758
answered Feb 16 '15 at 1:59
drs
3,27342758
answered Feb 16 '15 at 1:59
drs
3,27342758
3,27342758
add a comment |Â
add a comment |Â
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f184941%2fgnome-prevents-high-resolution-vga-without-edid-info-over-vga%23new-answer', 'question_page');
);
Post as a guest
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
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
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
Try removing the
monitors.xmlfile in~/.config/, rebooting, and setting the desired resolution withxrandr.– drs
Feb 15 '15 at 17:20
@drs That works, now it switches to the right resolution. It even works through reboot so long as the mode is added to xrandr. If you added this as a solution I would accept it.
– KaelanDuck
Feb 16 '15 at 0:49