Hi,
I have a dedicated grub2 partition from where I can chainload into my arch linux grub2 with
Code:
menuentry "Arch Linux" {
insmod ext2
set root='(hd0,6)'
search --no-floppy --fs-uuid --set d2c1d2c1-6b8e-4e9d-827b-1239bc470395
chainloader +1
}
now i'd also like to go back to the grub partition, so I added this to the arch grub2:
Code:
menuentry 'OS Selector' {
insmod ext2
set root='(hd0,3)' #this is sda3
chainloader +1
}
but just get 'invalid signature' errors.
what am i doing wrong?
Okay, after another 87 reboots I got it figured out now.
Apparently grub 1.98 still uses 'chainloader' for stuff like Windows, while grub itself works more like starting a linux kernel, using the 'multiboot' keyword instead of 'linux' though, and then pointing to the right file (grub-kernel-image: core.img). The result looks like this:
Code:
menuentry 'OS Selector' {
search --fs-uuid --set f5d9c7fc-23eb-4473-abb6-5f11fc6c3c1b
multiboot /boot/grub/core.img
}
the 'search...' line can be replaced with a conventional 'root (hdX,Y)', but I like it better this way, as moving around partitions won't affect it. Maybe it's even valid to use both; grub2 documentation is rather sparse though..
One thing I still don't get straight, is why 'chainloader +1' still works in the first instance of grub (which might be v1.96 , maybe that's why..).