Re: [decode-dimms] Crucial Ballistix BLS2K16G4D30AESB, cannot decode / understand timings

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 11 Apr 2019 14:16:57 +0100, Dreamcat4 wrote:
> Hey there!
> I have just run decode-dimms on this brand new ram kit. After
> following instructions here:
> 
> https://www.richud.com/wiki/Ubuntu_See_Live_RAM_Timings_Decode_DIMMS
> 
> And whilst the command executes, and prints some basic information
> about my memory. It unfortunately cannot see anything more than what
> gets printed below. So I was just hoping that this might simply be
> because the program does not know how to handle / decode this ram. And
> if I can be any help, for improving support. Then please let me know
> 
> [id:~] $ sudo modprobe i2c-i801
> [id:~] $ sudo i2cdetect -l
> i2c-1    i2c           NVIDIA i2c adapter 5 at 1:00.0      I2C adapter
> i2c-2    smbus         SMBus I801 adapter at f000          SMBus adapter
> i2c-0    i2c           NVIDIA i2c adapter 4 at 1:00.0      I2C adapter
> [id:~] $ sudo i2cdetect 2
> WARNING! This program can confuse your I2C bus, cause data loss and worse!
> I will probe file /dev/i2c-2.
> I will probe address range 0x03-0x77.
> Continue? [Y/n] y
>      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00:          -- -- -- -- -- 08 -- -- -- -- -- -- --
> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 30: 30 -- -- -- 34 35 -- -- -- -- -- -- -- -- -- --
> 40: -- -- -- -- 44 -- -- -- -- -- -- -- -- -- -- --
> 50: UU -- UU -- -- -- -- -- -- -- -- -- -- -- -- --
> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 70: -- -- -- -- -- -- -- --
> [id:~] $ sudo decode-dimms
> # decode-dimms version $Revision$
> 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/2-0050
> Guessing DIMM is in                              bank 1
> 
> ---=== SPD EEPROM Information ===---
> EEPROM Checksum of bytes 0-62                    OK (0x00)
> SPD Revision                                     Invalid
> Fundamental Memory type                          Unknown (0x00)
> 
> ---=== Manufacturing Information ===---
> Manufacturer                                     GTE
> Custom Manufacturer Data                         9B 00 19 10 E1 C4 CF
> ("???????")
> Manufacturing Location Code                      0x8D
> Part Number                                      BLS16G4D30AESB.M16

For DDR4 memory you need a different kernel driver. Remove the eeprom
(or at24) driver and load the ee1004 driver instead. Then decode-dimms
should work.

If the ee1004 driver is not available in your distribution, let me know
and I'll prepare a standalone driver for you.

-- 
Jean Delvare
SUSE L3 Support



[Index of Archives]     [Linux GPIO]     [Linux SPI]     [Linux Hardward Monitoring]     [LM Sensors]     [Linux USB Devel]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux