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

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

 



On Thu, 18 Apr 2019 18:19:46 +0300, Jarkko Nikula wrote:
> Same system. Working set (two DIMMs) is Micron and failing set is 
> Crucial. Interestingly decode-dimm was able to parse also Crucial when 
> plugged in together with Micron and all of them probed with ee1004 but 
> not when there were 2* or 4* Crusial DIMMs alone.

Dreamcat4, I have put an updated ee1004 driver at:

http://jdelvare.nerim.net/devel/lm-sensors/drivers/ee1004/

Please build it and give it a try. It includes a hack which may
workaround the weird behavior of your memory modules.

You'll still need to instantiate the 2 ee1004 devices manually, as
before. You should be able to read from the eeprom files without error
now, and hopefully decode-dimms will even print sensible values.

-- 
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