I'm dual booting Ubuntu and Fedora both on logical volumes with a shared home directory. The auto-detected Fedora system always results in the error that it cannot find (or load?) the kernel. However, I am able to boot with the following entries in /etc/grub.d/40_custom
# cat /etc/grub.d/40_custom
! /bin/sh
set -e
echo "
menuentry 'Fedora-Ubuntu, with Linux 3.6.10-2' --class fedora --class gnu-linux --class gnu --class os {
recordfail
insmod gzio
insmod lvm
insmod part_msdos
insmod ext2
set root='(vg_losgar-lv_fedora)'
search --no-floppy --fs-uuid --set=root e1726ee3-9b60-4d74-8995-fe714e94aec0
linux /vmlinuz-3.6.10-2.fc17.x86_64 root=/dev/mapper/vg_losgar-lv_fedora ro quiet splash vt.handoff=7
initrd /initramfs-3.6.10-2.fc17.x86_64.img
}
"
The issue with this workaround is it has to be manually updated and have update-grub re-run in Ubuntu everytime I update the fedora kernel.
The file /boot/grub/default no longer seems to be present
I can confirm this bug in 12.04.
I'm dual booting Ubuntu and Fedora both on logical volumes with a shared home directory. The auto-detected Fedora system always results in the error that it cannot find (or load?) the kernel. However, I am able to boot with the following entries in /etc/grub. d/40_custom
# cat /etc/grub. d/40_custom vg_losgar- lv_fedora) ' 9b60-4d74- 8995-fe714e94ae c0 3.6.10- 2.fc17. x86_64 root=/dev/ mapper/ vg_losgar- lv_fedora ro quiet splash vt.handoff=7 3.6.10- 2.fc17. x86_64. img
! /bin/sh
set -e
echo "
menuentry 'Fedora-Ubuntu, with Linux 3.6.10-2' --class fedora --class gnu-linux --class gnu --class os {
recordfail
insmod gzio
insmod lvm
insmod part_msdos
insmod ext2
set root='(
search --no-floppy --fs-uuid --set=root e1726ee3-
linux /vmlinuz-
initrd /initramfs-
}
"
The issue with this workaround is it has to be manually updated and have update-grub re-run in Ubuntu everytime I update the fedora kernel.
The file /boot/grub/default no longer seems to be present