Thanks! The output now reads: total used free shared buffers cached Mem: 130660 44004 86656 0 6000 16632 -/+ buffers/cache: 21372 109288 Swap: 136512 0 136512 I assuming this is all cool now. No chance that there still isn't the extra 64MB (for some bizzare reason) and Lilo now just behaves like there is? Can I specifically ping each RAM chip to test? Peter

From: matthew johnson Date: Mon, 21 May 2001 12:40:53 -0700 (PDT) To: Peter D Bethke Cc: Subject: Re: [SLE] Memory mismatch

Add this to near the top of lilo.conf

append="mem=128M"

Then re-run lilo, then all should be fine.

Basically lilo is not seeing all the RAM from the BIOs.

Matt

On Mon, 21 May 2001, Peter D Bethke wrote:

...

Hello list,

I (thought) my system had 128 megs, from 2 64MB EDO DIMMS (on a Pentium Pro 200). The bios reports 128 megs, and the diagnostics in the bios pass the 128 megs okay.

However, running "free" at the command line returns 64 MB total memory.

total used free shared buffers cached Mem: 66144 42772 23372 0 5964 16472 -/+ buffers/cache: 20336 45808 Swap: 136512 0 136512

Are there any other tests I can run to find out what the problem is?

Peter

-- 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/faq and the archives at http://lists.suse.com

-- 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/faq and the archives at http://lists.suse.com

If you have 7.1 you can use memtest. Memtest only fails on memory above 2gb, but that should not matter for the majority of users here... Also, try using top :-) Matt Peter D Bethke wrote:

Thanks!

The output now reads:

total used free shared buffers cached Mem: 130660 44004 86656 0 6000 16632 -/+ buffers/cache: 21372 109288 Swap: 136512 0 136512

I assuming this is all cool now. No chance that there still isn't the extra 64MB (for some bizzare reason) and Lilo now just behaves like there is? Can I specifically ping each RAM chip to test?

Peter

...

From: matthew johnson Date: Mon, 21 May 2001 12:40:53 -0700 (PDT) To: Peter D Bethke Cc: Subject: Re: [SLE] Memory mismatch

Add this to near the top of lilo.conf

append="mem=128M"

Then re-run lilo, then all should be fine.

Basically lilo is not seeing all the RAM from the BIOs.

Matt

On Mon, 21 May 2001, Peter D Bethke wrote:

...

Hello list,

I (thought) my system had 128 megs, from 2 64MB EDO DIMMS (on a Pentium Pro 200). The bios reports 128 megs, and the diagnostics in the bios pass the 128 megs okay.

However, running "free" at the command line returns 64 MB total memory.

total used free shared buffers cached Mem: 66144 42772 23372 0 5964 16472 -/+ buffers/cache: 20336 45808 Swap: 136512 0 136512

Are there any other tests I can run to find out what the problem is?

Peter

-- 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/faq and the archives at http://lists.suse.com

-- 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/faq and the archives at http://lists.suse.com

* Anders Johansson [Mon, 21 May 2001 22:10:51 +0200]:

A question: I thought this was fixed in the newer kernels, yet from time to time this problem pops up. Does anyone know why? Is it a problem with certain types of memory, certain bioses or what?

It's a BIOS problem. The original BIOS routine could only report up to 64 MB of memory, so new calls where invented that could report more. And then MS invented yet another BIOS call to be used by windows and BIOS vendors followed suit. Newer kernels do support the new call and may thus see the whole memory. -- Penguins to save the dinosaurs -- Handelsblatt on Linux for S/390