I’m setting up a new system on Proxmox 7.1 (ie, Debian Bullseye under the hood) with the following hardware:
- 5950X
- X570 Master Rev 1.0 F36b
- 4x Kingston 32GB ECC DIMMs
- bunch of drives
- Be Quiet 900 case
The system isn’t the BEST at airflow and when doing a lot of file xfer over ZFS the RAM gets taxed a bit. And I might have overclocked the RAM to 3600mhz (from 3200mhz, lots of stability testing).
I’d like to be able to monitor the DDR temps but I’m stuggling on figuring out how to access them in Debian.
Hodge-podging together a few search results (one here: How to read DIMM temperature on Linux? : linux (reddit.com)) it seems like I might be needing to use i2c infomation, with one hint sounding like I should be seeing smbus devices listed in i2cdetect. But … i2detect doesn’t show any smbus devices, only i2c. And I’m reaaaally unfamiliar with i2c and smbus in general.
This is the output from i2cdetect -l:
i2c-3 i2c nvkm-0000:0b:00.0-aux-0004 I2C adapter
i2c-10 i2c nvkm-0000:0b:00.0-bus-0008 I2C adapter
i2c-1 i2c nvkm-0000:0b:00.0-bus-0002 I2C adapter
i2c-8 i2c nvkm-0000:0b:00.0-bus-0007 I2C adapter
i2c-6 i2c nvkm-0000:0b:00.0-bus-0006 I2C adapter
i2c-13 i2c nvkm-0000:0b:00.0-aux-0009 I2C adapter
i2c-4 i2c nvkm-0000:0b:00.0-bus-0005 I2C adapter
i2c-11 i2c nvkm-0000:0b:00.0-aux-0008 I2C adapter
i2c-2 i2c nvkm-0000:0b:00.0-bus-0004 I2C adapter
i2c-0 i2c nvkm-0000:0b:00.0-bus-0001 I2C adapter
i2c-9 i2c nvkm-0000:0b:00.0-aux-0007 I2C adapter
i2c-7 i2c nvkm-0000:0b:00.0-aux-0006 I2C adapter
i2c-14 i2c sor-0006-0f82 I2C adapter
i2c-5 i2c nvkm-0000:0b:00.0-aux-0005 I2C adapter
i2c-12 i2c nvkm-0000:0b:00.0-bus-0009 I2C adapter
But that all might be a red herring.
With the RAM having a mild OC and the case being geared for quiet over airflow (I have all fan slots populated and have a small RAM fan on the way to me) I’d like to know what the right way to monitor RAM temps would be. Eventually I’ll be trying to set up a container with grafana and will want to figure out how to get the information to that … but for now a CLI check with sensors would be fine.