-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Understand why decode-dimms sometimes doesn't detect anything #11
Comments
Current output on arch:
Same computer, decode-dimms worked in 2018 and detected absolutely nothing in 2019. Now it's detecting something that has the correct checksum and nothing else. Great. |
decode-dimms is now recommending the ee1004 module, too |
Also test this alternative: https://www.phoronix.com/news/Linux-DIMM-Details-As-Root |
seems at least for the ee1004 module you have some additional steps needed to actually tell the driver where the spds are. https://hackaday.com/2023/04/18/linux-fu-reading-your-memorys-memory/ |
Some RAMs are not supported and that's it, but this article suggests that after loading some modules related to SMBus the program may work: https://www.richud.com/wiki/Ubuntu_See_Live_RAM_Timings_Decode_DIMMS
Unless it means the usual
at24
andeeprom
modules, which we are already loading.Also, why did it break completely on Arch and doesn't detect anything anymore, while 6 months ago it worked?
The text was updated successfully, but these errors were encountered: