vboard now uses uinput as its only input backend. This document covers common device and permission issues.
If vboard.py fails with:
OSError: [Errno 19] Failed to open the uinput device: No such device
it usually means the Linux uinput kernel module is not loaded, or the current user cannot access /dev/uinput.
- Check whether the module is loaded:
lsmod | grep uinput- Load it if needed:
sudo modprobe uinput- Check that the device exists and inspect its permissions:
ls -l /dev/uinput- For system installs of vboard, the package now installs
/etc/udev/rules.d/70-vboard-uinput.rulesautomatically. If permissions are still restrictive, reload the rule or log out/in:
sudo udevadm control --reload-rules
sudo udevadm trigger --subsystem-match=misc --sysname-match=uinput- If your distro does not grant access through
uaccess, add your user to theinputgroup and log out/in:
sudo usermod -a -G input $USER
newgrp input- To load
uinputautomatically at boot:
echo 'uinput' | sudo tee /etc/modules-load.d/uinput.conf- On some systems, installing the relevant package may also be required, such as
python3-uinput. - If the device still cannot be opened after loading the module, verify that your distro exposes
/dev/uinputand that no udev rule is blocking access.