On Sun, 21 Jan 2001, Suresh Ramasubramanian wrote:
> >Put the following line in lilo.conf (for 256M)
> >append="mem=256M"
> >save the file and run lilo -v
>
> Yes doc, folks - but that lilo hassle was with RAM >= 128 K, this guy had a
> problem with 64k ram getting detected as 13k - which makes me think its not
> a LILO hassle at all ... I doubt if even older LILOs had a hassle with
> 64MB RAM
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.
--
#!!! If anything can go wrong, _FIX_ it. (To hell with MURPHY)
Ajay kumar Dwivedi
[EMAIL PROTECTED]
----------------------------------------------
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.
