LILO stuck at LI from bootdisk installation

Posted on 1998-08-02
Last Modified: 2013-12-15
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.

Question by:ap9
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions

Expert Comment

ID: 1629108
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.

LVL 51

Expert Comment

ID: 1629109
Stopping at  LI  indicates a missing second stage boot loader (i.e. boot.b) or a damaged/wrong /
This usually could be fixed by running lilo again.
For details see lilo man-page.

Author Comment

ID: 1629110
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.

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!


Author Comment

ID: 1629111
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.

LVL 51

Expert Comment

ID: 1629112
Then lilo didn't what you need on you bootdisk.
Check you lilo.conf which you used for the disks, for example following entries:


Also check lilo's   -r  -c   options.

Author Comment

ID: 1629113
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.


LVL 51

Expert Comment

ID: 1629114
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.

Accepted Solution

Riva earned 200 total points
ID: 1629115
I had the same problem once.
But it disappeared when I recreated the boot and rootdisks from DOS instead of from Windows DOS-shell.

2nd thing to mention is that Windows98 uses FAT32x which is different from Windows95 FAT32. So their Windows DOS-shell is different (works differently);

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Setting up Secure Ubuntu server on VMware 1.      Insert the Ubuntu Server distribution CD or attach the ISO of the CD which is in the “Datastore”. Note that it is important to install the x64 edition on servers, not the X86 editions. 2.      Power on th…
SSH (Secure Shell) - Tips and Tricks As you all know SSH(Secure Shell) is a network protocol, which we use to access/transfer files securely between two networked devices. SSH was actually designed as a replacement for insecure protocols that sen…
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
Connecting to an Amazon Linux EC2 Instance from Windows Using PuTTY.

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question