seanc wrote:
> Install detects 128 mb of ram.
> top/free report only 64.
>
> Reinstalled. Same deal. Where is this setting kept and how can I change
> it? This is my workstation / game-box so it runs windoze too and it likes
> and uses all 128 mb.
>
> Oh yeah using loadlin rather than lilo. Could that be the problem? (Don't
> think so but I can't rule it out). 3 DIMMS (64,32,32 respectively).
>
> Any ideas??? (i'm frustrated and stumped).. I've gone through all the init
> scripts I could find and every config file with no luck.
>
> Sean Cody ([EMAIL PROTECTED])
> "Codito ergo sum" (I code therefore I am)
> Rasterman
I just posted a message about this. Linux and lilo take what is reported by
the BIOS.
Some common problems:
1. If you have the BIOS set for OS/2 you end at 64.
2. If you leave the memory hole open you get to see 14 or 15.
3. If you have anything memory mapped and you have an AMI BIOS likely it
will misreport.
The solution:
1. Figure out how much memory you have. Some video cards take a chunk of
it. Make sure you have the RAM available.
2. In lilo.conf add this line
append = "mem=xyzM"
where xyz = 120 for 120M of RAM, for example.
3. You likely will be root just to edit /etc/lilo.conf, so stay root long
enough for
# /sbin/lilo
Then you should see the right amount of memory on your next boot.
Q.E.D.
Why doesn't linux check its own memory and instead rely on either the BIOS or
a line in lilo? Well, consider memory-mapped video including video clock
registers. Checking memory destructively even if you read a word, write a
test word then replace the original word after verifying thereby being
"non-destructive" in net effect, you may have placed a clock in a runaway
condition that could damage a card or a monitor.
Civileme
--
experimentation involving more than 500 trials with an
ordinary slice of bread and a tablespoon of peanut butter
has determined that the probability a random toss will
land sticky side down (SSD) is approximately .98
