Strange LILO problem

Strange LILO problem

Post by Nic » Tue, 30 Sep 1997 04:00:00



Hey, I just finished installing DEBIAN 1.3.0 linux and everything
works pretty fine.  Well, everything except for LILO.  Whenever I try
to boot the system after it's installed it says "LI" and then just
pauses forever.  

When I first installed LILO I got this weird error:

ide: probable bad entry for dev/hdc
ide: run usr/src/linux/scripts/MAKEDEV.ide to fix it
warning: Bios Drive 0x82 may not be accessible

I installed Debian Linux to my 840mb Western Digital drive that is my
primary drive on my secondary controller.  I currently have the
following on my controllers:

Primary Controller
1.6 gig hard drive (2 dos partitions) /dev/hda1 and /dev/hda5
1.6 gig hard drive (2 dos partitions) /dev/hdb1 and /dev/hdb5

Secondary Controller
840mb hard drive (linux swap & native paritions) /dev/hdc1 & /dev/hdc5
Sanyo 6X IDE CD-ROM drive

So, what exactly is the problem?  Everything works fine other than
this.  Thanks

Nick Vlku,

 
 
 

Strange LILO problem

Post by Ohad Somj » Tue, 30 Sep 1997 04:00:00



>Hey, I just finished installing DEBIAN 1.3.0 linux and everything
>works pretty fine.  Well, everything except for LILO.  Whenever I try
>to boot the system after it's installed it says "LI" and then just
>pauses forever.  

how come everything works fine when you can't start linux ???

Quote:>When I first installed LILO I got this weird error:

>ide: probable bad entry for dev/hdc
>ide: run usr/src/linux/scripts/MAKEDEV.ide to fix it
>warning: Bios Drive 0x82 may not be accessible
->
>So, what exactly is the problem?  Everything works fine other than
>this.  Thanks

the answer is there :
# cd /ide
# ./MAKEDEV ide

Ohad.

 
 
 

Strange LILO problem

Post by David Directo » Tue, 30 Sep 1997 04:00:00



> Hey, I just finished installing DEBIAN 1.3.0 linux and everything
> works pretty fine.  Well, everything except for LILO.  Whenever I try
> to boot the system after it's installed it says "LI" and then just
> pauses forever.

[snip]

If you have the drive defined in your BIOS as "LBA" mode, LILO will
do exactly what you've described.  Set it to "LARGE" or "NORMAL"
(on my system, I use "LARGE"), and the problem should go away.

-- David

 
 
 

Strange LILO problem

Post by David Directo » Tue, 30 Sep 1997 04:00:00



> Hey, I just finished installing DEBIAN 1.3.0 linux and everything
> works pretty fine.  Well, everything except for LILO.  Whenever I try
> to boot the system after it's installed it says "LI" and then just
> pauses forever.

[snip]

If you have the drive defined in your BIOS as "LBA" mode, LILO will
do exactly what you've described.  Set it to "LARGE" or "NORMAL"
(on my system, I use "LARGE"), and the problem should go away.

-- David

 
 
 

Strange LILO problem

Post by Brian McCaule » Tue, 30 Sep 1997 04:00:00



> When I first installed LILO I got this weird error:

> ide: probable bad entry for dev/hdc
> ide: run usr/src/linux/scripts/MAKEDEV.ide to fix it

Yes this is due to an anachronism in LILO.  The major/minor device
numbers for IDE changed sometime in 1.3.x but LILO still contains some
code that uses the old numbers directly (rather than the entries in
/dev/).  It's harmless really as this code doesn't actually do
anything essential - it just judges whether or not to generate the
following warning.

Quote:> warning: Bios Drive 0x82 may not be accessible
> 1.6 gig hard drive (2 dos partitions) /dev/hda1 and /dev/hda5
> 1.6 gig hard drive (2 dos partitions) /dev/hdb1 and /dev/hdb5

> Secondary Controller
> 840mb hard drive (linux swap & native paritions) /dev/hdc1 & /dev/hdc5
> Sanyo 6X IDE CD-ROM drive

> So, what exactly is the problem?  Everything works fine other than
> this.  Thanks

The message is "Bios Drive 0x82 may not be accessible" and it means
what it says - although I suppose it could be clearer.

The boot-time part of LILO uses BIOS to access the HD.  Unfortunately,
LILO has no way of knowing at install-time if your BIOS will be
capable of accessing the secondary IDE controller (older ones can't).
If everything works fine then this means your BIOS *can* access the
secondary controller so you can ignore the warning.

For further details get the excellent LILO user guide.

--

 .  _\\__[oo       from       | Phones: +44 121 471 3789 (home)

.  l___\\    /~~) /~~[  /   [ | PGP-fp: D7 03 2A 4B D8 3A 05 37...
 # ll  l\\  ~~~~ ~   ~ ~    ~ | http://wcl-l.bham.ac.uk/~bam/

 
 
 

Strange LILO problem

Post by Nic » Wed, 01 Oct 1997 04:00:00





>>Hey, I just finished installing DEBIAN 1.3.0 linux and everything
>>works pretty fine.  Well, everything except for LILO.  Whenever I try
>>to boot the system after it's installed it says "LI" and then just
>>pauses forever.  

>how come everything works fine when you can't start linux ???

No I can BOOT into Linux and use my drives perfectly.  I just have to
use a Kernel Boot Disk.  I just can't boot linux from the HD

Quote:>>When I first installed LILO I got this weird error:

>>ide: probable bad entry for dev/hdc
>>ide: run usr/src/linux/scripts/MAKEDEV.ide to fix it
>>warning: Bios Drive 0x82 may not be accessible
>->
>>So, what exactly is the problem?  Everything works fine other than
>>this.  Thanks

>the answer is there :
># cd /ide
># ./MAKEDEV ide

>Ohad.

Oh, I did do that before also and it didn't fix my problem.  I think
it's because my HD currently has 1600+ cylinders according to the
bios.  Maybe if I try to set the bios from LDA to LARGE it'll be
fine... hmm... I'll get back to everyone

Thanks!
Nick

 
 
 

Strange LILO problem

Post by John Stran » Wed, 01 Oct 1997 04:00:00


: >
: > Hey, I just finished installing DEBIAN 1.3.0 linux and everything
: > works pretty fine.  Well, everything except for LILO.  Whenever I try
: > to boot the system after it's installed it says "LI" and then just
: > pauses forever.
: >

: [snip]

: If you have the drive defined in your BIOS as "LBA" mode, LILO will
: do exactly what you've described.  Set it to "LARGE" or "NORMAL"
: (on my system, I use "LARGE"), and the problem should go away.

: -- David

Do not just change mode, I did it and scrambled my disks.  The mode needs
to match the mode the disk was formated in.  I use LBA on three different
systems and do not have the "LI" boot problem.

I do recommend setting the mode LBA, deleting all partations, create partitions,
and format the new partitions.  This has allowed me to boot linux which exists
beond the 1024 cylinder location.

Do backup everything, twice. Verify that you can recover from the backups.

--
This posting represents the personal opinions of the author. It is not the
official opinion or policy of the author's employer. Warranty expired when you
opened this article and I will not be responsible for its contents or use.

 
 
 

Strange LILO problem

Post by David Directo » Wed, 01 Oct 1997 04:00:00


[snip]

Quote:

> Do not just change mode, I did it and scrambled my disks.  The mode needs
> to match the mode the disk was formated in.  I use LBA on three different
> systems and do not have the "LI" boot problem.

> I do recommend setting the mode LBA, deleting all partations, create partitions,
> and format the new partitions.  This has allowed me to boot linux which exists
> beond the 1024 cylinder location.

Interesting... I was unaware of that particular detail.  I probably
had no problem because I originally set up Linux under "LARGE", then
upgraded my motherboard.  The new MB apparently defaulted everything
to LBA, and it didn't work.  When I changed to LARGE, it was fine.

Thanks for the further info.

-- David

 
 
 

1. Strange LILO Problem (SLS 1.03)

Hello, who knows whats going on here. The system is a 486, SLS 1.03, Kernel
is 0.99pl12 . My problem is the following:

- the A1 disk coming with SLS 1.03 has a zImage pl11.

- due to the fact that I'm running a pl12 Kernel now, which incorporates some
  additional stuff (tape driver etc), I tried to setup an A1-disk of my own
  using my special pl12 kernel. I succeeded in doing so by replacing the
  zImage on a copy of the A1-disk by my kernel, by adding the additional
  driver and some utilities to the bin directory on the floppy, and by
  modifying the /etc/lilo/config on the floppy in a way, that it accesses
  the bootrecord of the A1-disk, when its mounted on /fd0 in my running
  system. Also executing LILO worked ok, I got a bootable floppy, which
  is valuable for instance in doing standalone backups of my disks. Booting
  from the new A1 disk works ok.

- So far, no problems. But then some day my system crashed during normal
  operation. I said, no problem, reboot with my new A1 disk, e2fsck and so
  on. But - booting from the new A1-disk resulted in LIL- , nothing else
  happened. Normally it worked ok. Booting from the SLS 1.03 A1 disks
  (unmodified) was ok. Trying to boot directly from harddisk resulted also
  in LIL- . Ok, I booted the pl11 from the original A1, did the e2fsck,
  no errors reported. Did an e2fsck -r until the system reported the
  disks to be clean. And then - oh wonder!! - booting from harddisk AND
  booting from my selfmade A1 worked ok again!!!! So, what did I do wrong?

-> I guess that LILO on my selfmade A1 checks the harddisks in a certain
   way. How can I avoid that? I want to have a REAL emergency A1 disk with
   my modified kernel on it. A disk, which is strictly supposed NOT to hang
   when the computer is hung... As long as I still keep some copies of
   the original A1 thats no problem, (see above), but not that elegant as
   I want to have it.

- Don't need to say, that the selfmade disk works under normal conditions,
  and that it never was in the machine not being write protected, only
  when I created it. So there could have been no accidental modification on
  it. The same effect shows up on the several copies I have of this disk.

Please help! Thanks a lot, Karsten
--
------------------>         Karsten Steffens        <---------------------

Marl - close to Recklinghausen     |         Institut fuer Kernphysik
  North of the Ruhrgebiet          |   Westf.Wilhelms-Universitaet Muenster

2. Installed RH9, Can't Mount CDROM?

3. strange LILO problem

4. Solved: Kernal Compile Problem

5. Strange lilo problem

6. NEW linux ftp site (banjo ressurected)

7. Strange LILO problem

8. Printer Problems Please Help

9. Strange Lilo "LI" problems

10. strange problems with LILO

11. Strange problem with LILO

12. HELP !!!!!!!!! Very strange problem with BIOS and LILO !!!!!

13. Strange problem with LILO (screen full of 01's)