On Sun, Jan 21, 2001 at 10:53:03AM +0530, Dwivedi Ajay kumar wrote:
> 
>       A friend here also had the same problem, his 128MB being detected
> as 13MB by default. He had AMD k6 with ASUS(?) mobo. We tried everything
> from changing the RAM to even harddisk (It aborted linux installation with
> signals 9 through 11 when tried with mem=128M).
>       Finally when we changed the mobo, the problem got corrected
> automatically. So the problem was not with lilo at all atleast in that
> case.
> 

With  mem=X option the kernel ignores what lilo has detected and
forcibly use this much memory. Try this option with more memory than what
you have, linux crashes when it starts using invalid memory. You can
even give mem=4M to simulate a low-memory device.

You can try progressively reducing the number by few meg, (like mem=125M)
and get around the buggy RAM chips.  Maybe that this motherboard uses 
some part of the RAM for its on-board chips ? 

(on one i810, bios reported 97M+1M: linux 2.2 uses 64M by default, 
 crashes with anything more than mem=95M, linux 2.4 probes bios instead
 of lilo and reports 94000k/97280k ) 


-Upendra



----------------------------------------------
LIH is all for free speech.  But it was created
for a purpose.  Violations of the rules of
this list will result in stern action.

Reply via email to