Three OS with Lilo

simeon.mattes · 04-07-2009, 09:24 AM

Hi,

I don't know if it is wise what I have done but since slackware uses lilo I wanted to try it.

I have installed in my pc three OS, i.e. Windows, Ubuntu, Slackware.

The easiest way to install these is Windows, Slackware, Ubuntu since grub automatically finds all the OS.

Though because I wanted to install Lilo the order I used was Windows, Ubuntu, Slackware.

The problem I have is with the lilo.conf which is:

Code:

# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/hdb3
  label = CLI
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends

# KDE bootable partition config begins
image = /boot/vmlinuz
  root = /dev/hdb3
  label = KDE
  append = 4
  read-only  # Partitions should be mounted read-only for checking
# KDE bootable partition config ends

# UBUNTU bootable partition config begins
image = /media/ubuntu/boot/vmlinuz-2.6.24-19-rt 
  root = /dev/hdb2
  label = ubuntu
  read-only  # Partitions should be mounted read-only for checking
# UBUNTU bootable partition config ends

# Windows bootable partition config begins
other = /dev/hda1
  label = windows
  table = /dev/hda
# Windows bootable partition config ends

In particular, the system crashes when I boot Ubuntu. Though if I have

Code:

# UBUNTU bootable partition config begins
image = /boot/vmlinuz
  root = /dev/hdb2
  label = ubuntu
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends

there is no problem with ubuntu but kernel 2.6.27.7 is started instead and I want the older one, i.e. 2.6.24-19-rt.

What can I do?

Thanks in Advance

TSquaredF · 04-07-2009, 09:44 AM

Disclaimer: I don't use lilo, just GRUB, but my 2 cents worth would be to move your Ubuntu kernel into '/boot', then change

Quote:

image = /media/ubuntu/boot/vmlinuz-2.6.24-19-rt

to

Quote:

image = /boot/vmlinuz-2.6.24-19-rt

You might also make a simlink, as root

Quote:

ln -s vmlinuz-2.6.24-19-rt ubuntu

then use

Quote:

image = /boot/ubuntu

rocinante · 04-07-2009, 10:30 AM

When you boot Ubuntu, is the path to the kernels /media/ubuntu/boot/vmlinuzXXX ? Or is that the path when you're booted in Slackware, and have the ubuntu partition mounted ?

Assuming the latter, shouldn't the image entry be :

Code:

/boot/vmlinuz-2.6.24-19-rt

since Ubuntu's /boot is where it expects to find it's kernel(s) ?

bgeddy · 04-07-2009, 01:57 PM

Quote:

Assuming the latter, shouldn't the image entry be :
Code:

/boot/vmlinuz-2.6.24-19-rt

since Ubuntu's /boot is where it expects to find it's kernel(s) ?

No - this should be where the Ubuntu disk is mounted under Slackware.

I'm not that familiar with Ubuntu but I thought it used an initial ram disk. If so you'll need to add an entry to your lilo.conf. The initrd should be in the Ubuntu /boot directory and named something like initrd.img-2.6.24-19-rt. If this is the case add this line to the Ubuntu section of lilo.conf:

Code:

initrd=/media/ubuntu/boot/initrd.img-2.6.24-19-rt

and rerun lilo.

metrofox · 04-07-2009, 02:16 PM

I'd use:

Code:

initrd=/dev/hdb2/media/ubuntu/boot/initrd.img-2.6.24-19-rt

OR

Code:

initrd=/media/ubuntu/boot/initrd.img-2.6.24-19-rt root=/dev/hdb2

If the first option shouldn't work use the second one. Any way...Just try it, and do not forget to rerun lilo.

bgeddy · 04-07-2009, 02:49 PM

Quote:

I'd use:

Code:

initrd=/dev/hdb2/media/ubuntu/boot/initrd.img-2.6.24-19-rt

Sorry metrofox but this won't work ! Lilo won't see the initial ram disk at the given directory.

The lilo statement I gave, (your second option), should work fine so long as the disk is mounted to that mount point.

simeon.mattes · 04-07-2009, 03:50 PM

Thanks all for your quick reply.

Actually I got a little bit confused. According to slackware in hdb1 is the swap, in hdb2 is ubuntu and in hdb3 is slackware. I have mounted hdb2 in /media/ubuntu. So in /media/ubuntu there is all the filesystem of ubuntu. So I should write something like this?

Code:

# UBUNTU bootable partition config begins
  initrd=/media/ubuntu/boot/initrd.img-2.6.24-19-rt
  image = /media/ubuntu/boot/vmlinuz-2.6.24-19-rt
  root = /dev/hdb2
  label = ubuntu
  read-only  # Partitions should be mounted read-only for checking
# UBUNTU bootable partition config ends

With this I take as a result when I run lilo the following:

Code:

Warning: LBA32 addressing assumed
Warning: The boot sector and map file are on different disks.
Added CLI *
Warning: The initial RAM disk is too big to fit between the kernel and
   the 15M-16M memory hole.  It will be loaded in the highest memory as
   though the configuration file specified "large-memory" and it will
   be assumed that the BIOS supports memory moves above 16M.
Added KDE ?
Added ubuntu
Added windows
3 warnings were issued.

I want also to ask something else. In /media/ubuntu/boot/grub/there is the configuration file menu.lst of grub which was set up after the installation of ubuntu and before this of slackware.

Code:

title           Ubuntu 8.04.1, kernel 2.6.24-19-rt
root            (hd1,1)
kernel          /boot/vmlinuz-2.6.24-19-rt root=UUID=deb5e720-10b1-4b10-98c0-6b848966252f ro quiet splash
initrd          /boot/initrd.img-2.6.24-19-rt
quiet

title           Ubuntu 8.04.1, kernel 2.6.24-19-rt (recovery mode)
root            (hd1,1)
kernel          /boot/vmlinuz-2.6.24-19-rt root=UUID=deb5e720-10b1-4b10-98c0-6b8
48966252f ro single
initrd          /boot/initrd.img-2.6.24-19-rt

title           Ubuntu 8.04.1, memtest86+
root            (hd1,1)
kernel          /boot/memtest86+.bin
quiet

In order to start right Ubuntu, should I write

Code:

root=UUID=deb5e720-10b1-4b10-98c0-6b848966252f ro quiet splash

also this option in lilo,i.e.

Code:

# UBUNTU bootable partition config begins
  initrd=/media/ubuntu/boot/initrd.img-2.6.24-19-rt
  image = /media/ubuntu/boot/vmlinuz-2.6.24-19-rt
  root = /dev/hdb2
  label = ubuntu
  append = "root=UUID=deb5e720-10b1-4b10-98c0-6b848966252f ro quiet splash"
  read-only  # Partitions should be mounted read-only for checking
# UBUNTU bootable partition config ends

TSquaredF · 04-07-2009, 06:21 PM

Your Ubuntu stanza should be:

Quote:

# UBUNTU bootable partition config begins
image = /boot/vmlinuz-2.6.24-19-rt
root = /dev/hdb2
label = ubuntu
read-only # Partitions should be mounted read-only for checking
# UBUNTU bootable partition config ends

The "/media/ubuntu" part is only applicable when booted into Slackware.
Regards,
Bill

bgeddy · 04-07-2009, 06:27 PM

Please don't take offence but I think your questions would be better asked in the Ubuntu forum as they relate to an Ubuntu install.

For what it's worth here are some pointers ..

Quote:

Actually I got a little bit confused. According to slackware in hdb1 is the swap, in hdb2 is ubuntu and in hdb3 is slackware. I have mounted hdb2 in /media/ubuntu. So in /media/ubuntu there is all the filesystem of ubuntu. So I should write something like this?

Be aware that directory references in lilo.conf are relative to what you are running when lilo is ran - i.e. Slackware.

Quote:

With this I take as a result when I run lilo the following:

I don't think these lilo warnings are fatal - I could be wrong however.

Quote:

In order to start right Ubuntu, should I write

Code:

root=UUID=deb5e720-10b1-4b10-98c0-6b848966252f ro quiet splash

Ubuntu's setup of grub uses the UUID of the disk - this is not necessary. In fact this is just another way of referring to the device.

You may find it easier to install Ubuntu and install grub to the superblock of hdb2 then chainload lilo to run this. However this should not be neccesary.

In any case - does your setup now work ?

bgeddy · 04-07-2009, 06:36 PM

Quote:

Your Ubuntu stanza should be:
Quote:
# UBUNTU bootable partition config begins
image = /boot/vmlinuz-2.6.24-19-rt
root = /dev/hdb2
label = ubuntu
read-only # Partitions should be mounted read-only for checking
# UBUNTU bootable partition config ends
The "/media/ubuntu" part is only applicable when booted into Slackware.
Regards,
Bill

Sorry Bill, I was composing my post when you posted hence the late reply.

However - as I understand it the OP is running lilo from Slackware so the mount point is what should be set in lilo.conf for the kernel and initial ram disk. In other words how Slackware sees the partition. I thought lilo was being ran from a Slackware boot.

simeon.mattes · 04-08-2009, 02:22 AM

Hi again. It's really a mess!!!

With this in my lilo.conf

Code:

# UBUNTU bootable partition config begins
image = /boot/vmlinuz-2.6.24-19-rt
root = /dev/hdb2
label = ubuntu
read-only # Partitions should be mounted read-only for checking
# UBUNTU bootable partition config ends

I get:

Code:

Fatal: open /boot/vmlinuz-2.6.24-19-rt: No such file or directory

With this I understand that while lilo is loaded at the beginning of my system somehow all harddisks have already been mounted. Am I wrong?

Is there any way to load grub through lilo?

brianL · 04-08-2009, 04:27 AM

Try installing grub to Ubuntu's root (/dev/hdb2), then add this to Slackware's lilo.conf:

Code:

other = /dev/hdb2
  label = Ubuntu

And add, just before all the VGA options:
lba32
Then run lilo.

bgeddy · 04-08-2009, 08:26 AM

Quote:

Hi again. It's really a mess!!!

With this in my lilo.conf

Code:

# UBUNTU bootable partition config begins
image = /boot/vmlinuz-2.6.24-19-rt
root = /dev/hdb2
label = ubuntu
read-only # Partitions should be mounted read-only for checking
# UBUNTU bootable partition config ends

I get:

Code:

Fatal: open /boot/vmlinuz-2.6.24-19-rt: No such file or directory

Look Simeon - a lot of people are giving bad advice here which must be confusing you no end. I have mentioned on a few occasions that the lilo stanzas must refer to the directories where Slackware sees the mount points - i.e. this will not work

Quote:

image = /boot/vmlinuz-2.6.24-19-rt

I have supplied the entire lilo.conf that should work. You have to have the Ubuntu disk mounted to /media/ubuntu for this to work.

Code:

# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/hdb3
  label = CLI
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends

# KDE bootable partition config begins
image = /boot/vmlinuz
  root = /dev/hdb3
  label = KDE
  append = 4
  read-only  # Partitions should be mounted read-only for checking
# KDE bootable partition config ends

# UBUNTU bootable partition config begins
  image = /media/ubuntu/boot/vmlinuz-2.6.24-19-rt 
  root = /dev/hdb2
  label = ubuntu
         initrd=/media/ubuntu/boot/initrd.img-2.6.24-19-rt     
 read-only  # Partitions should be mounted read-only for checking
# UBUNTU bootable partition config ends

# Windows bootable partition config begins
other = /dev/hda1
  label = windows
  table = /dev/hda
# Windows bootable partition config ends

This should boot all you OS's no probelm (Don't forget to rerun lilo). Alternatively you may want to try the grub "other" loaded method.

malekmustaq · 04-08-2009, 09:24 AM

simeon.mattes:

I assume in your ubuntu Grub is installed. So if you decide to give up at using lilo from Slack you only need to install grub from ubuntu into the mbr. Then configure menu.lst to point to the Slack kernel as the third default option. This way Grub can boot from all the OS's available in the hard disk including Windows.

I am not well informed about Lilo, I tried it once to load other OS's like youre doing now, but without joy. When I installed this Slackware I am using right now I didn't install any loader, I just configured the Grub menu.lst from other linux in other partition to load this kernel.

Hope it helps.

tommcd · 04-08-2009, 01:56 PM

Quote:

Originally Posted by malekmustaq

simeon.mattes:

I assume in your ubuntu Grub is installed. So if you decide to give up at using lilo from Slack you only need to install grub from ubuntu into the mbr. Then configure menu.lst to point to the Slack kernel as the third default option. This way Grub can boot from all the OS's available in the hard disk including Windows.

This is what I would do also. I have WindowsXP + Ubuntu + Slackware on my system and that is how I do it. IF I were just booting Slackware, or perhaps Slackware + WIndows, then I would probably just use lilo. But for booting multiple linix OSs grub is just easier imo. With lilo, every time there is a kernel update for Ubuntu you will have to boot into Slackware, edit lilo.conf, and rerun lilo before you can boot Ubuntu. With grub, the menu.lst can be edited from either Ubuntu or Slackware. Grub also makes it possible to edit the menu,lst entries 'on the fly' if you need to make changes.
To reinstall grub to the MBR see this:
http://ubuntuforums.org/showthread.p...highlight=fsck
Remeber to select the correct hard disk MBR depending on which disk you want grub installed to.