"Paul W. Abrahams" wrote:
Juergen Braukmann wrote:
"Paul W. Abrahams" wrote:
Hmmm. Did I miss it, or did you tell us you weren't using the append="MEM=128M" lilo boot statement?
Just curious to see if that's involved in your predicament.
I never heard of the MEM=128M statement. Is it supposed to be necessary? If so, it's another of those magical incantations.
It shouldn't be nessesarry with a 2.2.X Kernel, but it was nessesarry for the elder non SuSE 2.0.X series.
But Danian Slavek wrote:
Yes, I have 128 megs of ram but 6.2 didn't detect all of it. I added the aforementioned MEM=128M and after that everything worked great.
Where lieth the truth?
That was what I wondered when I read it as well. Just checked /etc/lilo.conf: no append mem=128. Free finds my 128 MB RAM. I remember old discussions about this from the 2.0.3x days. (could be in the archives) The SuSE kernels had a patch that found the RAM correctly, stock kernels needed the append mem=... statement. I also remember that it was said that this patch was standard for 2.2.x. One should dig the archives for that, if it matters. havn't tried a homebrewed kernel for a long while, so I can't tell. With a stock kernel in use, it could still be a patch. In that case, it leaves the question why it hasn't found it's way into the standard kernel. ;-( Juergen Juergen
Paul Abrahams
-- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/