Linux 6.3 Supports Sensor Monitoring For Many ASUS B650/B660/X670 Motherboards

[piorunz]

Thank you! Could you please make one more check on b350 with a currently installed kernel, version doesn't matter, run modprobe nct6775 and check what is the error in dmesg? It should say that sensor is detected, but have conflict with acpi resources.
it will be positive case as kernel just need add b350 boards to the accepted boards list to use Asus wmi methods.

Otherwise support b350 boards will more complicated story with search correct methods to have access to sensors or use it87 or some other sensors module with additional patches.

Server with b350 is on Debian Stable, and this module does not exist on it yet (5.10 kernel):
$ sudo modprobe nct6775
[sudo] password for
modprobe: ERROR: could not insert 'nct6775': No such device

However, sensors-detect on B350 board has detected something else, and added it to /etc/modules, jc42 module. Do you know what is it?
$ sensors
jc42-i2c-0-1b
Adapter: SMBus PIIX4 adapter port 0 at 0b00
temp1: +38.0°C (low = +0.0°C) ALARM (HIGH, CRIT)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C, hyst = +0.0°C)

jc42-i2c-0-19
Adapter: SMBus PIIX4 adapter port 0 at 0b00
temp1: +38.0°C (low = +0.0°C) ALARM (HIGH, CRIT)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C, hyst = +0.0°C)

nouveau-pci-0700
Adapter: PCI adapter
GPU core: 912.00 mV (min = +0.80 V, max = +1.19 V)
temp1: +40.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)

jc42-i2c-0-1a
Adapter: SMBus PIIX4 adapter port 0 at 0b00
temp1: +37.5°C (low = +0.0°C) ALARM (HIGH, CRIT)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C, hyst = +0.0°C)

jc42-i2c-0-18
Adapter: SMBus PIIX4 adapter port 0 at 0b00
temp1: +35.5°C (low = +0.0°C) ALARM (HIGH, CRIT)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C, hyst = +0.0°C)

k10temp-pci-00c3
Adapter: PCI adapter
Tctl: +35.8°C
Tdie: +35.8°C

This is now output on b350 board, before, it was just Ryzen CPU and Nvidia GPU, now I've got more sensors via jc42 module.

[denisdevelops]

Server with b350 is on Debian Stable, and this module does not exist on it yet (5.10 kernel):
$ sudo modprobe nct6775
[sudo] password for
modprobe: ERROR: could not insert 'nct6775': No such device

However, sensors-detect on B350 board has detected something else, and added it to /etc/modules, jc42 module. Do you know what is it?
$ sensors
jc42-i2c-0-1b
Adapter: SMBus PIIX4 adapter port 0 at 0b00
temp1: +38.0°C (low = +0.0°C) ALARM (HIGH, CRIT)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C, hyst = +0.0°C)

jc42-i2c-0-19
Adapter: SMBus PIIX4 adapter port 0 at 0b00
temp1: +38.0°C (low = +0.0°C) ALARM (HIGH, CRIT)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C, hyst = +0.0°C)

nouveau-pci-0700
Adapter: PCI adapter
GPU core: 912.00 mV (min = +0.80 V, max = +1.19 V)
temp1: +40.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)

jc42-i2c-0-1a
Adapter: SMBus PIIX4 adapter port 0 at 0b00
temp1: +37.5°C (low = +0.0°C) ALARM (HIGH, CRIT)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C, hyst = +0.0°C)

jc42-i2c-0-18
Adapter: SMBus PIIX4 adapter port 0 at 0b00
temp1: +35.5°C (low = +0.0°C) ALARM (HIGH, CRIT)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C, hyst = +0.0°C)

k10temp-pci-00c3
Adapter: PCI adapter
Tctl: +35.8°C
Tdie: +35.8°C

This is not output on b350 board, before, it was just Ryzen CPU and Nvidia GPU, now I've got more sensors via jc42 module.

Thank you!

jc42 looks like sensors on memory sticks https://www.kernel.org/doc/html/v5.12/hwmon/jc42.html, at least Google said such.


"modprobe: ERROR: could not insert 'nct6775': No such device" looks like more related to unable found sensor or some errors with access, in dmesg could be more information about it.

Main question what sensors b350 has? It could be nct6775, it87 or something else. Older boards have used it87 and different access method on Asus board, but UEFI dump contains new style method.

It can be https://www.kernel.org/doc/html/latest/hwmon/it87.html, and board requires to use force flags for load module correctly that is unsafe solution.

[piorunz]

Thank you!

jc42 looks like sensors on memory sticks https://www.kernel.org/doc/html/v5.12/hwmon/jc42.html, at least Google said such.


"modprobe: ERROR: could not insert 'nct6775': No such device" looks like more related to unable found sensor or some errors with access, in dmesg could be more information about it.

Main question what sensors b350 has? It could be nct6775, it87 or something else. Older boards have used it87 and different access method on Asus board, but UEFI dump contains new style method.

It can be https://www.kernel.org/doc/html/latest/hwmon/it87.html, and board requires to use force flags for load module correctly that is unsafe solution.

Great, thanks! Indeed jc42 is showing my memory sticks! That works perfectly well both on B350 and B550 boards.
"sudo modprobe nct6775" does not show anything in dmesg in Debian Stable, while it works in Debian Testing on B550.
I guess I will have to wait until new Debian is released this year, with 6.1 LTS kernel, then I will try again on B350 board

[Namelesswonder]

Great, thanks! Indeed jc42 is showing my memory sticks! That works perfectly well both on B350 and B550 boards.
"sudo modprobe nct6775" does not show anything in dmesg in Debian Stable, while it works in Debian Testing on B550.
I guess I will have to wait until new Debian is released this year, with 6.1 LTS kernel, then I will try again on B350 board

I don't think ASUS began using Nuvoton chips on AMD until the 500-series motherboards, before that they used ITE chips.
My X370-F had an IT8665E, so your B350 will most likely have an IT8665E or an IT8655E.

Roeck gave up on trying to support the it87 module since ITE gave no support, back then I had to use an out of tree patched module, from a search it looks like there is a more modern fork that is used by Arch.

https://github.com/frankcrawford/it87

[Keith Myers]

Using a Asus X670E Crosshair Hero board.

sudo sensors-detect finds no identifiable sensors but does show a couple of 'somethings'

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

and

Trying family `ITE'... Yes
Found unknown chip with ID 0x8883
(logical device 4 has address 0x290, could be sensors)

(This is a ITE USB chip. No driver for it yet)

sudo modprobe nct6775 produces:
modprobe: ERROR: could not insert 'nct6775': No such device

Finally stumbled on a Reddit post that gave me a clue.

sudo modprobe nct6775 force_id=0xd420

Which produces:

$ sudo dmesg |grep nct6775
[ 4.310583] nct6775: Found NCT6796D or compatible chip at 0x2e:0x290


~$ sensors
nct6796-isa-0290
Adapter: ISA adapter
Vcore: 744.00 mV (min = +0.00 V, max = +1.74 V)
in1: 992.00 mV (min = +0.00 V, max = +0.00 V) ALARM
AVCC: 3.41 V (min = +0.00 V, max = +0.00 V) ALARM
+3.3V: 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: 1.01 V (min = +0.00 V, max = +0.00 V) ALARM
in6: 1.13 V (min = +0.00 V, max = +0.00 V) ALARM
3VSB: 3.41 V (min = +0.00 V, max = +0.00 V) ALARM
Vbat: 3.31 V (min = +0.00 V, max = +0.00 V) ALARM
in9: 1.66 V (min = +0.00 V, max = +0.00 V) ALARM
in10: 528.00 mV (min = +0.00 V, max = +0.00 V) ALARM
in11: 528.00 mV (min = +0.00 V, max = +0.00 V) ALARM
in12: 1.02 V (min = +0.00 V, max = +0.00 V) ALARM
in13: 1.21 V (min = +0.00 V, max = +0.00 V) ALARM
in14: 1.23 V (min = +0.00 V, max = +0.00 V) ALARM
fan1: 0 RPM (min = 0 RPM)
fan2: 2000 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
fan6: 0 RPM (min = 0 RPM)
fan7: 1928 RPM (min = 0 RPM)
SYSTIN: +34.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: +19.0°C sensor = thermistor
AUXTIN1: +22.0°C sensor = thermistor
AUXTIN2: +22.0°C sensor = thermistor
AUXTIN3: +14.0°C sensor = thermistor
PECI Agent 0 Calibration: +34.0°C
PCH_CHIP_CPU_MAX_TEMP: +0.0°C
PCH_CHIP_TEMP: +0.0°C
PCH_CPU_TEMP: +0.0°C
TSI0_TEMP: +45.1°C
intrusion0: ALARM
intrusion1: ALARM
beep_enable: disabled

Then I added nct6775 to /etc/modules-load.d/modules.conf file and then created nct6775.conf file in /etc/modprobe.d with contents of:
options nct6775 force_id=0xd420

Not as simple as just modprobing the nct6775 module as all other posts have depicted.

[Keith Myers]

Just a update to this sensors saga. After updating to kernel 6.5-rc2, I can modprobe the nct6775 module without the force load of the 6796 chip id. That kernel has the updated module to handle my nct6799D SIO chip natively. Benefit is that the proper fan outputs are found. I was missing fan5 on the 6796 module ID.
Believe the same thing is doable for the nct6768 versions of the SIO chip.