so - here we go :) Hardware-Detection in progress:
So - from what I see - you have a very interesting setup.
Never saw such kind of setup to be honest.
First drive on IDE-Controller 1 - a DVD-Rom Drive :) Cool. Most probably due to the fact you use the ATA100 Controller for your Harddrives, and the ATA66 controller for the DVD-Rom/CDrom.
So - let's identify the appartenance: IDE-Controller 0 - ATA66 hda: HITACHI DVD-ROM GD-5000, ATAPI CD/DVD-ROM drive - Master bus0 hdc: CR-48X9TE, ATAPI CD/DVD-ROM drive - Master bus 1
IDE-Controller 1 - ATA100 hde: FUJITSU MPG3204AT E, ATA DISK drive - Master Bus 0 hdf: Maxtor 91731U4, ATA DISK drive - Slave Bus 0 hdg: FUJITSU MPA3043ATU, ATA DISK drive - Master Bus 1
So - acfording to the dmesg output - you also disable DMA for boith CD/DVD Rom Drives. I usually ativate these :) Works here :)
MBR is on hde - Good. First Harddisk of IDE-Controller 1 OK - now go to the Lilo stuff.
boot=/dev/hde
map=/boot/map
vga=normal
keytable=/boot/uk.klt
prompt
nowarn
timeout=100
message=/boot/message
menu-scheme=wb:bw:wb:bw
# Here - we tell lilo what the BIOS tells the System upon boot.
disk=/dev/hde bios=0x80
image=/boot/vmlinuz-2.4.19-16mdk
label=Mandrake_9.0-2.
root=/dev/hdf1
initrd=/boot/initrd-2.4.19-16mdk.img
append="nobiospnp mem=512M nopentium devfs=mount hdc=ide-scsi"
read-only
image=/boot/vmlinuz
label=failsafe
root=/dev/hdf1
initrd=/boot/initrd.img
append="failsafe mem=512M nopentium devfs=nomount hdc=ide-scsi"
read-only
other=/dev/hde1
label=windowsOriginal
table=/dev/hde
map-drive=0x80 to=0x81
map-drive=0x81 to=0x80
# My proposal is to try out if the System takes everything as is -
# without the remapping - as the hde is already declared as 0x80 by the # BIOS. Right now - I boot windows from hdc - well - last time I did is
# 4 weeks back.
other=/dev/hde1
label=windows_2
table=/dev/hde
other=/dev/fd0
label=floppy
unsafe
I'm actually missing hde6 in your fstab. Dunno what kernel version was there - but I bet that you could boot it still by adding:
image=/mnt/hde6/boot/vmlinuz-2.4.<your kernel version>
label=Mandrake_8.2
root=/dev/hde6
initrd=/mnt/hde6/boot/initrd-2.4.19-16mdk.img
append="nobiospnp mem=512M nopentium devfs=mount hdc=ide-scsi"
read-onlyYou need to take into account that you have to mount your /dev/hde6 partition under /mnt/hde6 before you execute lilo. Be very carefull to not execute lilo under Mandrake 8.2 though - as it would overwrite your Master Boot record again - and make it not possible for you to boot into 9.0 :)
Back in time - I used another trick for that kind of setups. Very easy - but very efficient.
I installed on the old operating Linux partition the lilo into the partition table of my root-partition while running under OS that version - means in your case under Mandrake-8.2:
boot=/dev/hde6
map=/boot/map
vga=normal
keytable=/boot/uk.klt
prompt
nowarn
timeout=0
message=/boot/message
menu-scheme=wb:bw:wb:bw
# Here - we tell lilo what the BIOS tells the System upon boot.
disk=/dev/hde bios=0x80
image=/boot/vmlinuz-<your kernel version>
label=Mandrake_8.2
root=/dev/hdf1
initrd=/boot/initrd-<your kernel version>
append="nobiospnp mem=512M nopentium devfs=mount hdc=ide-scsi"
read-onlyExecute Lilo - then boot into the new version, and append only a little:
other=/dev/hde6
label=Mandrake_8.2
table=/dev/hdeIt has one advantage - you won't write with one LILO into the partition of the other LILO - and you can update your kernels under both operating systems without having to fear you go out of sync anywhere, or overwriting the Lilo-information of the other OS-Version.
The Drawback is that you'll have to navigate through 2 LILO's.
That's also the reason I did set the timeout message to 0. Holding the Ctrl-Key down while going into the second-Lilo instance will give you the ability to add something though ;)
Please note that you might need to tweak the settings a little bit.
Back in time - it was easyer to cheat on lilo. They have built many logical-Checkings into it - to prevent from user-mistakes, if they don't know what to do. I still prefere doing the lilo.conf using vi :) Hardcore way :)
Note2: If the LIlO tells you he made a mistake - don't reboot as long as you have not fixed it ;) usually lilo should write only if syntax and logic checkings have occured - but I happened to have screwed my lilo install several times. Always keep a Bootdisk by hand that works before fiddling with lilo ...
Cheers
Joerg -- ------------------------------------------------------------------------ | Joerg Mertin : [EMAIL PROTECTED] (Home)| | in Neuchâtel/Schweiz : [EMAIL PROTECTED] (Work)| | Stardust's LiNUX System : | | PGP 2.6.3in Key on Demand : Voice & Fax: +41(0)32 / 725 52 54 | ------------------------------------------------------------------------ Home-Page: http://www.solsys.org
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
