AORUS Z790 Master

[daloki83]

Hi, first of all thanks for this project! Since a few month, Linux is my main OS and so i try to get most things running like it was in WIN. Therefore I'm fairly no expert in that kind of stuff and just try my best.

long story, short: Is it somehow possible to get my 2 missing fans detected?

from BIOS Point of view i have the following Fan ports: CPU Fan --> AIO Fans (FAN1) @it8689-isa-0a40 CPU Opt --> Front bottom (FAN5) @it8689-isa-0a40 SysFan1 --> Back Out (FAN2) @it8689-isa-0a40 SysFan2 --> not connected SysFan3 --> bottom back (FAN4) @it8689-isa-0a40 SysFan4 --> bottom front (FAN3) @it87952-isa-0b10 SysFan5 Pump --> AIO Pump (FAN1) @it87952-isa-0b10 SysFan6 Pump --> not connected SysFan7 Pump --> front top (NOT DETECTED) SysFan8 Pump --> front middle (NOT DETECTED)

watch -n1 -d 'sensors | grep fan':

fan1:        1854 RPM  (min =   10 RPM)
fan2:           0 RPM  (min =    0 RPM)
fan3:         378 RPM  (min =    0 RPM)
fan1:         604 RPM  (min =   10 RPM)
fan2:         467 RPM  (min =    0 RPM)
fan3:           0 RPM  (min =    0 RPM)
fan4:         448 RPM  (min =    0 RPM)
fan5:         811 RPM  (min =    0 RPM)

sensors gives me:

it87952-isa-0b10
Adapter: ISA adapter
in0:         748.00 mV (min =  +0.00 V, max =  +2.81 V)
in1:           1.24 V  (min =  +0.00 V, max =  +2.81 V)
in2:         814.00 mV (min =  +0.00 V, max =  +2.81 V)
+3.3V:         1.43 V  (min =  +0.00 V, max =  +5.61 V)
in4:           1.18 V  (min =  +0.00 V, max =  +2.81 V)
in5:           1.83 V  (min =  +0.00 V, max =  +2.81 V)
in6:           1.42 V  (min =  +0.00 V, max =  +2.81 V)
3VSB:          3.32 V  (min =  +0.00 V, max =  +5.61 V)
Vbat:          3.08 V  
fan1:        1864 RPM  (min =   10 RPM)
fan2:           0 RPM  (min =    0 RPM)
fan3:         375 RPM  (min =    0 RPM)
temp1:        +40.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp2:        +27.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp3:        +35.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
intrusion0:  ALARM

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +32.0°C  (high = +80.0°C, crit = +100.0°C)
Core 0:        +29.0°C  (high = +80.0°C, crit = +100.0°C)
Core 4:        +29.0°C  (high = +80.0°C, crit = +100.0°C)
Core 8:        +29.0°C  (high = +80.0°C, crit = +100.0°C)
Core 12:       +28.0°C  (high = +80.0°C, crit = +100.0°C)
Core 16:       +28.0°C  (high = +80.0°C, crit = +100.0°C)
Core 20:       +27.0°C  (high = +80.0°C, crit = +100.0°C)
Core 24:       +28.0°C  (high = +80.0°C, crit = +100.0°C)
Core 28:       +25.0°C  (high = +80.0°C, crit = +100.0°C)
Core 32:       +31.0°C  (high = +80.0°C, crit = +100.0°C)
Core 33:       +31.0°C  (high = +80.0°C, crit = +100.0°C)
Core 34:       +31.0°C  (high = +80.0°C, crit = +100.0°C)
Core 35:       +31.0°C  (high = +80.0°C, crit = +100.0°C)
Core 36:       +30.0°C  (high = +80.0°C, crit = +100.0°C)
Core 37:       +30.0°C  (high = +80.0°C, crit = +100.0°C)
Core 38:       +30.0°C  (high = +80.0°C, crit = +100.0°C)
Core 39:       +30.0°C  (high = +80.0°C, crit = +100.0°C)
Core 40:       +30.0°C  (high = +80.0°C, crit = +100.0°C)
Core 41:       +30.0°C  (high = +80.0°C, crit = +100.0°C)
Core 42:       +30.0°C  (high = +80.0°C, crit = +100.0°C)
Core 43:       +30.0°C  (high = +80.0°C, crit = +100.0°C)
Core 44:       +30.0°C  (high = +80.0°C, crit = +100.0°C)
Core 45:       +30.0°C  (high = +80.0°C, crit = +100.0°C)
Core 46:       +30.0°C  (high = +80.0°C, crit = +100.0°C)
Core 47:       +30.0°C  (high = +80.0°C, crit = +100.0°C)

enp6s0-pci-0600
Adapter: PCI adapter
PHY Temperature:  +39.0°C  
MAC Temperature:  +39.0°C  

nvme-pci-0800
Adapter: PCI adapter
Composite:    +43.9°C  (low  = -273.1°C, high = +81.8°C)
                       (crit = +84.8°C)
Sensor 1:     +43.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +44.9°C  (low  = -273.1°C, high = +65261.8°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +27.8°C  

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:            N/A  

it8689-isa-0a40
Adapter: ISA adapter
in0:         756.00 mV (min =  +0.00 V, max =  +3.06 V)
in1:           2.00 V  (min =  +0.00 V, max =  +3.06 V)
in2:           2.00 V  (min =  +0.00 V, max =  +3.06 V)
in3:           2.03 V  (min =  +0.00 V, max =  +3.06 V)
in4:          48.00 mV (min =  +0.00 V, max =  +3.06 V)
in5:           1.80 V  (min =  +0.00 V, max =  +3.06 V)
in6:           1.98 V  (min =  +0.00 V, max =  +3.06 V)
3VSB:          3.31 V  (min =  +0.00 V, max =  +6.12 V)
Vbat:          3.10 V  
fan1:         604 RPM  (min =   10 RPM)
fan2:         468 RPM  (min =    0 RPM)
fan3:           0 RPM  (min =    0 RPM)
fan4:         440 RPM  (min =    0 RPM)
fan5:         791 RPM  (min =    0 RPM)
temp1:        +41.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = disabled
temp2:        +42.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = disabled
temp3:        +32.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = Intel PECI
temp4:        +41.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp5:        +37.0°C  (low  =  +0.0°C, high = -124.0°C)  sensor = thermistor
temp6:        +26.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
intrusion0:  ALARM

nvme-pci-0300
Adapter: PCI adapter
Composite:    +44.9°C  (low  = -40.1°C, high = +83.8°C)
                       (crit = +87.8°C)
Sensor 1:     +65.8°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +39.9°C  (low  = -273.1°C, high = +65261.8°C)

nvme-pci-0200
Adapter: PCI adapter
Composite:    +48.9°C  (low  =  -5.2°C, high = +89.8°C)
                       (crit = +93.8°C)

nvme-pci-0500
Adapter: PCI adapter
Composite:    +43.9°C  (low  = -273.1°C, high = +81.8°C)
                       (crit = +84.8°C)
Sensor 1:     +43.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +50.9°C  (low  = -273.1°C, high = +65261.8°C)

sensors-detect gives me:

# sensors-detect version 3.6.0
# System: Gigabyte Technology Co., Ltd. Z790 AORUS MASTER [-CF]
# Kernel: 6.9.0-custom x86_64
# Processor: 13th Gen Intel(R) Core(TM) i9-13900K (6/183/1)

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
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'...               No
Trying family `ITE'...                                      Yes
Found unknown chip with ID 0x8689
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'...                                      Yes
Found unknown chip with ID 0x8695

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): Found unknown SMBus adapter 8086:7a23 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.

Next adapter: SMBus I801 adapter at efa0 (i2c-0)
Do you want to scan it? (YES/no/selectively): 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
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Client found at address 0x53
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No

Next adapter: Synopsys DesignWare I2C adapter (i2c-1)
Do you want to scan it? (YES/no/selectively): Adapter doesn't support all probing functions.
Some addresses won't be probed.

Next adapter: Synopsys DesignWare I2C adapter (i2c-2)
Do you want to scan it? (YES/no/selectively): Adapter doesn't support all probing functions.
Some addresses won't be probed.

Next adapter: Synopsys DesignWare I2C adapter (i2c-3)
Do you want to scan it? (YES/no/selectively): Adapter doesn't support all probing functions.
Some addresses won't be probed.
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'...                                No

Next adapter: Synopsys DesignWare I2C adapter (i2c-4)
Do you want to scan it? (YES/no/selectively): Adapter doesn't support all probing functions.
Some addresses won't be probed.

Next adapter: Synopsys DesignWare I2C adapter (i2c-5)
Do you want to scan it? (YES/no/selectively): Adapter doesn't support all probing functions.
Some addresses won't be probed.

Next adapter: Synopsys DesignWare I2C adapter (i2c-6)
Do you want to scan it? (YES/no/selectively): Adapter doesn't support all probing functions.
Some addresses won't be probed.

Next adapter: NVIDIA i2c adapter 1 at 1:00.0 (i2c-7)
Do you want to scan it? (yes/NO/selectively): 
Next adapter: NVIDIA i2c adapter 2 at 1:00.0 (i2c-8)
Do you want to scan it? (yes/NO/selectively): 
Next adapter: NVIDIA i2c adapter 3 at 1:00.0 (i2c-9)
Do you want to scan it? (yes/NO/selectively): 
Next adapter: NVIDIA i2c adapter 4 at 1:00.0 (i2c-10)
Do you want to scan it? (yes/NO/selectively): 
Next adapter: NVIDIA i2c adapter 5 at 1:00.0 (i2c-11)
Do you want to scan it? (yes/NO/selectively): 
Next adapter: NVIDIA i2c adapter 6 at 1:00.0 (i2c-12)
Do you want to scan it? (yes/NO/selectively): Client found at address 0x58
Probing for `Analog Devices ADT7462'...                     No
Probing for `Andigilog aSC7512'...                          No
Client found at address 0x5c
Probing for `Analog Devices ADT7462'...                     No
Probing for `SMSC EMC1072'...                               No
Probing for `SMSC EMC1073'...                               No
Probing for `SMSC EMC1074'...                               No

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)

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

Monitoring programs won't work until the needed modules are
loaded. You may want to run '/etc/init.d/kmod start'
to load them.

Unloading cpuid... OK

***************************************************************
Warning: the preferred way to run this script non-interactively
is with option --auto. Other methods are discouraged and may
stop working at some point in the future.
***************************************************************

and my /etc/modprobe.d/it87.conf options it87 ignore_resource_conflict=1 i didnt use "force_id=0x8622" because i couldnt see a difference.

~~ahh, and my GRUB line has: GRUB_CMDLINE_LINUX_DEFAULT="acpi_enforce_resources=lax enabled"~~

EDIT: Based on Windows HWINFO this board has

• IT8689E
• IT87952E
• and Gigabyte EC ??

[daloki83]

Not sure if this is helping, but saw that you requested for similar issues:

blacklisted and rebooted:

isadump 0x4e 0x4f 7:

WARNING! Running this program can cause system crashes, data loss and worse!
I will probe address register 0x4e and data register 0x4f.
Probing bank 7 using bank register 0x07.
Continue? [Y/n] y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00: 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 00 
10: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 
20: 86 95 01 40 01 00 ff 00 fe 18 02 00 8a 64 00 00 
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
60: 00 00 0b 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 01 20 38 00 00 00 00 00 00 00 00 00 00 00 00 
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
b0: 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00 00 
c0: 01 00 00 7e 08 00 00 00 00 00 00 16 00 c0 9e 00 
d0: ff 00 00 10 00 00 00 00 00 00 00 00 00 04 00 00 
e0: 00 00 00 00 00 00 00 00 00 20 20 20 00 3e 3e 0c 
f0: 00 00 00 00 00 00 2c 00 00 00 00 00 ff 00 00 00

isadump 0x2e 0x2f 7:

WARNING! Running this program can cause system crashes, data loss and worse!
I will probe address register 0x2e and data register 0x2f.
Probing bank 7 using bank register 0x07.
Continue? [Y/n] y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
80: ff ff ff ff ff ff ff 86 ff ff ff ff ff ff ff ff 
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

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): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      Yes
Found unknown chip with ID 0x8689
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'...                                      Yes
Found unknown chip with ID 0x8695

isadump 0x4e 0x4f 7:

WARNING! Running this program can cause system crashes, data loss and worse!
I will probe address register 0x4e and data register 0x4f.
Probing bank 7 using bank register 0x07.
Continue? [Y/n] y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

isadump 0x2e 0x2f 7:

WARNING! Running this program can cause system crashes, data loss and worse!
I will probe address register 0x2e and data register 0x2f.
Probing bank 7 using bank register 0x07.
Continue? [Y/n] y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
80: ff ff ff ff ff ff ff 86 ff ff ff ff ff ff ff ff 
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 

isadump 0xa45 0xa46

WARNING! Running this program can cause system crashes, data loss and worse!
I will probe address register 0xa45 and data register 0xa46.
Continue? [Y/n] y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00: 19 10 00 80 df ff 00 20 ff 98 20 40 30 5c 97 ff 
10: fe ff ff 77 c7 d0 e0 e0 04 05 ff ff ff ff ff ff 
20: 3e a7 a7 a9 04 96 a5 8b 81 27 2e 20 2a 26 17 80 
30: ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 
40: 7f 7f 7f 7f 7f 7f 5f 40 ad 6a d4 00 00 00 00 00 
50: ff 18 7f 7f 7f 40 00 00 90 64 1c 12 65 00 00 00 
60: 00 00 64 33 00 01 00 00 00 00 52 34 00 01 00 ff 
70: 00 14 3c 3f 05 00 00 2e 00 1d 64 00 00 01 00 c0 
80: ff ff ff ff ff ff ff ff 02 30 01 02 01 d8 e0 1c 
90: 00 00 00 00 ff 10 10 10 40 97 00 00 40 c1 c1 04 
a0: 00 00 64 00 00 01 00 c8 7f 7f 96 80 00 00 0f 98 
b0: bc 7f 83 75 7f 7f 84 00 7f 7f 80 27 80 80 80 00 
c0: 00 c0 00 99 e3 01 10 10 10 10 10 10 10 10 10 10 
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 01 
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff 00 00 

isadump 0xa65 0xa66:

WARNING! Running this program can cause system crashes, data loss and worse!
I will probe address register 0xa65 and data register 0xa66.
Continue? [Y/n] y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

[frankcrawford]

Thanks for all that.

I'm not sure at present what the "Gigabyte EC" is, although I have seen reports that Gigbyte are putting in some other chips to manage some things around fans.

[ChirpyTurnip]

Misery loves company I hear! :-(

I have the same board more or less (Gigabyte Aorus Z790M Elite AX) and I'm running Unraid. Have installed the ITE IT87 plugin and the Dynamix system temp / fan add ins.

My results are essentially the same as above but my set up is slightly different. I have four fans:

• CPU = CPU (Unraid detected as FAN1)
• CPU_OPT = Not used
• SYS_FAN1 = Drive Bay Rear (Unraid detected as FAN2)
• SYS_FAN2 = Drive Bay Front Lower (Unraid detected as FAN3)
• SYS_FAN3 = Drive Bay Front Upper (Unraid detected as FAN4)
• PUMP = Unused

This is verified by finger-braking the fans and seeing the changing values come through.

After installing the plugin sensors-detect give me:

# sensors-detect version 3.6.0
# System: Gigabyte Technology Co., Ltd. Z790M AORUS ELITE AX
# Kernel: 6.1.106-Unraid x86_64
# Processor: Intel(R) Core(TM) i7-14700K (6/183/1)

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): 
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'...               No
Trying family `ITE'...                                      Yes
Found unknown chip with ID 0x8689
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): 
Found unknown SMBus adapter 8086:7a23 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 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
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Client found at address 0x53
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No

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

Next adapter: i915 gmbus dpb (i2c-2)
Do you want to scan it? (yes/NO/selectively): yes

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

Next adapter: i915 gmbus tc1 (i2c-4)
Do you want to scan it? (yes/NO/selectively): yes

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

Next adapter: i915 gmbus tc3 (i2c-6)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus tc4 (i2c-7)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus tc5 (i2c-8)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus tc6 (i2c-9)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AUX USBC2/DDI TC2/PHY C (i2c-10)
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 `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yes
Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors
for initialization at boot time.
You should now start the lm_sensors service to load the required
kernel modules.

Unloading i2c-dev... OK

And sensors gives me this:

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +16.8°C  (crit = +20.8°C)
MB Temp:      +27.8°C  (crit = +105.0°C)

nvme-pci-0600
Adapter: PCI adapter
Composite:    +44.9°C  (low  = -273.1°C, high = +81.8°C)
                       (crit = +84.8°C)
Sensor 1:     +44.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +51.9°C  (low  = -273.1°C, high = +65261.8°C)

nvme-pci-0700
Adapter: PCI adapter
Composite:    +47.9°C  (low  = -273.1°C, high = +81.8°C)
                       (crit = +84.8°C)
Sensor 1:     +47.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +53.9°C  (low  = -273.1°C, high = +65261.8°C)

it8689-isa-0a40
Adapter: ISA adapter
in0:           1.46 V  (min =  +0.00 V, max =  +3.06 V)
in1:           1.98 V  (min =  +0.00 V, max =  +3.06 V)
in2:           2.02 V  (min =  +0.00 V, max =  +3.06 V)
in3:           2.00 V  (min =  +0.00 V, max =  +3.06 V)
in4:         144.00 mV (min =  +0.00 V, max =  +3.06 V)
in5:           1.81 V  (min =  +0.00 V, max =  +3.06 V)
in6:           1.99 V  (min =  +0.00 V, max =  +3.06 V)
3VSB:          3.36 V  (min =  +0.00 V, max =  +6.12 V)
Vbat:          3.12 V  
fan1:        1735 RPM  (min =   10 RPM)
fan2:        1439 RPM  (min =    0 RPM)
fan3:        1161 RPM  (min =    0 RPM)
fan4:        1188 RPM  (min =    0 RPM)
temp1:        +35.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp2:        +44.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp3:        +59.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = Intel PECI
temp4:        +41.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp5:        +47.0°C  (low  =  +0.0°C, high = -124.0°C)  sensor = thermistor
temp6:        +32.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
intrusion0:  ALARM

coretemp-isa-0000
Adapter: ISA adapter
CPU Temp:     +64.0°C  (high = +80.0°C, crit = +100.0°C)
Core 0:       +64.0°C  (high = +80.0°C, crit = +100.0°C)
Core 4:       +54.0°C  (high = +80.0°C, crit = +100.0°C)
Core 8:       +56.0°C  (high = +80.0°C, crit = +100.0°C)
Core 12:      +55.0°C  (high = +80.0°C, crit = +100.0°C)
Core 16:      +55.0°C  (high = +80.0°C, crit = +100.0°C)
Core 20:      +56.0°C  (high = +80.0°C, crit = +100.0°C)
Core 24:      +56.0°C  (high = +80.0°C, crit = +100.0°C)
Core 28:      +56.0°C  (high = +80.0°C, crit = +100.0°C)
Core 32:      +55.0°C  (high = +80.0°C, crit = +100.0°C)
Core 33:      +55.0°C  (high = +80.0°C, crit = +100.0°C)
Core 34:      +55.0°C  (high = +80.0°C, crit = +100.0°C)
Core 35:      +55.0°C  (high = +80.0°C, crit = +100.0°C)
Core 36:      +58.0°C  (high = +80.0°C, crit = +100.0°C)
Core 37:      +58.0°C  (high = +80.0°C, crit = +100.0°C)
Core 38:      +58.0°C  (high = +80.0°C, crit = +100.0°C)
Core 39:      +58.0°C  (high = +80.0°C, crit = +100.0°C)
Core 40:      +53.0°C  (high = +80.0°C, crit = +100.0°C)
Core 41:      +53.0°C  (high = +80.0°C, crit = +100.0°C)
Core 42:      +53.0°C  (high = +80.0°C, crit = +100.0°C)
Core 43:      +53.0°C  (high = +80.0°C, crit = +100.0°C)

nvme-pci-0900
Adapter: PCI adapter
Composite:    +47.9°C  (low  = -273.1°C, high = +81.8°C)
                       (crit = +84.8°C)
Sensor 1:     +47.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +51.9°C  (low  = -273.1°C, high = +65261.8°C)

The fans are also jammed up at 100% which is a real pain because that's loud.

Running pwmconfig also achieves nothing:

# pwmconfig version 3.6.0
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.

We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.

Found the following devices:
   hwmon0 is nvme
   hwmon1 is nvme
   hwmon2 is nvme
   hwmon3 is coretemp
   hwmon4 is acpitz
   hwmon5 is it8689

Found the following PWM controls:
   hwmon5/pwm1           current value: 57
   hwmon5/pwm2           current value: 63
hwmon5/pwm2 is currently setup for automatic speed control.
In general, automatic mode is preferred over manual mode, as
it is more efficient and it reacts faster. Are you sure that
you want to setup this output for manual control? (n) 
   hwmon5/pwm3           current value: 79
   hwmon5/pwm4           current value: 63
hwmon5/pwm4 is currently setup for automatic speed control.
In general, automatic mode is preferred over manual mode, as
it is more efficient and it reacts faster. Are you sure that
you want to setup this output for manual control? (n) 
   hwmon5/pwm5           current value: 79
   hwmon5/pwm6           current value: 63
hwmon5/pwm6 is currently setup for automatic speed control.
In general, automatic mode is preferred over manual mode, as
it is more efficient and it reacts faster. Are you sure that
you want to setup this output for manual control? (n) 

Giving the fans some time to reach full speed...
Found the following fan sensors:
   hwmon5/fan1_input     current speed: 1739 RPM
   hwmon5/fan2_input     current speed: 1436 RPM
   hwmon5/fan3_input     current speed: 1159 RPM
   hwmon5/fan4_input     current speed: 1186 RPM
   hwmon5/fan5_input     current speed: 0 ... skipping!
   hwmon5/fan6_input     current speed: 0 ... skipping!

Warning!!! This program will stop your fans, one at a time,
for approximately 5 seconds each!!!
This may cause your processor temperature to rise!!!
If you do not want to do this hit control-C now!!!
Hit return to continue: 

Testing pwm control hwmon5/pwm1 ...
  hwmon5/fan1_input ... speed was 1739 now 1730
    no correlation
  hwmon5/fan2_input ... speed was 1436 now 1439
    no correlation
  hwmon5/fan3_input ... speed was 1159 now 1161
    no correlation
  hwmon5/fan4_input ... speed was 1186 now 1188
    no correlation

No correlations were detected.
There is either no fan connected to the output of hwmon5/pwm1,
or the connected fan has no rpm-signal connected to one of
the tested fan sensors. (Note: not all motherboards have
the pwm outputs connected to the fan connectors,
check out the hardware database on http://www.almico.com/forumindex.php)

One odd thing I have found is that when I do not run _sudo modprobe it87 forceid=0x8689 and I ask Fan Auto Control to detect the pwm fan I get this mapping:

• PWM1 = FAN2
• PWM2 = FAN2
• PWM3 = FAN1
• PWM4 = FAN1
• PWM5 = FAN3
• PWM6 = FAN2

When I run _sudo modprobe it87 forceid=0x8689 I get this mapping:

• PWM1 = FAN3
• PWM2 = FAN1
• PWM3 = FAN2
• PWM4 = FAN1
• PWM5 = FAN4
• PWM6 = FAN1

If I run sudo modprobe -r it87 and reboot then try the mapping again I get:

• PWM1 = FAN2
• PWM2 = FAN1
• PWM3 = FAN1
• PWM4 = FAN2
• PWM5 = FAN2
• PWM6 = FAN2

This is odd so I just hit DETECT multiple times and noted that it is picking up random / different fans every time...so there is no consistency. I got PWM6 to flag as FAN1, FAN2, FAN3, and , but never FAN4. It seems that only comes out when the chip is forced.

In the logs I can see it is trying to do something:

Sep 12 17:39:42 Svalbard autofan: Highest disk temp is 36C, adjusting fan speed from: FULL (100% @ 1149rpm) to: 57 (22% @ 1101rpm)
Sep 12 17:39:42 Svalbard autofan: Highest disk temp is 36C, adjusting fan speed from: FULL (100% @ 1439rpm) to: 79 (30% @ 1436rpm)
Sep 12 17:39:42 Svalbard autofan: Highest disk temp is 36C, adjusting fan speed from: FULL (100% @ 1182rpm) to: 79 (30% @ 1184rpm)
Sep 12 17:41:48 Svalbard autofan: Highest disk temp is 36C, adjusting fan speed from: FULL (100% @ 1436rpm) to: 79 (30% @ 1439rpm)
Sep 12 17:41:48 Svalbard autofan: Highest disk temp is 36C, adjusting fan speed from: FULL (100% @ 1186rpm) to: 79 (30% @ 1188rpm)

But the fans just always stay stuck on max. Which is annoying as the system is doing something as otherwise the BIOS would allow then to ramp down and track the CPU. I can set all the PWMs in Auto Fan Control to 'disabled' and clear the PWM fan allocation etc.....but nothing allows the fans ramp down.

On rebooting the machine is mercifully quiet, but once the array starts and everything loads we're back to permanent full noise. I wish I could find out what is causing that because right now peace an quiet would be preferable over fan control. Unfortunately I'm dumb at Linux so I don't fancy my chances...

Let me know if you want me to run / try something in terms of providing more details for the bug.

[ChirpyTurnip]

Also if it helps, here is the log from boot up:

Sep 12 18:16:37 Svalbard root: plugin: installing: it87-driver.plg
Sep 12 18:16:37 Svalbard root: Executing hook script: pre_plugin_checks
Sep 12 18:16:37 Svalbard root: plugin: creating: /usr/local/emhttp/plugins/it87-driver/README.md - from INLINE content
Sep 12 18:16:37 Svalbard root: plugin: running: anonymous
Sep 12 18:16:37 Svalbard root: 
Sep 12 18:16:37 Svalbard root: -----------------------IT87 Drivers found locally------------------------
Sep 12 18:16:37 Svalbard kernel: it87: it87 driver version v1.0-166-g14b1de2.20240816
Sep 12 18:16:37 Svalbard kernel: it87: Found IT8689E chip at 0xa40, revision 2
Sep 12 18:16:37 Svalbard kernel: it87: Beeping is supported
Sep 12 18:16:37 Svalbard kernel: ACPI Warning: SystemIO range 0x0000000000000A45-0x0000000000000A46 conflicts with OpRegion 0x0000000000000A45-0x0000000000000A46 (\GSA1.SIO1) (20220331/utaddress-204)
Sep 12 18:16:37 Svalbard kernel: ACPI: OSL: Resource conflict; ACPI support missing from driver?
Sep 12 18:16:37 Svalbard root: 
Sep 12 18:16:37 Svalbard root: ----------------Installation of IT87 Drivers successful------------------
Sep 12 18:16:37 Svalbard root: 
Sep 12 18:16:37 Svalbard root: plugin: it87-driver.plg installed
Sep 12 18:16:37 Svalbard root: plugin: it87-driver.plg installed

[frankcrawford]

@ChirpyTurnip Looking at the pwmconfig script, it really doesn't know what fan is associated with which PWM, rather, it changes the PWM settings and then checks to see which fan changes at the same time. Unfortunately, this means that when it is not really working it just gets random associations.

The problem is almost certainly the issue listed in issue #11 where Gigabyte have introduced a new chip into the mix and currently none of the drivers handle it. If you read through that issue you will see some workarounds you can try.

Also, as a minor fix, I've added you board into the default list to ignore ACPI support, so you no longer need to add ignore_resource_conflict=1 to the command line.

[frankcrawford]

@daloki83 if you are still following this, see the comment above, but also, can you send me the details you get from cat /sys/class/dmi/id/board_vendor and /sys/class/dmi/id/board_name just so I can track what chips are in which boards.