lilo + Slackware + Slamd64

Daedra · 02-19-2009, 05:06 PM

I thought I would give Slamd64 a try since I bought a old hard drive off of a friend of mine. Anyway I installed windows first then Slackware and then slamd64. The problem I am having is during the install of slamd64 i choose not to install lilo since its already installed with slackware. After the install of slamd64 I reboot into slackware and add a line in /etc/lilo.conf for slamd64 and reboot. However everytime I try to boot slamd64 I get a kernel panic because its not mounting the root file system in time so it panics. I am pretty sure its a lilo problem, here is the relevant section of my lilo.conf. Can someone point me in the right direction

# Windows bootable partition config begins
other = /dev/sda1
label = Windows
table = /dev/sda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sdb1
label = Linux
append = "video=uvesafb:1920x1200-32,mtrr:3,ywrap"
read-only
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sdc1
label = slamd64
#append = "video=uvesafb:1920x1200-32,mtrr:3,ywrap"
read-only
# Linux bootable partition config ends

Alien Bob · 02-19-2009, 05:20 PM

For the slamd64 label, you boot your Slackware 32bit kernel and then tell it to use a root filesystem populated with 64bit binaries... that will not work.

Instead, you will have to instruct slamd64's lilo to install itself into the slamd64 root partition and then tell Slackware's lilo (which resides in the MBR) to chainload slamd64. This is what the slamd64 section should look like in Slackware's /etc/lilo.conf:

Code:

# Linux bootable partition config begins
other = /dev/sdc1
label = slamd64

Eric

Didier Spaier · 02-19-2009, 05:23 PM

Foe slamd64, 'image = /boot/vmlinuz' is wrong.

While under Slackware you should mount /dev/scd1 somewhere (e.g. /mnt/slamd64, after having made that directory) and write 'image = /mnt/slamd64/boot/vmlinuz' in lilo.conf for it.

Otherwise lilo would take the Slackware image to boot Slamd64.

Then check with 'lilo -t -v' before issuing 'lilo'.

[EDIT, Eric's response not seen before posting] Or do what Eric propose, he knows better than me how lilo work.

Daedra · 02-20-2009, 12:36 AM

Quote:

Originally Posted by Alien Bob

For the slamd64 label, you boot your Slackware 32bit kernel and then tell it to use a root filesystem populated with 64bit binaries... that will not work.

Instead, you will have to instruct slamd64's lilo to install itself into the slamd64 root partition and then tell Slackware's lilo (which resides in the MBR) to chainload slamd64. This is what the slamd64 section should look like in Slackware's /etc/lilo.conf:

Code:

# Linux bootable partition config begins
other = /dev/sdc1
label = slamd64

Eric

Thanks Eric, that worked perfectly