Page 1 of 1

F5-221 Reports incorrect memory information in DMI table

Posted: 30 Dec 2020, 00:13
by DiscoSi
In reference to another thread:

viewtopic.php?f=26&t=310&start=10

It appears that the F5-221 reports incorrect memory information in the DMI table using the dmidecode command, compared to the F2-221 which seems to show the right information.

Code: Select all

# dmidecode -t memory
# dmidecode 3.1
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.

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

Handle 0x002E, DMI type 17, 40 bytes
Memory Device
	Array Handle: 0x002D
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 2048 MB
	Form Factor: SODIMM
	Set: None
	Locator: ChannelA-DIMM0
	Bank Locator: BANK 0
	Type: DDR3
	Type Detail: Synchronous
	Speed: 1600 MT/s
	Manufacturer: 0000
	Serial Number: 00000000
	Asset Tag: 9876543210
	Part Number:  .  ..  .      .. 
	Rank: Unknown
	Configured Clock Speed: 1600 MT/s
	Minimum Voltage: 1.5 V
	Maximum Voltage: 1.5 V
	Configured Voltage: 1.5 V
Looking at the output from my unit it only shows a single available memory bank which is occupied by the built in 2GB memory. It doesn't show the additional expansion slot as either empty or when memory is installed. This isn't a problem most of the time as "cat /proc/meminfo", "top" and "free" all report the full amount. When this becomes an issue is where some software, that isn't specifically written to run on these units, uses the DMI table information (rightly or wrongly) to find out the maximum installed memory.

I find it strange that the F2-221 reports the information correctly in the DMI table when the two units are likely very similar at the BIOS/motherboard level. Is there an updated BIOS or other means for the F5-221 to resolve this?

Re: F5-221 Reports incorrect memory information in DMI table

Posted: 31 Dec 2020, 16:47
by TMSupport
Hello, thank you for the reporting, we will confirm it first and get back to you later.