The module errors you see in the log (copied below) there are evidence of my discovery in bug 525989 . The reason is you ended up booting with a karmic (or some other) ramdisk that did not have a /lib/modules/2.6.32-14-server . Instead, it had a /lib/modules/<kernel-version-that-it-was-built-for> .
WARNING: Couldn't open directory /lib/modules/2.6.32-14-server: No such file or directory FATAL: Could not open /lib/modules/2.6.32-14-server/modules.dep.temp for writing: No such file or directory Couldn't get a file descriptor referring to the console Begin: Loading essential drivers... ... FATAL: Could not load /lib/modules/2.6.32-14-server/modules.dep: No such file or directory FATAL: Could not load /lib/modules/2.6.32-14-server/modules.dep: No such file or directory FATAL: Could not load /lib/modules/2.6.32-14-server/modules.dep: No such file or directory -- console errors about modules https://bugs.launchpad.net/bugs/525994 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
