I have a question related to this nice project : where did you get your ectool binary from ?
I’m running the latest Linux Mint and the one i got only spits errors. I got it working at some point a long time ago but i guess that trying different projects about fan control got it messed up.
I’ll take any reliable source. I can compile.
thanks !
This project doesn’t use ectool. Instead, it uses OP’s own CrOS_EC_Python library to communicate with the EC. YAFI works on linux, but you need to follow the installation instructions for linux.
I like this implementation because I don’t have to install one of the buggy beta BIOS’s for FW16 that support the EC driver, or unsigned drivers. PawnIO can take the role of the signed driver on Windows.
Sorry for the noise then, i get it.
I used the the portable executable for Linux, moved the udev rule to the right place and i got this error :
OSError: Could not auto detect device, check you have the required permissions, or specify manually.
I noticed i don’t even have the cros_ec_lpc module loaded, so that might explain it 
I tried under W11 with and without PawnIO and also got an error.
No worries. May I ask what hardware you’re using? There seem to be compatibility issues with this tool on some intel systems. Also, on Windows 11, note that you need to run the application as admin if you’re using PawnIO. Would you mind sharing the error message you got when running on Win11?
I’ve released v0.5 fixing some of the bugs in this post: Release v0.5 - Bug fixes and extra debugging info · Steve-Tech/YAFI · GitHub
Also I’d like to ask people to respond to this poll if YAFI is working for you: What laptop are you using YAFI on? · Steve-Tech/YAFI · Discussion #7 · GitHub or create an issue if it doesn’t.
I just filed one bug report and posted a comment under one other because i had the same error on Win 11.
To Linux users :
I just got bitten by past me, so If Yafi complains about
“Could not auto detect device, check you have the required permissions, or specify manually"
on your Framework, check if the needed modules are loaded with
lsmod | grep cros
if that returns nothing, try
modprobe cros_ec
modprobe cros_ec_lpcs
If that is working, check /etc/modprobe.d folder for a .conf file that would blacklist cros_ec and/or blacklist cros_ec_lpcs
I’m thinking of doing something like this, if anyone’s got any feedback!
Nice! I was today years old when I learned that Framework had an embedded controller that allows you to program it how you like it.
Just wanna clarify since ‘program’ is a little ambiguous here; YAFI just configures the EC, it does not modify its firmware.
I don’t have my Framework 16 yet (preordered), and I didn’t see anyone reporting on how this behaves for AMD laptops. Will I be the first to try it when, months from now, I finally get to try it? 
At present, the 16s only use AMD chipset. So folks using it for their 16 are using it with AMD. I haven’t tried it yet personally as I am waiting on my 370 series mainboard and then I may come back to visit.
Round off both the inside and outside corners of the gear to match the roundedness of the rest of the design. Or square off the rest of the design.
Thanks, rounding off the outside corners makes it look way better!
I probably just suck at inkscape, but I can’t round off the inside corners in a way that I like.
I’ve also been making a splash screen for the standalone builds, since they can take a few seconds to start:
Looks great!
I’ve released 0.6, which adds the logo and some other things: Release v0.6 - New Logo! · Steve-Tech/YAFI · GitHub
YAFI is also on Flathub now: Install Yet Another Framework Interface on Linux | Flathub
I tried running the Flatpak version and got an error implying my computer is not a Framework PC. Should I also just post the error log?
Do you have the udev rules mentioned in the readme? GitHub - Steve-Tech/YAFI: Yet Another Framework Interface
Otherwise is cros_ec_dev loaded in lsmod?
I do need to make the udev rules requirement clearer for the flatpak, sorry!
Also the error log, and the debug info in about > troubleshooting would be handy.
I use the charge limiter to 80% and i disable the battery extender, but these settings do not survive a reboot. Is that the expected behaviour ?
Yeah it is, but I’m hoping to fix that with a damonised version.
