On 27 October 2011 15:28, Andrew Worsley <amworsley@gmail.com> wrote:
Hope these ideas are some use.
Thanks!
Sounds like it loaded it eventually? Does ifconfig eth0 show it is up?
Yes, networking works perfectly when I bring it up manually. Am using it now to send this email in fact.
Obvious question - but perhaps not relevant - do you have any networking file system mounts?
No network file systems.
If the network taking a while to start or not loading is the issue?
Have wondered if it is a network issue, not entire convinced either way yet. It would seem strange that mounting the filesystems by the recovery menu should also try to bring up the network, yet this process hangs unless I do it manually at the command line.
You should be able to boot in non-graphically mode and get the console output showing the steps. e.g. Does you boot load have a "quiet" or "rgb" or something telling it to do a graphical boot which hides these steps? Perhaps detailing your booting system grub, grub2, lilo et cetera and configuration file ... can allow suggestions
I boot with the boot option in Grub that has the recover. This turns on all the kernel debugging stuff. However the problem happens after user space starts.
Don't know what recovery mode is perhaps it is single user mode? Perhaps you can try to switch to another virtual console after the graphics have started (before it has hung?)
No virtual consoles configured in recovery mode.
You can try switching to multiuser mode via telinit - e.g.
telinit 2 or telinit 3
and see if you can see what is failing.
Hmmm. Could try that I guess. However Ubuntu start up scripts seem to be very quiet, and I think that is the problem with trying to work out what step it is failing on. -- Brian May <brian@microcomaustralia.com.au>