Comment 2 for bug 23689

Below is the output from ddcprobe. The 'more or less' on the resolution chooser
algorithm seens to be fooled by displays that report the same resolution twice
but with different refresh ratio. I couldn't find a documentation about ctiming
and dtiming, I imagine it's non-interlaced and interlaced mode. If the second
highest resolution haven't considered interlaced modes, the resolution choosen
(1280x1024) would be fine (although 1152x864, the resolution I'm using right
now, looks better - and it's not listed by ddcprobe). May be it could be a good
idea to try a good non-interlaced mode instead of trying interlaced mode.
Actually, I'd prefer interlaced mode as a last resource (instead of a main option).

vbe: VESA 3.0 detected.
oem: NVIDIA
vendor: NVIDIA Corporation
product: NV18 Board - V32-B04z Chip Rev A4
memory: 65536kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x16
mode: 800x600x256
mode: 1024x768x16
mode: 1024x768x256
mode: 320x200x64k
mode: 320x200x16m
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x64k
mode: 1024x768x16m
edid: 1 3
id: 0312
eisa: PBR0312
serial: 1dde37c4
manufacture: 3 2005
input: sync on green, analog signal.
screensize: 31 23
gamma: 1.270000
dpms: RGB, active off, suspend, standby
timing: 720x400@70 Hz (VGA 640x400, IBM)
timing: 640x480@75 Hz (VESA)
timing: 800x600@60 Hz (VESA)
timing: 800x600@72 Hz (VESA)
timing: 800x600@75 Hz (VESA)
timing: 1024x768@87 Hz Interlaced (8514A)
timing: 1024x768@75 Hz (VESA)
ctiming: 800x600@85
ctiming: 800x600@100
ctiming: 1024x768@85
ctiming: 1600x1200@60
ctiming: 1280x1024@60
ctiming: 640x480@85
dtiming: 1600x1200@78
monitorid: Serie 786NS
monitorname: Serie 786NS
monitorrange: 30-75, 60-100