Jump to content

Boot third OS?


WilliamS
 Share

Recommended Posts

I admit it - I don't know enough.

Trying to point LILO to boot my test mdk on hdb4, haven't found the right lines to put in /etc/lilo.conf.

The test mandrake - named ml2 - is at hdb4, I use hda. Windose is on hdb1. Everything on hdb1 boots from lilo (mdk is default) when I unplug hda.

Here's my /fstab

 

/dev/hda1 / ext3 defaults 1 1

none /dev/pts devpts mode=0620 0 0

/dev/hda6 /home ext3 defaults 1 2

none /mnt/cdrom supermount dev=/dev/hdc,fs=auto,ro,--,iocharset=iso8859-1,codepage=850,umask=0 0 0

none /mnt/cdrom2 supermount dev=/dev/scd0,fs=auto,ro,--,iocharset=iso8859-1,codepage=850,umask=0 0 0

none /mnt/floppy supermount dev=/dev/fd0,fs=auto,--,iocharset=iso8859-1,sync,codepage=850,umask=0 0 0

/dev/hdb4 /mnt/ml2 ext3 defaults 1 2

/dev/hdb1 /mnt/windows vfat iocharset=iso8859-1,codepage=850,umask=0 0 0

none /proc proc defaults 0 0

/dev/hda5 swap swap defaults 0 0

/dev/hdb3 swap swap defaults 0 0

 

And here is lilo.conf

 

boot=/dev/hda

map=/boot/map

default="linux"

keytable=/boot/us.klt

prompt

nowarn

timeout=100

message=/boot/message

menu-scheme=wb:bw:wb:bw

image=/boot/vmlinuz

label="linux"

root=/dev/hda1

initrd=/boot/initrd.img

append="devfs=mount hdd=ide-scsi acpi=off quiet"

vga=788

read-only

image=/boot/vmlinuz

label="linux-nonfb"

root=/dev/hda1

initrd=/boot/initrd.img

append="devfs=mount hdd=ide-scsi acpi=off"

read-only

image=/boot/vmlinuz

label="failsafe"

root=/dev/hda1

initrd=/boot/initrd.img

append="devfs=nomount hdd=ide-scsi acpi=off failsafe"

read-only

other=/dev/hdb1

label="dos"

table=/dev/hdb

map-drive=0x80

to=0x81

map-drive=0x81

to=0x80

#other=/dev/hdb4

# label=ml2

# table=/dev/hdb

# loader=?

other=/dev/fd0

label="floppy"

unsafe

 

image=/boot/vmlinuz-2.4.21-0.25mdk

label=2421-25

root=/dev/hda1

read-only

optional

vga=788

append=" devfs=mount hdd=ide-scsi acpi=off quiet"

initrd=/boot/initrd-2.4.21-0.25mdk.img

image=/boot/vmlinuz-2.4.21-0.13mdk

label=2421-13

root=/dev/hda1

read-only

optional

vga=788

append=" devfs=mount hdd=ide-scsi acpi=off quiet"

initrd=/boot/initrd-2.4.21-0.13mdk.img

 

I had the first three lines only for hdb4 when I ran lilo -v, and got this:

"Fatal: First section of /dev/hdb4 doesn't have a valid boot signature."

 

 

Can someone tell me what else I need do? :?:

Link to comment
Share on other sites

instead of

 

#other=/dev/hdb4

# label=ml2

# table=/dev/hdb

# loader=?

 

Try:

image=/boot/vmlinuz-2.4.21-0.13mdk (or whatever your boot image is for the test mdk)

label="ml2"

root=/dev/hdb4

initrd=/boot/initrd-2.4.21-0.13mdk.img (or whatever your initrd is)

append=""

read-only

Link to comment
Share on other sites

I always copy my kernel, map, and initrd into my primary /boot. Specify the lables for a particular boot in the lilo section. Here is my lilo:

boot=/dev/hda

map=/boot/map

default="linux"

keytable=/boot/us.klt

prompt

nowarn

timeout=100

message=/boot/message

menu-scheme=wb:bw:wb:bw

disk=/dev/hdd bios=0x81

image=/boot/vmlinuz-2.4.21-0.24mdk

label="linux"

root=/dev/hdd1

initrd=/boot/initrd-2.4.21-0.24mdk.img

append="devfs=mount hdb=ide-scsi hdc=ide-scsi acpi=off"

vga=788

read-only

image=/boot/vmlinuz-2.4.22-6mdk

label="9.2rc2"

root=/dev/hdd8

initrd=/boot/initrd-2.4.22-6mdk.img

append="devfs=mount hdb=ide-scsi hdc=ide-scsi acpi=off"

vga=788

read-only

image=/boot/vmlinuz

label="linux-nonfb"

root=/dev/hdd1

initrd=/boot/initrd.img

append="devfs=mount hdb=ide-scsi acpi=off"

read-only

image=/boot/vmlinuz

label="failsafe"

root=/dev/hdd1

initrd=/boot/initrd.img

append="devfs=nomount hdb=ide-scsi acpi=off failsafe"

read-only

other=/dev/hda1

label="windows_xp"

table=/dev/hda

other=/dev/fd0

label="floppy"

unsafe

Link to comment
Share on other sites

It worked! :D

It booted with a black screen (runlevel 3?) and many inscrutable lines, then made some sleazy offers which I declined (wanna config?)

CDrom 2 not longer will read, but that no problem for the moment.

 

Is there a doc or readme that tells the meaning of what I copied into lilo.config? Couldn't find it in google.

 

Thanks much - will be easier to play now. :D

Link to comment
Share on other sites

Put this in your append line for your new entry:

 

append="devfs=mount hdd=ide-scsi acpi=off quiet"

 

When you installed, your cd writer was set up for scsi emulation and you didn't pass that parameter on your lilo append line(hdd=ide-scsi). If you do that, the system will see the cd writer as new hardware and try to set it up to run without scsi emulation.

Link to comment
Share on other sites

Already filled in the append line, everything works now.

I'm guessing that vga=788 would give the blue boot screen, instead of the black one.

 

Haven't used grub since Lycoris, as several times it stopped loading, and the rescue disk was too mysterious for me. Still don't know what "kermel panic" means.

This maybe not grub, but haven't had a problem with lilo. Yet.

 

Thanks to all, every post good for learning.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...