Unable to get the hardware temperature

[kaleaves]

Hi there,

Is me again. Thanks for leesteken help me to solve the network failure.
I would like to install lm-sensor and display on Web-GUI in the machine however it didnt read the cpu temperature properly.

root@pve:~# sensors
nouveau-pci-0100
Adapter: PCI adapter
fan1:        1418 RPM
temp1:        +41.0°C  (high = +95.0°C, hyst =  +3.0°C)
                       (crit = +105.0°C, hyst =  +5.0°C)
                       (emerg = +135.0°C, hyst =  +5.0°C)

nvme-pci-0600
Adapter: PCI adapter
Composite:    +47.9°C  (low  =  -0.1°C, high = +69.8°C)
                       (crit = +84.8°C)
ERROR: Can't get value of subfeature temp2_min: I/O error
ERROR: Can't get value of subfeature temp2_max: I/O error
Sensor 1:     +53.9°C  (low  =  +0.0°C, high =  +0.0°C)

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:            N/A

PC Spec:
CPU: AMD 5700g
Kernal: 5.13
PVEversion: 7.1-7

Thx again

 

[shrdlicka]

Hi,

did you run sensors-detect?

 

[kaleaves]

Yes, I do.
Here is the part of result: Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): Yes 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... No 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): Yes 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 NCT6792D Super IO Sensors' Success! (address 0x290, driver `nct6775') 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

 

[Dark26]

do you add the module at the end of the command sensors-detect ?

you should have something like this in /etc/modules :

root@proxmoxsan:~# cat /etc/modules # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with "#" are ignored. vfio vfio_iommu_type1 vfio_pci vfio_virqfd # Generated by sensors-detect on Sat Mar 6 15:58:05 2021 # Chip drivers coretemp nct6775

you have to reboot after, or do a modprobe of the module.

in my example

modprobe nct6775

for you maybe : modprobe NCT6792D

 

[kaleaves]

do you add the module at the end of the command sensors-detect ?

you should have something like this in /etc/modules :

root@proxmoxsan:~# cat /etc/modules # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with "#" are ignored. vfio vfio_iommu_type1 vfio_pci vfio_virqfd # Generated by sensors-detect on Sat Mar 6 15:58:05 2021 # Chip drivers coretemp nct6775

you have to reboot after, or do a modprobe of the module.

in my example

modprobe nct6775

for you maybe : modprobe NCT6792D

Yep, my chip device is NCT6792D but there is no driver for NCT6792D

nct6792-isa-0290
Adapter: ISA adapter
in0:                   976.00 mV (min =  +0.00 V, max =  +1.74 V)
in1:                     0.00 V  (min =  +0.00 V, max =  +0.00 V)
in2:                     3.34 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in3:                     3.34 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in4:                     0.00 V  (min =  +0.00 V, max =  +0.00 V)
in5:                     0.00 V  (min =  +0.00 V, max =  +0.00 V)
in6:                   632.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in7:                     3.41 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in8:                     3.28 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in9:                     1.84 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in10:                  192.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in11:                  144.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in12:                    1.86 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in13:                    1.70 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in14:                    0.00 V  (min =  +0.00 V, max =  +0.00 V)
fan1:                   974 RPM  (min =    0 RPM)
fan2:                   783 RPM  (min =    0 RPM)
fan3:                     0 RPM  (min =    0 RPM)
fan4:                     0 RPM  (min =    0 RPM)
fan5:                     0 RPM  (min =    0 RPM)
SYSTIN:                +113.0°C  (high =  +0.0°C, hyst =  +0.0°C)  sensor = thermistor
CPUTIN:                 +41.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
AUXTIN0:                +47.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = thermistor
AUXTIN1:               +106.0°C    sensor = thermistor
AUXTIN2:               +104.0°C    sensor = thermistor
AUXTIN3:               -128.0°C    sensor = thermistor
SMBUSMASTER 0:          +44.5°C 
PCH_CHIP_CPU_MAX_TEMP:   +0.0°C 
PCH_CHIP_TEMP:           +0.0°C 
PCH_CPU_TEMP:            +0.0°C 
intrusion0:            OK
intrusion1:            ALARM
beep_enable:           disabled

I changed the modprobe to nct6792 and no feed-back There is only NCT6775 driver can be used for nct6792

root@pve:~# cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.


# Generated by sensors-detect on Fri Jun  3 17:30:13 2022
# Chip drivers
nct6775

 

[GoZippy]

I think this would be an excellent future addon for Proxmox gui... https://wiki.archlinux.org/title/lm_sensors I was just thinking about how to manage it via proxmox. What I was really hoping for was a way to set custom rules so that if one of my nodes is basically doing nothing - it will slow fans and go into minimal power mode until called on or tasks are migrated over. I have over 40 nodes mostly sitting idle - would love to save some power but not have to shut them off... or find some way to wake on lan to wake them and then live migrate as needed... but mostly wanted to see if we can monitor lm_sensor data via gui and then start setting rules for power saving somehow...
https://www.reddit.com/r/homelab/comments/rhq56e/displaying_cpu_temperature_in_proxmox_summery_in/

 

[datschlatscher]

Thanks for your suggestions!

What I was really hoping for was a way to set custom rules so that if one of my nodes is basically doing nothing - it will slow fans and go into minimal power mode until called on or tasks are migrated over.

There is a load balancing feature in the works, though I am not sure whether that entails power saving features for the cluster node itself. I think the way corosync clusters work might become a problem here, because one would have to "dynamically" fiddle with the votes per node and the values for expected votes.
It seems your best bet in this regard would be to keep your system's hardware up to date. As those should automatically greatly reduce power consumption, especially if the systems are idling a lot.

but mostly wanted to see if we can monitor lm_sensor data via gui and then start setting rules for power saving somehow...

This feature was recently taken up for active development (see issue Temperature sensors instrumentation included in Proxmox web interface) but I can't tell you when it will be ready. You might want to keep up with the issue on Bugzilla and/or subscribe to the PVE-Development mailing list for this.

Nonetheless, if you have a suggestion feel free to contribute to an existing discussion / create a new issue for something that is not tracked yet via an issue in our bug tracker (https://bugzilla.proxmox.com/).