Only use this on Linux if your machine is listed in the compatibility table in the main readme or if you know what you're doing.
Because on Linux, this tool writes directly to hardware addresses where data persists after rebooting. If something goes wrong, you might need to do something like this.
As for how to figure out whether the addresses are the same on your machine – not that simple, I might do a talk or write an article at some point. Let me know if you actually need this.
- Node.js (Needs to be available to root - see e.g. https://github.com/nodesource/distributions#installation-instructions )
- Installing the kernel module acpi_call and running it on startup. (Enables issuing of fan control commands.)
Linux pros - feel free to contribute either to the following guide or automating the workflow! 🙂 (See notes in the Wishlist section though.)
If you've never installed a kernel module, one way is like the following (If you have secure boot
enabled, you need to do this first.
Plus, make might complain if you're missing compilers but it worked out of the box on Mint for me.):
sudo make dkms-add
sudo make dkms-build
sudo make dkms-install
sudo modprobe acpi_call
If your distro uses systemd, you can use this really simple method. Installing makes acpi_call available to be loaded just like described there.
If it doesn't, I'm afraid you'll have to do research yourself.
- Grab the latest release, extract it to wherever you want alfc to live and run
install.sh
A service for alfc will be created and started.
- Somehow including
acpi_callin the installation process. But there are two problems:- People who have secure boot enabled need that whole separate step of signing the module.
- How the module can be loaded on startup might vary from distro to distro.