lm-sensors
- Joey Houy (Unlicensed)
Install
yum install lm-sensors ## 'yum' above for CentOS, 'apt-get' if you are using Ubuntu sensors-detect sensors ## if sensors-detect does not work, and above lm-sensors command does says 'nothing to do', try below instead yum install lm_sensors.x86_64
[root@rdlab ~]# sensors coretemp-isa-0000 Adapter: ISA adapter Physical id 0: +42.0°C (high = +80.0°C, crit = +90.0°C) Core 0: +33.0°C (high = +80.0°C, crit = +90.0°C) Core 1: +35.0°C (high = +80.0°C, crit = +90.0°C) Core 2: +36.0°C (high = +80.0°C, crit = +90.0°C) Core 3: +30.0°C (high = +80.0°C, crit = +90.0°C) Core 4: +33.0°C (high = +80.0°C, crit = +90.0°C) Core 5: +32.0°C (high = +80.0°C, crit = +90.0°C)
Monitoring 'sensors'
watch -n 1 -d sensors ## continuously prints and highlights changes
k10temp-pci-00c3 (on Ubuntu 20.04)
This sensor is provided by the k10temp kernel module which handles the AMD CPU.
iwlwifi_1-virtual-0 Adapter: Virtual device temp1: +67.0°C enp68s0-pci-4400 Adapter: PCI adapter PHY Temperature: +84.0°C k10temp-pci-00c3 Adapter: PCI adapter Tdie: +93.0°C (high = +70.0°C) Tctl: +93.0°C ## ^ this is pretty hot
Known-oddities with lm_sensors
It doesn't work well with CentOS 8.x. It only does one sensor, but it is not clear on what that sensor tracks.
groans
What happens if you run 'sensors' without running 'sensors-detect'
exx@rdlab:~$ sensors
iwlwifi_1-virtual-0 <Wi-Fi adapter>
Adapter: Virtual device
temp1: +32.0°C
enp69s0-pci-4500 <Seems exclusive to TRX40>
Adapter: PCI adapter
PHY Temperature: +63.3°C
k10temp-pci-00c3 <Tdie, which is true CPU temperature; Tctl is the mirrored offset that triggers fan RPM's to increase/decrease>
Adapter: PCI adapter
Tdie: +40.1°C (high = +70.0°C)
Tctl: +40.1°C
Warning, you are going to need to manually type in 'y' for about 20-30 sensors
exx@rdlab:~$ sensors-detect
You need to be root to run this script.
exx@rdlab:~$ sudo bash
[sudo] password for exx:
exx@rdlab:~$ sudo bash
[sudo] password for exx:
root@rdlab:/home/exx# sensors-detect
# sensors-detect version 3.6.0
# Board: ASRock TRX40 Creator
# Kernel: 5.4.0-80-generic x86_64
# Processor: AMD Ryzen Threadripper 3960X 24-Core Processor (23/49/0)
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): Y
root@rdlab:/home/exx# sensors-detect # sensors-detect version 3.6.0 # Board: ASRock TRX40 Creator # Kernel: 5.4.0-80-generic x86_64 # Processor: AMD Ryzen Threadripper 3960X 24-Core Processor (23/49/0) This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): ^C root@rdlab:/home/exx# sensors-detect # sensors-detect version 3.6.0 # Board: ASRock TRX40 Creator # Kernel: 5.4.0-80-generic x86_64 # Processor: AMD Ryzen Threadripper 3960X 24-Core Processor (23/49/0) This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): Y Module cpuid loaded successfully. Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 16h thermal sensors... No AMD Family 17h thermal sensors... Success! (driver `k10temp') AMD Family 15h power sensors... No AMD Family 16h power sensors... No Hygon Family 18h thermal sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips contain embedded sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): y Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes Found `Nuvoton NCT6683D eSIO' Success! (address 0xa20, driver `nct6683') Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, we have to read from arbitrary I/O ports to probe for such interfaces. This is normally safe. Do you want to scan for IPMI interfaces? (YES/no): y Probing for `IPMI BMC KCS' at 0xca0... No Probing for `IPMI BMC SMIC' at 0xca8... No Some hardware monitoring chips are accessible through the ISA I/O ports. We have to write to arbitrary I/O ports to probe them. This is usually safe though. Yes, you do have ISA I/O ports even if you do not have any ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): y Probing for `National Semiconductor LM78' at 0x290... No Probing for `National Semiconductor LM79' at 0x290... No Probing for `Winbond W83781D' at 0x290... No Probing for `Winbond W83782D' at 0x290... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): y Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus Next adapter: Synopsys DesignWare I2C adapter (i2c-0) Do you want to scan it? (YES/no/selectively): y Adapter doesn't support all probing functions. Some addresses won't be probed. y Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-1) Do you want to scan it? (yes/NO/selectively): Client found at address 0x28 Probing for `National Semiconductor LM78'... No Probing for `National Semiconductor LM79'... No Probing for `National Semiconductor LM80'... No Probing for `National Semiconductor LM96080'... No Probing for `Winbond W83781D'... No Probing for `Winbond W83782D'... No Probing for `Nuvoton NCT7802Y'... No Probing for `Winbond W83627HF'... No Probing for `Winbond W83627EHF'... No Probing for `Winbond W83627DHG/W83667HG/W83677HG'... No Probing for `Asus AS99127F (rev.1)'... No Probing for `Asus AS99127F (rev.2)'... No Probing for `Asus ASB100 Bach'... No Probing for `Analog Devices ADM1029'... No Probing for `ITE IT8712F'... No Client found at address 0x51 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Client found at address 0x53 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-2) Do you want to scan it? (yes/NO/selectively): y Next adapter: SMBus PIIX4 adapter port 1 at 0b20 (i2c-3) Do you want to scan it? (yes/NO/selectively): y Client found at address 0x2a Probing for `National Semiconductor LM78'... No Probing for `National Semiconductor LM79'... No Probing for `National Semiconductor LM80'... No Probing for `National Semiconductor LM96080'... No Probing for `Winbond W83781D'... No Probing for `Winbond W83782D'... No Probing for `Nuvoton NCT7802Y'... No Probing for `Winbond W83627HF'... No Probing for `Winbond W83627EHF'... No Probing for `Winbond W83627DHG/W83667HG/W83677HG'... No Probing for `Asus AS99127F (rev.1)'... No Probing for `Asus AS99127F (rev.2)'... No Probing for `Asus ASB100 Bach'... No Probing for `Analog Devices ADM1021'... No Probing for `Analog Devices ADM1021A/ADM1023'... No Probing for `Maxim MAX1617'... No Probing for `Maxim MAX1617A'... No Probing for `Maxim MAX1668'... No Probing for `Maxim MAX1805'... No Probing for `Maxim MAX1989'... No Probing for `Maxim MAX6655/MAX6656'... No Probing for `TI THMC10'... No Probing for `National Semiconductor LM84'... No Probing for `Genesys Logic GL523SM'... No Probing for `Onsemi MC1066'... No Probing for `Maxim MAX1618'... No Probing for `Maxim MAX1619'... No Probing for `National Semiconductor LM82/LM83'... Success! (confidence 6, driver `lm83') Probing for `Maxim MAX6654'... No Probing for `Maxim MAX6690'... No Probing for `Maxim MAX6680/MAX6681'... No Probing for `Maxim MAX6695/MAX6696'... No Probing for `Texas Instruments TMP400'... No Probing for `Texas Instruments TMP421'... No Probing for `Texas Instruments TMP441'... No Probing for `National Semiconductor LM95231'... No Probing for `National Semiconductor LM95233'... No Probing for `National Semiconductor LM95241'... No Probing for `Analog Devices ADM1029'... No Probing for `ITE IT8712F'... No Client found at address 0x4f Probing for `National Semiconductor LM75'... No Probing for `National Semiconductor LM75A'... No Probing for `Dallas Semiconductor DS75'... No Probing for `Maxim MAX6642'... No Probing for `Texas Instruments TMP421'... No Probing for `Texas Instruments TMP422'... No Probing for `Texas Instruments TMP435'... No Probing for `Texas Instruments TMP441'... No Probing for `Maxim MAX6633/MAX6634/MAX6635'... No Probing for `NXP/Philips SA56004'... No Next adapter: NVIDIA i2c adapter 1 at 1:00.0 (i2c-4) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 2 at 1:00.0 (i2c-5) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 5 at 1:00.0 (i2c-6) Do you want to scan it? (yes/NO/selectively): y Client found at address 0x4a Probing for `National Semiconductor LM75'... No Probing for `National Semiconductor LM75A'... No Probing for `Dallas Semiconductor DS75'... No Probing for `National Semiconductor LM77'... No Probing for `Analog Devices ADT7410/ADT7420'... No Probing for `Analog Devices ADT7411'... No Probing for `Maxim MAX6642'... No Probing for `Texas Instruments TMP435'... No Probing for `National Semiconductor LM73'... No Probing for `National Semiconductor LM92'... No Probing for `National Semiconductor LM76'... No Probing for `Maxim MAX6633/MAX6634/MAX6635'... No Probing for `NXP/Philips SA56004'... No Client found at address 0x4b Probing for `National Semiconductor LM75'... No Probing for `National Semiconductor LM75A'... No Probing for `Dallas Semiconductor DS75'... No Probing for `National Semiconductor LM77'... No Probing for `Analog Devices ADT7410/ADT7420'... No Probing for `Analog Devices ADT7411'... No Probing for `Maxim MAX6642'... No Probing for `Texas Instruments TMP435'... No Probing for `National Semiconductor LM92'... No Probing for `National Semiconductor LM76'... No Probing for `Maxim MAX6633/MAX6634/MAX6635'... No Probing for `NXP/Philips SA56004'... No Probing for `Analog Devices ADT7481'... No Next adapter: NVIDIA i2c adapter 6 at 1:00.0 (i2c-7) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 7 at 1:00.0 (i2c-8) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 8 at 1:00.0 (i2c-9) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 1 at 21:00.0 (i2c-10) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 2 at 21:00.0 (i2c-11) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 5 at 21:00.0 (i2c-12) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 6 at 21:00.0 (i2c-13) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 7 at 21:00.0 (i2c-14) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 8 at 21:00.0 (i2c-15) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 1 at 4b:00.0 (i2c-16) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 2 at 4b:00.0 (i2c-17) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 5 at 4b:00.0 (i2c-18) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 6 at 4b:00.0 (i2c-19) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 7 at 4b:00.0 (i2c-20) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 8 at 4b:00.0 (i2c-21) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 1 at 4c:00.0 (i2c-22) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 2 at 4c:00.0 (i2c-23) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 5 at 4c:00.0 (i2c-24) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 6 at 4c:00.0 (i2c-25) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 7 at 4c:00.0 (i2c-26) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 8 at 4c:00.0 (i2c-27) Do you want to scan it? (yes/NO/selectively): y Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `nct6683': * ISA bus, address 0xa20 Chip `Nuvoton NCT6683D eSIO' (confidence: 9) Driver `lm83': * Bus `SMBus PIIX4 adapter port 1 at 0b20' Busdriver `i2c_piix4', I2C address 0x2a Chip `National Semiconductor LM82/LM83' (confidence: 6) Driver `k10temp' (autoloaded): * Chip `AMD Family 17h thermal sensors' (confidence: 9) To load everything that is needed, add this to /etc/modules: #----cut here---- # Chip drivers lm83 nct6683 #----cut here---- If you have some drivers built into your kernel, the list above will contain too many modules. Skip the appropriate ones! Do you want to add these lines automatically to /etc/modules? (yes/NO)y Successful! Monitoring programs won't work until the needed modules are loaded. You may want to run '/etc/init.d/kmod start' to load them. Unloading cpuid... OK root@rdlab:/home/exx#