diff options
| author | historia <historiavg@proton.me> | 2026-09-06 14:09:42 -0400 |
|---|---|---|
| committer | historia <historiavg@proton.me> | 2026-09-06 14:09:42 -0400 |
| commit | f2acc8db6b7eb1f93303a00dd2b1899067b81956 (patch) | |
| tree | 5888c00803ab0a0c66a8a8d386708f70d8c9f14a | |
| parent | 7b1f08ef608adc0650bf90565304580318a2cd01 (diff) | |
| download | vrising-camera-main.tar.gz | |
| -rw-r--r-- | README.md | 21 |
1 files changed, 0 insertions, 21 deletions
@@ -27,24 +27,3 @@ Log out/in, then run the script. | `-v`, `--verbose` | log key presses/releases, RMB injection, measured motion rate | | `--test-rmb [SECONDS]` | self-test: hold the injected RMB for `SECONDS` (default 3) and read events back from the kernel; no keyboard needed | | `--check` | show detected keyboards, uinput and grab status, then exit | - - -## Setup on Arch (KDE Wayland / X11 alike) - -1. Your user needs to read the keyboard event devices and, on Arch, that same - group membership also grants write access to `/dev/uinput`: - - ``` - sudo usermod -aG input $USER # log out and back in afterwards - ``` - (Arch autoloads the `uinput` module on first open; no udev rules needed.) -2. The script auto-creates `.venv` and installs `evdev` on first run — no - extra steps. -3. Run `./vrising-cam.py --check` — it should print `READY`: - `/dev/uinput` openable, your keyboards listed exposing Q+E, and no - "exclusively grabbed" warnings. - -Troubleshooting when something does fail — the script prints a targeted hint: -`/dev/uinput` unwritable (rare on Arch; sudo or a udev rule fixes it), module -missing (`modprobe uinput` then add it to `/etc/modules-load.d/`), or -keyboards unreadable (the `input` group again). |