this post was submitted on 21 May 2025

23 points (96.0% liked)

Linux

54492 readers

1303 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago

MODERATORS

[email protected]

[Solved] How to get fan sensors working? (reddthat.com)

submitted 1 week ago* (last edited 1 week ago) by [email protected] to c/[email protected]

10 comments fedilink hide all child comments

I recently wiped Windows in favor of CachyOS, and it's been lovely! However, I have one outstanding issue that I can't seem to figure out.

To start, I have a Gigabyte B550I Aorus Pro AX motherboard. I followed the guide on the Arch Wiki for my particular chipset.

I still can't seem to control my cooling fans.

I have lm_sensors installed
I installed CoolerControl
I used modprobe it87 force_id=0x8628
I tried adding the .conf files to /etc/modprobe.d/ and /etc/modules-load.d/
When the steps above didn't work, I installed the it87-dkms-git package

No matter what I've tried, the only time the fan sensors get detected is when I also specify acpi_enforce_resources=lax in GRUB. From what I barely understand, that's not an option you want to leave on permanently, but perhaps y'all know better or have other ideas.

If it helps:

Motherboard: Gigabyte B550I Aorus Pro AX
Latest CachyOS kernel
Boot: GRUB

Edit: I have a semi-solution.

sudo modprobe it87 force_id=0x8688 ignore_resource_conflict=1

...allows the module to load without completely changing the acpi policy. I still don't know how to make it cleanly permanent or automated, but this is significant progress.

Also note that it should have been 0x8688 in my case, as revealed by sensors-detect.

Edit 2: Added

/etc/modules-load.d/it87.conf
it87

And

/etc/modprobe.d/it87.conf
options it87 force_id=0x8688 ignore_resource_conflict=1

And everything loads automatically! Thanks everyone!

all 11 comments

sorted by: hot top controversial new old

[–] [email protected] 6 points 1 week ago (1 children)

Have you done "sudo sensors-detect"?

[–] [email protected] 3 points 1 week ago (1 children)

I did, but before I installed the modules. Do I need to also do it after?

[–] [email protected] 3 points 1 week ago (1 children)

yes.

[–] [email protected] 1 points 1 week ago (1 children)

Unfortunately, this didn't fix it, either before or after. sensors-detect can see the ITE chipset, but it says

Trying family 'ITE'...
Found unknown chip with ID 0x8688

After which it doesn't find any modules to load for it, despite having a DKMS module installed that includes that chip.

(Also, I realize that I was using the incorrect ID before, but it seemed to work anyway.)

[–] [email protected] 3 points 1 week ago* (last edited 1 week ago) (1 children)

is this your issue? https://github.com/lm-sensors/lm-sensors/issues/154

make sure the version you are using includes it too.

[–] [email protected] 2 points 1 week ago

Thanks, sounds very similar to what's going on with those users. I'll look into that thread a little more

[–] [email protected] 3 points 1 week ago (2 children)

You can try ignore_resource_conflict which is it87 specific, rather than a system wide acpi_enforce_resources.

modprobe it87 force_id=0x8628 ignore_resource_conflict=1

The reason why this is needed is ACPI claims the I/O ports required to talk to the it87, and Linux doesn't want to override that.

[–] [email protected] 3 points 1 week ago (1 children)

It worked, and I appreciate the explanation. I also realized I was using the wrong ID (which still worked, somehow); it should have been 0x8688.

I guess I can now figure out the best way to get that to run at startup or on login! Thanks again.

[–] [email protected] 2 points 1 week ago (1 children)

Epic!

You should be able to add options it87 force_id=0x8688 ignore_resource_conflict=1 to /etc/modprobe.d/it87.conf (or whatever filename) and it87 to /etc/modules. To get it to run at startup.

[–] [email protected] 2 points 1 week ago

Tried it, and it works! Loads at startup, and I don't have to reload the CoolerControl daemon or do any other manual intervention.

Thanks!