From: "Alejandro Bonilla" <abonilla@linuxwireless.org>
To: Dave Jones <davej@redhat.com>
Cc: Marcel Holtmann <marcel@holtmann.org>, linux-kernel@vger.kernel.org
Subject: Re: 4GB memory and Intel Dual-Core system
Date: Thu, 27 Oct 2005 18:13:57 -0400 [thread overview]
Message-ID: <20051027221158.M52510@linuxwireless.org> (raw)
In-Reply-To: <20051027220533.GA18773@redhat.com>
On Thu, 27 Oct 2005 18:05:33 -0400, Dave Jones wrote
> On Thu, Oct 27, 2005 at 05:15:50PM -0400, Alejandro Bonilla wrote:
> > On Thu, 27 Oct 2005 23:07:41 +0200, Marcel Holtmann wrote
> > > Hi Alejandro,
> > >
> > > > > the board in this system is a Intel D945GNT and the box
> tells me the > > > > maximum supported amount of RAM is 4 GB. So
> there should be a way to > > > > address this amount memory. > > >
> > > > The board did take the 4GB of RAM and it is finding them,
> therefore supports > > > them. It is just not designed to give a
> full 4GB of RAM to the system, it only > > > gives 3.4XGB RAM and
> the rest is really not used, then basically the system > > > just
> tries to give the 0.6xGB RAM remaining a task by it being used by "System
> > > > Resources"
> > > >
> > > > This isn't really Linux dependant.
> > >
> > > so there is no way to give me back the "lost" memory. Is it possible
> > > that another motherboard might help?
> >
> > AFAIK, No. AMD and Intel will always do the same thing until we
> all move to > real IA64.
>
> Somehow, I doubt AMD see it that way :-)
>
> Some boards at least have a BIOS option to support 'memory hoisting'
> to map the 'lost' memory above the 4G address space.
True, probably AMD added a "workaround" for this problem, but by nature, this
is what happens.
>
> I suspect a lot of the lower-end (and older) boards however don't
> have this option, as they were not tested with 4GB.
Probably no Intel boards have the option. So, it would be that Marcel contact
Intel so they can add a mapping option on the BIOS for this situation. It is
somehow missleading.
.Alejandro
>
> Dave
next prev parent reply other threads:[~2005-10-27 22:14 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 20:33 4GB memory and Intel Dual-Core system Marcel Holtmann
2005-10-27 20:44 ` Roland Dreier
2005-10-27 20:51 ` Marcel Holtmann
2005-10-27 20:54 ` Roland Dreier
2005-10-27 21:00 ` Marcel Holtmann
2005-10-27 21:06 ` Roland Dreier
2005-10-27 21:08 ` Marcel Holtmann
2005-10-27 21:10 ` Alejandro Bonilla
2005-10-27 20:57 ` Alejandro Bonilla
2005-10-27 20:54 ` Alejandro Bonilla
2005-10-27 20:57 ` Marcel Holtmann
2005-10-27 21:02 ` Alejandro Bonilla
2005-10-27 21:07 ` Marcel Holtmann
2005-10-27 21:15 ` Alejandro Bonilla
2005-10-27 21:19 ` Marcel Holtmann
2005-10-27 22:26 ` Joe Bob Spamtest
2005-10-27 22:05 ` Dave Jones
2005-10-27 22:09 ` Vladimir Lazarenko
2005-11-02 16:21 ` Lennart Sorensen
2005-10-27 22:11 ` Marcel Holtmann
2005-10-27 22:12 ` Dave Jones
2005-10-27 22:17 ` Marcel Holtmann
2005-10-27 22:20 ` Alejandro Bonilla
2005-10-28 0:33 ` Bernd Eckenfels
2005-10-30 22:26 ` Alan Cox
2005-10-31 3:39 ` Alejandro Bonilla Beeche
2005-10-31 13:02 ` Alan Cox
2005-10-31 23:03 ` Martin J. Bligh
2005-11-01 5:03 ` thockin
2005-10-27 22:29 ` Joel Jaeggli
2005-10-27 22:13 ` Alejandro Bonilla [this message]
2005-10-27 22:18 ` Marcel Holtmann
2005-10-28 2:35 ` Fawad Lateef
2005-10-28 3:09 ` Joel Jaeggli
2005-10-28 7:19 ` Fawad Lateef
2005-10-28 15:56 ` Joe Bob Spamtest
2005-10-28 15:29 ` Eric W. Biederman
2005-10-28 15:45 ` Alejandro Bonilla
2005-10-28 16:09 ` Eric W. Biederman
2005-10-30 22:24 ` Alan Cox
2005-11-02 16:20 ` Lennart Sorensen
2005-10-27 22:12 ` Andi Kleen
2005-10-27 21:09 ` linux-os (Dick Johnson)
2005-10-27 21:32 ` Bernd Eckenfels
-- strict thread matches above, loose matches on Subject: below --
2005-10-28 20:58 Lukas Hejtmanek
2005-10-29 3:32 ` Dave Jones
2005-10-29 11:15 ` Marcel Holtmann
2005-10-30 6:49 ` Dave Jones
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=20051027221158.M52510@linuxwireless.org \
--to=abonilla@linuxwireless.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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