-----------------------------Lilo way---------------------------

I gave out a lilo.conf in Post #6. All you need to do is to create a text file /etc/lilo.conf with the same content, except replacing sdb6 with sda4. Therefore you can make your Slackware chainloadable by issuing (inside the Slackwareby chroot from Ubuntu) the command
If you want Slackware to take over the MBR you omit the "4" in the "sda4". Once bootable you can then edit lilo.conf to boot the other systems. Read Post #6 again if you need help as a reference has been provided.

-----------------------------------------------Grub way-------------------

In Ubuntu Grub screen instead of selecting a system to boot you can press "c" key to drop into a Grub prompt. You can then boot Slackware manually this way

Ask Grub to tell you which partition has vmlinuz by command
Grub should respond back with (hd0,3) if sda4 holds Slackware. This is directly from the horse's mouth. You might get an answer including (hd0,2) because Ubuntu should have it too.

Having locate positively it is in (hd0,3) you can boot Slackware manually by commands in a Grub prompt
You can choose to boot "vmlinuz-generic-smp-2.6.21.5-smp" too instead of "vmlinuz."

Booting a Linux manually is way to prove the commands needed in menu.lst. Grub responds to each command and a user therefore is able to know any command that Grub has an issue with.

If vmlinuz is unaavilable or vmlinuz-generic-smp-2.6.21.5-smp does boot then it would appears to me a wrong kernel has been installed and a different kernel may have to be sourced from the installation CD/DVD, unless you want to go down arubin's suggested way to create an initrd yourself.

As I have said at nauseum. The official Slackware line is that it is recommended that you use the so-called generic kernel and this does need an initrd. That is not my opinion. That is what Pat Volkerding has written in his instructions for setting up Slackware 12 (and slackware 11 if you want to use the 2.6 kernel supplied)

tenicus.

You should have a file /boot/readme.initrd or something like it. If you want to use the generic kernel you need to follow the instructions in that file.

Alternatively change

/boot/vmlinuz-generic-smp-2.6.21.5-smp ro root=/dev/sda4

to point to the huge kernel by

/boot/vmlinuz-whatever ro root=/dev/sda4

Change vmlinuz-whatever to the file name for the huge kernel. You should find that by having a look at the contents of /boot/

It might be that simple

/boot/vmlinuz ro root=/dev/sda4

works because vmlinuz is a link to the huge kernel

I am not sure, if tenicus found a solution for his problem, but I am in the same boat.

fdisk -l
Disk /dev/sda: 40.0 GB, 40007761920 bytes
255 heads, 63 sectors/track, 4864 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 247 1983996 e W95 FAT16 (LBA)
/dev/sda2 248 381 1076355 82 Linux swap
/dev/sda3 382 1581 9639000 f W95 Ext'd (LBA)
/dev/sda5 382 406 200781 6 FAT16
/dev/sda6 407 540 1076323+ 6 FAT16
/dev/sda7 * 541 798 2072353+ 83 Linux
/dev/sda8 * 799 1581 6289416 83 Linux

menu.lst (excerpt)
title Slackware 12.0
root (hd0,7)
kernel /boot/vmlinuz-huge-2.6.21.5 root=/dev/sda8 ro
boot

Results in:
Kernel panic - not syncing: VFS: unable to mount fs on unknown-block (0,0)

The two FAT16 partitions hold Slax and boot just fine.
Any suggestions?

Thanks.

Try that - it is a snippet from my GRUB menu.lst - no problems booting here. I use the huge-smp kernel currently for no other reason than "just because I can" but you should change it according to what you want to use. Good luck.

Forgot to mention - check your symlinks, too. Never know just what might be going on.

The version of GRUB that accompanies Slackware 12.0 does not support REISERFS.
You will either need to get a later version or patch the existing version.


L8r