I don't see any errors in the dmesg log and it looks like the nvidia kernel module is ready rather late in that log. Looking at the udev log I would guess that the module isn't loaded any sooner than about .31 seconds before the last entry in the udev log (if I'm reading it correctly).
@Seth: *IF* the theory hold up, I think your basic approach in https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/532047/comments/91 might make the most sense as a fix to propose. gdm should wait until the graphics system is ready--it's attempting to do that now. What would you think about the gdm job also waiting for udev to finish or udevtrigger to start rather than for the tty's? It might happen sooner than the tty's and it's probably no later than 1/3 second from the earliest it could happen without error, and actually the module might not be ready until even closer to the end of the udev run. I don't notice any other udev event that would necessarily match when the nvidia module is done initializing, much less one that would be emitted with the use of any graphics driver (and modeset/nomodeset). Do you see anything in the udev log that looks like it would work or know of any other trigger? Any other approach? Is this something you would like to experiment with? Anyone--any other ideas? -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
