FYI: Owners of certain ASUS motherboards

General system Kernel & Hardware
#1

(I have the PRIME X470-PRO model)
Because this board did not have sensors modules for Linux, I used this driver:

The problem was that my board, along with a few others, would have some or all of the chassis fans suddenly shut off, causing a major spike in heat. This would usually happen within the first 12 hours of a reboot.

I bring this up because this module has been incorporated into the v5.17 kernel. I didn’t even notice it when I upgraded yesterday, until I looked at my glances console and saw all of my sensors being displayed. So far, it’s running fine, so maybe the problem has been fixed. For most users, a more recent BIOS will do the trick; this did not, however, work for me.

From what I’ve gathered in investigating this issue, it was being caused by frequent polling of the WMI data (bugged in earlier BIOS releases).

1 Like
#2

I have a B550-F gaming, not sure if its affected, but thanks for the info, I’ll be watching my coolers and temps…

#3

You should be OK. From the asus_wmi_sensors.c file:

* HWMON driver for ASUS motherboards that provides sensor readouts via WMI
* interface present in the UEFI of the X370/X470/B450/X399 Ryzen motherboards.

What does lsmod | grep asus_wmi return?

1 Like
#4

While not the OP, and was completely unaware of this, I have one of those ASUS boards, and I get this:

% lsmod | grep asus_wmi ~ arco-desktop
asus_wmi 65536 1 eeepc_wmi
sparse_keymap 16384 1 asus_wmi
platform_profile 16384 1 asus_wmi
rfkill 32768 4 asus_wmi
video 57344 1 asus_wmi
wmi 40960 3 asus_wmi,wmi_bmof,mxm_wmi

Does appear my chipset doesn’t yet give info though via sensors.

#5 
$ lsmod | grep asus_wmi
asus_wmi               65536  1 eeepc_wmi
sparse_keymap          16384  1 asus_wmi
platform_profile       16384  1 asus_wmi
rfkill                 32768  4 asus_wmi
video                  57344  1 asus_wmi
wmi                    40960  2 asus_wmi,wmi_bmof
#6

For motherboards that are not supported by this driver you can check here.
I have been using it with a TUF B450 Gaming Plus for a long time without any problems.

EDIT:
Don´t use the link above. There´s a newer version in AUR.

1 Like
Gnome performance mode doesn't show after reboot
#7

I may have to give this a shot, although I’m a bit leery since the author discontinued updating it since 2018.

Today my system overheated, CPU fan completely shutoff and spiked the CPU temp to over 90 degrees before the system shut off. I’ve blacklisted the module.

#8

@ajgringo619
You got the problems with this it87 kernel driver I posted?

#9

No, haven’t tried it yet. I just don’t like using software that’s been abandoned.

#10

Yeah, I agree. But wanted it for sensors to be shown in conky :roll_eyes: so I tried :wink:

#11

This package has been integrated into the 5.17 and later kernel mainline. Unless I am misunderstanding something, you shouldn’t need the package if you are running a current kernel version.

#12

If you’re talking about the asus_wmi_sensors package, then you are correct. This is the one that is sending my chassis/CPU fans into chaos. The it87 module is not loaded on my system.

@sandman - Arch has a much-newer version of the it87 module: https://aur.archlinux.org/packages/it87-dkms-git

2 Likes
#13

Strange. I can’t remember if i installed the package linked above or if i took the one from the AUR.
But…

└──╼ yay it87
1 aur/it87-dkms-git 152.2b8b4fe-3 (+31 1.55) (Installiert: 163.c93d61a-1)

#14

WMI fixes in 5.18rc5 ?

https://www.phoronix.com/scan.php?page=news_item&px=Gigabyte-B660-GAMING-X-Sensors

#15

Sadly, my board is not on the list.

#16

With the upgrade to kernel 5.19, I found that this module was renamed to asus_ec_sensors; whether it’s based on the same code or not, I cannot be sure. I’ve blacklisted it as well, at least until I can investigate further.

UPDATE: since this driver is completely unrelated to the one that crashed my system - looks to be implemented in a safer way, without the polling of WMI - I’m going to give it a spin to see what happens. I don’t leave my system on overnight anymore, so that’s one less thing to worry about.

#17

UPDATE #2: yes, definitely have to maintain the blacklisting of the WMI module; it shows my chassis/CPU fans while the new one doesn’t, which kinda sucks. For now, running this blacklist file:

blacklist asus_wmi_sensors
#blacklist asus_ec_sensors
#18

It seems that here is working fine now…

sensors 
k10temp-pci-00c3
Adapter: PCI adapter
Tctl:         +35.2°C  
Tccd1:        +28.8°C  

nvme-pci-0100
Adapter: PCI adapter
Composite:    +37.9°C  (low  =  -5.2°C, high = +83.8°C)
                       (crit = +87.8°C)

amdgpu-pci-0a00
Adapter: PCI adapter
vddgfx:        6.00 mV 
fan1:           0 RPM  (min =    0 RPM, max = 3500 RPM)
edge:         +35.0°C  (crit = +110.0°C, hyst = -273.1°C)
                       (emerg = +115.0°C)
junction:     +37.0°C  (crit = +110.0°C, hyst = -273.1°C)
                       (emerg = +115.0°C)
mem:          +34.0°C  (crit = +105.0°C, hyst = -273.1°C)
                       (emerg = +110.0°C)
PPT:           6.00 W  (cap = 230.00 W)

nct6798-isa-0290
Adapter: ISA adapter
in0:                      504.00 mV (min =  +0.00 V, max =  +1.74 V)
in1:                        1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in2:                        3.41 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in3:                        3.31 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in4:                        1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:                      936.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:                      240.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in7:                        3.39 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in8:                        3.34 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in9:                      912.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in10:                     336.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in11:                       1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in12:                       1.03 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in13:                     328.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in14:                     240.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
fan1:                      631 RPM  (min =    0 RPM)
fan2:                      534 RPM  (min =    0 RPM)
fan3:                      520 RPM  (min =    0 RPM)
fan4:                      582 RPM  (min =    0 RPM)
fan5:                        0 RPM  (min =    0 RPM)
fan6:                        0 RPM  (min =    0 RPM)
fan7:                      545 RPM  (min =    0 RPM)
SYSTIN:                    +29.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
CPUTIN:                    +32.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
AUXTIN0:                   +89.0°C    sensor = thermistor
AUXTIN1:                   +44.0°C    sensor = thermistor
AUXTIN2:                   -62.0°C    sensor = thermistor
AUXTIN3:                   +81.0°C    sensor = thermistor
PECI Agent 0 Calibration:  +32.0°C  
PCH_CHIP_CPU_MAX_TEMP:      +0.0°C  
PCH_CHIP_TEMP:              +0.0°C  
PCH_CPU_TEMP:               +0.0°C  
TSI0_TEMP:                 +35.4°C  
intrusion0:               ALARM
intrusion1:               ALARM
beep_enable:              disabled

nvme-pci-0500
Adapter: PCI adapter
Composite:    +33.9°C  (low  =  -5.2°C, high = +79.8°C)
                       (crit = +84.8°C)
1 Like
#19

I see you got your fan speeds; while I’d like them, it’s not that critical (mine glow in the dark, so I can easily see if they’re failing).

1 Like
#20

Things are about to change:

1 Like