🚀 go-pugleaf

Hi dagger

I've seen this before ... but ...memory parity error :))

Could be damaged boot record - I assume you don't have any DOS/FAT
partitions from your description - get Linux up and redo your LILO
installation with linuxconf (at the command line)

If that fails, it could be that you don't have an active partition, or maybe
you only have an extended partition without any primary partition which
would probably be an invalid configuration. With fdisk, you should be able
to activate your partition, but if you only have an extended partition, you
might have to reinstall from scratch using a primary partition instead.

One other possibility is that your hard disk has got more than 1023
cylinders even though its not that big - some early drives only have two
heads and over 1023 cyls - check in your C-MOS settings - if the drive is
using LBA, you may have that problem. (not that likely though)

Hope this helps
Dave
dagger wrote in message ...
>I am currently installing Redhat 5.2 on a 486DX2/33, everything has
>installed fine - but when it tries to boot off the hardrive it hangs at
>where the LILO: prompt should be at LI
>
>If I boot off the install floppy and enter vmlinuz root=/dev/hda1
>read-only at the boot: prompt, it boots off the hardrive fine.
>
>Any reccomendations on how to fix this? It's only a 520mb drive (485
>extended partition, and 32mb swap) so I doubt it suffers from the
>too-many-cylenders problem.
>
>The other thing is, this machine only has 10mb of physical RAM - but this
>shouldn't be a problem?
>
>--
>dagger
><mailto:dagger@bayside.net>
>(Too much blood in my caffeine system...)

> I am currently installing Redhat 5.2 on a 486DX2/33, everything has
> installed fine - but when it tries to boot off the hardrive it hangs at
> where the LILO: prompt should be at LI
> 
> If I boot off the install floppy and enter vmlinuz root=/dev/hda1
> read-only at the boot: prompt, it boots off the hardrive fine.
> 
> Any reccomendations on how to fix this? It's only a 520mb drive (485
> extended partition, and 32mb swap) so I doubt it suffers from the
> too-many-cylenders problem.
> 
> The other thing is, this machine only has 10mb of physical RAM - but this
> shouldn't be a problem?
> 

For what its worth, I had the same symptom...

By mistake I had used  boot=hda5 in /etc/lilo.conf
 (I have Windows on the first partition).
This stopped LILO at LI as in your problem because it tried
to boot off the fifth partition rather than off the MBR.

All I had to do to fix it was delete the 5, ie use boot=hda in the
lilo.conf file.

Brett McSweeney

In article <7femn3$2jk$1@nornet2.nor.com.au>, "Dave Chapman"
<chappo@nor.com.au> wrote:

>Hi dagger

Hello. :)

>I've seen this before ... but ...memory parity error :))
>
>Could be damaged boot record - I assume you don't have any DOS/FAT
>partitions from your description - get Linux up and redo your LILO
>installation with linuxconf (at the command line)

No dos/fat partition, I have reinstalled lilo (did lilo -v) checked the
config, tried to boot off a lilo boot floppy (created by the linux during
install), but i got a LI 10 10 10 10 10, and so on on boot.

>If that fails, it could be that you don't have an active partition, or maybe
>you only have an extended partition without any primary partition which
>would probably be an invalid configuration. With fdisk, you should be able
>to activate your partition, but if you only have an extended partition, you
>might have to reinstall from scratch using a primary partition instead.

Can you expand on this a little more please? I'm unfamilar with fdisk, any
directions on how to check and do so would be much appreciated

>One other possibility is that your hard disk has got more than 1023
>cylinders even though its not that big - some early drives only have two
>heads and over 1023 cyls - check in your C-MOS settings - if the drive is
>using LBA, you may have that problem. (not that likely though)

No, it only has 583 cylinders. I can't find a CMOS setting for lba....

Thanks in advance, :)

-- 
dagger
<mailto:dagger@bayside.net>
(Too much blood in my caffeine system...)

In article <01be8a43$b9807cc0$5fa7868b@bsm>, "Brett McSweeney"
<bsm@bigpond.com> wrote:

>> I am currently installing Redhat 5.2 on a 486DX2/33, everything has
>> installed fine - but when it tries to boot off the hardrive it hangs at
>> where the LILO: prompt should be at LI
>> 
>> If I boot off the install floppy and enter vmlinuz root=/dev/hda1
>> read-only at the boot: prompt, it boots off the hardrive fine.
>> 
>> Any reccomendations on how to fix this? It's only a 520mb drive (485
>> extended partition, and 32mb swap) so I doubt it suffers from the
>> too-many-cylenders problem.
>> 
>> The other thing is, this machine only has 10mb of physical RAM - but this
>> shouldn't be a problem?
>> 
>
>For what its worth, I had the same symptom...
>
>By mistake I had used  boot=hda5 in /etc/lilo.conf
> (I have Windows on the first partition).
>This stopped LILO at LI as in your problem because it tried
>to boot off the fifth partition rather than off the MBR.
>
>All I had to do to fix it was delete the 5, ie use boot=hda in the
>lilo.conf file.
>
>Brett McSweeney

It's set to boot off /dev/hda1, when i boot off the disk and enter vmlinuz
root=/dev/hda1 read-only at the boot prompt, it loads fine. :\

Thanks anyway,

-- 
dagger
<mailto:dagger@bayside.net>
(Too much blood in my caffeine system...)

dagger wrote:

> I am currently installing Redhat 5.2 on a 486DX2/33, everything has
> installed fine - but when it tries to boot off the hardrive it hangs at
> where the LILO: prompt should be at LI
>
> If I boot off the install floppy and enter vmlinuz root=/dev/hda1
> read-only at the boot: prompt, it boots off the hardrive fine.
>
> Any reccomendations on how to fix this? It's only a 520mb drive (485
> extended partition, and 32mb swap) so I doubt it suffers from the
> too-many-cylenders problem.
>
> The other thing is, this machine only has 10mb of physical RAM - but this
> shouldn't be a problem?
>
> --
> dagger
> <mailto:dagger@bayside.net>
> (Too much blood in my caffeine system...)

Check the file /etc/lilo.conf if the file has the root partition set well
rerun /sbin/lilo and zou should be set up.
Bye Sasa

You need to add a line to your /etc/lilo.conf:
linear
Just that one word. The different letters of LILO stand for things, and LI
means there is a disk geometry error.
>I am currently installing Redhat 5.2 on a 486DX2/33, everything has
>installed fine - but when it tries to boot off the hardrive it hangs at
>where the LILO: prompt should be at LI
>
>If I boot off the install floppy and enter vmlinuz root=/dev/hda1
>read-only at the boot: prompt, it boots off the hardrive fine.
>
>Any reccomendations on how to fix this? It's only a 520mb drive (485
>extended partition, and 32mb swap) so I doubt it suffers from the
>too-many-cylenders problem.
>
>The other thing is, this machine only has 10mb of physical RAM - but this
>shouldn't be a problem?
>
>--
>dagger
><mailto:dagger@bayside.net>
>(Too much blood in my caffeine system...)