full amount of ram not detected MSI board and Leap 42.1

Hi,

I have a fairly new MSI motherboard that I purchased with 4 8gb Kingston
ram for a total of 32gb of memory. My MSI board is a 7693v4.0 MSI gaming
motherboard (I am not a gamer, I just like to use things that have good
performance). My processor is an AMD Phenom™ II X4 955 Processor.

My memory chips are Kingston Hyperx 8gb 1866MHz chips. The specific code
on the box for them is HX318C10FB/8.

I am running opensuse Leap 42.1 with KDE Plasma 5. I first installed
this on 13.2, and I had the same results as on 42.1, which I will
describe below.

My motherboard is able to handle 32gb of ram, according to the
manufacturer (although it does say it limits access to the very last gb,
so really only 31 gb is available).

In the BIOS (UEFI), it detects the full 32gb of ram.

In opensuse, it only detects 24gb of ram, as you can see here:


> free -m
total       used       free     shared    buffers     cached
Mem:         24010       4467      19542         57        195       1571
-/+ buffers/cache:       2700      21309
Swap:        15281          0      15281

So, I would certainly like to make sure I have full access to all 32gb
of memory.

My kernel is:


> uname -a
Linux tribaltrekker 4.1.13-5-default #1 SMP PREEMPT Thu Nov 26 16:35:17
UTC 2015 (49475c3) x86_64 x86_64 x86_64 GNU/Linux

and this is a memory output from dmicode:


# dmidecode -t memory
# dmidecode 2.12
# SMBIOS entry point at 0x000f04c0
SMBIOS 2.8 present.

Handle 0x0027, DMI type 16, 23 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 32 GB
Error Information Handle: Not Provided
Number Of Devices: 4


Handle 0x0029, DMI type 17, 40 bytes

Memory Device

Array Handle: 0x0027

Error Information Handle: Not Provided

Total Width: 64 bits

Data Width: 64 bits

Size: 8192 MB
Form Factor: DIMM
Set: None
Locator: A1_DIMM0
Bank Locator: A1_BANK0
Type: DDR3
Type Detail: Synchronous Unbuffered (Unregistered)
Speed: 933 MHz
Manufacturer: Kingston
Serial Number: 4C027A56
Asset Tag: A1_AssetTagNum0
Part Number: KHX1866C10D3/8G
Rank: 2
Configured Clock Speed: 800 MHz
Minimum voltage:  Unknown
Maximum voltage:  Unknown
Configured voltage:  Unknown

Handle 0x002B, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x0027
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 8192 MB
Form Factor: DIMM
Set: None
Locator: A1_DIMM1
Bank Locator: A1_BANK1
Type: DDR3
Type Detail: Synchronous Unbuffered (Unregistered)
Speed: 933 MHz
Manufacturer: Kingston
Serial Number: 5002F88B
Asset Tag: A1_AssetTagNum1
Part Number: KHX1866C10D3/8G
Rank: 2
Configured Clock Speed: 800 MHz
Minimum voltage:  Unknown
Maximum voltage:  Unknown
Configured voltage:  Unknown

Handle 0x002D, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x0027
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 8192 MB
Form Factor: DIMM
Set: None
Locator: A1_DIMM2
Bank Locator: A1_BANK2
Type: DDR3
Type Detail: Synchronous Unbuffered (Unregistered)
Speed: 933 MHz
Manufacturer: Kingston
Serial Number: 5202308C
Asset Tag: A1_AssetTagNum2
Part Number: KHX1866C10D3/8G
Rank: 2
Configured Clock Speed: 800 MHz
Minimum voltage:  Unknown
Maximum voltage:  Unknown
Configured voltage:  Unknown

Handle 0x002F, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x0027
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 8192 MB
Form Factor: DIMM
Set: None
Locator: A1_DIMM3
Bank Locator: A1_BANK3
Type: DDR3
Type Detail: Synchronous Unbuffered (Unregistered)
Speed: 933 MHz
Manufacturer: Kingston
Serial Number: 77021CED
Asset Tag: A1_AssetTagNum3
Part Number: KHX1866C10D3/8G
Rank: 2
Configured Clock Speed: 800 MHz
Minimum voltage:  Unknown
Maximum voltage:  Unknown
Configured voltage:  Unknown

So dmicode indicates all 4 slots are being read. Curiously though it has
2 listed at 800MHz speed and 2 listed at 933MHz speed, while I know that
the chips I bought are 1866 MHz.

Here is one last item:


# cat /proc/meminfo | grep MemTotal
MemTotal:       24586524 kB

Does anyone have an idea why it would not be seeing all my memory? Is
there some kernel parameter I can change to get it to read the memory?

Thanks in advance,


G.O.
Box #1: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB
Box #2: 13.1 | KDE 4.12 | AMD Athlon X3 | 64 | 4GB
Laptop #1: 13.1 | KDE 4.12 | Core i7-2620M | 64 | 8GB
Laptop #2: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB

On Tue 12 Jan 2016 08:39:43 AM CST, grglsn wrote:

Hi,

I have a fairly new MSI motherboard that I purchased with 4 8gb
Kingston ram for a total of 32gb of memory. My MSI board is a 7693v4.0
MSI gaming motherboard (I am not a gamer, I just like to use things
that have good performance). My processor is an AMD Phenom™ II X4
955 Processor.

My memory chips are Kingston Hyperx 8gb 1866MHz chips. The specific
code on the box for them is HX318C10FB/8.

I am running opensuse Leap 42.1 with KDE Plasma 5. I first installed
this on 13.2, and I had the same results as on 42.1, which I will
describe below.

My motherboard is able to handle 32gb of ram, according to the
manufacturer (although it does say it limits access to the very last
gb, so really only 31 gb is available).

In the BIOS (UEFI), it detects the full 32gb of ram.

In opensuse, it only detects 24gb of ram, as you can see here:

free -m
total used free shared buffers
cached Mem: 24010 4467 19542 57
195 1571 -/+ buffers/cache: 2700 21309
Swap: 15281 0 15281

So, I would certainly like to make sure I have full access to all 32gb
of memory.

My kernel is:

uname -a
Linux tribaltrekker 4.1.13-5-default #1 SMP PREEMPT Thu Nov 26 16:35:17
UTC 2015 (49475c3) x86_64 x86_64 x86_64 GNU/Linux

and this is a memory output from dmicode:

dmidecode -t memory

dmidecode 2.12

SMBIOS entry point at 0x000f04c0

SMBIOS 2.8 present.

Handle 0x0027, DMI type 16, 23 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 32 GB
Error Information Handle: Not Provided
Number Of Devices: 4

Handle 0x0029, DMI type 17, 40 bytes

Memory Device

Array Handle: 0x0027

Error Information Handle: Not Provided

Total Width: 64 bits

Data Width: 64 bits

Size: 8192 MB
Form Factor: DIMM
Set: None
Locator: A1_DIMM0
Bank Locator: A1_BANK0
Type: DDR3
Type Detail: Synchronous Unbuffered (Unregistered)
Speed: 933 MHz
Manufacturer: Kingston
Serial Number: 4C027A56
Asset Tag: A1_AssetTagNum0
Part Number: KHX1866C10D3/8G
Rank: 2
Configured Clock Speed: 800 MHz
Minimum voltage: Unknown
Maximum voltage: Unknown
Configured voltage: Unknown

Handle 0x002B, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x0027
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 8192 MB
Form Factor: DIMM
Set: None
Locator: A1_DIMM1
Bank Locator: A1_BANK1
Type: DDR3
Type Detail: Synchronous Unbuffered (Unregistered)
Speed: 933 MHz
Manufacturer: Kingston
Serial Number: 5002F88B
Asset Tag: A1_AssetTagNum1
Part Number: KHX1866C10D3/8G
Rank: 2
Configured Clock Speed: 800 MHz
Minimum voltage: Unknown
Maximum voltage: Unknown
Configured voltage: Unknown

Handle 0x002D, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x0027
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 8192 MB
Form Factor: DIMM
Set: None
Locator: A1_DIMM2
Bank Locator: A1_BANK2
Type: DDR3
Type Detail: Synchronous Unbuffered (Unregistered)
Speed: 933 MHz
Manufacturer: Kingston
Serial Number: 5202308C
Asset Tag: A1_AssetTagNum2
Part Number: KHX1866C10D3/8G
Rank: 2
Configured Clock Speed: 800 MHz
Minimum voltage: Unknown
Maximum voltage: Unknown
Configured voltage: Unknown

Handle 0x002F, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x0027
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 8192 MB
Form Factor: DIMM
Set: None
Locator: A1_DIMM3
Bank Locator: A1_BANK3
Type: DDR3
Type Detail: Synchronous Unbuffered (Unregistered)
Speed: 933 MHz
Manufacturer: Kingston
Serial Number: 77021CED
Asset Tag: A1_AssetTagNum3
Part Number: KHX1866C10D3/8G
Rank: 2
Configured Clock Speed: 800 MHz
Minimum voltage: Unknown
Maximum voltage: Unknown
Configured voltage: Unknown

So dmicode indicates all 4 slots are being read. Curiously though it
has 2 listed at 800MHz speed and 2 listed at 933MHz speed, while I know
that the chips I bought are 1866 MHz.

Here is one last item:

cat /proc/meminfo | grep MemTotal

MemTotal: 24586524 kB

Does anyone have an idea why it would not be seeing all my memory? Is
there some kernel parameter I can change to get it to read the memory?

Thanks in advance,

Hi
Were they all matched (as in purchased a 4x8GB matched)?

No BIOS settings for voltage etc to set as per the RAM specs?

What does the following show;


journalctl -b |grep e820


Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 SP1|GNOME 3.10.2|3.12.51-60.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

Nope, you’ve misread, as it says the exact same thing for all four in regards to the frequencies … further, it looks like it is simply stating that the modules are capable of 933, but currently running at 800 … it is not uncommon that mem gets down clocked when all DIMM slots are populated. Consult your motherboard manual, as it will likely address this. If there is no limitation, then likely you only need to set it (mem speed/fq) correctly in the bios/uefi

while I know that the chips I bought are 1866 MHz.
that’s the dual data rate … 2x933 … see DDR3 SDRAM - Wikipedia

(currently, it looks like you’re running 1600)

In the BIOS (UEFI), it detects the full 32gb of ram.

In opensuse, it only detects 24gb of ram, as you can see here:

Does anyone have an idea why it would not be seeing all my memory?
No idea offhand, sorry. But Malcolm’s suggestion to read through your journal is a good first step.

Here is one last item:

cat /proc/meminfo | grep MemTotal

MemTotal: 24586524 kB

Note that this will report the same as free because free parses it from /proc/meminfo :stuck_out_tongue: … see “man free”

On 01/12/2016 08:40 PM, malcolmlewis wrote:

> Hi
> Were they all matched (as in purchased a 4x8GB matched)?
>
> No BIOS settings for voltage etc to set as per the RAM specs?
>
> What does the following show;
>

journalctl -b |grep e820

a) Yes, all matched, purchased as part of a matched set.

b) I could not find any BIOS settings for voltage or any other
specifications on the memory, except that it indicates the memory is there.

c) output from the command was empty:


george@tribaltrekker:~> journalctl -b | grep e820
george@tribaltrekker:~>


G.O.
Box #1: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB
Box #2: 13.1 | KDE 4.12 | AMD Athlon X3 | 64 | 4GB
Laptop #1: 13.1 | KDE 4.12 | Core i7-2620M | 64 | 8GB
Laptop #2: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB

Has to be as root, else there’s no output.

Have you run a memory check should be on the boot screen. If not then on the install media boot screen. Run at least over night. Just because it is new does not mean it is good.

On 01/13/2016 01:26 PM, brunomcl wrote:
>
> grglsn;2748287 Wrote:
>> c) output from the command was empty
>
> Has to be as root, else there’s no output.
>
>
Oops! Ok thanks. Here it is:


tribaltrekker:/home/george # journalctl -b | grep e820
Jan 13 11:16:07 tribaltrekker kernel: e820: BIOS-provided physical RAM map:
Jan 13 11:16:07 tribaltrekker kernel: BIOS-e820: [mem
0x0000000000000000-0x000000000009ffff] usable
Jan 13 11:16:07 tribaltrekker kernel: BIOS-e820: [mem
0x0000000000100000-0x00000000dd5ddfff] usable
Jan 13 11:16:07 tribaltrekker kernel: BIOS-e820: [mem
0x00000000dd5de000-0x00000000dd60dfff] reserved
Jan 13 11:16:07 tribaltrekker kernel: BIOS-e820: [mem
0x00000000dd60e000-0x00000000dd61dfff] ACPI data
Jan 13 11:16:07 tribaltrekker kernel: BIOS-e820: [mem
0x00000000dd61e000-0x00000000dd9fdfff] ACPI NVS
Jan 13 11:16:07 tribaltrekker kernel: BIOS-e820: [mem
0x00000000dd9fe000-0x00000000dea51fff] reserved
Jan 13 11:16:07 tribaltrekker kernel: BIOS-e820: [mem
0x00000000dea52000-0x00000000dea52fff] usable
Jan 13 11:16:07 tribaltrekker kernel: BIOS-e820: [mem
0x00000000dea53000-0x00000000dec58fff] ACPI NVS
Jan 13 11:16:07 tribaltrekker kernel: BIOS-e820: [mem
0x00000000dec59000-0x00000000df060fff] usable
Jan 13 11:16:07 tribaltrekker kernel: BIOS-e820: [mem
0x00000000df061000-0x00000000df7e1fff] reserved
Jan 13 11:16:07 tribaltrekker kernel: BIOS-e820: [mem
0x00000000df7e2000-0x00000000df7fffff] usable
Jan 13 11:16:07 tribaltrekker kernel: BIOS-e820: [mem
0x00000000fec00000-0x00000000fec01fff] reserved
Jan 13 11:16:07 tribaltrekker kernel: BIOS-e820: [mem
0x00000000fec10000-0x00000000fec10fff] reserved
Jan 13 11:16:07 tribaltrekker kernel: BIOS-e820: [mem
0x00000000fed00000-0x00000000fed00fff] reserved
Jan 13 11:16:07 tribaltrekker kernel: BIOS-e820: [mem
0x00000000fed61000-0x00000000fed70fff] reserved
Jan 13 11:16:07 tribaltrekker kernel: BIOS-e820: [mem
0x00000000fed80000-0x00000000fed8ffff] reserved
Jan 13 11:16:07 tribaltrekker kernel: BIOS-e820: [mem
0x00000000fef00000-0x00000000ffffffff] reserved
Jan 13 11:16:07 tribaltrekker kernel: BIOS-e820: [mem
0x0000000100001000-0x000000061fffffff] usable
Jan 13 11:16:07 tribaltrekker kernel: e820: update [mem
0x9826c018-0x9828a057] usable ==> usable
Jan 13 11:16:07 tribaltrekker kernel: e820: update [mem
0x9825f018-0x9826b057] usable ==> usable
Jan 13 11:16:07 tribaltrekker kernel: e820: update [mem
0x00000000-0x00000fff] usable ==> reserved
Jan 13 11:16:07 tribaltrekker kernel: e820: remove [mem
0x000a0000-0x000fffff] usable
Jan 13 11:16:07 tribaltrekker kernel: e820: last_pfn = 0x620000
max_arch_pfn = 0x400000000
Jan 13 11:16:07 tribaltrekker kernel: e820: update [mem
0xdf800000-0xffffffff] usable ==> reserved
Jan 13 11:16:07 tribaltrekker kernel: e820: last_pfn = 0xdf800
max_arch_pfn = 0x400000000
Jan 13 11:16:07 tribaltrekker kernel: e820: [mem 0xdf800000-0xfebfffff]
available for PCI devices
Jan 13 11:16:07 tribaltrekker kernel: e820: reserve RAM buffer [mem
0x9825f018-0x9bffffff]
Jan 13 11:16:07 tribaltrekker kernel: e820: reserve RAM buffer [mem
0x9826c018-0x9bffffff]
Jan 13 11:16:07 tribaltrekker kernel: e820: reserve RAM buffer [mem
0xdd5de000-0xdfffffff]
Jan 13 11:16:07 tribaltrekker kernel: e820: reserve RAM buffer [mem
0xdea53000-0xdfffffff]
Jan 13 11:16:07 tribaltrekker kernel: e820: reserve RAM buffer [mem
0xdf061000-0xdfffffff]
Jan 13 11:16:07 tribaltrekker kernel: e820: reserve RAM buffer [mem
0xdf800000-0xdfffffff]



G.O.
Box #1: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB
Box #2: 13.1 | KDE 4.12 | AMD Athlon X3 | 64 | 4GB
Laptop #1: 13.1 | KDE 4.12 | Core i7-2620M | 64 | 8GB
Laptop #2: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB

On 01/14/2016 03:56 AM, gogalthorp wrote:
>
> Have you run a memory check should be on the boot screen. If not then on
> the install media boot screen. Run at least over night. Just because it
> is new does not mean it is good.
>
>
A memory test on the boot screen - do you mean that I should install the
package memtest86+? I downloaded it and installed it, but not sure what
to do next. Do I need to run a mkinitrd and reinstall grub2 to get it
set up in the grub menu?

Or is there some other way to run a memory test on the boot screen?


G.O.
Box #1: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB
Box #2: 13.1 | KDE 4.12 | AMD Athlon X3 | 64 | 4GB
Laptop #1: 13.1 | KDE 4.12 | Core i7-2620M | 64 | 8GB
Laptop #2: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB

Hi
Do you have a 13.2 or 13.1 cd/dvd? If so it should have it on there.

So a quick check of the e820 usable areas confirms 24GB, I would suggest to run the memory test to see if there are errors.

Hi
You might also be interested in the Mailing List thread;
http://lists.opensuse.org/opensuse/2015-12/msg00813.html

So if they all pass testing, might be worth contacting the support folks
from the RAM manufacturer to see if they have any thoughts.


Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 SP1|GNOME 3.10.4|3.12.51-60.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

Another option (if available) is to try to update the Bios/uefi … example of similar situation you face: https://forums.opensuse.org/showthread.php/510568-Total-amount-of-RAM-not-detected

On 01/14/2016 09:56 PM, malcolmlewis wrote:
> Do you have a 13.2 or 13.1 cd/dvd? If so it should have it on there.
>
> So a quick check of the e820 usable areas confirms 24GB, I would suggest
> to run the memory test to see if there are errors.
>
>
I have not been able to get memtest to run. I downloaded and installed
the package, and it shows up in the grub menu, but when I select it to
boot into it, it never loads. The computer just sits there forever with
the grub screen saying it is loading memtest, but it never loads.


G.O.
Box #1: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB
Box #2: 13.1 | KDE 4.12 | AMD Athlon X3 | 64 | 4GB
Laptop #1: 13.1 | KDE 4.12 | Core i7-2620M | 64 | 8GB
Laptop #2: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB

On 01/15/2016 12:06 AM, Tyler K wrote:
>
> Another option (if available) is to try to update the Bios/uefi …
> example of similar situation you face: http://tinyurl.com/zfsu8q8
>
>
Ok, I have downloaded the latest bios, but when I boot into the bios
screen and try and flash it, my pc locks up on the bios screen. I
noticed through some other searching that a windows guy with this mobo
was not able to flash the bios from a usb, but he loaded the bios on his
c drive, and then in the bios it found that file and flashed it from
there. So I am working on seeing if I need to put this file on one of my
hard drives and then see if it will show up as one of the flash bios
options when I boot up.

One of my problems that I am also dealing with (for another thread) is
that the new plasma5 is really buggy and keeps locking up on me while I
am trying to figure out what is necessary to flash the bios and see if
that solves the memory problem. I may have to focus on kde for a while
and come back to this problem.


G.O.
Box #1: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB
Box #2: 13.1 | KDE 4.12 | AMD Athlon X3 | 64 | 4GB
Laptop #1: 13.1 | KDE 4.12 | Core i7-2620M | 64 | 8GB
Laptop #2: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB

My guess it needs to be a Windows drive maybe in any case you should contact the manufacturer since a botched BIOS flash can brick a machine. So you must be absolutely certain of the procedure.

As to memory test there is one on the install media us that one. you do not have to install some arbitrary code off the net. There is also one in the13.2 bot menu but maybe they dropped it for Leap :’(

A bad memory may show up on the chip enumeration but not be added to the pool if errors are seen

On 01/17/2016 12:26 PM, gogalthorp wrote:
>
> My guess it needs to be a Windows drive maybe in any case you should
> contact the manufacturer since a botched BIOS flash can brick a machine.
> So you must be absolutely certain of the procedure.
>
> As to memory test there is one on the install media us that one. you do
> not have to install some arbitrary code off the net. There is also one
> in the13.2 bot menu but maybe they dropped it for Leap :’(
>
>
>
> A bad memory may show up on the chip enumeration but not be added to
> the pool if errors are seen
>
>
Yes, I need to contact the manufacturer. What do they normally do? I
tried flashing the bios with multiple usb sticks, and every time I click
on to load the bios, the bios freezes up. I even made the usb sticks in
windows. Fortunately I haven’t bricked it. Sending my mobo back to be
fixed, without having some kind of replacement, will leave me without a
desktop (my old one with 13.1 is packed away and I can’t get to it). I
am considering just leaving it, since at least I can get my machine
running. Any suggestions?


G.O.
Box #1: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB
Box #2: 13.1 | KDE 4.12 | AMD Athlon X3 | 64 | 4GB
Laptop #1: 13.1 | KDE 4.12 | Core i7-2620M | 64 | 8GB
Laptop #2: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB

Be sure you have read all the doc’s there maybe a jumper that has to be added/removed to allow the flash.

Hi
Have you re-read the ML thread, there have been a few updates… the suppler sent him 128GB of RAM :wink:

I would contact the MB supplier and see what they suggest…