Sounds like a conflicting module might be loaded during the regular startup... if you start gdm while in recovery mode, does it still lock up?
If not, you might try switching to another console as it's booting and/or specifying a console only runlevel for the boot. (see http://caulfield.info/emmet/2008/03/add-a-textonly-runlevel-to-ubu.html ) If you can figure out the offending module, you could blacklist it to keep it from loading... Of course it may just be a bug for your hardware... Cheers, Vern Simón Ruiz wrote: > Ack! > > Show-stopper. > > The wireless card is a Realtek RTL-8185 based adapter. The right > modules for this are not in the standard Hardy kernel. > > I read a possible solution at > <http://willdaniels.co.uk/articles/howto-guides/10-howto/15-rtl8180-hardy> > which involved adding a PPA with a newer build of the kernel that had > the right module in place. > > And, having gone through that, I can confirm that if I boot into the > new kernel, the rtl8180 module is in place. The only problem is I can > only confirm that when running said kernel in recovery mode. If I try > to boot it into full multi-user glory, it freezes at about the time > that GDM should be starting up. > > Thankfully I can boot up using the older kernel just fine, so it's not > COMPLETELY bricked; just...well...useless by virtue of no network > connection... > > Which also makes the OSD a lot less useful, since it can only get to > videos through USB, rather than on the network which is what makes it > damned spiffy > > *sigh* ah well... > > Simón > > _______________________________________________ > Fwlug mailing list > [email protected] > http://fortwaynelug.org/mailman/listinfo/fwlug_fortwaynelug.org _______________________________________________ Fwlug mailing list [email protected] http://fortwaynelug.org/mailman/listinfo/fwlug_fortwaynelug.org
