barjac wrote:FWIW Mageia uses legacy grub - Ubuntu uses grub2.
Ubuntu has a bug in it's OS-prober that stops it adding Mageia (or Mandriva) to it's menu correctly.
Mageia (and any distro with legacy grub AFAIK) cannot add systems using grub2 to the boot menu automatically.
barjac wrote:Both of the above problems have relatively easy workarounds
Ecky wrote:...mind giving me a hint? I'd like to make friends with Mageia but she doesn't seem to get along with my old pal Ubuntu, it's either one or the other!
sudo gedit /boot/grub/grub.cfg
menuentry "linux (on /dev/sdb7)" {
insmod ext2
set root='(hd1,7)'
search --no-floppy --fs-uuid --set 9d93628f-b81a-4e6d-a436-173697556020
linux /boot/vmlinuz BOOT_IMAGE=linux root=UUID=9d93628f-b81a-4e6d-a436-173697556020 resume=UUID=1097bb8c-3820-4b3a-b796-b417c9aa56d8 splash=silent vga=788
initrd (hd1,6)/boot/initrd.img
wobo wrote:Ubuntu installed after all others. Ubuntu's grub menue shows all present systems (windows, 2x mageia), even the rescue system of Windows. So I was surprised reading about that "bug" in Ubuntu's grub.
barjac wrote:Did you look at the grub.cfg in your Ubuntu install and check the Mageia entry?
Is it correct, or does OS-prober still get it wrong ?
wobo wrote:I wonder why so many people jump through all those loops instead using chainloader.
Ecky wrote:wobo wrote:I wonder why so many people jump through all those loops instead using chainloader.
I don't (wonder). If you read carefully my previous message, you may get a hint.
wobo wrote:Reading all this makes me wonder why I do not write such a nice HowTo as mentioned in my first paragraph. But of course nobody will read it before he comes to the forum with a borked system (such as yours).
wobo wrote:while it is so easy and uncomplicated.
Say, I start out with a distribution A using grub legacy. I let the install system put that into the MBR, so in the boot menue I have SYSTEM A, SYSTEM A failsafe and (if on the hd) Windows.
Now I install distribution B with grub2. I let the installer install the bootloader into the root partition of SYSTEM B.
Then I boot SYSTEM A and edit the /boot/grub/menu.lst and add 3 lines:
label SYSTEM B
root (0,x)
chainloader +
Advantages:
- it does not matter what version of grub is in distribution B
title Ubuntu 9.10 (grub 2)
root (0,6)
kernel /boot/grub/core.img
barjac wrote:To boot into grub2 from grub you will probably need an entry in menu.lst of the form:-
- Code: Select all
title Ubuntu 9.10 (grub 2)
root (0,6)
kernel /boot/grub/core.img
...unless you are very lucky.
I have heard of rare cases where chainloading works - and you may be one of these, but in general the above method is more reliable.
Users browsing this forum: Google [Bot] and 1 guest