From: Mikael Pettersson <mikpe@it.uu.se>
To: linux-kernel@vger.kernel.org, thomas@stewarts.org.uk
Subject: Re: Only 3.2G ram out of 4G seen in an i386 box
Date: Tue, 8 Aug 2006 11:13:00 +0200 (MEST) [thread overview]
Message-ID: <200608080913.k789D0fC019037@harpo.it.uu.se> (raw)
On Tue, 8 Aug 2006 09:24:29 +0100, Thomas Stewart wrote:
> I have a Dell Optiplex GX280, a Pentium 4 with an Intel chipset. It has
> 4G of ram. The problem is I can only see 3.2G, even tho the bios reports
> 4G.
>
> While using debian 2.6.16-2-686:
> thomas@coke:~$ uname -a
> Linux coke 2.6.16-2-686 #1 Sat Jul 15 21:59:21 UTC 2006 i686 GNU/Linux
> thomas@coke:~$ grep MemTotal /proc/meminfo
> MemTotal: 3375484 kB
>
> This is expected as the standard debian kernels don't set
> CONFIG_HIGHMEM64G. My understanding is that this needs to be set for the
> full 4G to work on i386.
>
> So I downloaded 2.6.18-rc3-git3 and 2.6.18-rc2-mm1 to give them a try. I
> used the debian config as a starting point for oldconfig. Then from
> menuconfig, "Processor type and featues" -> "High Memory Support" and
> selected 64G. I then compiled both, rebooted and got these results:
>
> 2.6.18-rc2-mm1 reported MemTotal: 3376192 kB
> 2.6.18-rc3-git3 reported MemTotal: 3376236 kB
Most likely the BIOS is reserving large parts of the [0,4GB[ range for
PCI devices and some for itself. Please post the E820 memory map the
kernel prints near the start of the boot sequence on your machine.
> Is there anything I can do to make use of the 800M or so of ram that's
> unused? Changing to amd64 or anything else that's sane or better does
> not count ;-)
You need a chipset+BIOS that can relocate RAM to above the 4GB boundary.
I don't know how common those are in the 32-bit x86 world.
next reply other threads:[~2006-08-08 9:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 9:13 Mikael Pettersson [this message]
2006-08-08 10:01 ` Thomas Stewart
[not found] <fa.FhtZk3YiH9OyGCt4iXIGt+vYtos@ifi.uio.no>
2006-08-08 14:22 ` Robert Hancock
-- strict thread matches above, loose matches on Subject: below --
2006-08-08 8:24 Thomas Stewart
2006-08-08 10:15 ` Paul P Komkoff Jr
2006-08-08 19:51 ` David Schwartz
2006-08-09 6:51 ` gmu 2k6
2006-08-09 14:48 ` Joel Jaeggli
2006-08-09 14:54 ` gmu 2k6
2006-08-10 21:09 ` Simen Thoresen
2006-08-11 11:08 ` gmu 2k6
2006-08-13 10:54 ` Simen Thoresen
2006-08-10 13:04 ` Thomas Stewart
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=200608080913.k789D0fC019037@harpo.it.uu.se \
--to=mikpe@it.uu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@stewarts.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®