PDA

View Full Version : update broke VGA resolution?


nittanylion
October 13th, 2008, 02:23 PM
I've been using monitor output on my laptop, running it at 1440x900 and the laptop at 1280x800. Every startup, I'd run this command:

xrandr --output VGA --mode 1440x900 --above LVDS

Just updated, restart as request, and now xrandr won't recognize 1440x900. Now:

a@b:~$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 2048 x 2048
VGA connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
1360x768 59.8
1152x864 60.0
1024x768 60.0*
800x600 60.3
640x480 59.9
LVDS connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
1280x800 60.0 +
1024x768 85.0 75.0 70.1 60.0*
832x624 74.6
800x600 85.1 72.2 75.0 60.3 56.2
640x480 85.0 72.8 75.0 59.9
720x400 85.0
640x400 85.1
640x350 85.1
TV disconnected (normal left inverted right x axis y axis)


Contents of /etc/X11/xorg.conf (which have never changed):
# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "ZAxisMapping" "4 5"
Option "Buttons" "9"
EndSection

Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizEdgeScroll" "0"
EndSection

Section "Device"
Identifier "Configured Video Device"
EndSection

Section "Monitor"
Identifier "Configured Monitor"
EndSection

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
SubSection "Display"
Virtual 2048 2048
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Synaptics Touchpad"
EndSection

I am perfectly well aware that I can add new modes in xrandr, or change my setup in xorg.conf. However, before the updates applied in the past 24 hours, everything worked plug-and-play (minus the xrandr command, which I probably could've done in System --> Preferences --> Screen Resolution anyway). I've had horrible nightmares trying to add modelines under Heron, sooo any thoughts on finding out what went wrong?

nittanylion
October 15th, 2008, 10:01 AM
bumping with new details

Having been relegated to using the xrandr --newmode command every time xserver gets updated, a few new issues have arisen. After I change to a resolution on VGA output, occasionally the VGA output will just die. I can bring up the terminal on the LVDS display and attempt to change the VGA resolution, but no matter the resolution, the VGA monitor shows no input.

Furthermore, since it's detecting my monitor at incorrect resolutions (1360x768? for some unknown reason), I'll add the mode using the proper modeline, and sometimes xrandr will simply ignore the command. No error message, it just will not add the new mode. Sometimes I have to restart the xserver a few times before it xrandr will actually add the new mode.

And for what it's worth, this has always persisted (even before the update that really screwed me over): if I set up an expanded desktop with 2 different resolutions, any attempt to change an individual resolution will crash the xserver entirely.

For all 3 of these details, I have not found any details in various logs that would hint at what's going on. Beyond looking to the logs, I'm at a loss how to troubleshoot this. I'd file a bug report if I had any idea what's causing this behavior.

nittanylion
October 22nd, 2008, 07:05 PM
bumping b/c update did it again

Plus xrandr is giving this error message:

$ xrandr --output VGA --newmode "1440x900_60.00" 106.50 1440 1528 1672 1904 900 903 909 934 -hsync +vsync
X Error of failed request: BadName (named color or font does not exist)
Major opcode of failed request: 153 (RANDR)
Minor opcode of failed request: 16 ()
Serial number of failed request: 16
Current serial number in output stream: 16

Xrandr:
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 2048 x 2048
VGA connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
1360x768 59.8
1152x864 60.0
1024x768 60.0*
800x600 60.3
640x480 59.9
LVDS connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
1280x800 60.0 +
1024x768 85.0 75.0 70.1 60.0*
832x624 74.6
800x600 85.1 72.2 75.0 60.3 56.2
640x480 85.0 72.8 75.0 59.9
720x400 85.0
640x400 85.1
640x350 85.1
TV disconnected (normal left inverted right x axis y axis)
1440x900_60.00 (0xb0) 106.5MHz
h: width 1440 start 1528 end 1672 total 1904 skew 0 clock 55.9KHz
v: height 900 start 903 end 909 total 934 clock 59.9Hz

Oh, also (just incase):

$ cvt 1440 900
# 1440x900 59.89 Hz (CVT 1.30MA) hsync: 55.93 kHz; pclk: 106.50 MHz
Modeline "1440x900_60.00" 106.50 1440 1528 1672 1904 900 903 909 934 -hsync +vsync