OpenRiot v7.9.56 — Two Hands on the Wheel
“The kernel was adjusting the volume. i3 was adjusting the volume. Neither knew the other existed. Every key press was two adjustments fighting over the same mixer. You pressed up for 5% and got 8%. The machine wasn’t broken — it was over-eager. Two hands on the same wheel, both turning. The Turing Police would call it ‘redundant input handling.’ We call it the kernel not knowing when to let go.” — The OpenRiot Crew, v7.9.56
Release Overview
One fix. The volume keys now step by exactly 5% instead of the
erratic 8-10% double-step that’s been happening since the dawn of
the construct. The kernel was intercepting multimedia keys and
adjusting the mixer directly, while i3 was also running
openriot --volume inc. Two controllers, one fader. The installer
now tells the kernel to stand down.
Total changes: 1 fix, 6 lines.
🔊 Volume Keys: The Kernel Steps Aside
kern.audio.kbdcontrol is an OpenBSD kernel setting that, when
enabled, intercepts XF86AudioRaiseVolume and XF86AudioLowerVolume
keys and adjusts the mixer directly. The kernel doesn’t know about
i3. i3 doesn’t know about the kernel. They both grab the key and
both adjust the volume. The result is a double-step — 5% from the
kernel plus 5% from openriot, landing somewhere between 8% and
10% depending on rounding.
The fix is simple: the installer now sets
kern.audio.kbdcontrol=0 in /etc/sysctl.conf and applies it
immediately. The kernel stops handling audio keys. i3 and
openriot become the sole authority. One hand on the wheel instead
of two.
Users who already installed OpenRiot can run:
doas sysctl kern.audio.kbdcontrol=0
And add the same line to /etc/sysctl.conf for persistence.
🧾 Files Changed
| File | Change |
|---|---|
install/packages.yaml |
system.services now disables |
kern.audio.kbdcontrol during |
|
| install — prevents kernel from | |
| double-firing volume key events. |
🗣️ Final Words
“It was never a bug. It was two systems doing exactly what they were told to do, and nobody told them about each other. The kernel handled the volume key because that’s what kernels do. i3 handled the volume key because that’s what window managers do. The result was 8% when you asked for 5. The construct doesn’t tolerate redundant authority. One system, one voice, one step. The Feds, as always, would have added a third handler and called it a feature.” — The OpenRiot Crew, v7.9.56