The app can't recognize I'm on a framework laptop

[scerelli]

Hello, I'm on a framework 13, but the app seems to not be able to see that.

YAFI Debug Information

PermissionError: [Errno 13] Permission denied: '/dev/cros_ec'

Traceback (most recent call last):
  File "/app/share/yafi/yafi/main.py", line 77, in do_activate
    self.cros_ec = get_cros_ec()
                   ~~~~~~~~~~~^^
  File "/app/lib/python3.13/site-packages/cros_ec_python/cros_ec.py", line 74, in get_cros_ec
    return dev.CrosEcDev(**kwargs)
           ~~~~~~~~~~~~~^^^^^^^^^^
  File "/app/lib/python3.13/site-packages/cros_ec_python/devices/dev.py", line 56, in __init__
    fd = open("/dev/cros_ec", "wb", buffering=0)
PermissionError: [Errno 13] Permission denied: '/dev/cros_ec'


Python Version: 3.13.9 (main, Nov 10 2011, 15:00:00) [GCC 15.2.0]
GTK Version: 4.20.3
Adwaita Version: 1.8.2
Platform: Linux-6.17.8-300.fc43.x86_64-x86_64-with-glibc2.42
Processor: x86_64
Installed Packages: [('cros_ec_python', '0.3.0'), ('PyGObject', '3.54.5'), ('attrs', '25.4.0'), ('Jinja2', '3.1.6'), ('Mako', '1.3.10.dev0'), ('Markdown', '3.10'), ('MarkupSafe', '3.0.3'), ('packaging', '25.0'), ('pycairo', '1.29.0'), ('setuptools', '80.9.0')]
Manufacturer: Framework
Model: Laptop 13 (AMD Ryzen AI 300 Series)
SKU: FRANVCCP09
Board: FRANMGCP09
BIOS Vendor: INSYDE Corp.
BIOS Version: 03.05
BIOS Date: 10/30/2025

[Steve-Tech]

Have you installed the udev rules in the readme? curl -Lfs yafi.stevetech.au/udev.sh | sudo sh is the easiest way to do that.

Or if you did it more than 10 days ago, do it again as they were bugged previously.

[Filz0r]

Hello I also have this issue, I installed the application via flatpak, and ran the udev rule commands manually on the terminal and when I open the application the same exact error shows up telling me that I need to enable access to the EC or that I don't have a Framework computer.
I haven't tried a reboot yet since its the middle of the day, I'll update my comment at the end of the day to see if a reboot helps.

[Steve-Tech]

You can run sudo chmod 666 /dev/cros_ec as a work around.

However I would like to chase this issue down properly:

• What distro are you guys running?
• Did any errors get printed when you ran the udev.sh script?
• Are the rules being installed correctly (run cat /etc/udev/rules.d/60-yafi.rules)?

[Filz0r]

Running sudo chmod 666 /dev/cros_ecdid allow me to launch the program.

And here's the output of the cat command on the udev rule:

❯ cat /etc/udev/rules.d/60-yafi.rules              
KERNEL==cros_ec, TAG+=uaccess

I literally just ran these 2 commands on the terminal to create the rule as per the readme:

• echo KERNEL==\"cros_ec\", TAG+=\"uaccess\" | sudo tee /etc/udev/rules.d/60-yafi.rules just outputed the result of the tee as in KERNEL=="cros_ec", TAG+="uaccess"
• sudo udevadm control --reload-rules && sudo udevadm trigger. didn't even give me any output

Can't really say anything about the script since it was just 2 commands I didn't really ran it

[Steve-Tech]

Running sudo chmod 666 /dev/cros_ec did allow me to launch the program.

Ahh, perfect!

And here's the output of the cat command on the udev rule:

❯ cat /etc/udev/rules.d/60-yafi.rules              
KERNEL==cros_ec, TAG+=uaccess

Hmm, that's missing the quotes which should've been fixed in #16. When did you run the commands and what shell are you using?

I literally just ran these 2 commands on the terminal to create the rule as per the readme
Can't really say anything about the script since it was just 2 commands I didn't really ran it

Fair enough, sorry for assuming.

[Filz0r]

Ohh that makes sense then, since I copied the command from the readme to straight to the shell, my terminal probably removed the escape sequence from the quotes when I pasted it into the prompt, I don't really see an explanation other than this.

Hmm, that's missing the quotes which should've been fixed in #16. When did you run the commands and what shell are you using?

After checking that issue I immediately thought that it was ZSH acting weird, but after checking my command history I can see that the first time I ran the command it removed the escape before the quotes

❯ history        
13992  yay -Ss yafi
13993  flatpak install flathub au.stevetech.yafi
13994  echo KERNEL=="cros_ec", TAG+="uaccess" | sudo tee /etc/udev/rules.d/60-yafi.rules <- Pasted from the readme using CTRL+SHIFT+V on the kitty terminal
13995  sudo udevadm control --reload-rules && sudo udevadm trigger
13996  hyprctl clients
13997  flatpak run au.stevetech.yafi
13998  cat /boot/loader/entries/arch.conf
13999  uname -a
14000  sudo dmidecode -s bios-version
14001  cat /etc/udev/rules.d/60-yafi.rules
14002  sudo chmod 666 /dev/cros_ec
14003  sudo udevadm control --reload-rules && sudo udevadm trigger
14004  echo KERNEL==\"cros_ec\", TAG+="uaccess" | sudo tee /etc/udev/rules.d/60-yafi.rules <- manually edited the prompt to add the escape char
14005  cat /etc/udev/rules.d/60-yafi.rules <- quotes were already wrapping cros_ec in the file after that
14006  echo KERNEL==\"cros_ec\", TAG+=\"uaccess\" | sudo tee /etc/udev/rules.d/60-yafi.rules
14007  cat /etc/udev/rules.d/60-yafi.rules

It doesn't make much sense but I think its safe to assume that it was the pasting action that removed the \ from the command, since the readme as the correct commands.

I also tried to run the command with bash -c to see if the quotes were being consumed by the shell and unless you run it exactly like I'll paste bellow bash will always consume the quotes if they aren't escaped, and also wrapping the command in double quotes instead of single will make bash also consume all the quotes, with or without the \ before the quotes.
bash -c 'echo KERNEL==\"cros_ec\", TAG+=\"uaccess\" | sudo tee /etc/udev/rules.d/60-yafi.rules' <- This forces the command to be ran inside bash and doesn't consume any quotes and from what I was able to test it didn't remove the backslashes when I pasted it into my terminal

Since ZSH can have some differences when it comes to consuming quotes from Bash, and since some terminals like kitty sometimes sanitize buffers before pasting them I would recommend adding a warning in the readme about this case as well as adding the bash command with proper escape sequence as an alternative to the command you are currently providing, and maybe even forcing the setup script to run the commands using bash instead of the default shell of the user to avoid more issues.

Other than this, thank you for your work! I can finally tune the fan curve of my framework easily

[Steve-Tech]

Sorry I just installed zsh and Kitty, and I still can't replicate the backslashes being removed. Maybe there was some weird caching issue or you accidentally selected an older commit, and copied the command from that?

I did also consider, this works for me in dash, bash, and zsh: echo 'KERNEL=="cros_ec", TAG+="uaccess"' | sudo tee /etc/udev/rules.d/60-yafi.rules, so maybe I'll just use that instead, in case there is some issue with backslashes.