Ubuntu GRUB and antix - Page 2

dolphin_oracle · posted: 2009-07-22 21:14

Dumb thought, but does the mepis kernel understand the UUID information in the ubuntu-version grub entry. The error messages are almost like it can't find the roof file system specified.

masinick · posted: 2009-07-23 01:09

dolphin_oracle, I would not be able to find the roof file system either, but I jest. You may have a point there. The MEPIS documentation does not mention using UUID, though this is commonly supported. I'd have to see which version of GRUB is being used. IF it is a recent vintage version of GRUB, then the old notations or the more recent UUID notation ought to work.

JawsThemeSwimming428 · posted: 2009-07-23 01:34

The GRUB I was using in the beginning that I couldn't get antiX to boot with was the default GRUB that comes with Ubuntu 9.04. I then installed the antiX 8 GRUB and that allowed Ubuntu 9.04 as well as Windows XP and antiX to boot. Not sure if that helps.

masinick · posted: 2009-07-23 01:56

JawsThemeSwimming428 wrote:The GRUB I was using in the beginning that I couldn't get antiX to boot with was the default GRUB that comes with Ubuntu 9.04. I then installed the antiX 8 GRUB and that allowed Ubuntu 9.04 as well as Windows XP and antiX to boot. Not sure if that helps.

The GRUB that comes with Ubuntu works with UUID, no question about that. But just because it works with UUID does not mean that it sets it up correctly. What I often do, as I showed in my example - and I will show it again, is that I use a config file (you can also use a chainloader approach) to point to each distro's boot loader, and let each distro point to as many kernels as it wants to support or you want to support.

Here is a working example, just an excerpt of my complete /boot/grub/menu.lst. This consistently works. Prerequisite: install GRUB, not to the MBR, but to the ROOT FILE SYSTEM of each distro, then also install GRUB to the MBR on just one of them, then this works beautifully every time:

Code: Select all

## ## End Default Options ##

title        Debian GNU/Linux, kernel 2.6.30-2.slh.1-sidux-686
root        (hd0,7)
kernel        /boot/vmlinuz-2.6.30-2.slh.1-sidux-686 root=UUID=56694975-98d4-49e0-9516-d383eee269b0 ro quiet vga=791
initrd        /boot/initrd.img-2.6.30-2.slh.1-sidux-686

title        Debian GNU/Linux, kernel 2.6.30-1.slh.5-sidux-686
root        (hd0,7)
kernel        /boot/vmlinuz-2.6.30-1.slh.5-sidux-686 root=UUID=56694975-98d4-49e0-9516-d383eee269b0 ro quiet vga=791
initrd        /boot/initrd.img-2.6.30-1.slh.5-sidux-686

title        Debian GNU/Linux, kernel memtest86+
root        (hd0,7)
kernel        /boot/memtest86+.bin

### END DEBIAN AUTOMAGIC KERNELS LIST

title SimplyMEPIS at sda10, newest kernel (sda10)
root (hd0,9)
kernel /boot/vmlinuz root=/dev/sda10 nomce quiet splash vga=791
boot

title Xubuntu 9.04 (hd0,4) sda5
root (hd0,4)
configfile /boot/grub/menu.lst

title antiX at sda7, configfile
root (hd0,6)
configfile /boot/grub/menu.lst

title Karsten LinuxOS (sda6)
root (hd0,5)
configfile /boot/grub/menu.lst

title Kubuntu 9.04 (sda9)
root (hd0,8)
configfile /boot/grub/menu.lst

title        Debian GNU/Linux (hd0,1)
root        (hd0,1)
configfile /boot/grub/menu.lst

title        gOS GNU/Linux (hd0,0)
root        (hd0,0)
configfile /boot/grub/menu.lst

secipolla · posted: 2009-07-23 03:02

I see now. In this case when you choose one of those you jump to another Grub list.

masinick · posted: 2009-07-23 04:02

secipolla wrote:I see now. In this case when you choose one of those you jump to another Grub list.

Yes, that's right. You can do the same thing with chainloader, but with this approach, if you use the config file, it goes to the other system's boot loader and loads that instance. Then you can select whatever that distribution has in its configuration.