Hello,
even so I installed the 64bit version of opensuse 11.2 only 3 instead of the 4Gb Ram installed are recognized.
In the BIOS 4096M are recognized.
I tried to fix it by adding mem=4096M to the grub configuration but nothing changed.
I’m working on some engineering simulations so memory is important.
Any suggestions how to fix the problem?
Who exactly says only 3GB are adressed?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I don’t remember the maximum of memory recognized by default, I
supose you’re using the Desktop kernel, try the PAE kernel
VampirD
Microsoft Windows is like air conditioning
Stops working when you open a window.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAkwH86UACgkQJQ+0ABWtaVk1WwCgu5+BudZWZOofkgrvnlEAO9Mn
L3YAoL9KScJ3tRskHcPKfYhCKlKtOq2f
=qz/T
-----END PGP SIGNATURE-----
I supose you’re using the Desktop kernel, try the PAE kernel
SuSEs desktop-Kernel is a pae-Kernel.
Of course, all of you know that PAE is a 32-bit concept, and that the
subject says this is a 64-bit system.
What does the free command say?
free -m says:
total used free shared buffers cached
Mem: 3017 2088 929 0 66 1655
-/+ buffers/cache: 366 2650
Swap: 3151 0 3151
Check your BIOS for an option called “Memory Remapping” or the like and enable it in case it’s deactivated.
there is no such option “memory remapping” - I have a MSI P6N SLI board.
What does ‘uname -a’ return?
If you run memtest86+, how much memory does it find?
there is no such option “memory remapping” - I have a MSI P6N SLI board.
Just did some research - memory remapping is enabled by default on this board, so the problem is caused by something else. Yet the symptoms are not too exotic with P6N-boards, but the solutions I read deal with installing some patch in Vista or lowering the RAMs voltage (both topics I have no idea about).
i do not have a copy of the user/setup manual for that board, and i’m
not gonna track one down on the web…but, you should…and read the
RAM requirements…closely…
make sure you meet them…
-right type
-right sizes
-right install layout…for example, some boards will let you have
(say) one 2GB stick and two 1GB sticks to total 4GB, some will ONLY
allow 2 with each of 2GB, etc etc etc (see, i don’t know if your board
has four slots or 15…maybe you have 8 times .5GB, i don’t
know)…the point is you MUST follow the rules laid out in the
motherboards manual…oh, and i guess some boards might let you mix
RAM speeds, i don’t know…but, you have to know what your board will
allow, or it will not work…unfortunately you can’t just make it up
depending on what RAM is on sale today…
and, who knows if the box maker followed the board maker’s rules?
my guess it it is either an install mis-match or you have a MB problem…
–
DenverD (Linux Counter 282315)
CAVEAT: http://is.gd/bpoMD
posted via NNTP w/TBird 2.0.0.23 | KDE 3.5.7 | openSUSE 10.3
2.6.22.19-0.4-default SMP i686
AMD Athlon 1 GB RAM | GeForce FX 5500 | ASRock K8Upgrade-760GX |
CMedia 9761 AC’97 Audio
gropiuskalle wrote:
>
> Who exactly says only 3GB are adressed?
>
Also remember that a fully populated memory will show less than 4GB
because of the system requirements such as the graphics cards
memory blocking some of the usable memory. Example 4GB system (max
memory 4GB)with 512MB graphic card will show roughly 3.5GB
available. If you have a 3 GB system it will show all the 3GB
available. This is true on Linux or Windows.
–
Russ
| openSUSE 11.2 (2.6.31.12-0.2-desktop) x86_64 | KDE 4.4.3 | Intel
Core 2 Dual E7200 | 4 GB RAM | GeForce 8400 GS | 320GB Disc (2) |
The board is OK, BIOS shows 4 GB. But BIOS does not test RAM. Run memtest on it, perform the full test, my 2 cents are that one of the RAM bars is faulty.
Any 64bit linux should be able to see RAM up to 128 TB (no typo), so that leaves only the RAM itself.
To run an extra check: download a 64bit KDE4 LiveCD, boot from it, see what sysinfo in Konqueror says. If this says 4GB, there’s something wrong in your install, couldn’t imagine what. Or it would be a DVD that has a 64bit sticker on it, but is containing the 32bit version…
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
So, what is the difference between the kernel-desktop and the
kernel-pae? only optimization for the desktop?
And why are people trying to find a hardware fail in detect the 4GB of
RAM if the OP has said the BIOS detect 4GB?
VampirD
Microsoft Windows is like air conditioning
Stops working when you open a window.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAkwJW6oACgkQJQ+0ABWtaVnXxwCdGjr8/5cY6qzgmtiNv1IuiRAi
IhkAnAuHc7zed7qXSYoJUeO0L5GA6sBC
=PM1B
-----END PGP SIGNATURE-----
Collect more information. Do
dmesg | grep BIOS
This should give you a map. Mine for example shows that some memory has been remapped above 4G to allow for some non-memory areas under 4G.
0.000000] BIOS-provided physical RAM map:
0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
0.000000] BIOS-e820: 0000000000100000 - 00000000cfee0000 (usable)
0.000000] BIOS-e820: 00000000cfee0000 - 00000000cfee3000 (ACPI NVS)
0.000000] BIOS-e820: 00000000cfee3000 - 00000000cfef0000 (ACPI data)
0.000000] BIOS-e820: 00000000cfef0000 - 00000000cff00000 (reserved)
0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
0.000000] BIOS-e820: 0000000100000000 - 0000000130000000 (usable)
0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
0.000000] #4 [000009f800 - 0000100000] BIOS reserved ==> [000009f800 - 0000100000]
Hello,
here is the cause of the problem:dmesg | grep BIOS
0.000000] BIOS-provided physical RAM map:
0.000000] BIOS-e820: 0000000000000000 - 000000000009b000 (usable)
0.000000] BIOS-e820: 000000000009b000 - 00000000000a0000 (reserved)
0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
0.000000] BIOS-e820: 0000000000100000 - 00000000bffd0000 (usable)
0.000000] BIOS-e820: 00000000bffd0000 - 00000000bffde000 (ACPI data)
0.000000] BIOS-e820: 00000000bffde000 - 00000000c0000000 (ACPI NVS)
0.000000] BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
0.000000] BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
0.000000] BIOS-e820: 0000000100000000 - 0000000140000000 (usable)
0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working around it.
0.000000] WARNING: BIOS bug: CPU MTRRs don't cover all of memory, losing 1024MB of RAM.
0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
0.000000] #4 [000009b000 - 0000100000] BIOS reserved ==> [000009b000 - 0000100000]
0.000000] Calgary: detecting Calgary via BIOS EBDA area
1.692366] ata1: nv_mode_filter: 0x3f39f&0x3f39f->0x3f39f, BIOS=0x3f000 (0xc600c0c0) ACPI=0x3f01f (20:900:0x11)
1.872494] ata2: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc600c0c0) ACPI=0x701f (60:60:0x15)
1.872499] ata2: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc600c0c0) ACPI=0x701f (60:60:0x15)
31.476125] BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
What can I do?
The RAM map includes areas above 4GB, as this line shows. So in principle, the 64-bit kernel should be able to use it.
0.000000] BIOS-e820: 0000000100000000 - 0000000140000000 (usable)
Not sure why it doesn’t. Are you absolutely sure you are running an x86_64 kernel? What does
uname -a
print out?
That’s why I asked if he was sure that it’s not a 64bit sticker on a medium containing 32bit packages.
uname -a
2.6.31.12-0.2-desktop #1 SMP PREEMPT 2010-03-16 21:25:39 +0100 x86_64 x86_64 x86_64 GNU/Linux
I downloaded Opensuse 11.2 x86_64 from the opensuse website.
Try replacing kernel-desktop by kernel-default. Accept the changes, reboot, reinstall video driver if installed manually and see what happens.