[ale] ram

[Robert Hoffman]

Be very careful before you just add the full amount of ram to the apend line. In the three machines I've had this happen to me on, the machine would not come back up unless I specified a few meg less than I actually had. i.e. append="mem=124M" when you really have 128M of memory.

I discuss this here:

www.frankenlinux.com/guides/tweaks.html

Hope this helps,

-Rob Hoffman


---------- Original Message ----------------------------------
From: Wandered Inn <esoteric at atlnet.com>
To: ale at ale.org
Date: Mon, 25 Sep 2000 22:59:30 -0400

>jiin wrote:
>> A question from a friend:
>> 
>> His boxen is only reading 64 of his 128 megs of ram. I have an article about
>> this very subject in an issue of Linux Magazine but cant find the mag right now
>> and he needs an answer. he is using Mandrake 7.x.
>> 
>> The article explained it simply but I dont remember how. Any suggestions?
>
>Well, using the append="mem=128M" in the lilo.conf file is what you were
>probably reading about, but I thought that the later kernels dealt with
>this problem?  I've got one machine with 128M and another with 256M and
>both recognize full amount of memory without any magic.
>
>Am I wrong on this one.  Is it particular MB or MB vendors that seem to
>still have this problem?
>
>> 
>> jiin
>> --
>> To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.
>
>--
>Until later: Geoffrey		esoteric at denali.atlnet.com
>
>"Great spirits have always found violent opposition from mediocre minds.
>The
>latter cannot understand it when a man does not thoughtlessly submit to
>hereditary prejudices but honestly and courageously uses his
>intelligence."
>- Albert Einstein
>--
>To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.
>
--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.