Comment 13 for bug 179472

Revision history for this message
Daniel Hahler (blueyed) wrote :

The autoconfiguration of the display fails with messages like this:
(II) NV(0): Not using default mode "1024x768" (hsync out of range)

It looks like no mode gets set by default?!

The relevant part from the log seems to be:
(II) NV(0): Not using default mode "1600x1200" (hsync out of range)
(II) NV(0): Not using default mode "800x600" (hsync out of range)
(II) NV(0): Not using default mode "1792x1344" (width too large for virtual size)
[...]
(II) NV(0): Not using default mode "1024x768" (hsync out of range)
(II) NV(0): Not using default mode "2048x1536" (width requires unsupported line pitch)
(II) NV(0): Not using default mode "1024x768" (hsync out of range)
(--) NV(0): Virtual size is 1600x1200 (pitch 1600)
(**) NV(0): *Driver mode "1600x1200": 204.8 MHz, 94.1 kHz, 75.0 Hz
(II) NV(0): Modeline "1600x1200"x75.0 204.75 1600 1720 1888 2176 1200 1203 1207 1255 -hsync +vsync (94.1 kHz)
[.....]
(**) NV(0): *Default mode "320x175": 15.8 MHz, 37.9 kHz, 85.3 Hz (D)
(II) NV(0): Modeline "320x175"x85.3 15.75 320 336 368 416 175 191 192 222 doublescan +hsync -vsync (37.9 kHz)
(**) NV(0): Display dimensions: (360, 270) mm
(**) NV(0): DPI set to (112, 112)