11:23 a.m.
All,
I am running F7 in 64-bit mode on a laptop. I have upgraded the memory
from 3G to 4G (Bios confirms it) but kernel sees only 3.2G (i have
passed mem=4096M kernel parameter). Wondering if i am missing anything here.
Snippet from dmesg
Kernel command line: ro root=LABEL=/ rhgb quiet mem=4096M
Memory: 3345780k/3407424k available (2321k kernel code, 61256k reserved,
1377k data, 316k init)
Thanks
Srikanth
3:35 p.m.
Srikanth Konjarla wrote:
I am running F7 in 64-bit mode on a laptop. I have upgraded the
memory
from 3G to 4G (Bios confirms it) but kernel sees only 3.2G (i have
passed mem=4096M kernel parameter). Wondering if i am missing anything
here.
Snippet from dmesg
Kernel command line: ro root=LABEL=/ rhgb quiet mem=4096M
Memory: 3345780k/3407424k available (2321k kernel code, 61256k reserved,
1377k data, 316k init)
Just a hunch but I think it might have something to do with PCI/PCI-E
address space allocations. Do you have a graphics card with a lot of RAM
on it for example? See if your BIOS has a feature similar to "remap PCI
address space above physical memory" or similar sounding option and
enable it.
--
Ian Chapman.
7:46 p.m.
Srikanth Konjarla <srikanth.konjarla(a)gmail.com> writes:
I am running F7 in 64-bit mode on a laptop. I have upgraded the
memory
from 3G to 4G (Bios confirms it) but kernel sees only 3.2G (i have
passed mem=4096M kernel parameter). Wondering if i am missing anything
here.
What you are missing is the really nasty design of IBM-PC legacy
memory allocations. ;-)
Play around in your BIOS and see if you can map the excess memory
above 4GB. Often the labels for the settings will have the term
"MTRR" in the name. When you get it right "cat /proc/mtrr" should
show the extra 750MBytes mapped above 4 Gigs. The setting names might
not make much sense (at least they don't on my Tyan). You might need
to just try them all and see what effect they have on the linux mttr
settings. Here is what it looks like on my board when I have it set
to see all 4 GBytes:
$ cat /proc/mtrr
reg00: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1
reg01: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
reg02: base=0xc0000000 (3072MB), size= 256MB: write-back, count=1
reg03: base=0xcff00000 (3327MB), size= 1MB: uncachable, count=1
reg04: base=0x100000000 (4096MB), size= 512MB: write-back, count=1
reg05: base=0x120000000 (4608MB), size= 256MB: write-back, count=1
reg06: base=0xd8000000 (3456MB), size= 128MB: write-combining, count=2
Notice the first 3 entries are 3.25 GBytes (reg00, reg01 and reg02).
The last 0.75GBytes are mapped above 4GByte (reg04 and reg05).
-wolfgang
--
Wolfgang S. Rupprecht http://www.wsrcc.com/wolfgang/
IPv6 on Fedora 7 http://www.wsrcc.com/wolfgang/fedora/ipv6-tunnel.html
9:37 p.m.
Thanks for the response. Interestingly, i could not find any BIOS
options pertaining to memory.
I found the following.
# cat /proc/mtrr
reg00: base=0xfeda0000 (4077MB), size= 128KB: write-back, count=1
reg01: base=0xfff00000 (4095MB), size= 1MB: write-protect, count=1
reg02: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1
reg03: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
reg04: base=0xc0000000 (3072MB), size= 256MB: write-back, count=1
Could be incompatible memory modules or something?
Thanks
Srikanth
Wolfgang S. Rupprecht wrote:
Srikanth Konjarla <srikanth.konjarla(a)gmail.com> writes:
> I am running F7 in 64-bit mode on a laptop. I have upgraded the memory
> from 3G to 4G (Bios confirms it) but kernel sees only 3.2G (i have
> passed mem=4096M kernel parameter). Wondering if i am missing anything
> here.
What you are missing is the really nasty design of IBM-PC legacy
memory allocations. ;-)
Play around in your BIOS and see if you can map the excess memory
above 4GB. Often the labels for the settings will have the term
"MTRR" in the name. When you get it right "cat /proc/mtrr" should
show the extra 750MBytes mapped above 4 Gigs. The setting names might
not make much sense (at least they don't on my Tyan). You might need
to just try them all and see what effect they have on the linux mttr
settings. Here is what it looks like on my board when I have it set
to see all 4 GBytes:
$ cat /proc/mtrr
reg00: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1
reg01: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
reg02: base=0xc0000000 (3072MB), size= 256MB: write-back, count=1
reg03: base=0xcff00000 (3327MB), size= 1MB: uncachable, count=1
reg04: base=0x100000000 (4096MB), size= 512MB: write-back, count=1
reg05: base=0x120000000 (4608MB), size= 256MB: write-back, count=1
reg06: base=0xd8000000 (3456MB), size= 128MB: write-combining, count=2
Notice the first 3 entries are 3.25 GBytes (reg00, reg01 and reg02).
The last 0.75GBytes are mapped above 4GByte (reg04 and reg05).
-wolfgang
2:36 a.m.
Try use the kernel-PAE!
Read a section 9.3 this document:
http://mirror.atrpms.net/fedora/linux/releases/7/Fedora/i386/os/RELEASE-N...
On Mon, 2007-07-02 at 22:37 -0400, Srikanth Konjarla wrote:
Thanks for the response. Interestingly, i could not find any BIOS
options pertaining to memory.
I found the following.
# cat /proc/mtrr
reg00: base=0xfeda0000 (4077MB), size= 128KB: write-back, count=1
reg01: base=0xfff00000 (4095MB), size= 1MB: write-protect, count=1
reg02: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1
reg03: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
reg04: base=0xc0000000 (3072MB), size= 256MB: write-back, count=1
Could be incompatible memory modules or something?
Thanks
Srikanth
Wolfgang S. Rupprecht wrote:
> Srikanth Konjarla <srikanth.konjarla(a)gmail.com> writes:
>> I am running F7 in 64-bit mode on a laptop. I have upgraded the memory
>> from 3G to 4G (Bios confirms it) but kernel sees only 3.2G (i have
>> passed mem=4096M kernel parameter). Wondering if i am missing anything
>> here.
>
> What you are missing is the really nasty design of IBM-PC legacy
> memory allocations. ;-)
>
> Play around in your BIOS and see if you can map the excess memory
> above 4GB. Often the labels for the settings will have the term
> "MTRR" in the name. When you get it right "cat /proc/mtrr"
should
> show the extra 750MBytes mapped above 4 Gigs. The setting names might
> not make much sense (at least they don't on my Tyan). You might need
> to just try them all and see what effect they have on the linux mttr
> settings. Here is what it looks like on my board when I have it set
> to see all 4 GBytes:
>
> $ cat /proc/mtrr
> reg00: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1
> reg01: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
> reg02: base=0xc0000000 (3072MB), size= 256MB: write-back, count=1
> reg03: base=0xcff00000 (3327MB), size= 1MB: uncachable, count=1
> reg04: base=0x100000000 (4096MB), size= 512MB: write-back, count=1
> reg05: base=0x120000000 (4608MB), size= 256MB: write-back, count=1
> reg06: base=0xd8000000 (3456MB), size= 128MB: write-combining, count=2
>
> Notice the first 3 entries are 3.25 GBytes (reg00, reg01 and reg02).
> The last 0.75GBytes are mapped above 4GByte (reg04 and reg05).
>
> -wolfgang
11:29 a.m.
At 4:36 AM -0300 7/3/07, Marcelo de Souza Sant'Anna wrote:
Try use the kernel-PAE!
...
He's running in 64 bit mode. Read the thread:
>> Srikanth Konjarla
>><<mailto:srikanth.konjarla@gmail.com>srikanth.konjarla@gmail.com>
writes:
>>> I am running F7 in 64-bit mode on a laptop. I have upgraded the memory
Switching back to 32 bit mode won't help. He has a problem with the BIOS
and MTRR, and hasn't found a BIOS section for setting up the memory. IIRC,
advice on this list in the past month about MTRR showed how to work around
the issue.
--
____________________________________________________________________
TonyN.:' <mailto:tonynelson@georgeanelson.com>
' <http://www.georgeanelson.com/>
2:38 a.m.
Read this too:
http://fedora.kiewel-online.de/repoview/linux/releases/7/Everything/i386/...
On Mon, 2007-07-02 at 22:37 -0400, Srikanth Konjarla wrote:
Thanks for the response. Interestingly, i could not find any BIOS
options pertaining to memory.
I found the following.
# cat /proc/mtrr
reg00: base=0xfeda0000 (4077MB), size= 128KB: write-back, count=1
reg01: base=0xfff00000 (4095MB), size= 1MB: write-protect, count=1
reg02: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1
reg03: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
reg04: base=0xc0000000 (3072MB), size= 256MB: write-back, count=1
Could be incompatible memory modules or something?
Thanks
Srikanth
Wolfgang S. Rupprecht wrote:
> Srikanth Konjarla <srikanth.konjarla(a)gmail.com> writes:
>> I am running F7 in 64-bit mode on a laptop. I have upgraded the memory
>> from 3G to 4G (Bios confirms it) but kernel sees only 3.2G (i have
>> passed mem=4096M kernel parameter). Wondering if i am missing anything
>> here.
>
> What you are missing is the really nasty design of IBM-PC legacy
> memory allocations. ;-)
>
> Play around in your BIOS and see if you can map the excess memory
> above 4GB. Often the labels for the settings will have the term
> "MTRR" in the name. When you get it right "cat /proc/mtrr"
should
> show the extra 750MBytes mapped above 4 Gigs. The setting names might
> not make much sense (at least they don't on my Tyan). You might need
> to just try them all and see what effect they have on the linux mttr
> settings. Here is what it looks like on my board when I have it set
> to see all 4 GBytes:
>
> $ cat /proc/mtrr
> reg00: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1
> reg01: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
> reg02: base=0xc0000000 (3072MB), size= 256MB: write-back, count=1
> reg03: base=0xcff00000 (3327MB), size= 1MB: uncachable, count=1
> reg04: base=0x100000000 (4096MB), size= 512MB: write-back, count=1
> reg05: base=0x120000000 (4608MB), size= 256MB: write-back, count=1
> reg06: base=0xd8000000 (3456MB), size= 128MB: write-combining, count=2
>
> Notice the first 3 entries are 3.25 GBytes (reg00, reg01 and reg02).
> The last 0.75GBytes are mapped above 4GByte (reg04 and reg05).
>
> -wolfgang
3:17 a.m.
Check the kernel version and update.
If in any case the problems persist, make a simply test with the last
kernel version 2.6.21.5
With 4 Gbyte of ram i have a problems on sata controller because that
dont recognize the HD device, but i fixed with the kernel upgrade.
Look here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242969
Bye
Giancarlo
Marcelo de Souza Sant'Anna ha scritto:
Read this too:
http://fedora.kiewel-online.de/repoview/linux/releases/7/Everything/i386/...
On Mon, 2007-07-02 at 22:37 -0400, Srikanth Konjarla wrote:
> Thanks for the response. Interestingly, i could not find any BIOS
> options pertaining to memory.
>
> I found the following.
>
> # cat /proc/mtrr
> reg00: base=0xfeda0000 (4077MB), size= 128KB: write-back, count=1
> reg01: base=0xfff00000 (4095MB), size= 1MB: write-protect, count=1
> reg02: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1
> reg03: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
> reg04: base=0xc0000000 (3072MB), size= 256MB: write-back, count=1
>
> Could be incompatible memory modules or something?
>
> Thanks
>
> Srikanth
>
> Wolfgang S. Rupprecht wrote:
> > Srikanth Konjarla <srikanth.konjarla(a)gmail.com
<mailto:srikanth.konjarla@gmail.com>> writes:
> >> I am running F7 in 64-bit mode on a laptop. I have upgraded the memory
> >> from 3G to 4G (Bios confirms it) but kernel sees only 3.2G (i have
> >> passed mem=4096M kernel parameter). Wondering if i am missing anything
> >> here.
> >
> > What you are missing is the really nasty design of IBM-PC legacy
> > memory allocations. ;-)
> >
> > Play around in your BIOS and see if you can map the excess memory
> > above 4GB. Often the labels for the settings will have the term
> > "MTRR" in the name. When you get it right "cat /proc/mtrr"
should
> > show the extra 750MBytes mapped above 4 Gigs. The setting names might
> > not make much sense (at least they don't on my Tyan). You might need
> > to just try them all and see what effect they have on the linux mttr
> > settings. Here is what it looks like on my board when I have it set
> > to see all 4 GBytes:
> >
> > $ cat /proc/mtrr
> > reg00: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1
> > reg01: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
> > reg02: base=0xc0000000 (3072MB), size= 256MB: write-back, count=1
> > reg03: base=0xcff00000 (3327MB), size= 1MB: uncachable, count=1
> > reg04: base=0x100000000 (4096MB), size= 512MB: write-back, count=1
> > reg05: base=0x120000000 (4608MB), size= 256MB: write-back, count=1
> > reg06: base=0xd8000000 (3456MB), size= 128MB: write-combining, count=2
> >
> > Notice the first 3 entries are 3.25 GBytes (reg00, reg01 and reg02).
> > The last 0.75GBytes are mapped above 4GByte (reg04 and reg05).
> >
> > -wolfgang
>
>
--
------------------------------------------------------------------------
Giancarlo del Rossi
RHCE - System Administrator
EnterMED s.r.l - Via liberta' 56 - 90143 Palermo
+39917303009 - +3991305023 - +3497609610
http://www.entermed.it - gdelrossi(a)entermed.it
-- Ennyn Durin Aran Moria: pedo mellon a minno --
------------------------------------------------------------------------
6:44 a.m.
After the installation, does the Kernel see 4G RAM?
Giancarlo del Rossi wrote:
Check the kernel version and update.
If in any case the problems persist, make a simply test with the last
kernel version 2.6.21.5
With 4 Gbyte of ram i have a problems on sata controller because that
dont recognize the HD device, but i fixed with the kernel upgrade.
Look here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242969
Bye
Giancarlo
Marcelo de Souza Sant'Anna ha scritto:
> Read this too:
>
>
http://fedora.kiewel-online.de/repoview/linux/releases/7/Everything/i386/...
>
>
> On Mon, 2007-07-02 at 22:37 -0400, Srikanth Konjarla wrote:
>> Thanks for the response. Interestingly, i could not find any BIOS
>> options pertaining to memory.
>>
>> I found the following.
>>
>> # cat /proc/mtrr
>> reg00: base=0xfeda0000 (4077MB), size= 128KB: write-back, count=1
>> reg01: base=0xfff00000 (4095MB), size= 1MB: write-protect, count=1
>> reg02: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1
>> reg03: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
>> reg04: base=0xc0000000 (3072MB), size= 256MB: write-back, count=1
>>
>> Could be incompatible memory modules or something?
>>
>> Thanks
>>
>> Srikanth
>>
>> Wolfgang S. Rupprecht wrote:
>> > Srikanth Konjarla <srikanth.konjarla(a)gmail.com
<mailto:srikanth.konjarla@gmail.com>> writes:
>> >> I am running F7 in 64-bit mode on a laptop. I have upgraded the memory
>> >> from 3G to 4G (Bios confirms it) but kernel sees only 3.2G (i have
>> >> passed mem=4096M kernel parameter). Wondering if i am missing anything
>> >> here.
>> >
>> > What you are missing is the really nasty design of IBM-PC legacy
>> > memory allocations. ;-)
>> >
>> > Play around in your BIOS and see if you can map the excess memory
>> > above 4GB. Often the labels for the settings will have the term
>> > "MTRR" in the name. When you get it right "cat
/proc/mtrr" should
>> > show the extra 750MBytes mapped above 4 Gigs. The setting names might
>> > not make much sense (at least they don't on my Tyan). You might need
>> > to just try them all and see what effect they have on the linux mttr
>> > settings. Here is what it looks like on my board when I have it set
>> > to see all 4 GBytes:
>> >
>> > $ cat /proc/mtrr
>> > reg00: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1
>> > reg01: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
>> > reg02: base=0xc0000000 (3072MB), size= 256MB: write-back, count=1
>> > reg03: base=0xcff00000 (3327MB), size= 1MB: uncachable, count=1
>> > reg04: base=0x100000000 (4096MB), size= 512MB: write-back, count=1
>> > reg05: base=0x120000000 (4608MB), size= 256MB: write-back, count=1
>> > reg06: base=0xd8000000 (3456MB), size= 128MB: write-combining, count=2
>> >
>> > Notice the first 3 entries are 3.25 GBytes (reg00, reg01 and reg02).
>> > The last 0.75GBytes are mapped above 4GByte (reg04 and reg05).
>> >
>> > -wolfgang
>>
>>
--
------------------------------------------------------------------------
Giancarlo del Rossi
RHCE - System Administrator
EnterMED s.r.l - Via liberta' 56 - 90143 Palermo
+39917303009 - +3991305023 - +3497609610
http://www.entermed.it - gdelrossi(a)entermed.it
-- Ennyn Durin Aran Moria: pedo mellon a minno --
------------------------------------------------------------------------
6:40 a.m.
Marcelo,
Thanks for the links. First, i think PAE is for 32 bit kernel and
second, it is needed if you have more than 4G (>4G). My machine does not
fall under any category.
Srikanth
Marcelo de Souza Sant'Anna wrote:
Read this too:
http://fedora.kiewel-online.de/repoview/linux/releases/7/Everything/i386/...
On Mon, 2007-07-02 at 22:37 -0400, Srikanth Konjarla wrote:
> Thanks for the response. Interestingly, i could not find any BIOS
> options pertaining to memory.
>
> I found the following.
>
> # cat /proc/mtrr
> reg00: base=0xfeda0000 (4077MB), size= 128KB: write-back, count=1
> reg01: base=0xfff00000 (4095MB), size= 1MB: write-protect, count=1
> reg02: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1
> reg03: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
> reg04: base=0xc0000000 (3072MB), size= 256MB: write-back, count=1
>
> Could be incompatible memory modules or something?
>
> Thanks
>
> Srikanth
>
> Wolfgang S. Rupprecht wrote:
> > Srikanth Konjarla <srikanth.konjarla(a)gmail.com
<mailto:srikanth.konjarla@gmail.com>> writes:
> >> I am running F7 in 64-bit mode on a laptop. I have upgraded the memory
> >> from 3G to 4G (Bios confirms it) but kernel sees only 3.2G (i have
> >> passed mem=4096M kernel parameter). Wondering if i am missing anything
> >> here.
> >
> > What you are missing is the really nasty design of IBM-PC legacy
> > memory allocations. ;-)
> >
> > Play around in your BIOS and see if you can map the excess memory
> > above 4GB. Often the labels for the settings will have the term
> > "MTRR" in the name. When you get it right "cat /proc/mtrr"
should
> > show the extra 750MBytes mapped above 4 Gigs. The setting names might
> > not make much sense (at least they don't on my Tyan). You might need
> > to just try them all and see what effect they have on the linux mttr
> > settings. Here is what it looks like on my board when I have it set
> > to see all 4 GBytes:
> >
> > $ cat /proc/mtrr
> > reg00: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1
> > reg01: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
> > reg02: base=0xc0000000 (3072MB), size= 256MB: write-back, count=1
> > reg03: base=0xcff00000 (3327MB), size= 1MB: uncachable, count=1
> > reg04: base=0x100000000 (4096MB), size= 512MB: write-back, count=1
> > reg05: base=0x120000000 (4608MB), size= 256MB: write-back, count=1
> > reg06: base=0xd8000000 (3456MB), size= 128MB: write-combining, count=2
> >
> > Notice the first 3 entries are 3.25 GBytes (reg00, reg01 and reg02).
> > The last 0.75GBytes are mapped above 4GByte (reg04 and reg05).
> >
> > -wolfgang
>
2:46 p.m.
On Tue, 03 Jul 2007 07:40:43 -0400
Srikanth Konjarla <srikanth.konjarla(a)gmail.com> wrote:
First, i think PAE is for 32 bit kernel
My understanding is the same.
and second, it is needed if you have more than 4G (>4G).
I think that's 4gb or more, not more that 4gb. I base this on the fact that I
set up a 4gb machine a few weeks ago and had to use the PAE kernel to get it to
recognize all of the installed ram.
--
MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com
6175
days inactive
6176
days old
10 comments
7 participants
participants (7)
-
Frank Cox -
Giancarlo del Rossi -
Ian Chapman -
Marcelo de Souza Sant'Anna -
Srikanth Konjarla -
Tony Nelson -
Wolfgang S. Rupprecht