Maverick xorg results in "out of range" error w/Intel i945 & 22" LCD

[Erick Brunzell]

Binary package hint: xorg

Sorry for the generalization filing this against "xorg" but I've been following bug 640807, and even commented there, but I see Tormod Volden mentioned a few bugs where xorg actually generated "wrong modes". I didn't however see any of those addressing the "identical" behaviour and hardware so I decided to be lazy and let apport help me collect info.

I was finally able to get the Maverick RC Live CD to boot by pressing F6, then ESC, then typing "text" (w/o the quotes), and then typing:

gconftool-2 --type bool -s "/apps/gnome_settings_daemon/xrandr/turn_on_external_monitors_at_startup" false

Then just typing "startx" (again w/o the quotes) I got a desktop with the expected modes:

ubuntu@ubuntu:~$ xrandr
Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 4096 x 4096
VGA1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm x 297mm
   1680x1050 60.6*+ 74.9
   1600x1200 75.0 60.0
   1400x1050 74.9 60.0
   1280x1024 75.0 60.0
   1280x960 60.0
   1152x864 75.0
   1024x768 75.1 70.1 60.0
   832x624 74.6
   800x600 72.2 75.0 60.3 56.2
   640x480 72.8 75.0 66.7 60.0
   720x400 70.1

Due to limited vision it's difficult to continue this dialogue at the default resolution. That however is typical and unrelated to this bug, so I'll stop for now and report more once I can manually adjust to 1440x900 as I usually do. I just didn't want to make any modifications before filing this bug report.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
DRM.card0.VGA.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1680x1050 1600x1200 1600x1200 1680x1050 1400x1050 1400x1050 1280x1024 1280x1024 1280x960 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400
 edid-base64: AP///////wAiZGkkAQEBAQ4TAQMKLx547txVo1lIniQRUFS/74CzD6lAkECQT4GAgUBxT6lPITmQMGIaHEBosDYA2ikRAAAcAAAA/QA4TBheFQAKICAgICAgAAAA/wA5MTRNSjNYWTA3NzI3AAAA/ABIYW5ucy5HIEhpMjIxAOs=
Date: Mon Oct 4 16:14:26 2010
GdmLog: Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/gdm/:0.log'] failed with exit code 1: cat: /var/log/gdm/:0.log: No such file or directory
GdmLog1: Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory
GdmLog2: Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928)
ProcCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- text
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
dmi.bios.date: 03/24/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: LakePort
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd03/24/2009:svn:pn:pvr:rvn:rnLakePort:rvr:cvn:ct3:cvr:
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-22-generic

[Tormod Volden (tormodvolden)]

Thanks for filing your own report! Would you be able to tell us which mode is broken, that is, the one that is chosen when it is "Out of range"? Running "xrandr --verbose :0" on the ctrl-alt-F1 console while X is broken should tell.

[Erick Brunzell (lbsolost)]

Running "xrandr --verbose :0" simply shows all xrandr options, same if I copy-n-paste from a working install:

lance@lance-desktop:~$ xrandr --verbose :0
usage: xrandr [options]
  where options are:
...............................................................................

If I run xrandr with any other options I just get "Can't open display".

I do still have a broken Maverick installed (it was an RC upgrade test from Lucid), would it be possible to snag anything from it's logs?

[Tormod Volden (tormodvolden)]

Sorry I forgot the -d in there!
 xrandr --verbose -d :0

[Erick Brunzell (lbsolost)]

The output of "xrandr --verbose -d :0" is so long that I can't see the top portion, which I can see after playing is what we really need to see, but I did manage to get the output of "xrandr -d :0". This is the broken one:

ubuntu@ubuntu:~$ xrandr -d :0
Screen 0: minimum 320 x 200, current 1600 x 1200, maximum 4096 x 4096
VGA1 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 474mm x 297mm
   1680x1050 60.6+ 74.9
   1600x1200 75.0* 60.0
   1400x1050 74.9 60.0
   1280x1024 75.0 60.0
   1280x960 60.0
   1152x864 75.0
   1024x768 75.1 70.1 60.0
   832x624 74.6
   800x600 72.2 75.0 60.3 56.2
   640x480 72.8 75.0 66.7 60.0
   720x400 70.1

This is what it should be (copied from a Beta Live CD):

ubuntu@ubuntu:~$ xrandr -d :0
Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 4096 x 4096
VGA1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm x 297mm
   1680x1050 60.6*+ 74.9
   1600x1200 75.0 60.0
   1400x1050 74.9 60.0
   1280x1024 75.0 60.0
   1280x960 60.0
   1152x864 75.0
   1024x768 75.1 70.1 60.0
   832x624 74.6
   800x600 72.2 75.0 60.3 56.2
   640x480 72.8 75.0 66.7 60.0
   720x400 70.1

So it's normal to have a mode for 1600x1200@75.0Hz but it shouldn't be selected, in fact 1680x1050@60.6Hz is shown as the preferred mode but possibly the bug in g-s-d is resulting in 1600x1200@75Hz being selected?

I'm going to shut down this monitor and disconnect it for a while because it's acting flaky now :^( It did this once before while trying to figure this out and disconnecting it for a few hours did the trick, so I'm hoping that'll do it again :^)

[Tormod Volden (tormodvolden)]

Thanks. You can always redirect the command output to a file, and attach the file, for instance:
 xrandr --verbose -d :0 > xrandr.white.txt

I am not sure it is normal to have a 1600x1200@75.0Hz mode in your case, especially if it makes the monitor flaky! Please attach the verbose output so we can see the EDID information from the monitor.

[Tormod Volden (tormodvolden)]

The EDID information from the monitor lists 1600x1200@75Hz as a supported Standard Timing, and the clock rates are within ranges, although close to the limits. So this might be false information built in to your monitor (or it can not handle its own stated specifications) and not a bug in the X server.

[Erick Brunzell (lbsolost)]

Thanks for all the help Tormod.

I've marked this as a duplicate of bug 640807.