From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Frank Fiene <ffiene@veka.com>
Cc: Robert Hancock <hancockr@shaw.ca>,
linux-kernel@vger.kernel.org, tytso@thunk.org
Subject: Re: Kernel doesn't recognize complete memory
Date: Sun, 1 Jul 2007 04:54:31 +0100 [thread overview]
Message-ID: <20070701035430.GA27489@srcf.ucam.org> (raw)
In-Reply-To: <200706301946.46918.ffiene@veka.com>
The 945 chipset used in the Z61 can only address 4GB of physical address
space and your BIOS is using some of this for PCI and other bits of
hardware. That only leaves 3GB for RAM. I believe that this restriction
is mentioned on the IBM website somewhere.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2007-07-01 3:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.8WY71RLqV3Tqf8TkTOMOg/ub4Cs@ifi.uio.no>
2007-06-29 23:18 ` Kernel doesn't recognize complete memory Robert Hancock
2007-06-30 17:46 ` Frank Fiene
2007-06-30 18:24 ` Robert Hancock
2007-07-01 3:54 ` Matthew Garrett [this message]
2007-06-29 20:25 Frank Fiene
2007-06-30 0:34 ` Russell Harmon
2007-06-30 1:08 ` Matti Aarnio
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=20070701035430.GA27489@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=ffiene@veka.com \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@thunk.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