Comment 2 for bug 55112

No such luck I'm afraid.. For informational purpouses I copied the entries
from the grub boot list, although taking into account they are almost
completely identical, its rather useless.. the only thing that does change
is the kernel number and after the -25 version I started using the 686
version to see wether that made a difference.. I'm using a P4..

Any other ideas or suggestions that I might try? or is there any other
information that you might require? I'd also be willing to modprobe drivers
untill it works.. but I've just got no idea what so ever how to probe into a
kernel that isn't running and I've got no idea which ones to probe..

Either way, thanks a lot for the attention so far! This is the first
suggestion I've had towards fixing this after asking on several different
locations, it's /really/ appreciated!

-Rian

These don't work:
----------------------------------
title Ubuntu, kernel 2.6.15-26-686
root (hd1,0)
kernel /boot/vmlinuz-2.6.15-26-686 root=/dev/sdb1 ro quiet splash
initrd /boot/initrd.img-2.6.15-26-686
savedefault
boot

title Ubuntu, kernel 2.6.15-25-386
root (hd1,0)
kernel /boot/vmlinuz-2.6.15-25-386 root=/dev/sdb1 ro quiet splash
initrd /boot/initrd.img-2.6.15-25-386
savedefault
boot

This one DOES work:
----------------------------------
title Ubuntu, kernel 2.6.15-19-386
root (hd1,0)
kernel /boot/vmlinuz-2.6.15-19-386 root=/dev/sdb1 ro quiet splash
initrd /boot/initrd.img-2.6.15-19-386
savedefault
boot

On Tuesday 08 August 2006 18:45, Ben Collins wrote:
> I suspect that the newer kernel is working properly and that your drive
> is showing up as sda instead of hda (or the other way around).
>
> You could try booting the new kernel with root=/dev/sdaX to test this
> theory.