Building a Diskless Kiosk with Alpine: Keyboard and Mouse not working in Xorg

Keyboard and mouse not working in Xorg on an Alpine Linux diskless kiosk usually stems from missing input drivers or incorrect HAL/udev configuration. Alpine uses OpenRC instead of systemd, which changes how devices are detected. Ensuring the correct kernel modules are loaded and that the Xorg server can locate the input devices via udev rules is the primary fix for this hardware detection failure.

Verifying Kernel Module Loading

The most common cause for input device failure in a minimal environment like Alpine Linux is that the necessary kernel modules for USB HID (Human Interface Device) support are not loaded automatically. Unlike full desktop distributions, Alpine does not include every driver by default to keep the image small. You must ensure that the hid_generic, usbhid, and potentially specific driver modules for your keyboard or mouse controller are present and active. Start by checking the current loaded modules with the lsmod command. Look for entries related to usbhid or hid_*. If these are missing, you need to load them manually using modprobe. For example, running modprobe usbhid should make the system aware of basic USB input devices. To make this persistent across reboots, add these module names to the /etc/modules file or configure them within your OpenRC startup scripts. This step ensures the kernel itself can communicate with the physical peripherals before Xorg even starts.

Configuring udev Rules for Input Devices

Alpine Linux relies heavily on udev for dynamic device management. In a diskless setup, where the root filesystem might be mounted over NFS or stored in RAM, udev rules might not find the correct permissions or symlinks for input devices. Xorg depends on these udev properties to identify which nodes correspond to keyboards and mice. Check the output of udevadm info --query=all --name=/dev/input/eventX replacing eventX with your actual event number. Verify that the key-value pairs for EVDEV and INPUT_CLASS are present. If they are missing, you may need to create custom udev rules in /etc/udev/rules.d/. A simple rule can force the creation of symlinks or set appropriate permissions for input groups. Ensure the input group exists and that your user running Xorg is a member of it. Without proper udev attribution, Xorg will ignore the input events entirely, leading to a frozen cursor.

Checking Xorg Configuration Files

Once the kernel and udev layers are functioning, the issue often lies within the Xorg configuration itself. Alpine users frequently rely on xorg.conf files generated by xorgconf or manual edits in /etc/X11/xorg.conf.d/. In many cases, especially with modern hardware, a full xorg.conf is unnecessary and can actually hinder auto-detection. If you have a custom xorg.conf, try renaming it temporarily to see if Xorg falls back to automatic detection. If you need a configuration file, create a snippet in /etc/X11/xorg.conf.d/40-input.conf that explicitly defines the input drivers. Use the evdev driver rather than older mouse or kbd drivers, as evdev is more robust for modern USB devices. Ensure the Option "CoreKeyboard" and Option "CorePointer" directives are correctly assigned to the respective sections. This forces Xorg to treat the specified devices as the primary input sources.

Debugging with Xorg Logs

When graphical interfaces fail silently, the Xorg log file is your best diagnostic tool. By default, Xorg logs to /var/log/Xorg.0.log on Alpine systems. Start Xorg with verbose logging enabled by adding -verbose 3 to the start command or setting LogVerbose in the config. Search the log for lines containing EE (Error) or WW (Warning) specifically related to Input or evdev. Look for messages indicating that no input driver matches the detected device. If you see errors about cannot open device, check the permissions again. If you see no devices detected, revisit the udev and kernel module steps. Often, the log will reveal that the server is waiting for a specific protocol that your hardware does not support, guiding you toward the correct driver selection.

Ensuring Proper Session Initialization

In a diskless kiosk, the session manager plays a crucial role in initializing the display server. If you are using a lightweight window manager or a dedicated kiosk launcher, ensure it starts after the input subsystem is fully ready. Sometimes, starting Xorg too early in the boot process, before udev has finished scanning all USB buses, results in missed devices. Add a delay or a dependency check in your OpenRC service script for the Xorg or display manager. You can use udevadm settle in your startup script to wait until all device additions are complete before launching the X server. This simple synchronization step resolves many race conditions in embedded or headless environments where hardware enumeration timing is critical.

Frequently Asked Questions

How do I check if my USB keyboard is recognized by the kernel?

Run dmesg | grep -i hid to see kernel messages regarding Human Interface Devices. If your keyboard appears in the output with a registered input event, the kernel layer is working correctly.

Why does Xorg work with a wired mouse but not a wireless one?

Wireless mice often require additional firmware or specific hid-generic handling that might not be loaded by default. Ensure the usbhid module is loaded and consider adding a slight delay in your startup script to allow the dongle to pair before Xorg initializes.

Can I use a single xorg.conf for both keyboard and mouse?

Yes, you can define multiple InputDevice sections in a single xorg.conf file. However, it is generally recommended to use separate snippets in /etc/X11/xorg.conf.d/ for better modularity and easier debugging on Alpine systems.

What should I do if Xorg reports 'No screens found'?

This error indicates a graphics driver issue rather than an input problem. Check that your GPU kernel module is loaded and that you have the correct proprietary or open-source drivers installed for your specific hardware model.

Does Alpine Linux use systemd-logind for Xorg sessions?

No, Alpine Linux uses OpenRC. Therefore, you do not need systemd-logind integration. Instead, rely on standard Unix permissions and udev rules to manage session ownership and device access for the X server.