[SOLVED] Ryzen CPU temperature

rvdmeer

Member
May 11, 2020
14
9
23
42
Netherlands
Hi all,

I was wondering what is needed to get CPU temperature readouts working with sensors. I'm using a AMD Ryzen 3950x but the sensors detected are very limited. I hoped installing the newest 5.4 kernel would solve this but still no go

Running: Linux 5.4.30-1-pve #1 SMP PVE 5.4.30-1 (Fri, 10 Apr 2020 09:12:42 +0200) x86_64 GNU/Linux, All updates installed.

Bash:
~# sensors-detect
# sensors-detect revision $Revision$
# Board: ASUSTeK COMPUTER INC. Pro WS X570-ACE
# Kernel: 5.4.30-1-pve x86_64
# Processor: AMD Ryzen 9 3950X 16-Core Processor (23/113/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):
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
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):
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 NCT6796D 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

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):
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):

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):
Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus

Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No
Client found at address 0x52
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-1)
Do you want to scan it? (YES/no/selectively):

Next adapter: nvkm-0000:09:00.0-bus-0001 (i2c-2)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:09:00.0-bus-0002 (i2c-3)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:09:00.0-bus-0004 (i2c-4)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:09:00.0-aux-0004 (i2c-5)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:09:00.0-bus-0005 (i2c-6)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:09:00.0-aux-0005 (i2c-7)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:09:00.0-bus-0006 (i2c-8)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:09:00.0-aux-0006 (i2c-9)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:09:00.0-bus-0007 (i2c-10)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:09:00.0-aux-0007 (i2c-11)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:09:00.0-bus-0008 (i2c-12)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:09:00.0-aux-0008 (i2c-13)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:09:00.0-bus-0009 (i2c-14)
Do you want to scan it? (yes/NO/selectively):

Next adapter: nvkm-0000:09:00.0-aux-0009 (i2c-15)
Do you want to scan it? (yes/NO/selectively):

Next adapter: sor-0006-0f82 (i2c-16)
Do you want to scan it? (YES/no/selectively):
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
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                Yes
    (confidence 8, not a hardware monitoring chip)


Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `nct6775':
  * ISA bus, address 0x290
    Chip `Nuvoton NCT6796D Super IO Sensors' (confidence: 9)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
nct6775
#----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)

Unloading cpuid... OK

Bash:
~# sensors
nouveau-pci-0900
Adapter: PCI adapter
fan1:           0 RPM
temp1:        +38.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)

k10temp-pci-00c3
Adapter: PCI adapter
Tdie:         +38.9°C  (high = +70.0°C)
Tctl:         +38.9°C

Could someone point me in the right direction?
 
  • Like
Reactions: HeyRob and Longun
Hi,
the CPU temp is shown in your output.

k10temp-pci-00c3 Adapter: PCI adapter Tdie: +38.9°C (high = +70.0°C) Tctl: +38.9°C

What do you expect?
 
Hi,

I didn't recoqnize Tdie as CPU temperature. Because of the name: "PCI adapter" I thought it was a sensor near the PCI-E lane on the motherboard . I was searching for something like CPUTemp. Thanks for answering @wolfgang

For those interested I managed to get a lot of readouts available by following the steps below the output. Hope this helps.

Adapter: ISA adapter
in0: +1.26 V (min = +0.00 V, max = +1.74 V)
in1: +1.00 V (min = +0.00 V, max = +0.00 V) ALARM
in2: +3.38 V (min = +0.00 V, max = +0.00 V) ALARM
in3: +3.30 V (min = +0.00 V, max = +0.00 V) ALARM
in4: +1.70 V (min = +0.00 V, max = +0.00 V) ALARM
in5: +0.59 V (min = +0.00 V, max = +0.00 V) ALARM
in6: +1.07 V (min = +0.00 V, max = +0.00 V) ALARM
in7: +3.38 V (min = +0.00 V, max = +0.00 V) ALARM
in8: +3.23 V (min = +0.00 V, max = +0.00 V) ALARM
in9: +0.89 V (min = +0.00 V, max = +0.00 V) ALARM
in10: +0.01 V (min = +0.00 V, max = +0.00 V) ALARM
in11: +0.08 V (min = +0.00 V, max = +0.00 V) ALARM
in12: +1.03 V (min = +0.00 V, max = +0.00 V) ALARM
in13: +1.34 V (min = +0.00 V, max = +0.00 V) ALARM
in14: +0.89 V (min = +0.00 V, max = +0.00 V) ALARM
fan1: 849 RPM (min = 0 RPM)
fan2: 986 RPM (min = 0 RPM)
fan3: 773 RPM (min = 0 RPM)
fan4: 785 RPM (min = 0 RPM)
fan7: 0 RPM (min = 0 RPM)
SYSTIN: +27.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
CPUTIN: +44.5°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
AUXTIN0: +22.5°C sensor = thermistor
AUXTIN1: +127.0°C sensor = thermistor
AUXTIN2: +113.0°C sensor = thermistor
AUXTIN3: +32.0°C sensor = thermistor
PCH_CHIP_CPU_MAX_TEMP: +0.0°C
PCH_CHIP_TEMP: +0.0°C
PCH_CPU_TEMP: +0.0°C
PCH_MCH_TEMP: +0.0°C
intrusion0: ALARM
intrusion1: OK
beep_enable: disabled

nouveau-pci-0900
Adapter: PCI adapter
fan1: 0 RPM
temp1: +34.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)

k10temp-pci-00c3
Adapter: PCI adapter
Tdie: +69.0°C (high = +70.0°C)
Tctl: +69.0°C

Steps I did to make these available or the following:

1) Add nct6775 to /etc/modules
~# 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.
#
# Chip drivers
nct6775

2) Add acpi_enforce_resources=lax as boot-option in /etc/default/grub
# cat /etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Proxmox Virtual Environment"
GRUB_CMDLINE_LINUX_DEFAULT="quiet acpi_enforce_resources=lax"
GRUB_CMDLINE_LINUX=""

# Disable os-prober, it might add menu entries for each guest
GRUB_DISABLE_OS_PROBER=true

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

3) Updated to latest pve-kernel
# apt-get install pve-kernel-5.4.30-1-pve
 
  • Like
Reactions: HeyRob and Longun
Updated to latest pve-kernel
This is not the command what you need.
You must upgrade the Grub. The installation does this too but it is better to run "update-grub".
 
  • Like
Reactions: HeyRob

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!