ap9
asked on
LILO stuck at LI from bootdisk installation
Hi! I'm trying to install Linux on a friend's system, using
Slackware 3.4 (November 97), on a system using an AMD chip and UltraDMA disks (and an EIDE CDROM). I made the boot (bare.i) and rootdisks, but when I try to boot from the bootdisk, it gives me "LI" and stops there.
I looked around on the newsgroup archives, and there are similar questions, but they seem to involve LILO AFTER Linux has been installed to disk (and seem to involve having installed the root partition at >1024 cylinders or what not)-- whereas here I can't even boot into the installation rootdisk!
For reference, I made the boot and rootdisks from within a Win98 DOS window, though I don't see why this should make a difference.
Any help would be appreciated.
Ap9
Slackware 3.4 (November 97), on a system using an AMD chip and UltraDMA disks (and an EIDE CDROM). I made the boot (bare.i) and rootdisks, but when I try to boot from the bootdisk, it gives me "LI" and stops there.
I looked around on the newsgroup archives, and there are similar questions, but they seem to involve LILO AFTER Linux has been installed to disk (and seem to involve having installed the root partition at >1024 cylinders or what not)-- whereas here I can't even boot into the installation rootdisk!
For reference, I made the boot and rootdisks from within a Win98 DOS window, though I don't see why this should make a difference.
Any help would be appreciated.
Ap9
If the bootdisks are working on other computers, it is probably because the system of your friend is faulty.. might even be the processor or memory (mixed different brands ...) . Linux is very hardware sensitive.
Stopping at LI indicates a missing second stage boot loader (i.e. boot.b) or a damaged/wrong /System.map
This usually could be fixed by running lilo again.
For details see lilo man-page.
This usually could be fixed by running lilo again.
For details see lilo man-page.
ASKER
Well, the thing is that Linux isn't even INSTALLED yet. I had just made the bootdisk and tried booting from it, and this happens.
ASKER
Well, the thing is that Linux isn't even INSTALLED yet. I had just made the bootdisk and tried booting from it, and this happens.
Then lilo didn't what you need on you bootdisk.
Check you lilo.conf which you used for the disks, for example following entries:
boot=/dev/fd0
root=/dev/fd0
ramdisk=
Also check lilo's -r -c options.
Check you lilo.conf which you used for the disks, for example following entries:
boot=/dev/fd0
root=/dev/fd0
ramdisk=
Also check lilo's -r -c options.
ASKER
Would these be on the disk itself, or the CDROM? The bootdisks I'm using are straight from the root and bootdsks directory on the CDROM, done via RAWRITE.
Thanks,
AP9
Thanks,
AP9
I would expect that bootdisks from a CDROM distribution work without any modifications, but you never know.
Check the kernel image on the disk with rdev, then you may see if it fits to your environment. If not, you may alter it using rdev (and/or some of its aliases) and/or using lilo as mentioned before.
Please refer to man rdev before.
Check the kernel image on the disk with rdev, then you may see if it fits to your environment. If not, you may alter it using rdev (and/or some of its aliases) and/or using lilo as mentioned before.
Please refer to man rdev before.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.