PDA

View Full Version : Post Hdd install boot (lilo) question



bigjohn
09-28-2003, 08:27 PM
Having just finished doing the hard disc install, I followed the instructions at the FAQ's and most things have gone well.

So far the only major thing that I can't do is boot it with lilo. Below is the extract that dealt with the debian install that I have installed the knoppix 3.3 over the top of.

image=/debian/vmlinuz
label="debian"
root=/dev/hda4
initrd=/debian/boot/initrd.img
append="devfs=mount hdc=ide-scsi acpi=off"
vga=normal
read-only

Apart from the label and root directory, can anyone tell me what I need to change or modify to get it to boot the knoppix install please?

Many thanks.

regards

John

Stephen
09-28-2003, 10:19 PM
image=/debian/vmlinuz
label="debian"
root=/dev/hda4
initrd=/debian/boot/initrd.img
append="devfs=mount hdc=ide-scsi acpi=off"
vga=normal
read-only



Change to:


image=/vmlinuz
label="debian"
root=/dev/hda4
initrd=/boot/initrd.img
append="hdc=ide-scsi acpi=off"
vga=normal
read-only

bigjohn
09-28-2003, 10:57 PM
Cheers for the pointer Stephen,

I changed it to be the same as per your post, the only difference is that I left it as

image=/boot/vmlinuz

Which started it, but dropped me into a command prompt, level 2 or is it 3?

so I logged in, and tried the "kdm" but had to su to root, and then it wouldn't start kde or kdm.

Have you any other suggestions that I might try? Oh, and I can still boot into debian/knoppix with the floppy, but when I try to see if anything on the floppy might help, I get /mnt/floppy file or directory no longer exists.

regards

John

bigjohn
09-28-2003, 11:15 PM
Well,

I just went back and changed it to



image=/vmlinuz

to see if that made any difference, but no.

One thing that I did notice, was that when it was booting (having selected debian) It seemed to be trying to boot the mandrake kernel version - and gave loads of errors refering to that.

Though when I boot with the floppy, it seems to boot correctly.

Any idea's what I need to do??

regards

John

Stephen
09-28-2003, 11:36 PM
Well,

I just went back and changed it to



image=/vmlinuz

to see if that made any difference, but no.

One thing that I did notice, was that when it was booting (having selected debian) It seemed to be trying to boot the mandrake kernel version - and gave loads of errors refering to that.

Though when I boot with the floppy, it seems to boot correctly.

Any idea's what I need to do??

regards

John
You could just chainload to your knoppix install use:


other=/dev/hda4
label=Knoppix

in your Mandrake lilo and after having booted from the floppy /sbin/lilo -b /dev/hda4 to write lilo to your / partition instead of your MBR then when you select Knoppix from your Mandrake lilo you will get another lilo to boot the actual install. Alternatively you could copy vmlinuz from your /dev/hda4 root Knoppix directory to your Mandrake / and it will use that kernel image to boot with instead of trying to use your Mandrake kernel to boot the knoppix root you will most likely need to rename it something like vmlinuz-knoppix to stop it from overwriting your Mandrake one.

With the floppy error you should try to access it by just /floppy that should be there or if not then /dev/fd0 that is guarenteed to exist.

oscar
09-29-2003, 12:40 AM
Cheers for the pointer Stephen,

I changed it to be the same as per your post, the only difference is that I left it as

image=/boot/vmlinuz




John

image=/boot/vmlinuz ?

look into your boot directory, knoppix kernel
is something like

vmlinuz-2.4.20-xfs

then
image=/boot/vmlinuz-2.4.20-xfs

bigjohn
09-29-2003, 02:45 AM
Edited due to total "balls up"

bigjohn
09-29-2003, 06:22 AM
well, after 8 or 9 hours of messing about, it still won't boot from the hard drive.

I have reburned the disc, re-installed about 4 or 5 times, and have managed to get things back to "square 1"

The only difference being, that last time I re-installed, I managed to install a boot loader with the knoppix.

I then checked the /etc/lilo.conf and got the details that should have been in the mandrake bootloader in the first place.

I have then re-installed the mandrake bootloader and modified the knoppix entry to read

image=/boot/vmlinuz-2.4.22-xfs
label="Knoppix"
root=/dev/hda4
initrd=/boot/initrd.gz
append="hdc=ide-scsi acpi=off"
vga=normal
read-write

and as far as I can tell, this entry should be correct.

But it still won't boot the knoppix install.

The only apparent way of booting into knoppix is with a boot floppy.

I can only presume that there is more to it than what I have managed to find out (which isn't much!).

Does anyone have any other idea's please?

regards

John

Stephen
09-29-2003, 06:27 AM
Have you copied the vmlinuz and possibly the initrd.gz of knoppix to your mandrake install that is where it will be looking for it and have you tried just chainloading it like I suggested above?

bigjohn
09-29-2003, 02:43 PM
could you elaborate on that please Stephen, i.e. how would I do that?

regards

John

p.s. Sorry if it sounds like a stupid question, my linux/mandrake/debian/knoppix knowledge is that vast, I could write it all on the back of a very small postage stamp :D

oscar
09-29-2003, 07:12 PM
p.s. Sorry if it sounds like a stupid question, my linux/mandrake/debian/knoppix knowledge is that vast, I could write it all on the back of a very small postage stamp :D

cut&paste your full lilo.conf
Do you know that after editing lilo.conf you must run
lilo -v ?

bigjohn
10-02-2003, 08:27 AM
OK, this is my lilo.conf (I have it in the mandrake install - the person who helped me before said something about not having a lilo.conf in a debian/knoppix install as well as the one in mandrake due to possible conflicts).

boot=/dev/hda
map=/boot/map
vga=normal
default="XP"
keytable=/boot/uk.klt
prompt
nowarn
timeout=100
message=/boot/message
menu-scheme=wb:bw:wb:bw
image=/boot/vmlinuz
label="Mandrake"
root=/dev/hda3
initrd=/boot/initrd.img
append="quiet noapic devfs=mount hdc=ide-scsi acpi=off"
vga=788
read-only
image=/boot/vmlinuz-2.4.22-xfs
label="Knoppix"
root=/dev/hda4
initrd=/boot/initrd.gz
append="hdc=ide-scsi acpi=off"
vga=normal
read-write
image=/boot/vmlinuz
label="linux-nonfb"
root=/dev/hda3
initrd=/boot/initrd.img
append="noapic devfs=mount hdc=ide-scsi acpi=off"
read-only
image=/boot/vmlinuz
label="failsafe"
root=/dev/hda3
initrd=/boot/initrd.img
append="failsafe noapic devfs=nomount hdc=ide-scsi acpi=off"
read-only
other=/dev/hda1
label="XP"
table=/dev/hda
other=/dev/fd0
label="floppy"
unsafe


Also, below is the output of "lilo -v" command

[root@localhost john]# lilo -v
LILO version 22.4.1, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2002 John Coffman
Released 27-Jan-2003 and compiled at 11:11:26 on Feb 5 2003.

Reading boot sector from /dev/hda
Using GRAPHIC secondary loader
Calling map_insert_data
Mapping message file /boot/message -> message-graphic
Calling map_insert_file

Boot image: /boot/vmlinuz -> vmlinuz-2.4.21-0.13mdk
Mapping RAM disk /boot/initrd.img -> initrd-2.4.21-0.13mdk.img
Added Mandrake

Boot image: /boot/vmlinuz-2.4.22-xfs
Mapping RAM disk /boot/initrd.gz
Added Knoppix

Boot image: /boot/vmlinuz -> vmlinuz-2.4.21-0.13mdk
Mapping RAM disk /boot/initrd.img -> initrd-2.4.21-0.13mdk.img
Added linux-nonfb

Boot image: /boot/vmlinuz -> vmlinuz-2.4.21-0.13mdk
Mapping RAM disk /boot/initrd.img -> initrd-2.4.21-0.13mdk.img
Added failsafe

Boot other: /dev/hda1, on /dev/hda, loader CHAIN
Added XP *

Boot other: /dev/fd0, loader CHAIN
Pseudo partition start: 0
Added floppy

/boot/boot.0300 exists - no backup copy made.
Writing boot sector.
[root@localhost john]#

I thought it might be pertinent to include the lilo -v stuff, though I don't really know how to interpret it.

Any suggestions much appreciated.

regards

John

oscar
10-03-2003, 04:03 AM
try this
copy&paste to /etc/lilo.conf and the run lilo -v
(note that this must be image=/mnt/hda4/boot/vmlinuz-2.4.22-xfs and not image=/boot/vmilnuz-.....)


boot=/dev/hda
map=/boot/map
vga=normal
default="XP"
keytable=/boot/uk.klt
prompt
nowarn
timeout=100
message=/boot/message
menu-scheme=wb:bw:wb:bw

image=/boot/vmlinuz
label="Mandrake"
root=/dev/hda3
initrd=/boot/initrd.img
append="quiet noapic devfs=mount hdc=ide-scsi acpi=off"
vga=788
read-only

image=/mnt/hda4/boot/vmlinuz-2.4.22-xfs
label="Knoppix"
root=/dev/hda4
#initrd=/boot/initrd.gz
append="hdc=ide-scsi acpi=off"
vga=normal
read-only

image=/boot/vmlinuz
label="linux-nonfb"
root=/dev/hda3
initrd=/boot/initrd.img
append="noapic devfs=mount hdc=ide-scsi acpi=off"
read-only

image=/boot/vmlinuz
label="failsafe"
root=/dev/hda3
initrd=/boot/initrd.img
append="failsafe noapic devfs=nomount hdc=ide-scsi acpi=off"
read-only

other=/dev/hda1
label="XP"
table=/dev/hda
other=/dev/fd0
label="floppy"
unsafe

bigjohn
10-03-2003, 02:47 PM
Ok, the lilo.conf looks like this now

boot=/dev/hda
map=/boot/map
vga=normal
default="XP"
keytable=/boot/uk.klt
prompt
nowarn
timeout=100
message=/boot/message
menu-scheme=wb:bw:wb:bw
image=/boot/vmlinuz
label="Mandrake"
root=/dev/hda3
initrd=/boot/initrd.img
append="quiet noapic devfs=mount hdc=ide-scsi acpi=off"
vga=788
read-only
image=/mnt/hda4/boot/vmlinuz-2.4.22-xfs
label="Knoppix"
root=/dev/hda4
#initrd=/boot/initrd.gz
append="noapic devfs=mount hdc=ide-scsi acpi=off"
vga=normal
read-write
image=/boot/vmlinuz
label="linux-nonfb"
root=/dev/hda3
initrd=/boot/initrd.img
append="noapic devfs=mount hdc=ide-scsi acpi=off"
read-only
image=/boot/vmlinuz
label="failsafe"
root=/dev/hda3
initrd=/boot/initrd.img
append="failsafe noapic devfs=nomount hdc=ide-scsi acpi=off"
read-only
other=/dev/hda1
label="XP"
table=/dev/hda
other=/dev/fd0
label="floppy"
unsafe

But when I run lilo, I get this


[root@localhost john]# lilo -v
LILO version 22.4.1, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2002 John Coffman
Released 27-Jan-2003 and compiled at 11:11:26 on Feb 5 2003.

Reading boot sector from /dev/hda
Using GRAPHIC secondary loader
Calling map_insert_data
Mapping message file /boot/message -> message-graphic
Calling map_insert_file

Boot image: /boot/vmlinuz -> vmlinuz-2.4.21-0.13mdk
Mapping RAM disk /boot/initrd.img -> initrd-2.4.21-0.13mdk.img
Added Mandrake

Boot image: /mnt/hda4/boot/vmlinuz-2.4.22-xfs
Fatal: open /mnt/hda4/boot/vmlinuz-2.4.22-xfs: No such file or directory
[root@localhost john]#

That's the first time I've had a problem with lilo. I presume that that means that it can't see the boot image.

regards

John

oscar
10-03-2003, 05:22 PM
Boot image: /mnt/hda4/boot/vmlinuz-2.4.22-xfs
Fatal: open /mnt/hda4/boot/vmlinuz-2.4.22-xfs: No such file or directory
[root@localhost john]#

is your knoppix partition /mnt/hda4 or is it anyelse?
is your knoppix partition mounted?

cut&paste here your /etc/fstab file

bigjohn
10-03-2003, 06:29 PM
Oscar,

I managed to get something working, but it was wrong, because it would boot the knoppix but not the mandrake - I got a kernel panic when booting into mandrake.

so I have re-installed the mandrake and now I'm back to square one.

Which might be good - as it is starting fresh.

So here's the /etc/fstab

/dev/hda3 / ext3 defaults 1 1
/dev/hda4 /Knoppix ext3 defaults 1 2
none /dev/pts devpts mode=0620 0 0
none /mnt/cdrom supermount dev=/dev/hdb,fs=auto,ro,--,iocharset=iso8859-15,codepage=850,umask=0 0 0
none /mnt/cdrom2 supermount dev=/dev/scd0,fs=auto,ro,--,iocharset=iso8859-15,codepage=850,umask=0 0 0
none /mnt/floppy supermount dev=/dev/fd0,fs=auto,--,iocharset=iso8859-15,sync,codepage=850,umask=0 0 0
/dev/hda1 /mnt/windows ntfs iocharset=iso8859-15,ro,umask=0 0 0
none /proc proc defaults 0 0
/dev/hda2 swap swap defaults 0 0

And here's the lilo.conf as it stands at the moment.

boot=/dev/hda
map=/boot/map
vga=normal
default="XP"
keytable=/boot/uk.klt
prompt
nowarn
timeout=100
message=/boot/message
menu-scheme=wb:bw:wb:bw
image=/boot/vmlinuz
label="Mandrake"
root=/dev/hda3
initrd=/boot/initrd.img
append="quiet devfs=mount hdc=ide-scsi acpi=off"
vga=788
read-only
image=/boot/vmlinuz
label="knoppix"
root=/dev/hda4
initrd=/boot/initrd.gz
append="devfs=mount apm=power-off hdc=scsi initrd=initrd.gz"
vga=791
read-only
image=/boot/vmlinuz
label="linux-nonfb"
root=/dev/hda3
initrd=/boot/initrd.img
append="devfs=mount hdc=ide-scsi acpi=off"
read-only
image=/boot/vmlinuz
label="failsafe"
root=/dev/hda3
initrd=/boot/initrd.img
append="failsafe devfs=nomount hdc=ide-scsi acpi=off"
read-only
other=/dev/hda1
label="XP"
table=/dev/hda

other=/dev/fd0
label="floppy"
unsafe

As I'm not entirely sure how it actually all works, is it that the lilo.conf can't see either the knoppix version of vmlinuz... or the initrd.gz ? So does it need a copy of both on /dev/hda4 ? because it can see them on the floppy, but doesn't seem to see them on the hard disc - Or have I "got the wrong end of the stick?"

regards

John

oscar
10-04-2003, 03:14 AM
change this in lilo.conf

image=/boot/vmlinuz
label="knoppix"
root=/dev/hda4
initrd=/boot/initrd.gz
append="devfs=mount apm=power-off hdc=scsi initrd=initrd.gz"
vga=791
read-only

to this

image=/Knoppix/boot/vmlinuz-2.4.22-xfs
label="knoppix"
root=/dev/hda4
#initrd=/Knoppix/boot/initrd.gz
append="devfs=mount apm=power-off hdc=scsi "
vga=791
read-only


then run

mount -rw /dev/hda4 /Knoppix (in order to mount yor knoppix partition)


then goto to /Knoppix/boot to confirm that vmlinuz-2.4.22-xfs is there

now you may run lilo -v

oscar
10-04-2003, 03:36 AM
an alternative is to boot into knoppix with the diskette
and copy the following to /etc/lilo.conf

boot=/dev/hda
map=/boot/map
vga=normal
default="Windows"
#keytable=/boot/uk.klt
prompt
nowarn
timeout=200
message=/boot/message
#menu-scheme=wb:bw:wb:bw


image=/mnt/hda3/boot/vmlinuz
label="Mke-hda3"
root=/dev/hda3
#initrd=/boot/initrd.img
append="quiet devfs=mount hdc=ide-scsi acpi=off"
vga=788
read-only

image=/boot/vmlinuz-2.4.22-xfs
label="knpx-hda4"
root=/dev/hda4
initrd=/boot/initrd.gz
append="devfs=mount apm=power-off hdc=scsi initrd=initrd.gz"
vga=791
read-only

other=/dev/hda1
label="Windows"
#table=/dev/hda


then run
kdf
right clik over /dev/hda3 (mandrake)
mount /dev/hd3 mandrake (if it is not mounted yet)

then run lilo -v

bigjohn
10-04-2003, 06:43 PM
Yippeeeeeeeeeeeeeeee!

Many many thanks for your extended assistance Oscar (and all the others who have posted ideas and suggestions)

I tried the first of the solutions and it seems to have worked a treat. I just wish that the publishers of the "dummies" series,produced an "Almanack" of IT terminology - then I might also be in a position to offer such excellent assistance (but I suppose thats the price I have to pay, not working in IT - and lets face it, truck drivers are well known for our "incredible interlectual abilities" :D)

again, many thanks

regards

John :D:D:D