No CPU FAN sensor monitoring on ASUS ROG STRIX X570-I MB

[NTMan]

# sensors -u
iwlwifi-virtual-0
Adapter: Virtual device
temp1:
ERROR: Can't get value of subfeature temp1_input: Can't read

k10temp-pci-00c3
Adapter: PCI adapter
Tdie:
  temp1_input: 72.625
  temp1_max: 70.000
Tctl:
  temp2_input: 72.625

nvme-pci-0100
Adapter: PCI adapter
Composite:
  temp1_input: 40.850
  temp1_alarm: 0.000

amdgpu-pci-0b00
Adapter: PCI adapter
vddgfx:
  in0_input: 0.731
fan1:
  fan1_input: 908.000
  fan1_min: 0.000
  fan1_max: 3850.000
edge:
  temp1_input: 48.000
  temp1_crit: 100.000
  temp1_crit_hyst: -273.150
  temp1_emergency: 105.000
junction:
  temp2_input: 50.000
  temp2_crit: 110.000
  temp2_crit_hyst: -273.150
  temp2_emergency: 115.000
mem:
  temp3_input: 50.000
  temp3_crit: 94.000
  temp3_crit_hyst: -273.150
  temp3_emergency: 99.000
power1:
  power1_average: 42.000
  power1_cap: 250.000

sensors-detect says that this MB uses Nuvoton NCT6798D-R super I/O chip

# sensors-detect
# sensors-detect version 3.6.0
# Board: ASUSTeK COMPUTER INC. ROG STRIX X570-I GAMING
# Kernel: 5.5.0-0.rc6.git3.2.fc32.x86_64 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): YES
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): 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 NCT6798D 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): YES
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): 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): YES
Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus
Module i2c-dev loaded successfully.

Next adapter: AMDGPU DM i2c hw bus 0 (i2c-0)
Do you want to scan it? (yes/NO/selectively): NO

Next adapter: dmdc (i2c-1)
Do you want to scan it? (yes/NO/selectively): NO

Next adapter: AMDGPU DM i2c hw bus 1 (i2c-2)
Do you want to scan it? (yes/NO/selectively): NO

Next adapter: dmdc (i2c-3)
Do you want to scan it? (yes/NO/selectively): NO

Next adapter: AMDGPU DM i2c hw bus 2 (i2c-4)
Do you want to scan it? (yes/NO/selectively): NO

Next adapter: dmdc (i2c-5)
Do you want to scan it? (yes/NO/selectively): NO

Next adapter: AMDGPU DM i2c hw bus 3 (i2c-6)
Do you want to scan it? (yes/NO/selectively): NO

Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-7)
Do you want to scan it? (YES/no/selectively): YES
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)
Client found at address 0x77
Probing for `Asus Mozart-2'...                              No

Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-8)
Do you want to scan it? (YES/no/selectively): YES


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

Driver `k10temp' (autoloaded):
  * Chip `AMD Family 17h thermal sensors' (confidence: 9)

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

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): YES
Unloading i2c-dev... OK

Motherboard photo confirms this:

[risyasin]

I have the same problem as well

[yas@dxarch ~]$ sudo dmidecode -t 2
# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 3.2.0 present.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
	Manufacturer: ASUSTeK COMPUTER INC.
	Product Name: ROG STRIX X570-I GAMING
	Version: Rev X.0x
	Serial Number: 190957676100539
	Asset Tag: Default string
	Features:
		Board is a hosting board
		Board is replaceable
	Location In Chassis: Default string
	Chassis Handle: 0x0003
	Type: Motherboard
	Contained Object Handles: 0

[yas@dxarch ~]$ sudo dmidecode -t 34
# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 3.2.0 present.

Handle 0x0023, DMI type 34, 11 bytes
Management Device
	Description: NCT6798D-R
	Type: Other
	Address: 0x00000295
	Address Type: I/O Port

Mods

[yas@dxarch ~]$ lsmod | grep nct6775
nct6775                73728  0
hwmon_vid              16384  1 nct6775
[yas@dxarch ~]$ lsmod | grep k10temp 
k10temp                16384  0

Sensor data

[yas@dxarch ~]$ sensors
sensors               sensors-conf-convert  sensors-detect        
[yas@dxarch ~]$ sensors
iwlwifi-virtual-0
Adapter: Virtual device
temp1:        +41.0°C  

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

amdgpu-pci-0b00
Adapter: PCI adapter
vddgfx:      775.00 mV 
fan1:           0 RPM  (min =    0 RPM, max = 3200 RPM)
edge:         +47.0°C  (crit = +118.0°C, hyst = -273.1°C)
                       (emerg = +99.0°C)
junction:     +47.0°C  (crit = +99.0°C, hyst = -273.1°C)
                       (emerg = +99.0°C)
mem:          +48.0°C  (crit = +99.0°C, hyst = -273.1°C)
                       (emerg = +99.0°C)
power1:        8.00 W  (cap = 165.00 W)

Config

# Generated by sensors-detect on Thu Jan 23 00:44:21 2020
# This file is sourced by /etc/init.d/lm_sensors and defines the modules to
# be loaded/unloaded.
#
# The format of this file is a shell script that simply defines variables:
# HWMON_MODULES for hardware monitoring driver modules, and optionally
# BUS_MODULES for any required bus driver module (for example for I2C or SPI).

HWMON_MODULES="k10temp nct6775"

According to this https://github.com/torvalds/linux/blob/master/drivers/hwmon/nct6775.c
NCT6798D-R is supported by kernel via nct6775 Seems like fan values must be there too.

[risyasin]

Update:
I've installed new driver for Nuvoton NCT6798D-R https://github.com/tonylambiris/nct6775

Now I can see more data provided to lm_sensors via new nct6775 but no fan speeds :(

[yas@dxarch ~]$ sensors 
iwlwifi-virtual-0
Adapter: Virtual device
temp1:        +41.0°C  

zenpower-pci-00c3
Adapter: PCI adapter
SVI2_Core:     1.46 V  
SVI2_SoC:      1.09 V  
Tdie:         +46.4°C  (high = +70.0°C)
Tctl:         +46.4°C  
Tccd1:        +41.0°C  
SVI2_P_Core:   7.71 W  
SVI2_P_SoC:    9.93 W  
SVI2_C_Core:   8.56 A  
SVI2_C_SoC:    9.12 A  

amdgpu-pci-0b00
Adapter: PCI adapter
vddgfx:      775.00 mV 
fan1:           0 RPM  (min =    0 RPM, max = 3200 RPM)
edge:         +46.0°C  (crit = +118.0°C, hyst = -273.1°C)
                       (emerg = +99.0°C)
junction:     +46.0°C  (crit = +99.0°C, hyst = -273.1°C)
                       (emerg = +99.0°C)
mem:          +48.0°C  (crit = +99.0°C, hyst = -273.1°C)
                       (emerg = +99.0°C)
power1:        8.00 W  (cap = 165.00 W)

[berniyh]

Same thing here for an ASUS ROG STRIX X570-E.
Has the same nuvoton NCT6798D-R chip on it.

[berniyh]

Just noticed that there is already an issue about that, see:
#197

With said boot parameter acpi_enforce_resources=lax the sensor monitoring and also fan monitoring does work for me now.

[lbibass]

Hey, I still can't get this to work. I'm new to Linux, but I've put "acpi_enforce_resources=lax" into the kernel parameters after "quiet spash" (no quotes). It can see the sensor, but it never shows me anything from it. Here's the output from sensors.

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +56.0°C  

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

amdgpu-pci-0b00
Adapter: PCI adapter
vddgfx:      725.00 mV 
fan1:         787 RPM  (min =    0 RPM, max = 3200 RPM)
edge:         +46.0°C  (crit = +118.0°C, hyst = -273.1°C)
                       (emerg = +99.0°C)
junction:     +51.0°C  (crit = +99.0°C, hyst = -273.1°C)
                       (emerg = +99.0°C)
mem:          +62.0°C  (crit = +99.0°C, hyst = -273.1°C)
                       (emerg = +99.0°C)
power1:       30.00 W  (cap = 180.00 W)

[lbibass]

Sorry: I ended up getting it to work. I just needed to type in

sudo modprobe nct6775

into the terminal. Now it's reading from the sensor. Hope this helps anyone else who had the same problem.

[Darxus]

Just wanted to confirm I had a similar experience. What I needed to do was run sensors-detect, and allow it to add nct6775 to /etc/modules, then change /etc/default/grub to include:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_enforce_resources=lax"
Then I ran update-grub.

Before, I had video and CPU temps, but no fans. Now I also have 7 fans. On my Asus Tuf Gaming X570-Plus motherboard. Ubuntu 20.04, kernel 5.4.0-48-generic.

[regulator-g]

Hey guys

I have the same issue on my b550 motherboard

On the newer kernel(s) I was able to get sensors using the steps suggested. No luck on 5.4 LTS kernel though.

will these sensors eventually become native in the kernel and not require extra steps to function?

I had a lot of issues with the built in Ethernet and WiFi too but again these are mostly resolved in newer kernels

sudo dmidecode -t 2
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
	Manufacturer: ASUSTeK COMPUTER INC.
	Product Name: ROG STRIX B550-F GAMING (WI-FI)
	Version: Rev X.0x
	Serial Number: 
	Asset Tag: Default string
	Features:
		Board is a hosting board
		Board is replaceable
	Location In Chassis: Default string
	Chassis Handle: 0x0003
	Type: Motherboard
	Contained Object Handles: 0

[peacepenguin]

This issue is related to an upstream kernel driver bug in the nct6775 driver. The nct6775 driver/kernel module is used for the chip many asus boards have: nct6798. Sensors (lm_sensors) uses the nct6775 driver to query the fan, temp, and voltage info on these asus motherboards.

https://bugzilla.kernel.org/show_bug.cgi?id=204807

There's a patch being actively worked on, and works great if you get it compiled. So far these boards have been reported as affected and fixed by the patch:

ROG CROSSHAIR VIII IMPACT
ROG STRIX B550-E GAMING
ROG STRIX B550-F GAMING (WI-FI)
ROG STRIX Z490-I GAMING
TUF GAMING B550M-PLUS
TUF GAMING B550M-PLUS (WI-FI)
TUF GAMING B550-PLUS
TUF GAMING X570-PLUS
TUF GAMING X570-PRO (WI-FI)

The patch is available for testing at the bugzilla link above. So far the patch works great on my Fedora 34 system, with a TUF GAMING X570-PLUS motherboard. Some more clean-up work is needed to get the patch committed to the kernel tree, so anyone with Kernel driver skills please check out the bugzilla link in this post to see if you can help out in that effort.

For now though, the workaround mentioned by @Darxus works fine, but it is a "risk" to system stability. The new patch removes the need for "lax", and instead uses WMI to get the sensor data instead of direct ACPI calls.

run sensors-detect, and allow it to add nct6775 to /etc/modules, then change /etc/default/grub to include:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_enforce_resources=lax"
Then I ran update-grub.

[NoahDar]

For now though, the workaround mentioned by @Darxus works fine, but it is a "risk" to system stability. The new patch removes the need for "lax", and instead uses WMI to get the sensor data instead of direct ACPI calls.

run sensors-detect, and allow it to add nct6775 to /etc/modules, then change /etc/default/grub to include:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_enforce_resources=lax"
Then I ran update-grub.

I can tell you the grub fix works perfectly fine with my ASUS ROG STRIX X570-E GAMING WIFI running on Debian 11 KDE with Debian 5.10.46-5 (2021-09-23) x86_64 GNU/Linux kernel. AMD Ryzen 9 5950X

What is the system stability you're referring to? I've read somewhere using WMI on this motherboard may cause the fans to stop working altogether. Also been suggested not to leave the computer alone? Can WMI just set as read-only since that's all we care about?

[laurensbl]

Getting no data from sensors (doesn't show in output) on: TUF H370-PRO GAMING, so TUF H370-PRO GAMING seems also affected.

It does detect it though:

sudo sensors-detect
...
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
...

sudo dmidecode -t 2
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 3.2.1 present.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
        Manufacturer: ASUSTeK COMPUTER INC.
        Product Name: TUF H370-PRO GAMING
        Version: Rev 1.xx
        Serial Number: 180221078400849
        Asset Tag: Default string
        Features:
                Board is a hosting board
                Board is replaceable
        Location In Chassis: Default string
        Chassis Handle: 0x0003
        Type: Motherboard
        Contained Object Handles: 0

sudo dmidecode -t 34
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 3.2.1 present.

Handle 0x002B, DMI type 34, 11 bytes
Management Device
        Description: Nuvoton NCT5582D
        Type: Other
        Address: 0x00000295
        Address Type: I/O Port

lsmod | grep nct6775
nct6775                69632  0
hwmon_vid              16384  1 nct6775

[winklevos]

Will add that ROG STRIX Z590-E GAMING WIFI seems to also be impacted

sudo sensors-detect
# sensors-detect version 3.6.0
# Board: ASUSTeK COMPUTER INC. ROG STRIX Z590-E GAMING WIFI
# Kernel: 5.10.28-Unraid x86_64
# Processor: Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz (6/165/5)

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
Intel digital thermal sensor...                             Success!
    (driver `coretemp')
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 NCT6798D Super IO Sensors'                   Success!
    (address 0x290, driver `nct6775')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               Yes
Found unknown chip with ID 0x0101

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): 
Found unknown SMBus adapter 8086:43a3 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.
Module i2c-dev loaded successfully.

Next adapter: SMBus I801 adapter at efa0 (i2c-0)
Do you want to scan it? (YES/no/selectively): 
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)

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

Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)

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

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): 
To load everything that is needed, add this to one of the system
initialization scripts (e.g. /etc/rc.d/rc.local):

#----cut here----
# Chip drivers
modprobe coretemp
modprobe nct6775
/usr/bin/sensors -s
#----cut here----

You really should try these commands right now to make sure everything
is working properly. Monitoring programs won't work until the needed
modules are loaded.

Unloading i2c-dev... OK

sudo dmidecode -t 2
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
        Manufacturer: ASUSTeK COMPUTER INC.
        Product Name: ROG STRIX Z590-E GAMING WIFI
        Version: Rev 1.xx
        Serial Number: 210179633200111
        Asset Tag: Default string
        Features:
                Board is a hosting board
                Board is replaceable
        Location In Chassis: Default string
        Chassis Handle: 0x0003
        Type: Motherboard
        Contained Object Handles: 0

sudo dmidecode -t 34
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0032, DMI type 34, 11 bytes
Management Device
        Description: Nuvoton NCT6798D
        Type: Other
        Address: 0x00000295
        Address Type: I/O Port

sudo sensors
acpitz-acpi-0
Adapter: ACPI interface
MB Temp:      +27.8°C  (crit = +105.0°C)

coretemp-isa-0000
Adapter: ISA adapter
CPU Temp:     +61.0°C  (high = +82.0°C, crit = +100.0°C)
Core 0:       +49.0°C  (high = +82.0°C, crit = +100.0°C)
Core 1:       +45.0°C  (high = +82.0°C, crit = +100.0°C)
Core 2:       +46.0°C  (high = +82.0°C, crit = +100.0°C)
Core 3:       +47.0°C  (high = +82.0°C, crit = +100.0°C)
Core 4:       +46.0°C  (high = +82.0°C, crit = +100.0°C)
Core 5:       +45.0°C  (high = +82.0°C, crit = +100.0°C)
Core 6:       +60.0°C  (high = +82.0°C, crit = +100.0°C)
Core 7:       +49.0°C  (high = +82.0°C, crit = +100.0°C)
Core 8:       +56.0°C  (high = +82.0°C, crit = +100.0°C)
Core 9:       +57.0°C  (high = +82.0°C, crit = +100.0°C)

lsmod | grep nct6775
nct6775                53248  0
hwmon_vid              16384  1 nct6775

[peacepenguin]

Just a reminder, this issue is caused by an upstream kernel hwmon driver problem with the nct6775 driver that the nct6798 devices use. Nothing to fix on the lm_sensors side.

Patch for a variety of asus mobos is almost ready to be merged into the linux kernel, status and the patches being merged can be found here:

https://bugzilla.kernel.org/show_bug.cgi?id=204807

If you're up for it, you can implement the fixes now by pulling in the patches and compiling the nct6775 driver yourself, usually using dkms. Working well for me on a tuf gaming x570 plus by manually compiling the patches.

Good luck!