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

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

 



BTW I also just tried compiling the module from the .c file you linked
in your 2nd message. However it's same result (no new device
detected).

Could this be anything to do with the motherboard?
This is an 'asus maximus ix apex' motherboard.



On Thu, Apr 11, 2019 at 5:47 PM Dreamcat4 <dreamcat4@xxxxxxxxx> wrote:
>
> Thank you,
> I have just upgraded my kernel to 5.0.7 (ubuntu source). I believe
> that i may have followed your instruction (best i can!). However
> unfortunately there was some kind of a problem. Not sure why.
>
> # modprobe ee1004
>
> However it is not seem to work as expected. Because there is no new
> i2c device appearing, only the other 2 entries for my nvidia gpu.
>
> [root:/sys/bus/i2c/devices] # ls
> i2c-0  i2c-1
>
> So then there is no new folder created at the location:
>
> /sys/bus/i2c/devices/i2c-2
>
> and therefore cannot write strings like 0x50 to 'new_device'
>
> What i can still do is:
>
> # sudo modprobe i2c-i801
>
> to create the missing i2c-2 device there. But you told me that was
> wrong, not to load that module.
> And anyhow the next command does not work:
>
> [root:/sys/bus/i2c/devices/i2c-2] 1 # echo ee1004 0x50 >
> /sys/bus/i2c/devices/i2c-2/new_device
> bash: echo: write error: Invalid argument
>
> root:/sys/bus/i2c/devices/i2c-2] # cat new_device
> cat: new_device: Permission denied
>
> Of course later on 'decode-dimms' then also fails, maybe due to
> previous error(s)
>
> # decode-dimms
> No EEPROM found, try loading the eeprom or at24 module
>
>
>
> (Any further help appreciated)
> Kind Regards
>
> On Thu, Apr 11, 2019 at 5:25 PM Jean Delvare <jdelvare@xxxxxxx> wrote:
> >
> > On Thu, 11 Apr 2019 18:17:39 +0200, Jean Delvare wrote:
> > > 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.
> >
> > Oh, I forgot... The ee1004 driver does not currently instantiate
> > devices automatically. You'll have to let it know where your SPD
> > EEPROMs are:
> >
> > # modprobe ee1004
> > # echo ee1004 0x50 > /sys/bus/i2c/devices/i2c-2/new_device
> > # echo ee1004 0x52 > /sys/bus/i2c/devices/i2c-2/new_device
> >
> > > If the ee1004 driver is not available in your distribution, let me know
> > > and I'll prepare a standalone driver for you.
> >
> > It's ready if you need it:
> >
> > http://jdelvare.nerim.net/devel/lm-sensors/drivers/ee1004/
> >
> > Generic instructions for building a standalone driver are at:
> >
> > http://jdelvare.nerim.net/devel/lm-sensors/drivers/INSTALL
> >
> > --
> > 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