# GitHub - Steve-Tech/YAFI: Yet Another Framework Interface

**URL:** <https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012>\
**Category:** Creators & Developers\
**Tags:** project\
**Created:** [September 8, 2025, 4:14am UTC](https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012 "2025-09-08T04:14:06Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![batinste](https://avatars.discourse-cdn.com/v4/letter/b/edb3f5/32.png) [@batinste](https://community.frame.work/u/batinste)\
**Post date:** [September 14, 2025, 1:05pm UTC](https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012/21 "2025-09-14T13:05:21Z")

</div>

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 !

---

<div class="post-metadata">

**Author:** ![Jacob\_Padgett](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/jacob_padgett/32/1553_2.png) [@Jacob\_Padgett](https://community.frame.work/u/Jacob_Padgett)\
**Post date:** [September 14, 2025, 7:38pm UTC](https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012/22 "2025-09-14T19:38:38Z")

</div>

This project doesn’t use ectool. Instead, it uses OP’s own [CrOS\_EC\_Python](https://github.com/Steve-Tech/CrOS_EC_Python) library to communicate with the EC. YAFI works on linux, but you need to follow the [installation instructions for linux](https://github.com/Steve-Tech/YAFI?tab=readme-ov-file#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.

---

<div class="post-metadata">

**Author:** ![batinste](https://avatars.discourse-cdn.com/v4/letter/b/edb3f5/32.png) [@batinste](https://community.frame.work/u/batinste)\
**Post date:** [September 15, 2025, 2:37pm UTC](https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012/23 "2025-09-15T14:37:32Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Jacob\_Padgett](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/jacob_padgett/32/1553_2.png) [@Jacob\_Padgett](https://community.frame.work/u/Jacob_Padgett)\
**Post date:** [September 15, 2025, 7:40pm UTC](https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012/24 "2025-09-15T19:40:56Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![Steve-Tech](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/steve-tech/32/19871_2.png) [@Steve-Tech](https://community.frame.work/u/Steve-Tech)\
**Post date:** [September 16, 2025, 1:59am UTC](https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012/25 "2025-09-16T01:59:14Z")

</div>

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](https://github.com/Steve-Tech/YAFI/releases/tag/0.5)

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](https://github.com/Steve-Tech/YAFI/discussions/7) or create an issue if it doesn’t.

---

<div class="post-metadata">

**Author:** ![batinste](https://avatars.discourse-cdn.com/v4/letter/b/edb3f5/32.png) [@batinste](https://community.frame.work/u/batinste)\
**Post date:** [September 16, 2025, 7:39am UTC](https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012/26 "2025-09-16T07:39:13Z")

</div>

I just filed one bug report and posted a comment under one other because i had the same error on Win 11.

---

<div class="post-metadata">

**Author:** ![batinste](https://avatars.discourse-cdn.com/v4/letter/b/edb3f5/32.png) [@batinste](https://community.frame.work/u/batinste)\
**Post date:** [September 16, 2025, 9:31am UTC](https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012/27 "2025-09-16T09:31:58Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Steve-Tech](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/steve-tech/32/19871_2.png) [@Steve-Tech](https://community.frame.work/u/Steve-Tech)\
**Post date:** [September 16, 2025, 12:33pm UTC](https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012/28 "2025-09-16T12:33:23Z")

</div>

I’m thinking of doing something like this, if anyone’s got any feedback!

![Draft YAFI Logo](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/3X/d/9/d9a9132855b31792458d3aaffbf25f0e2ee0467e.svg)

---

<div class="post-metadata">

**Author:** ![tansiret](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/tansiret/32/42020_2.png) [@tansiret](https://community.frame.work/u/tansiret)\
**Post date:** [September 16, 2025, 9:06pm UTC](https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012/29 "2025-09-16T21:06:05Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Steve-Tech](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/steve-tech/32/19871_2.png) [@Steve-Tech](https://community.frame.work/u/Steve-Tech)\
**Post date:** [September 16, 2025, 11:08pm UTC](https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012/30 "2025-09-16T23:08:09Z")

</div>

Just wanna clarify since ‘program’ is a little ambiguous here; YAFI just configures the EC, it does not modify its firmware.

---

<div class="post-metadata">

**Author:** ![sounds](https://avatars.discourse-cdn.com/v4/letter/s/bc79bd/32.png) [@sounds](https://community.frame.work/u/sounds)\
**Post date:** [September 17, 2025, 3:25pm UTC](https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012/31 "2025-09-17T15:25:40Z")

</div>

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? 😁

---

<div class="post-metadata">

**Author:** ![OVER\_CL0CK](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/over_cl0ck/32/38829_2.png) [@OVER\_CL0CK](https://community.frame.work/u/OVER_CL0CK)\
**Post date:** [September 17, 2025, 5:08pm UTC](https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012/32 "2025-09-17T17:08:32Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![XenoCow](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/xenocow/32/318_2.png) [@XenoCow](https://community.frame.work/u/XenoCow)\
**Post date:** [September 18, 2025, 6:29am UTC](https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012/33 "2025-09-18T06:29:08Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Steve-Tech](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/steve-tech/32/19871_2.png) [@Steve-Tech](https://community.frame.work/u/Steve-Tech)\
**Post date:** [September 19, 2025, 2:36am UTC](https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012/34 "2025-09-19T02:36:34Z")

</div>

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.

![New YAFI Logo](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/3X/e/0/e0d8d9a038265007a543c433a7bbd72c088dae15.svg)

I’ve also been making a splash screen for the standalone builds, since they can take a few seconds to start:

 ![New YAFI Splash](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/3X/6/7/671b656859eba29d1fd7dbf0f80cf00ccece7ccc.png)

---

<div class="post-metadata">

**Author:** ![XenoCow](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/xenocow/32/318_2.png) [@XenoCow](https://community.frame.work/u/XenoCow)\
**Post date:** [September 19, 2025, 5:13pm UTC](https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012/35 "2025-09-19T17:13:23Z")

</div>

Looks great!

---

<div class="post-metadata">

**Author:** ![Steve-Tech](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/steve-tech/32/19871_2.png) [@Steve-Tech](https://community.frame.work/u/Steve-Tech)\
**Post date:** [September 29, 2025, 7:02am UTC](https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012/36 "2025-09-29T07:02:17Z")

</div>

I’ve released 0.6, which adds the logo and some other things: [Release v0.6 - New Logo! · Steve-Tech/YAFI · GitHub](https://github.com/Steve-Tech/YAFI/releases/tag/0.6)

YAFI is also on Flathub now: [Install Yet Another Framework Interface on Linux | Flathub](https://flathub.org/en/apps/au.stevetech.yafi)

---

<div class="post-metadata">

**Author:** ![MrTrismegistus](https://avatars.discourse-cdn.com/v4/letter/m/958977/32.png) [@MrTrismegistus](https://community.frame.work/u/MrTrismegistus)\
**Post date:** [October 3, 2025, 8:39pm UTC](https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012/37 "2025-10-03T20:39:21Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![Steve-Tech](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/steve-tech/32/19871_2.png) [@Steve-Tech](https://community.frame.work/u/Steve-Tech)\
**Post date:** [October 3, 2025, 9:00pm UTC](https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012/38 "2025-10-03T21:00:21Z")

</div>

Do you have the udev rules mentioned in the readme? [GitHub - Steve-Tech/YAFI: Yet Another Framework Interface](https://github.com/Steve-Tech/YAFI?tab=readme-ov-file#linux)

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.

---

<div class="post-metadata">

**Author:** ![batinste](https://avatars.discourse-cdn.com/v4/letter/b/edb3f5/32.png) [@batinste](https://community.frame.work/u/batinste)\
**Post date:** [October 6, 2025, 7:08am UTC](https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012/39 "2025-10-06T07:08:39Z")

</div>

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 ?

---

<div class="post-metadata">

**Author:** ![Steve-Tech](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/steve-tech/32/19871_2.png) [@Steve-Tech](https://community.frame.work/u/Steve-Tech)\
**Post date:** [October 6, 2025, 7:22am UTC](https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012/40 "2025-10-06T07:22:00Z")

</div>

Yeah it is, but I’m hoping to fix that with a damonised version.

> [@Steve-Tech](#):
>
> - Settings often get reset by the BIOS initialisation so they don’t stay after a reboot.

[Previous page](https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012.md?page=1)

[Next page](https://community.frame.work/t/github-steve-tech-yafi-yet-another-framework-interface/75012.md?page=3)
