From: Tom Moore <tmoore@spatial.ca>
To: Satyam Sharma <satyam.sharma@gmail.com>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
linux-kernel@vger.kernel.org
Subject: Re: 4Gb ram not showing up
Date: Thu, 07 Jun 2007 09:33:52 -0400 [thread overview]
Message-ID: <46680940.3070707@spatial.ca> (raw)
In-Reply-To: <a781481a0706061418m7f51dc1bke079e6e6b7d5f930@mail.gmail.com>
Satyam Sharma wrote:
> On 6/6/07, Lennart Sorensen <lsorense@csclub.uwaterloo.ca> wrote:
>> [...]
>> A better description would be:
>>
>> "Select this if you have a 32-bit processor and memory mapped in the 1GB
>> to 4GB address range."
>> [...]
>> That one would be better as:
>>
>> "Select this if you have a 32-bit processor and ram mapped in the
>> address
>> range above 4GB."
>
> Ugh, no! How can we expect the user compiling a kernel to be *so*
> familiar with address space re-mapping / BIOSen (_his_ particular
> BIOS, specifically, and what / how it re-maps memory) / etc to be
> able to answer such questions? "Select ... if you have ... RAM
> installed" is perfectly clear, simple, and all that's needed.
>
However the KConfig help message as it is currently written is wrong.
> BTW, just imagine what a user would need to do to make things
> work as per your proposal. Build some kernel (don't care about
> memory loss), boot and find what his firmware prefers to do with
> address space (or else read up the BIOS documentation!) and
> _then_ again build a new kernel, this time selecting the options
> appropriately ...
I tried to do this, but the Kconfig help message was misleading. I
still needed to come here for help.
>
> Also, note that the change you're proposing is unnecessary! As
> Andi pointed out, this issue has more to do with broken BIOSen
> and the proper fix for Tom is to contact his vendor and flash /
> upgrade the BIOS firmware. I don't see anything wrong with the
> Kconfig help texts.
Andi was wrong. It appears that he read the first sentence of my email
and jumped to a conclusion. The /proc/mtrr output that I included in my
first post showed the my bios was doing the right thing. My problem was
that I was using CONFIG_HIGHMEM4G, which is what the KConfig help
message told me to do. After switching to CONFIG_HIGHMEM64G the OS was
able to map all of my ram.
total used free shared buffers cached
Mem: 4016768 3924312 92456 0 360132 3030336
-/+ buffers/cache: 533844 3482924
Swap: 5116692 2676 5114016
Thanks to those with the correct advice. I'm sure I would have got this
by trying each memory model in turn, but at least now I know what is
going on.
Tom
next prev parent reply other threads:[~2007-06-07 13:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 15:14 4Gb ram not showing up Tom Moore
2007-06-04 19:10 ` Lennart Sorensen
2007-06-04 19:45 ` Tom Moore
2007-06-04 22:28 ` Wakko Warner
2007-06-05 13:12 ` Tom Moore
2007-06-05 13:37 ` Joseph Fannin
[not found] ` <46646B4C.2070707@spatial.ca>
2007-06-05 18:57 ` Lennart Sorensen
2007-06-06 21:18 ` Satyam Sharma
2007-06-07 6:58 ` Jan Engelhardt
2007-06-07 13:33 ` Tom Moore [this message]
2007-06-07 20:13 ` Lennart Sorensen
2007-06-06 11:45 ` Andi Kleen
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=46680940.3070707@spatial.ca \
--to=tmoore@spatial.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=satyam.sharma@gmail.com \
/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