Comment 11 for bug 42932

Hi,

Testing with todays livecd (20060513) with casper 1.52 this problem is still present.
I'm wondering if the problem isn't somewhere else, since I found the following in the X logging:

(--) NV(0): CRTC 0 is currently programmed for DFP
(II) NV(0): Using DFP on CRTC 0
(--) NV(0): Panel size is 1440 x 900
(II) NV(0): Panel is LVDS
(--) NV(0): VideoRAM: 131072 kBytes
(==) NV(0): Using gamma correction (1.0, 1.0, 1.0)
(II) NV(0): Generic Monitor: Using hsync range of 28.00-51.00 kHz
(II) NV(0): Generic Monitor: Using vrefresh range of 43.00-60.00 Hz
(II) NV(0): Clock range: 12.00 to 400.00 MHz

And after that a bunch of statements on:

(II) NV(0): Not using default mode "xxxxx" (vrefresh out of range)

and

(II) NV(0): Not using default mode "xxxxx" (bad mode clock/interlace/doublescan)

Isn't the problem that a "Generic Monitor" is used, with certain hsync/vrefresh settings and those perhaps not match with my 1440 x 900 panel?