Using VIA on Linux With udev Rules

KM16 Macropad is a VIA-compatible aluminium pad with sixteen keycaps and three knobs. On Linux, ordinary typing and VIA configuration use different access paths, so a pad can type normally while the configurator still cannot open it.

Why can VIA need a udev rule?

The Linux guidance for VIA-compatible configurators explains that the application communicates through a raw HID interface. Normal user sessions may not have permission to open the relevant hidraw node. A udev rule can grant appropriate access when the matching device appears.

This rule is for configuration access, not a magical keyboard driver. Once a stored mapping works, ordinary key events generally travel through the normal Linux input path. If the pad types but VIA cannot connect, permissions, browser support and compatible firmware are separate things to check.

How do you identify the correct device?

Run the distribution's USB listing tool, note the result, connect the pad and compare the list again. Record the vendor and product identifiers belonging to the new entry. You can also inspect udev information for the associated hidraw device. Avoid copying identifiers from a guide because its example hardware is not your pad.

Repeat the connect-and-disconnect test before writing a rule. A narrow match reduces the chance of changing permissions for every keyboard, security token or HID accessory on the machine.

Should you use a general or device-specific rule?

Official community guidance describes both broad hidraw access and rules limited to particular devices. Prefer the device-specific form when the identifiers are known. Broad rules are convenient for testing many boards, but they grant access to more interfaces than one configurator needs.

Create the rule with administrative access only after reading the documentation for your distribution and VIA-compatible firmware. Then reload the udev rules or reconnect the device as your system instructs. Do not weaken permissions on all device nodes manually, since those changes are hard to audit and may vanish after reconnecting.

What if VIA still cannot see the pad?

Check each layer separately: data-capable USB connection, device enumeration, hidraw node, rule match, user-session permission, browser or desktop-app support and firmware compatibility. Close stale configurator tabs and authorize only the intended device. A successful USB listing does not prove that VIA support is active.

The KM16 Macropad has confirmed VIA remapping, but Linux policy still varies by distribution and managed-computer rules. Keep the final rule in a documented configuration backup, include only verified identifiers and remove abandoned test rules when setup is complete. Record the rule filename and the command used to inspect the match so another Linux upgrade can be diagnosed methodically.