[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
I'm confused.....first usage of Grub2.......
From: |
Another Sillyname |
Subject: |
I'm confused.....first usage of Grub2....... |
Date: |
Sat, 28 Apr 2012 14:48:53 +0100 |
I have setup a laptop as a triple boot configuration.
1. /dev/sda1 Win 7
2. /dev/sda2 boot
3. /dev/sda3 Fedora14 - Because I hate Gnome 3 so will be staying
on F14 for foreseeable future.
4. /dev/sda4 Extended Partition
5. /dev/sda5 Ubuntu inc Grub2 installer
6. /dev/sda6 swap used by both Fed14 and Ubuntu
7. /dev/sda7 large shared ntfs partition for all 3 OS's
I had all three booting fine and then looked at how to configure grub2
to remove some of the extraneous entries.
I'm a fairly experienced grub legacy hacker and having read that it's
better to use update-grub and /etc/grub.d/whattask script files
instead of hand editing the config files have been working that way.
I created a pretty simple Fed14 booter as my first attempt in /etc/grub.d.....
#!/bin/sh -e
echo "My First GRUB2 loader Script"
cat << EOF
menuentry "Fed14 - 2.6.35.14-106.fc14.x86_64" {
insmod ext2
set root='(hd0,2)'
search --no-floppy --fs-uuid --set "uuid of /dev/sda2 partition"
linux /vmlinuz.2.6.35.14-106.fc14.x86_64 ro root=UUID="uuid of
/dev/sda3 partition" ro rhgb quiet nouveau.modeset=0
rdblacklist=nouveau
initrd /initramfs-2.6.35.14-106.fc14.x86_64.img
}
EOF
I then ran update-grub and sure enough the contents of this script
appeared in /boot/grub/grub.cfg as expected...
However when I try to boot to this entry I get a file not found error
and then a load a kernel first message.
Also some of the later entries from the 30_os-prober section have been
modified and are now broken
for example....
menuentry "Ubuntu, with Linux 2.6.39.4 (on /dev/sda3)" {
insmod ext2
set root='(hd0,2)'
search --no-floppy --fs-uuid --set "uuid of /dev/sda2"
linux /vmlinuz-2.6.39.4 root=UUID="uuid of /dev/sda5" ro text
splash vga=791
initrd /initrd.img-2.6.39.4
}
menuentry "Ubuntu, with Linux 2.6.35.14-106.fc14.x86_64 (on /dev/sda3)" {
insmod ext2
set root='(hd0,2)'
search --no-floppy --fs-uuid --set "uuid of /dev/sda2"
linux /vmlinuz-2.6.35.14-106.fc14.x86_64 root=/dev/sda5 ro
text splash vga=791
}
The first entry is the genuine Ubuntu install and I assume has been
picked up from the original grub file?
The second entry is actually the Fedora install (even though it says
it's Ubuntu) and as can be seen sets root as /dev/sda5 on the linux
line, this is wrong and doesn't boot, however hand editing it to
/dev/sda3 allows it to boot to the fedora install - does anyone know
why it sets the root to /dev/sda5 even though it says in it's own
generated menuentry it's /dev/sda3?
I know I can hand edit these things to work but would really rather
try to learn the new methodology.
Any ideas folks?
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- I'm confused.....first usage of Grub2.......,
Another Sillyname <=