problems with lilo - difference sda and hda in opensuse 11.1 and slackware 12.2

seancrawford · 02-21-2009, 02:01 AM

I have a perfectly functioning Slackware 12.2 system and wanted to try out opensuse to see what the differences are. The suse with kde4live started from CD without any problem. The installation process worked fine except I couldn't install grub. So I added
# Suse 11.1 begins
image = /boot/vmlinuz-2.6.27.7-9-default
initrd = /boot/initrd-2.6.27.7-9-default
root = /dev/hdb1
label = Open-SUSE
read-only
# Suse bootable partition config ends
to my lilo.conf and executed lilo. Then I copied the kernel vmlinuz-2.6.27.7-9-default to my /boot folder on /dev/hda1 where the slackware system is.

If I try to start suse from the lilo menu everything starts out fine. However after identifying all the usb-devices the folowing line appears and the boot process stops. :
waiting for /dev/root to appear ........
I assumed it was a problem with the different names for the hard disc drives in suse and slackware. Suse calls them sda, sdb, ... In Slackware it's hda, hdb, ... So I changed my lilo.conf to:
# Suse 11.1 begins
image = /boot/vmlinuz-2.6.27.7-9-default
initrd = /boot/initrd-2.6.27.7-9-default
root = /dev/sdb1
label = Open-SUSE
read-only
# Suse bootable partition config ends
and added a link /dev/sdb1 pointing to /dev/hdb1 in the Slackware system because without it, lilo wouldn't write the MBR anew. Unfortunately, the problem remains.

HELP, please!

Drakeo · 02-21-2009, 07:08 PM

I have Know Idea what your trying to say ok. But what I gather is.
1 gather you installed Suse And you changed your lilo.conf file so you need to be in the system your are running to do this and then you must run as root lilo or /sbin/lilo
two if you want to install grub for slackware down load it it is in slackware 12.2 extra.
install it run grubconf then go back and edit your /grub/menu.1st

2 if you want to change lilo the esay way is to open kde control admin configure boot then youu will see lilo does everything through a host OS . look at my lilo and you will see.

Quote:

image="/boot/vmlinuz"
root="/dev/hda1"
label="Linux"
read-only
# Linux bootable partition config ends

image=/mnt/hda2/boot/vmlinuz24
label="slack12.1-24"
root=/dev/hda2
read-only

image=/mnt/hda2/boot/vmlinuz27
label="slack12.1-27"
root=/dev/hda2
read-only

image=/mnt/hdb1/boot/vmlinuz-2.6.18.8.tex5
label="pcl2007"
root=/dev/hdb1
read-only
initrd="/mnt/hdb1/boot/initrd-2.6.18.8.tex5.img"
append="acpi=on resume=/dev/hda3 splash=silent"

image=/mnt/hdc1/boot/vmlinuz-2.6.24-22-generic
label="gos3"
root=/dev/hdc1
read-only
initrd="/mnt/hdc1/boot/initrd.img-2.6.24-22-generic"

image="/pup412/vmlinuz"
label="pup412"
initrd="/pup412/initrd.gz"

image="/mnt/hda2/boot/vmlinuz"
label="slack12.1-28"
root="/dev/hda2"
read-only

seancrawford · 02-22-2009, 02:31 AM

Quote:

Originally Posted by Drakeo

I have Know Idea what your trying to say ok. But what I gather is.
1 gather you installed Suse And you changed your lilo.conf file so you need to be in the system your are running to do this and then you must run as root lilo or /sbin/lilo
two if you want to install grub for slackware down load it it is in slackware 12.2 extra.
install it run grubconf then go back and edit your /grub/menu.1st

2 if you want to change lilo the esay way is to open kde control admin configure boot then youu will see lilo does everything through a host OS . look at my lilo and you will see.

Sorry to tell you, but you really have no idea what I'm talking about. Editing lilo is not the problem. Thanks anyway

Drakeo · 02-22-2009, 09:14 PM

Quote:

to my lilo.conf and executed lilo. Then I copied the kernel vmlinuz-2.6.27.7-9-default to my /boot folder on /dev/hda1 where the slackware system is.

the reason why lilo will not write to mbr. boot. look at the out put. Thanks any ways

Reuti · 02-23-2009, 11:22 AM

I noticed it also once in a system, and I had to fiddle with unusual lilo.conf settings IIRC:

disk=/dev/hdb
bios=0x80
disk=/dev/hda
bios=0x81

Maybe similar things also help in your case.