1 |
Hi there! |
2 |
|
3 |
So I installed another 4 GiB RAM into a Gentoo amd64 system that had 4 GiB |
4 |
already. But it still sees only 4 GiB, not 8 GiB: |
5 |
|
6 |
leela ~ # uname -a |
7 |
Linux leela 3.6.11-gentoo #3 SMP Mon Feb 4 15:37:48 CET 2013 x86_64 AMD |
8 |
A6-3500 APU with Radeon(tm) HD Graphics AuthenticAMD GNU/Linux |
9 |
|
10 |
leela ~ # |
11 |
free -m total used free shared buffers cached |
12 |
Mem: 3688 3269 419 0 108 1050 |
13 |
-/+ buffers/cache: 2110 1577 |
14 |
Swap: 2047 54 1993 |
15 |
|
16 |
Huh? Any idea why this is? The BIOS shows the full 8GiB, and lshw finds |
17 |
it. dmidecode shows that 8G should work: |
18 |
|
19 |
leela ~ # dmidecode -t 16 |
20 |
# dmidecode 2.11 |
21 |
SMBIOS 2.7 present. |
22 |
|
23 |
Handle 0x0008, DMI type 16, 23 bytes |
24 |
Physical Memory Array |
25 |
Location: System Board Or Motherboard |
26 |
Use: System Memory |
27 |
Error Correction Type: None |
28 |
Maximum Capacity: 8 GB |
29 |
Error Information Handle: Not Provided |
30 |
Number Of Devices: 2 |
31 |
|
32 |
In case this helps, I uploaded the outputs of dmesg [1], lshw -c memory |
33 |
[2] and full dmidecode output [3]. The dmesg output is somewhat weird |
34 |
though, it has several 'vmalloc: allocation failure: 0 bytes' entries. I |
35 |
suspected those were causing the problem, but I found that I needed to |
36 |
activate CONFIG_KALLSYMS=y, and they are gone. But still only 4 GiB RAM. |
37 |
The system is using an old kernel right now, so I cannot get the current |
38 |
dmesg, sorry for this. |
39 |
|
40 |
Probably related: Since I inserted this 2nd RAM module, wakeup |
41 |
from hibernate-ram does no longer work. |
42 |
|
43 |
Does this ring any bells? I'm out of ideas. Except than pulling out the 4 |
44 |
GB, or trying another mainboard. |
45 |
|
46 |
[1] http://www.wonkology.org/tmp/lshw.txt |
47 |
[2] http://www.wonkology.org/tmp/dmesg.txt |
48 |
[3] http://www.wonkology.org/tmp/dmidecode.txt |
49 |
|
50 |
Wonko |