You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the --thermal flag, framework_tool reports appropriately three fan RPM values for the Framework Desktop, corresponding to the PWM inputs for APU fan, Sys1, and Sys2.
Issues are:
1. Fans aren't labelled, all three outputs just show up as 'Fan Speed'
2. If only the APU fan is plugged in, the RPM reading corresponds to the second readout, but if a fan is plugged into Sys1 then APU fan becomes first readout and the Sys1 fan becomes the second one. This behaviour is a potential source of confusion / error. I don't have a fan to put into Sys2 so I don't know what the behaviour will be if that slot is occupied.
3. The --autofanctrl flag resets all of the fans. There is no way to only reset a single fan.
I imagine these are novel issues as the average laptop user doesn't tend to have to worry about multiple fans, but I'd be grateful if they could be looked at.
Fans aren't labelled, all three outputs just show up as 'Fan Speed'
If only the APU fan is plugged in, the RPM reading corresponds to the second readout, but if a fan is plugged into Sys1 then APU fan becomes first readout and the Sys1 fan becomes the second one. This behaviour is a potential source of confusion / error. I don't have a fan to put into Sys2 so I don't know what the behaviour will be if that slot is occupied.
Okay thanks, that looks wrong, I'll check it out.
The --autofanctrl flag resets all of the fans. There is no way to only reset a single fan.
The host command supports that, I didn't implement that in the commandline for simplicity. Can add it.
I haven't had a chance to get back to this yet, but thinking about it now, I think that'll need to be fixed in the EC. No change needed here in software.
I haven't had a chance to get back to this yet, but thinking about it now, I think that'll need to be fixed in the EC. No change needed here in software.
I've been using my plugin that calls the existing framework tool, with minimal changes, for a few months now. My requested fixes are very much low priority 'nice-to-haves'.
If only the APU fan is plugged in, the RPM reading corresponds to the second readout, but if a fan is plugged into Sys1 then APU fan becomes first readout and the Sys1 fan becomes the second one. This behaviour is a potential source of confusion / error. I don't have a fan to put into Sys2 so I don't know what the behaviour will be if that slot is occupied.
I'm not sure I understand, APU fan is always the first one. Maybe try again with the decoded names.
Apologies, I've not had time to play with this in quite a while. I've closed the issue. For what it's worth the plugin has been working fine for some time now.
Activity
JohnAZoidberg commentedon Oct 29, 2025
Okay thanks, that looks wrong, I'll check it out.
The host command supports that, I didn't implement that in the commandline for simplicity. Can add it.
JohnAZoidberg commentedon Oct 29, 2025
fyi @amstan
JohnAZoidberg commentedon Oct 29, 2025
For 3: #229
JohnAZoidberg commentedon Jan 18, 2026
I haven't had a chance to get back to this yet, but thinking about it now, I think that'll need to be fixed in the EC. No change needed here in software.
WindySIn commentedon Jan 19, 2026
I've been using my plugin that calls the existing framework tool, with minimal changes, for a few months now. My requested fixes are very much low priority 'nice-to-haves'.
JohnAZoidberg commentedon Jan 19, 2026
Oh what is the plugin and what are your changes?
I'm curious
WindySIn commentedon Jan 19, 2026
Ah sorry, I meant I hadn't had to change the plugin I wrote that uses the framework tool to interact with fan control.
JohnAZoidberg commentedon May 31, 2026
I'm adding fan name decoding for the Desktop in #343
JohnAZoidberg commentedon May 31, 2026
I'm not sure I understand, APU fan is always the first one. Maybe try again with the decoded names.
JohnAZoidberg commentedon Sep 20, 2026
@WindySIn is there still an issue?
WindySIn commentedon Sep 27, 2026
Apologies, I've not had time to play with this in quite a while. I've closed the issue. For what it's worth the plugin has been working fine for some time now.