-
Notifications
You must be signed in to change notification settings - Fork 77
Open
Description
The util/ectool
utility seems to be the only way to read the fan speed on some Framework models:
Fan speed - where is it reported to the OS? - Framework Laptop 13 / Linux - Framework Community)
It would be great if Framework supported the ectool as a package in Debian / Ubuntu, so we didn't have to compile it ourselves.
Since this repo is so large, I ended up using the extract of ectool at https://gitlab.howett.net/DHowett/ectool.git and figuring out how to build it with cmake, despite that being a bit nonstandard according to ChatGPT since it doesn't rely on a build directory.
cmake .
make
src/ectool help
Activity
JohnAZoidberg commentedon Jun 7, 2025
That is not true anymore.
Since Framework 13 Intel Core Ultra we report it through ACPI:
And on all systems it is reported through the cros_ec_hwmon driver:
Yes, ectool is not easy to build in this repository, you need the whole ChromeOS chroot: https://chromium.googlesource.com/chromiumos/platform/ec/+/HEAD/docs/getting_started_quickly.md
We have our own tool now as well: https://github.com/FrameworkComputer/framework-system
AhmedYasserrr commentedon Jun 9, 2025
Hi, I saw the discussion about ectool and wanted to ask — is the ectool code still considered valid and maintainable or in a state where it could be maintained to support all current and future Framework devices?
I’ve noticed tools like fw-fanctrl are built on top of ectool (though they rely on spawning the CLI, which adds overhead). I was planning to contribute by building pyectool: Python bindings for ectool that provide programmatic access. I’m about halfway through and close to a first release.
If ectool is still a viable path, I’d be very interested in contributing toward its maintenance and modernization—especially to ensure reliable support for current and future Framework devices.