This still happens with Lucid alpha-2 updated through today, but not always.
I think that this may not be a problem with the driver itself, but with timing related to the upstart scripts in /etc/init/ .
If I start the system in recovery mode, log in as root, and run the script
#!/bin/sh echo start some services like the ssh daemon and apache service ssh start service apache2 start echo start X service gdm start
then gdm always starts.
Note that Bug #945553 mentions this problem.
In the past, when a similar problem occurred, I could change the order in which gdm started from /init/rc2.d, relative to other daemons, but I don't know how to do this with the new upstart scripts.
This still happens with Lucid alpha-2 updated through today, but not always.
I think that this may not be a problem with the driver itself, but with timing related to the upstart scripts in /etc/init/ .
If I start the system in recovery mode, log in as root, and run the script
#!/bin/sh
echo start some services like the ssh daemon and apache
service ssh start
service apache2 start
echo start X
service gdm start
then gdm always starts.
Note that Bug #945553 mentions this problem.
In the past, when a similar problem occurred, I could change the order in which gdm started from /init/rc2.d, relative to other daemons, but I don't know how to do this with the new upstart scripts.