From: "Udo A. Steinberg" <us15@os.inf.tu-dresden.de>
To: linux-kernel@vger.kernel.org
Subject: Re: memory remapping, 4gb memory on 945gt
Date: Fri, 4 Jan 2008 20:35:58 +0100 [thread overview]
Message-ID: <20080104203558.73dd04a4@laptop.hypervisor.org> (raw)
In-Reply-To: <p73lk758sri.fsf@bingen.suse.de>
[-- Attachment #1: Type: text/plain, Size: 1419 bytes --]
On Fri, 04 Jan 2008 17:22:57 +0100 Andi Kleen (AK) wrote:
AK> felix-linuxkernel@fefe.de writes:
AK>
AK> > I recently put 4 GB of memory in my Acer Travelmate 8210 series
AK> > notebook. The BIOS only detects 3 GB.
AK>
AK> Actually it will detect 4GB, but put the PCI hole over the last GB.
AK> One way to get more usable memory is to configure the BIOS to use a
AK> smaller PCI hole (e.g. use smaller frame buffer/aperture etc.)
AK>
AK> > I googled around a little. It appears to be a chipset limitation of
AK> > the 945gt, which uses the fourth gig for devices.
AK> >
AK> > Now I can understand this explanation for 32-bit mode, but I'm running
AK> > in 64-bit mode. There should be a way to use the fourth gig under
AK> > Linux. Is there?
AK>
AK> The chipset limitation applies to 64bit mode as well as to 32bit mode
AK> (which actually does not have a 4GB limitation with PAE)
Using a 64-bit or PAE kernel won't give access to more than 4GB of RAM
because that only increases the linear address space of the CPU to 48 or
36 bits respectively. The limitation with 945GT is that the chipset only
supports 32-bit physical addresses. As Andi already pointed out, parts of
that 4GB physical address space are used by devices and their apertures,
so you can only try to shrink those devices ranges, if configurable, but
you won't be able to use the full 4GB RAM.
Cheers,
- Udo
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2008-01-04 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-04 15:49 memory remapping, 4gb memory on 945gt felix-linuxkernel
2008-01-04 16:22 ` Andi Kleen
2008-01-04 18:19 ` Dr. David Alan Gilbert
2008-01-04 22:03 ` H. Peter Anvin
2008-01-04 23:02 ` Parag Warudkar
2008-01-04 19:35 ` Udo A. Steinberg [this message]
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=20080104203558.73dd04a4@laptop.hypervisor.org \
--to=us15@os.inf.tu-dresden.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox