(SOLVED) lm_sensors failing to read actual cpu temp

miaofthestars · 2025-05-06 11:46:53

Hi there.

I have a Ryzen 5 9600X installed in an Asus Prime X670-P WiFi board. I've been trying since yesterday to get lm_sensors to load the actual CPU temperature that the cooling curve is based off, but it's instead reporting what seems to be the package or tcase temperature as shown in BIOS, no matter how much I run sudo sensors-detect.

The motherboard's BIOS reports two sensors; simply CPU and then CPU Package. In Asus's Q-fan config, it's set to do the cooling curve based off just simply "CPU" temp (i.e package is irrelevant-ish) therefore I would like the OS to display that

Package temp is offset upwards by about 10 degrees. I cannot for the life of me work out how to make lm_sensors report that instead of the package one.

Any help is appreciated, and please let me know what command outputs to add.

Thanks,

Last edited by miaofthestars (2025-05-06 13:00:09)

miaofthestars · 2025-05-06 11:53:09

Here is the output of sensors-detect:

# sensors-detect version 3.6.0+git
# Board: ASUSTeK COMPUTER INC. PRIME X670-P WIFI
# Kernel: 6.14.4-zen1-2-zen x86_64
# Processor: AMD Ryzen 5 9600X 6-Core Processor (26/68/0)
Running in automatic mode, default answers to all questions
are assumed.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
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
AMD Family 19h 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):
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 unknown chip with ID 0xd802
(logical device B has address 0x290, could be sensors)
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):
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):
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):
Adapter doesn't support all probing functions.
Some addresses won't be probed.
Next adapter: AMDGPU DM i2c hw bus 0 (i2c-1)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM i2c hw bus 1 (i2c-2)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM i2c hw bus 2 (i2c-3)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM i2c hw bus 3 (i2c-4)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM aux hw bus 0 (i2c-5)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM aux hw bus 1 (i2c-6)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM aux hw bus 3 (i2c-7)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM i2c hw bus 0 (i2c-8)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM i2c hw bus 1 (i2c-9)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM aux hw bus 1 (i2c-10)
Do you want to scan it? (yes/NO/selectively):
Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-11)
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 0x49
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 `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
Probing for `SMSC EMC1023'... No
Probing for `SMSC EMC1043'... No
Probing for `SMSC EMC1053'... No
Probing for `SMSC EMC1063'... 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 0x51
Handled by driver `spd5118' (already loaded), chip type `spd5118'
(note: this is probably NOT a sensor chip!)
Client found at address 0x53
Handled by driver `spd5118' (already loaded), chip type `spd5118'
(note: this is probably NOT a sensor chip!)
Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-12)
Do you want to scan it? (YES/no/selectively):
Next adapter: SMBus PIIX4 adapter port 1 at 0b20 (i2c-13)
Do you want to scan it? (YES/no/selectively):
Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
https://hwmon.wiki.kernel.org/device_support_status for driver status.

Xephon · 2025-05-06 12:12:29

There is your sensor

Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found unknown chip with ID 0xd802
    (logical device B has address 0x290, could be sensors)

What happens if you run

sudo modprobe nct6775 force_id=0xD802
sensors

miaofthestars · 2025-05-06 12:50:00

Thanks for the reply! With that command and then sensors, it adds this to the output:

nct6799-isa-0290
Adapter: ISA adapter
in0: 1.06 V (min = +0.00 V, max = +1.74 V)
in1: 1.02 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.36 V (min = +0.00 V, max = +0.00 V) ALARM
in4: 1.02 V (min = +0.00 V, max = +0.00 V) ALARM
in5: 1.04 V (min = +0.00 V, max = +0.00 V)
in6: 832.00 mV (min = +0.00 V, max = +0.00 V) ALARM
in7: 3.38 V (min = +0.00 V, max = +0.00 V) ALARM
in8: 3.28 V (min = +0.00 V, max = +0.00 V) ALARM
in9: 3.34 V (min = +0.00 V, max = +0.00 V) ALARM
in10: 1.38 V (min = +0.00 V, max = +0.00 V) ALARM
in11: 1.12 V (min = +0.00 V, max = +0.00 V) ALARM
in12: 1.04 V (min = +0.00 V, max = +0.00 V) ALARM
in13: 408.00 mV (min = +0.00 V, max = +0.00 V) ALARM
in14: 280.00 mV (min = +0.00 V, max = +0.00 V) ALARM
in15: 976.00 mV (min = +0.00 V, max = +0.00 V) ALARM
in16: 1.84 V (min = +0.00 V, max = +0.00 V) ALARM
in17: 1.27 V (min = +0.00 V, max = +0.00 V)
fan1: 703 RPM (min = 0 RPM)
fan2: 891 RPM (min = 0 RPM)
fan3: 862 RPM (min = 0 RPM)
fan4: 660 RPM (min = 0 RPM)
fan5: 0 RPM (min = 0 RPM)
fan7: 0 RPM (min = 0 RPM)
SYSTIN: +27.0°C (high = +80.0°C, hyst = +75.0°C)
(crit = +125.0°C) sensor = thermistor
CPUTIN: +33.0°C (high = +80.0°C, hyst = +75.0°C)
(crit = +125.0°C) sensor = thermistor
AUXTIN0: +35.0°C (high = +80.0°C, hyst = +75.0°C)
(crit = +125.0°C) sensor = thermistor
AUXTIN1: +6.0°C (high = +80.0°C, hyst = +75.0°C)
(crit = +125.0°C) sensor = thermistor
AUXTIN2: +20.0°C (high = +80.0°C, hyst = +75.0°C)
(crit = +100.0°C) sensor = thermistor
AUXTIN3: +85.0°C (high = +80.0°C, hyst = +75.0°C) ALARM
(crit = +100.0°C) sensor = thermistor
AUXTIN4: +24.0°C (high = +80.0°C, hyst = +75.0°C)
(crit = +100.0°C)
PECI/TSI Agent 0 Calibration: +33.0°C (high = +80.0°C, hyst = +75.0°C)
AUXTIN5: +12.0°C
PCH_CHIP_CPU_MAX_TEMP: +0.0°C
PCH_CHIP_TEMP: +0.0°C
PCH_CPU_TEMP: +0.0°C
TSI0_TEMP: +42.2°C
intrusion0: ALARM
intrusion1: ALARM
beep_enable: disabled

I'm not sure how to decipher this as I never encountered it on my old AM4 build. Thanks for the help!

miaofthestars · 2025-05-06 12:59:19

Update: I believe CPUTIN is the right temp, it matches the BIOS one. I've added the module to /etc/modules-load.d/ and it's working well now. Thanks for the help.

Marking as solved!

Arch Linux

#1 2025-05-06 11:46:53

(SOLVED) lm_sensors failing to read actual cpu temp

#2 2025-05-06 11:53:09

Re: (SOLVED) lm_sensors failing to read actual cpu temp

#3 2025-05-06 12:12:29

Re: (SOLVED) lm_sensors failing to read actual cpu temp

#4 2025-05-06 12:50:00

Re: (SOLVED) lm_sensors failing to read actual cpu temp

#5 2025-05-06 12:59:19

Re: (SOLVED) lm_sensors failing to read actual cpu temp

Board footer