Ideally it would work out of the box, if the “framework_tool” is working. The app installs framework_tool automatically via wget or if that’s not possible it tries downloading straght from the gh releases. So it will definitely install the tool.
The question is, will the framework_tool work?
If it’s not able to communicate with the EC. It will likely give an error similar to this. It’s what I got when I tried using it before the beta BIOS 3.06
If that’s the case, it’ll be pretty difficult to implement a thing where you build the EC tool from the ground up. (Not sure if even possible) There’s one repo online that did it but it was unsigned so you would have to disable secure boot to use so I never went that route and instead decided to wait and create the above linked issue.
So the answer is:
- It will either simply work out of the box
- Or it will be extremely difficult, thus you will have to wait…
1 Like
On the other hand, the TDP and Thermal Limit stuff I’m planning to add is a whole different path and uses a different tool → this guy. I still didn’t get the free time to play around with it 
.
That tool is also a kernel driver-level tool, so building something like that is no easy feat. You have to go through countless steps and pay for certifications and stuff unless you want to disable secure boot.
So we’re also at the mercy of the tool there because of the same reasons. If it works, it works. If not, well… As explained above.
2 Likes
Certainly appreciate you taking the time to provide all the information. I guess I will just try it when I get it and go from there! Here’s to hoping it works though. I really love what you made.
1 Like
We all appreciate your help, but it’s a shame that Framework hasn’t provided software to control the fans or the TDP. They should do it.
2 Likes
Hi I really like this project, but I’m afraid to make the move from BIOS v 3.05 to 3.06 beta. Is there anything I need to know about 3.06 before I make the switch?
1 Like
I’m on 3.07 alpha and thr app works fine.
1 Like
I’m still on 3.06 because I didn’t want to make the switch and it possibly not work. Glad to hear it works for 3.07. Maybe I’ll update 
Can confirm, updated to 3.07 alpha and is working just fine.
2 Likes
@Bogdan_Cook Welcome the the thread! I don’t think there’s much to be scared of in terms of switching but some users reported their cpu clock would get locked at 500mhz in some cases and would fix itself after a reboot.
I’ve been using 3.06 for a couple months now but seems like others have been enjoying 3.07, might be time for me to switch to 3.07 as well 
Any bios after 3.05 will have the EC driver included and this app will work with it.
Are there any deal breaking issues with v3.07?
Tested on Framework 12 btw: How to adjust fan ramping - #8 by okeeblow
Thanks for this. Nice to have manual control at the very least 
1 Like
Do you mind helping me out with a bunch of logs so we can get the fan curve working as well? Glad to hear that the manual control is working.
Since controlling the fans work, we might have an easy fix.
I built this project mainly for myself but other people also found it useful so I’m willing to try and help out when I can if it’s not working for some configs, in this case the FW12
1 Like
Honestly, just looking at your screenshots, I feel like you may be able to just make it work by changing the little target at the bottom to CPU and see what happens.
1 Like
I can’t speak for everyone, but I know I have mine set specifically for the CPU as I am running an external GPU. Would probably help others to set to CPU specifically even if they are using the 7700 or 5070 even though it is not “external” it is still a separate gpu compared to the 780 integrated in the chip and would use more reliable thermal readings. APU would be a better setting if they were running off the 780 for light cpu work and the gpu wasn’t being utilized. Just my theory/two cents anyway.
Oh yeah, that worked just perfectly. Thank you!
1 Like
It’s a bit weird at times. It really depends on how framework_tool reports its temp values. Ideally, it would be like you described, but that’s not always the case.
For me, I use the APU setting (why it’s the initial default) because that one is more accurate when I compare my actual temps to external apps like HWINFO. Even if I’m not technically using the “APU” and doing “CPU” heavy work. The one that’s reporting higher is probably the more accurate one.
But different systems have different values, so maybe I should code it in a way that it grabs all of them and takes the highest one… 
1 Like
Glad it worked, looks like your calibration is slightly off but I wont complain since I never tested this app on the FW12.
I guess we now support FW12 as well 
Still happy to provide any logs you would like if you let me know what/how. But yes I am not upset at all at very minor miscalibration 
I decided to make the switch to BIOS v3.07! I downloaded the app and so far so good! I’m new to creating manual fan curves so would you have any recommendations on how my curve should look like to begin with before I start fine tuning it to my own preferences?
Exponential Curve. Keep it below 40% up until 60C and than gradually to 100% at 100C. So you have it nearly silent during daily use and just ramp up when really neded. 4s hysteresis.
