Please help explain need for EEPROM for hardinfo System Profiler and Benchmark
EEPROM stands for Electrically Erasable Programmable Read Only Memory….
….but AFAIK it resides on a chip somewhere on the mainboard.
So is this statement on hardinfo page just saying that the eeprom it requires is just a reader of this semi-permanent memory needed to ascertain the RAM speed…? The module eeprom must be loaded to display info about your currently installed memory. Load with modprobe eeprom and refresh the module screen.
Not sure how to implement modpobe eeprom…? BTW my hardinfo is the Arch gtk2 version as I do not have any AUR packages at present.
Hey thanks for the type 17 command – did not know that one. Thought it was uppercase G or video? Anyway here is the output from the first bank – second bank is the same. As you can see RAM Speed is 1333 MT per second as is the second bank.
Please correct me if I am geeky wrong but think we should add the two banks together to give an effective RAM speed of 2666 MT/s. (megatransfers per second - 1 MT/s is one million transfers per second.)
[anglo@anglo-latitudee6420 ~]$ sudo dmidecode --type 17
[sudo] password for anglo:
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 2.6 present.
Handle 0x0042, DMI type 17, 28 bytes
Array Handle: 0x0041
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 4 GB
Form Factor: SODIMM
Bank Locator: BANK 0
Type Detail: Synchronous
Speed: 1333 MT/s
Serial Number: 624ACBEB
Asset Tag: 9876543210
Part Number: M471B5273DH0-CH9
Okay correct – but I am still learning and may get there one day.
This terminal command also gives the same output - sudo dmidecode -t memory
CPU-Z in Windows is what we need but hardinfo System Profiler and Benchmark needs EEPROM to get that function.
Reading SPD values from memory modules (optional)
To read the SPD timing values from memory modules, install the i2c-tools package. Once installed, load the eeprom kernel module.
# modprobe eeprom
Finally, view memory information with decode-dimms.
Here is partial output from one machine:
Memory Serial Presence Detect Decoder
By Philip Edelbrock, Christian Zuckschwerdt, Burkart Lingner,
Jean Delvare, Trent Piepho and others
Decoding EEPROM: /sys/bus/i2c/drivers/eeprom/0-0050
Guessing DIMM is in bank 1
---=== SPD EEPROM Information ===---
EEPROM CRC of bytes 0-116 OK (0x583F)
# of bytes written to SDRAM EEPROM 176
Total number of bytes in EEPROM 512
Fundamental Memory type DDR3 SDRAM
Module Type UDIMM
---=== Memory Characteristics ===---
Fine time base 2.500 ps
Medium time base 0.125 ns
Maximum module speed 1066MHz (PC3-8533)
Size 2048 MB
Banks x Rows x Columns x Bits 8 x 14 x 10 x 64
SDRAM Device Width 8 bits
Supported CAS Latencies (tCL) 8T, 7T, 6T, 5T
---=== Timing Parameters ===---
Minimum Write Recovery time (tWR) 15.000 ns
Minimum Row Active to Row Active Delay (tRRD) 7.500 ns
Minimum Active to Auto-Refresh Delay (tRC) 49.500 ns
Minimum Recovery Delay (tRFC) 110.000 ns
Minimum Write to Read CMD Delay (tWTR) 7.500 ns
Minimum Read to Pre-charge CMD Delay (tRTP) 7.500 ns
Minimum Four Activate Window Delay (tFAW) 30.000 ns
---=== Optional Features ===---
Operable voltages 1.5V
RZQ/6 supported? Yes
RZQ/7 supported? Yes
DLL-Off Mode supported? No
Operating temperature range 0-85C
Refresh Rate in extended temp range 1X
Auto Self-Refresh? Yes
On-Die Thermal Sensor readout? No
Partial Array Self-Refresh? No
Thermal Sensor Accuracy Not implemented
SDRAM Device Type Standard Monolithic
---=== Physical Characteristics ===---
Module Height (mm) 15
Module Thickness (mm) 1 front, 1 back
Module Width (mm) 133.5
Module Reference Card B
---=== Manufacturer Data ===---
Module Manufacturer Invalid
Manufacturing Location Code 0x02
Part Number OCZ3G1600LV2G
I don’t know why you are asking this? EndeavourOS is based on Arch. Yes it’s terminal centric. You can get all the info you need from the Arch Wiki and also using the tools provide such as man pages. You can install different tools which can be used to get this kind of information. You can get this information from your hardware which is more accurate.
Well with your help we got the software to work fine by fixing the one menu item which did not work - now that it works my mind wondered what is memory SPD and what are these “timings”
Out of interest I tried to find the terminal command for SPD memory and timings - I failed
As @Elloquin Jack pointed to Arch page with link you need to install the i2c-tools package to enable command decode-dimms
Thanks to all for the education