Booting into the Gusty kernel and getting a picture of the kernel crash
is important. Until then we won't know which kernel module caused the
kernel to crash. It is important to get the full kernel crash, and this
may have scrolled off the top of the screen. You can use Shift-PageUp
to scroll backwards in the console output (and Shift-PageDown to scroll
forwards again).
The output from dmesg, and lsmod on the working Feisty kernel will also
be useful, as this will show what working modules are being loaded.
On the crashing Gutsy kernel, if you get a shell prompt (you don't
mention it, but you should drop into a busybox shell prompt after the
modprobe failure), you could try the following commands
modprobe ide_generic
exit
This may allow the system to boot up. If it does then the problem is
definately due to the ide driver being loaded at bootup.
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
Status: New => Incomplete
--
Crash on boot after Gutsy upgrade. Same with LiveCD.
https://bugs.launchpad.net/bugs/162802
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
