Fails to detect display

[jcdutton]

Binary package hint: xserver-xorg-video-nv

When the PC first boots, if fails to detect the display and runs in low res, after a few restarts of gdm, it finally recognises the display and runs correctly:
Extract from Xorg.0.log
 (II) NV(0): I2C device "DDC:ddc2" registered at address 0xA0.
 (II) NV(0): ... none found
instead of
(II) NV(0): I2C device "DDC:ddc2" registered at address 0xA0.
(--) NV(0): DDC detected a CRT:
(II) NV(0): Manufacturer: ATE Model: 8506 Serial#: 942815280
(II) NV(0): Year: 2001 Week: 19
(II) NV(0): EDID Version: 1.3

Could this be a timing problem with the I2C detection code?

[jcdutton (james-superbug)]

Log showing the fix. Notice that it had to call the EDID probe function 4 times before it worked.
The patch will give up after 10 failures in order to avoid an infinite loop.

II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) NV(0): I2C bus "DDC" initialized.
(II) NV(0): Probing for analog device on output A...
(--) NV(0): ...found one
(II) NV(0): Probing for analog device on output B...
(--) NV(0): ...can't find one
(II) NV(0): Probing, for EDID on I2C bus A...
(II) NV(0): Probing, loop 0
(II) NV(0): I2C device "DDC:E-EDID segment register" registered at address 0x60.
(II) NV(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) NV(0): Probing, loop 1
(II) NV(0): Probing, loop 2
(II) NV(0): Probing, loop 3
(--) NV(0): DDC detected a CRT:
(II) NV(0): Manufacturer: ATE Model: 8506 Serial#: 942815280

[jcdutton (james-superbug)]

Suggestion by Aaron:
That seems wrong, you shouldn't have intermittent results like that. I
wonder if your monitor is just too slow to respond. Does increasing the
timeout in NVDACi2cInit help? You could try copying the timouts from
G80I2CInit.

I will try this when a get the chance

[jcdutton (james-superbug)]

I tried the suggested changes.
It did not help at all.

[Bryce Harrington (bryce)]

Thank you for reporting this issue about xserver-xorg-video-nv. Starting with Lucid, Ubuntu is transitioning to using the -nouveau video driver by default instead of -nv. The reason for this change is because upstream development for the -nv driver has been quite slow. We hope bugs will get fixed faster with -nouveau as well.

Because of this, I'm closing this bug report at this time. I'm marking it wontfix because what you describe is probably a valid issue, but we do not have intentions to work on it in Ubuntu. If you would still like to see this issue investigated, I would encourage you to file it upstream.

[jcdutton (james-superbug)]

I tried the nouveau drivers in Lucid. They fail to display anything at all, so it not a valid alternative for my graphics card at the moment. It just returned back to the text display saying there are problem with X.
Is it worth starting a new bug report for the nouveau driver?