Fan Speed control does not work with Gigabyte B650 Aorus Elite AX Rev 1.2 (but sensors do show)

[Florararie]

So, to outline what I did- I am on CachyOS which is based on Arch.

I git cloned this repo, and ran the dkms install script after using the sensors-detect command which gave me the unknown Chip ID of 0x8689. dmesg when loading the it87 module as well says Found IT8689E chip at 0xa40, revision 2 when not forcing an ID so I'm fairly certain I have the right ID / Chip.

I then ran the command sudo modprobe it87 ignore_resource_conflict=1 force_id=0x8689 after install. The sensors do appear to show. But I cannot control their speeds- at least through CoolerControl. I've yet to try other tools.

So while I can see the fans listed, and RPMs fluctuating- I cannot control them in any way. Which is what I was hoping to accomplish here

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'...                                      No

it8689-isa-0a40
Adapter: ISA adapter
in0:         936.00 mV (min =  +0.00 V, max =  +3.06 V)
in1:           1.99 V  (min =  +0.00 V, max =  +3.06 V)
in2:           2.03 V  (min =  +0.00 V, max =  +3.06 V)
in3:           2.03 V  (min =  +0.00 V, max =  +3.06 V)
in4:           1.28 V  (min =  +0.00 V, max =  +3.06 V)
in5:           1.15 V  (min =  +0.00 V, max =  +3.06 V)
in6:           1.99 V  (min =  +0.00 V, max =  +3.06 V)
3VSB:          3.34 V  (min =  +0.00 V, max =  +6.12 V)
Vbat:          3.22 V  
fan1:        1537 RPM  (min =    0 RPM)
fan2:         821 RPM  (min =    0 RPM)
fan3:           0 RPM  (min =    0 RPM)
fan4:           0 RPM  (min =    0 RPM)
fan5:        1679 RPM  (min =    0 RPM)
fan6:        2800 RPM  (min =    0 RPM)
temp1:        +30.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp2:        +37.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp3:        +45.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = AMD AMDSI
temp4:        +34.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp5:        +34.0°C  (low  =  +0.0°C, high = -125.0°C)  sensor = thermistor
temp6:        +35.0°C  (low  =  +0.0°C, high = -125.0°C)  sensor = thermistor
pwm1:              0%  (freq = 23437 Hz)  MANUAL CONTROL
pwm2:              0%  (freq = 23437 Hz)  MANUAL CONTROL
pwm3:            128%  (freq = 23437 Hz)
pwm4:            128%  (freq = 23437 Hz)
pwm5:              0%  (freq = 23437 Hz)  MANUAL CONTROL
pwm6:              0%  (freq = 23437 Hz)
intrusion0:  ALARM

If I've misunderstood something or done anything wrong- please correct me. I'd like to get this figured out asap.

[Koli0842]

Hey,

There are some chips that do not have control working correctly yet. It was the same on Windows some years back with librehardwaremonitor, and it's the same now with PawnIO, I posted some lead over at #11 but the maintainer didn't seem to have found time for it, I lack the experience to make it happen.

As for your modprobe, I don't think force_id should be necessary anymore, at least it wasn't in my case. On a lot of these boards you can have multiple chips, using that flag forces only one to be detected, I'm not sure you can force multiple ones. For me on X570 Aorus Pro, I have options it87 ignore_resource_conflict=1 in /etc/modprobe.d/it87.conf. Control works fine on my IT8688, doesn't work on my IT8792.

[Florararie]

Yeah I did happen to read that issue just after posting. It's unfortunate that no (public) progress has been made, but I also understand why. Lack of resources to work with, especially from Gigabyte's end make this.. hard.

I figured I'd try the modprobe with the force ID because as far as I know- this board has one chip. But I also tried without it and ended up with the same result. Pretty much the only other thing I could think of would be changing fan control modes and hoping by some chance it works that way instead. But in the end this isnt a huge issue. I can set up some fan curves in BIOS, even if it is rather tedious in comparison, as that was the main use case I required anyways (that and I prefer making custom sensors from an average for CPU temp, cant do that in BIOS afaik)

Thank you for the insight though. If nothing else can be done, then it is what it is haha

[Koli0842]

Yeah, sure thing, afterall I come back to comment on people's issues because I'm also invested in having a solution. My use case is mixed control source for case fans, especially bottom ones for the GPU which is also not possible from bios, and similar mixed control for extra temp sensor on the CPU heatsink, which is doable but I'd lose the fallback for core temps. I guess best we can do now is wait, or learn to do it ourselves

[TsunamiMommy]

This looks like a case of not having the out of tree driver installed. Your pwm settings don't make sense and with the out of tree driver you won't have to use force_id with it. So you need to clone this repo and install this driver and I bet things will probably work for you.

[Florararie]

@TsunamiMommy

This looks like a case of not having the out of tree driver installed. Your pwm settings don't make sense and with the out of tree driver you won't have to use force_id with it. So you need to clone this repo and install this driver and I bet things will probably work for you.

Was there another driver in the repo to install that I was unaware of? I've since wiped the install I was using and started fresh (on the same distro and [relatively] same environment though). Last time I cloned the repo and just ran the dkms-install.sh script, which seemed to work fine for installing the driver.

I didnt actually need to use force_id previously anyways, I just tried both with, and without to see if it made any difference. Running it without also loaded 0x8689. Which ended in the same result as previously shown with sensors showing, but unable to be directly controlled.

Sorry if I'm misunderstanding anything, this is a relatively new avenue for me so I apologize if that's the case. If you have any further direction it would be appreciated 😅

[TsunamiMommy]

@Florararie I was just wanting to make sure that you were using the driver from this repo. force_id in your case, won't do anything at all. Something you can do is you can run my dumping utility and I can take a look at your offsets as that'll tell me if it87 is setting the fan control correctly or not. #64 let me know if you have any questions regarding using it or not.

[Florararie]

@TsunamiMommy just installed and loaded the module. Havent done anything else past that (no control utils like CoolerControl are installed at the moment that I am aware of).

Loaded it87 with sudo modprobe it87 ignore_resource_conflict=1

Output of sudo bash ./gp_ec_9xx_tool_detect.sh --method auto dump is as follows

=== Super-I/O detection ===
0x2E ID: 0x8689  (ITE IT8689E)
0x2E SMFI active (reg 0x30): 0x00
0x4E ID (no-enter): 0xFFFF  (none/0xFFFF)
0x4E SMFI active (reg 0x30): 0xFF
0x4E SMFI F5=0xFF F6=0xFF FC=0xFF
============================

Method: SMFI
SIO 0x4E ID (no-enter): 0xFFFF (none/0xFFFF)
SMFI active (reg 0x30): 0xFF
SMFI F5=0xFF F6=0xFF FC=0xFF -> host=0xFFFFF000
Bridge: 00:14.3 (vendor 1022)
setpci: Invalid value "10000ffff".
Try `setpci --help' for more information.
Restored AMD window on 00:14.3

That is. Slightly concerning. So I've possibly done something wrong on my end. Also tried using ec_gui_table_v7b_live.py since I wasnt sure if you needed that as well and it errors out. Possibly a fault of my current environment? Not sure. (CachyOS [Arch], Wayland, Hyprland - USWM)

╰─>$ sudo python ec_gui_table_v7b_live.py
Authorization required, but no authorization protocol specified

Authorization required, but no authorization protocol specified

Traceback (most recent call last):
  File "/home/samuel/Downloads/ec_gui_table_v7b_live.py", line 983, in <module>
    main()
    ~~~~^^
  File "/home/samuel/Downloads/ec_gui_table_v7b_live.py", line 975, in main
    app=HexTableGUI()
  File "/home/samuel/Downloads/ec_gui_table_v7b_live.py", line 395, in __init__
    super().__init__()
    ~~~~~~~~~~~~~~~~^^
  File "/usr/lib/python3.13/tkinter/__init__.py", line 2465, in __init__
    self.tk = _tkinter.create(screenName, baseName, className, interactive, wantobjects, useTk, sync, use)
              ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
_tkinter.TclError: couldn't connect to display ":0"

[Florararie]

Got the Python script running by using xhost and some env variables.

$ xhost +SI:localuser:root
$ sudo env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY WAYLAND_DISPLAY=$WAYLAND_DISPLAY python ec_gui_table_v7b_live.py

Not sure what to show here though

[TsunamiMommy]

@Florararie The gp utility will give you that error as you don't have a second superio. The graphical one you can click the export hex button and it'll create a file with the full dump. I can then take that file and decode it fully to see what's happening.

[Florararie]

mmio_slot0_base_FE000000.hex.txt

This, right?

[TsunamiMommy]

@Florararie Yes. That's correct.

[TsunamiMommy]

@Florararie Do you have any software attempting to control your motherboard fans atm? Like Cooler Control?

[Florararie]

Not currently that I'm aware of, no.

[TsunamiMommy]

KK. As I was seeing that the smartfan control bits were still on. That's why I was asking. Do you intended to use CoolerControl or something similar? As those utilities would need to be running and you have a curve defined for them for me to see if they're controlling your device correctly or not.

[Florararie]

I do intend to yeah. I'll install it again real quick and redump. Any reboots needed or is the current session alright?