![](https://seccdn.libravatar.org/avatar/5d9661f2110f00363e99f5b309b530b9.jpg?s=120&d=mm&r=g)
From: Paul W. Abrahams
To: SuSE listserve Cc: Brad Shelton Subject: [SLE] MEM= Lilo parameter and memory > 64MB Date: Sunday, 13 February 2000 12:42 Brad Shelton pointed out to me the existence of a Lilo parameter `mem=' for specifying the amount of available RAM. On further investigation I discovered a few paragraphs on this subject in the Boot-Prompt Howto (not where I would have expected it).
It seems that the normal PC Bios is unable to report memory sizes greater than 64MB. Linux needs this parameter to find out how much memory is actually available. According to Linus the All-Knowing as quoted in that document, overstating the amount of available memory can cause all kinds of disasters. I suspect the problems I was having with a filesystem implosion were related to some nonuniformity in the mechanisms used by different system components for determining how much memory is present.
In my case I've specified `mem=128M'. Has anyone else found this
not yet, but I will shortly as i'm building an apachie datawarehouse server to clear off one of my friends tree a number of old NT3.51 boxes and their content to an easier accessable matrix (no i'm not going NT4, I made that clear at the start as being impractical, their drive mappings are a mess now with only Drive U: being free), and planning 512Meg as the starter. I wonder what the lilo limit is, the board can take 4gig if they can ever afford or need that volume of ram. csijon ---------- parameter
to be necessary?
Paul Abrahams
-- 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/
-- 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/