From: Terry Vernon <tvernon24@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel (64bit) 4GB memory support
Date: Tue, 10 May 2005 18:58:47 -0400 [thread overview]
Message-ID: <42813CA7.2030002@comcast.net> (raw)
In-Reply-To: <1115754522.4409.16.camel@cpu10>
"I do see the full 4G. With Fedora Core 2 32bit, I can use all
4G as well. All my problems started when I "upgraded" to x86_64 ..."
Are you using an old 32bit processor or a new 64bit processor? That would make a difference
Rudolf Usselmann wrote:
>On Mon, 2005-05-09 at 16:07 -0400, Lennart Sorensen wrote:
>
>
>>On Mon, May 09, 2005 at 10:56:25PM +0700, Rudolf Usselmann wrote:
>>
>>
>>>Just curious, did anybody ever look in to this at all ? I keep
>>>on downloading new kernels and trying 4GB of memory - still no
>>>luck.
>>>
>>>I did file a bug report but didn't get any notifications at all.
>>>I don't subscribe to the linux-kernel list so not sure if anything
>>>ever came up or not.
>>>
>>>Is there a way to get this fixed ?
>>>
>>>
>>How much ram do you see with 4GB installed running a 64bit kernel?
>>
>>What does /proc/meminfo show?
>>
>>How about the memory map dmesg shows at the start of boot?
>>
>>Len Sorensen
>>
>>
>
>I do see the full 4G. With Fedora Core 2 32bit, I can use all
>4G as well. All my problems started when I "upgraded" to x86_64 ...
>
>Best Regards,
>rudi
>=============================================================
>Rudolf Usselmann, ASICS World Services, http://www.asics.ws
>Your Partner for IP Cores, Design, Verification and Synthesis
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
next prev parent reply other threads:[~2005-05-11 0:00 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-11 8:16 kernel (64bit) 4GB memory support Rudolf Usselmann
2004-12-11 10:06 ` Jeff Garzik
2004-12-11 10:13 ` Rudolf Usselmann
2004-12-11 11:22 ` Andrew Walrond
2004-12-11 17:47 ` Jeff Garzik
2004-12-12 4:12 ` Rudolf Usselmann
2004-12-12 4:41 ` Zwane Mwaikambo
2004-12-12 5:10 ` Rudolf Usselmann
2004-12-12 8:32 ` Zwane Mwaikambo
2004-12-12 9:15 ` Rudolf Usselmann
2004-12-12 16:35 ` Zwane Mwaikambo
2004-12-14 12:25 ` Rudolf Usselmann
2004-12-15 4:22 ` Zwane Mwaikambo
[not found] ` <20041216074905.GA2417@c9x.org>
2004-12-16 16:09 ` Rudolf Usselmann
2004-12-20 19:49 ` Zwane Mwaikambo
2004-12-21 16:23 ` Rudolf Usselmann
2004-12-21 16:33 ` Zwane Mwaikambo
2004-12-21 16:39 ` Rudolf Usselmann
2004-12-21 16:56 ` Zwane Mwaikambo
2005-05-09 15:56 ` Rudolf Usselmann
2005-05-09 20:07 ` Lennart Sorensen
2005-05-10 19:48 ` Rudolf Usselmann
2005-05-10 20:03 ` Lee Revell
2005-05-11 5:02 ` Rudolf Usselmann
2005-05-10 22:58 ` Terry Vernon [this message]
2005-05-12 3:53 ` Stefan Smietanowski
2005-05-11 14:27 ` Lennart Sorensen
2005-05-12 3:56 ` Stefan Smietanowski
2005-05-12 4:04 ` Rudolf Usselmann
2005-05-12 15:13 ` William Lee Irwin III
2005-05-09 20:07 ` Andi Kleen
2005-05-09 22:24 ` Zwane Mwaikambo
2005-05-10 19:50 ` Rudolf Usselmann
2005-05-09 23:13 ` kernel (64bit) 4GB memory support II Andi Kleen
2005-01-13 17:26 ` kernel (64bit) 4GB memory support Rudolf Usselmann
2005-01-14 23:34 ` Zwane Mwaikambo
2005-01-15 5:34 ` Rudolf Usselmann
2005-01-17 4:54 ` Zwane Mwaikambo
2004-12-11 11:35 ` bert hubert
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=42813CA7.2030002@comcast.net \
--to=tvernon24@comcast.net \
--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