aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'README.md')
-rw-r--r--README.md21
1 files changed, 0 insertions, 21 deletions
diff --git a/README.md b/README.md
index 3f16465..22d4bde 100644
--- a/README.md
+++ b/README.md
@@ -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).