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