Did you verify those settings in the GRUB RAM editor? Error 15 is, IIRC, a "file not found" error.
Note: The default
F11 installation is to use two partitions: One ext3
boot partition and a second LVM partition containing swap
and an ext4
file system for everything except /boot
. So, if you used the defaults when you installed, the /boot
would be incorrect, since /dev/sdb8
would already be /boot
, and the rest of F11 would be on /dev/sdb9
as a LV.
You may, of course, have not used the defaults. But, anyhow, it's easy to verify in the RAM editor.
Note also that the GRUB used by Ubuntu is a more recent version than the one used by other distributions, where the root ...
directive may be replaced by a uuid
directive, and other boot options are supported. When I boot my F11 using the Ubuntu GRUB, the F11 boot stanza looks like this:
## END DEBIAN AUTOMAGIC KERNELS LIST
# This is a divider, added to separate the menu items below from the Debian
title --- Fedora 11 x86_64
title Kernel 220.127.116.11-217.2.8
kernel /boot/vmlinuz-18.104.22.168-217.2.8.fc11.x86_64 ro root=UUID=ffccf6e4-8321-46a7-9ef0-48e2aeedc325 quiet
title Kernel 22.214.171.124-217.2.8 (recovery mode)
kernel /boot/vmlinuz-126.96.36.199-217.2.8.fc11.x86_64 ro root=UUID=ffccf6e4-8321-46a7-9ef0-48e2aeedc325 quiet 3
Note that the uuid
directive specifies a different uuid
than the one used in the kernel
line. That's because the Ubuntu GRUB is set to look in the Ubuntu /boot
directory for the F11 boot images. I have to do it that way because the brain-dead BIOS of this laptop will not let me boot from sdb
where I have my F11 installed, so I can only boot from sda
where I keep Jaunty. (The BIOS problem is that my sdb
is a 320Gb SATA, and its too fast (3Gb/sec) for the BIOS to handle. F11 has to slow the access to 1.5Gb/sec to make it work, which the kernel does as it boots.)