Comment 4 for bug 297927

I upgraded another system with the same type of motherboard, chipset, and cpu. In this case, I used the alternate install CD as the primary source of new files, allowing access to the Internet for additional upgrades.

In this case, the symlink for starting gdm in /etc/rc2.d turned out to be S30gdm -> ../init.d/gdm - not S13gdm, as above, and the display started on the first reboot after installation.

So why was it S13gdm in my first upgrade installation? Could this have been left over from the installation of a previous version of Ubuntu - on the theory that the upgrade install does not change existing symlinks? Or could there be some difference between upgrades from the Internet versus upgrades primarily from the Alternate CD? I suspect that the former case is most likely.

It may be that for most hardware the order in which gdm is started relative to other daemons started in runlevel 2 is not so critical; but for this motherboard it is pretty critical.