Closed metamacro closed 2 years ago
I've seen a bunch of these issues come up over the years now. But every time I conclude that (1) implementing a clean workaround for this in thinkfan itself is non-trivial and (2) it's not really thinkfan's responsibility. A driver module isn't ready when it should be, so this is an issue of dependency management in the service manager. I'm currently depending on sysinit.target
and modules-load.service
, but apparently that's not enough. When looking through systemd.special (7), there really doesn't seem to be anything that would more explicitly indicate whether hardware monitoring is ready.
tl;dr: Been going back and forth on whether & how to fix this in thinkfan
Thank you for the detailed answer! In case I manage to find an answer I'll get back to you. Should I close the issue?
duplicate of #118 basically...
Thank you for the detailed answer! In case I manage to find an answer I'll get back to you. Should I close the issue?
I think we can just leave this open so people looking for a solution to this problem can find it easily.
fix is in development at https://github.com/vmatare/thinkfan/tree/init_retries and slated for the 2.0 release
Hi @andreiosg, this should be fixed in master now with a new config setting: https://github.com/vmatare/thinkfan/issues/189#issuecomment-1196011925
Hi, awesome, thanks for the heads up! ^^
thinkfan.service sometimes doesn't start on boot, however starting it manually always works. In other words, the file
/proc/acpi/ibm/thermal
sometimes causes problems on boot. Happens for boththinkfan
andthinkfan-git
from the AUR. System info: P14s AMD Gen 2 - Ryzen 7 PRO 5850U, Arch 5.13.12/etc/thinkfan.yaml
I've found a workaround. If it doesn't manage to get loaded on the first try it succeeds on the second, by adding the following lines to the
[Service]
section of the unit file/usr/lib/systemd/system/thinkfan.service
.A more elegant workaround was to add the following under the
[Service]
section:Adding
Wants/After
forproc-acpi-ibm-thermal
to the[Unit] section
didn't fix the issue.