If you start a shell early on in the boot process and then use tools such as netstat, ip and ifconfig so that they are cached, you can analyse the situation after the system supposedly “hangs”. You will then see that eth0 is down, although eth0 is required for the nfs-mounted / to work.
I assume the problem is in NetworkManager: It starts, then shuts down eth0 so that it can later initialise eth0 by itself, but before doing so requires a read from /, which then hangs (indefinitely) because eth0 is down. I think this problem was not present in intrepid alpha2 but appeared in intrepid alpha3. -- desktop/live cd netboot won't boot X https://bugs.launchpad.net/bugs/271958 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
