X570SI AORUS PRO AX (rev. 1.1) works with force-load

[mooninite]

FYI: On Fedora 36 / 5.17.6-300.fc36.x86_64 I can force load the module and I get temp monitors.

$ dmesg | grep -i gigabyte
[    0.000000] DMI: Gigabyte Technology Co., Ltd. X570S I AORUS PRO AX/X570S I AORUS PRO AX, BIOS F3c 05/12/2022
$ sudo rmmod gigabyte-wmi # it was already loaded
$ sudo modprobe gigabyte-wmi force-load=1
$ dmesg | tail -n 1
[ 2372.610555] gigabyte-wmi DEADBEEF-2001-0000-00A0-C90629100000: Forcing load on unknown platform

$ sensors
k10temp-pci-00c3
Adapter: PCI adapter
Tctl:         +56.6°C  
Tccd1:        +52.8°C  

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +16.8°C  (crit = +20.8°C)
temp2:        +16.8°C  (crit = +20.8°C)
temp3:        +16.8°C  (crit = +20.8°C)

gigabyte_wmi-virtual-0
Adapter: Virtual device
temp1:        +45.0°C  
temp2:        -55.0°C  
temp3:        +55.0°C  
temp4:        +21.0°C  
temp5:        +45.0°C  
temp6:        +45.0°C  

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

[t-8ch]

@mooninite Great to hear! This driver is now developed upstream as part of the Linux kernel.

Do you think you could submit a patch there directly?
You can look at https://lore.kernel.org/all/20220510120012.2167591-1-frank@crawford.emu.id.au/ for an example.

[got3nks]

On a fresh install of Ubuntu Server 22.04 LTS sensors isn't working with a B650 AORUS ELITE AX.

Is gigabyte-wmi-driver not part of kernel version 5.15.0-67?

$ sudo dmesg | grep -i gigabyte
[    0.000000] DMI: Gigabyte Technology Co., Ltd. B650 AORUS ELITE AX/B650 AORUS ELITE AX, BIOS F4 03/22/2023

$ uname -r
5.15.0-67-generic
$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.2 LTS
Release:	22.04

$ sudo sensors-detect
# sensors-detect version 3.6.0
# System: Gigabyte Technology Co., Ltd. B650 AORUS ELITE AX [Default string]
# Kernel: 5.15.0-67-generic x86_64
# Processor: AMD Ryzen 9 7900 12-Core Processor (25/97/2)

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...                             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'...               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):
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: 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.
Client found at address 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No

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.

[t-8ch]

@got3nks
Try "modinfo gigabyte-wmi" and the steps from #1.

[got3nks]

Which steps @t-8ch ?

# modinfo gigabyte-wmi
filename:       /lib/modules/5.15.0-67-generic/kernel/drivers/platform/x86/gigabyte-wmi.ko
license:        GPL
description:    Gigabyte WMI temperature driver
author:         Thomas Weißschuh <thomas@weissschuh.net>
srcversion:     B9B642473FA302BE7537A85
alias:          wmi:DEADBEEF-2001-0000-00A0-C90629100000
depends:        wmi
retpoline:      Y
intree:         Y
name:           gigabyte_wmi
vermagic:       5.15.0-67-generic SMP mod_unload modversions
sig_id:         PKCS#7
signer:         Build time autogenerated kernel key
sig_key:        6A:E4:82:93:16:0C:0A:72:F5:35:4E:E3:F6:7B:2E:81:B6:80:61:0E
sig_hashalgo:   sha512
signature:      85:46:45:AB:B4:0B:F5:22:B1:2C:6D:76:92:8D:62:D8:D3:10:3E:F8:
		A9:09:9B:32:B0:2E:BC:14:E9:EB:29:3B:56:61:87:01:F3:59:8F:8A:
		0F:6F:88:A1:4F:67:32:F9:E6:79:74:BD:AA:9B:76:0E:01:2C:94:AD:
		D9:26:51:39:6B:0E:A3:F3:35:98:B4:52:97:FF:D5:4A:11:8B:58:CE:
		66:D7:A7:6E:4A:7C:E8:1A:69:26:22:D2:D1:ED:1A:F7:F6:94:3C:73:
		F0:EF:CD:4C:F3:99:24:1D:78:D7:AE:A5:F0:FA:D1:93:06:52:3E:62:
		2C:B0:3B:E9:1B:1C:D2:EE:40:FF:D1:1B:01:AC:7A:07:A7:3D:DD:B5:
		EF:16:1C:6F:48:32:28:B9:2E:ED:51:D3:85:77:FD:E2:CC:8A:09:72:
		F9:1D:33:38:44:00:65:A0:6C:DC:13:AE:0A:BF:71:00:09:71:5D:7D:
		61:02:9D:45:68:10:CB:5E:00:06:07:EB:24:5A:04:CC:CB:6C:93:5B:
		9D:5F:F1:7B:55:E0:2D:A4:C1:B7:72:A6:50:46:7F:DB:E4:47:E2:7D:
		FC:18:EE:32:9C:31:7B:78:51:5B:DF:92:99:70:55:7C:3F:98:F5:DE:
		F9:7C:47:25:46:85:83:0E:09:EA:AF:28:BD:B4:AC:4E:55:BA:4A:8C:
		5B:3E:38:64:35:F5:44:6D:A9:B9:A8:58:0E:05:44:F0:54:79:A4:91:
		52:63:60:01:02:44:99:3A:3E:61:E1:7B:3C:70:86:EA:2A:9E:7E:EC:
		39:91:AC:BC:66:1F:C5:60:DD:96:CE:DE:B6:8F:1F:3B:18:C8:1A:3C:
		C1:6D:14:9B:CD:E8:3C:3A:B9:D1:83:87:EB:7B:0E:49:FA:80:BA:94:
		C0:F1:F8:5E:3C:37:EC:E0:3D:51:28:B6:60:A1:C9:9C:8D:59:38:94:
		BB:14:2C:0C:E1:8A:DE:66:68:95:86:13:76:FC:23:1A:D4:5A:A9:77:
		86:13:72:91:5D:E4:6C:F0:95:91:CC:44:DC:9D:FF:FD:A0:73:32:96:
		10:33:41:CA:BE:2F:E5:B5:35:CE:B6:5E:5F:DF:24:9A:A0:78:C9:A8:
		B4:74:42:93:08:58:BE:45:56:D8:82:0E:D1:CB:43:55:1F:E9:7B:01:
		A8:77:4B:0D:1D:34:7D:4A:56:4B:9A:9D:49:E7:5D:A1:A3:C7:1A:42:
		68:E0:B9:46:0B:8B:69:07:0A:2C:39:FF:EF:71:36:1E:FC:6C:C4:9B:
		AF:BA:3C:68:CA:2A:38:1F:CC:1D:F8:9E:B2:DF:E2:43:F7:C7:23:FF:
		E0:76:4D:97:BD:89:3E:39:02:86:67:8E
parm:           force_load:Force loading on unknown platform (bool)

[t-8ch]

@got3nks

sudo modprobe -r gigabyte-wmi
sudo modprobe gigabyte-wmi force_load=1
sudo dmesg
sensors

[got3nks]

Looks like it worked!

# sudo dmesg
[ 9039.538295] gigabyte-wmi DEADBEEF-2001-0000-00A0-C90629100000: Forcing load on unknown platform

# sensors
gigabyte_wmi-virtual-0
Adapter: Virtual device
temp1:        +31.0°C
temp2:        +36.0°C
temp3:        +65.0°C
temp4:        +33.0°C
temp5:        +34.0°C
temp6:        +35.0°C

Does it persist between reboots?

[t-8ch]

Looks like it worked!

Nice!

Does it persist between reboots?

No. The proper fix is to submit the hardware ID to the upstream kernel. (See #17 if you want to do it, or I can do it)

As a one-off fix for your machine you can do:

echo "options gigabyte-wmi force_load=1" > /etc/modprobe.d/gigabyte.conf

[got3nks]

Thanks @t-8ch!

# grep -r . /sys/class/dmi/id/
/sys/class/dmi/id/bios_date:03/22/2023
/sys/class/dmi/id/board_serial:Default string
/sys/class/dmi/id/uevent:MODALIAS=dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF4:bd03/22/2023:br5.26:svnGigabyteTechnologyCo.,Ltd.:pnB650AORUSELITEAX:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB650AORUSELITEAX:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
/sys/class/dmi/id/product_serial:Default string
/sys/class/dmi/id/product_name:B650 AORUS ELITE AX
/sys/class/dmi/id/chassis_vendor:Default string
/sys/class/dmi/id/chassis_asset_tag:Default string
/sys/class/dmi/id/sys_vendor:Gigabyte Technology Co., Ltd.
/sys/class/dmi/id/power/runtime_active_time:0
/sys/class/dmi/id/power/runtime_active_kids:0
/sys/class/dmi/id/power/runtime_usage:0
/sys/class/dmi/id/power/runtime_status:unsupported
grep: /sys/class/dmi/id/power/autosuspend_delay_ms: Input/output error
/sys/class/dmi/id/power/async:disabled
/sys/class/dmi/id/power/runtime_suspended_time:0
/sys/class/dmi/id/power/runtime_enabled:disabled
/sys/class/dmi/id/power/control:auto
/sys/class/dmi/id/bios_version:F4
/sys/class/dmi/id/bios_release:5.26
/sys/class/dmi/id/product_version:Default string
/sys/class/dmi/id/board_vendor:Gigabyte Technology Co., Ltd.
/sys/class/dmi/id/chassis_version:Default string
/sys/class/dmi/id/product_sku:Default string
/sys/class/dmi/id/chassis_type:3
/sys/class/dmi/id/chassis_serial:Default string
/sys/class/dmi/id/product_family:B650 MB
/sys/class/dmi/id/product_uuid:03560274-043c-0533-1706-5c0700080009
/sys/class/dmi/id/bios_vendor:American Megatrends International, LLC.
/sys/class/dmi/id/board_asset_tag:Default string
/sys/class/dmi/id/board_version:x.x
/sys/class/dmi/id/modalias:dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF4:bd03/22/2023:br5.26:svnGigabyteTechnologyCo.,Ltd.:pnB650AORUSELITEAX:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB650AORUSELITEAX:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
/sys/class/dmi/id/board_name:B650 AORUS ELITE AX

May be a bit off-topic, is it possible to change the fans speed from the OS?

[t-8ch]

/sys/class/dmi/id/board_name:B650 AORUS ELITE AX

Do you want me to add that to the upstream driver?

is it possible to change the fans speed from the OS?

I think it's possible either via the it87 driver (which has issues) or by reverse-engineering the WMI methods.

[got3nks]

I think it can be added as it seems to work as far as the 6 sensors I listed above.

[t-8ch]

The question was more if you want to submit the patch or if I should.

If I am to do it, do you have a name and email that I can use as reporter?

[got3nks]

You can submit the patch yourself of course. I have never done it before.

If I am to do it, do you have a name and email that I can use as reporter?

I'd rather not give my sensible information on a public post.

[t-8ch]

Submitted as https://lore.kernel.org/lkml/20230327-gigabyte-wmi-b650-elite-ax-v1-1-d4d645c21d0b@weissschuh.net/ and already picked up.