Comment 82 for bug 3731

Peter, attached is the output of sudo ddcprobe.
I can't use read-edid on my 64-bit system. I extracted the EDID hex data from Xorg.0.log, compiled my own parse-edid, and fed it into there. Here's what I got:

 # EDID version 1 revision 3
Section "Monitor"
 # Block type: 2:0 3:ff
 # Block type: 2:0 3:fd
 # Block type: 2:0 3:fc
 Identifier "VG2230wm"
 VendorName "VSC"
 ModelName "VG2230wm"
 # Block type: 2:0 3:ff
 # Block type: 2:0 3:fd
 HorizSync 30-82
 VertRefresh 50-75
 # Max dot clock (video bandwidth) 170 MHz
 # Block type: 2:0 3:fc
 # DPMS capabilities: Active off:yes Suspend:no Standby:no

 Mode "1680x1050" # vfreq 59.954Hz, hfreq 65.290kHz
  DotClock 146.250000
  HTimings 1680 1784 1960 2240
  VTimings 1050 1053 1059 1089
  Flags "+HSync" "-VSync"
 EndMode
 # Block type: 2:0 3:ff
 # Block type: 2:0 3:fd
 # Block type: 2:0 3:fc
EndSection

One more detail: The monitor does seem to support 1600x1200 mode. It's pretty strange, but it shrinks the display down to 1680x1050 when I use the mode. Everything gets blurry. When you boot from LiveCD, does Ubuntu try to use the highest resolution available? I don't think that's very wise.

The modes I end up deleting from xorg.conf (1680x1680, 1440x1440) seem to fall under the category "ctiming" here. I bet the issue could be solved by making Ubuntu ignore the "ctiming" modes, because they're obviously wrong here. There are some legitimate "ctiming" modes, though. I'm gonna find whatever's calculating those modes. Maybe somewhere, there's a hidden assumption about the aspect ratio. This is a widescreen 16:10 monitor, and maybe some software can't handle that.

Thank you very, very much for responding. :)