From: Erik Mouw <erik@harddisk-recovery.com>
To: "Froggy / Froggy Corp." <froggy@froggycorp.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Memory problem
Date: Wed, 27 Apr 2005 15:18:58 +0200 [thread overview]
Message-ID: <20050427131858.GC3918@harddisk-recovery.com> (raw)
In-Reply-To: <426BAFF2.54160A91@froggycorp.com>
On Sun, Apr 24, 2005 at 04:40:50PM +0200, Froggy / Froggy Corp. wrote:
> I just see a memory problem : i have 1Gb install on my computer and only
> 275Mb are available when i take a look with "free".
> I use kernel 2.6.10, the bios tell me that i really have 1Gb (2*512
> DDR), the kernel have 4Gb option enable, so i dont understand.
>
> If someone have an idea.
>
> Thx in advance for any help,
> Regards,
>
> Here is some information :
[snip]
> -------------------------------------------------------------------------
> Linux version 2.6.10 (root@Odyssee) (gcc version 3.3.5 (Debian
> 1:3.3.5-12)) #3 S
> MP Sun Apr 24 16:00:50 CEST 2005
> BIOS-provided physical RAM map:
> BIOS-e820: 0000000000000000 - 000000000009d800 (usable)
> BIOS-e820: 000000000009d800 - 00000000000a0000 (reserved)
> BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
> BIOS-e820: 0000000000100000 - 0000000011340400 (usable)
> BIOS-e820: 0000000011340400 - 0000000011343400 (ACPI NVS)
> BIOS-e820: 0000000011343400 - 0000000011350400 (ACPI data)
> BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
The kernel takes the amount of memory the BIOS tells it to use. If you
count all memory in the "usable" sections of the RAM map, it all adds
up to 275 MB.
erik@arthur:~> bc -l
ibase=16
(((11340400 - 100000) + (9D800)) / 400 / 400
274.8662109375
Might be a BIOS bug, or the BIOS RAM tester decided only 275 MB is
useable. Try upgrading the BIOS, or reset the CMOS.
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
next prev parent reply other threads:[~2005-04-27 13:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-24 14:40 Memory problem Froggy / Froggy Corp.
2005-04-27 13:18 ` Erik Mouw [this message]
2005-04-27 16:29 ` Froggy / Froggy Corp.
-- strict thread matches above, loose matches on Subject: below --
2004-12-14 20:25 MEMORY PROBLEM ppclinux
2004-12-14 21:07 ` Jerry Van Baren
2004-12-15 16:51 ` ppclinux
2004-09-13 11:11 (unknown) Ankit Jain
2004-09-13 11:51 ` memory problem Ron Michael Khu
2004-05-26 10:14 Memory problem Pankaj
2003-07-03 16:10 Daniel Chemko
2003-07-03 9:53 Cilliè Burger
2003-07-03 9:15 ` Filip Sneppe
[not found] ` <3F044612.8020903@sadomain.co.za>
2003-07-03 14:42 ` Filip Sneppe
2003-04-03 0:40 memory problem 최영일
2002-10-07 14:33 Memory Problem Philipp Steinkrueger
2002-10-07 14:33 ` Philipp Steinkrueger
2002-10-07 15:21 ` Rik van Riel
2002-10-07 15:21 ` Rik van Riel
2002-10-07 15:52 ` Dave Hansen
2002-10-07 17:10 ` Glynn Clements
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050427131858.GC3918@harddisk-recovery.com \
--to=erik@harddisk-recovery.com \
--cc=froggy@froggycorp.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.