Most graphics tablets will work out of the box on Arch Linux, but to unlock full potential-such as button remapping, aspect ratio corrections, and persistent calibration-some additional configuration is often necessary. This article compiles practical guidance drawn from user experiences and common workflows for XP-Pen and similar non-Wacom tablets under Arch Linux, focusing on DIGImend, HID-BPF, and xorg/xinput tooling.
Drivers and core compatibility
The Linux kernels include drivers from the linux-wacom project for Wacom devices, while support for non-Wacom manufacturers historically rested with DIGImend. It is noted that newer non-Wacom tablets can be supported via HID-BPF (eBPF programs) loaded by the kernel, with the udev-hid-bpf package facilitating this on Arch Linux. There is no universal central device list for HID‑BPF; you can inspect available programs with udev-hid-bpf list-bpf-programs.
In Arch Linux, most graphics tablets function out of the box, but enabling extra features typically requires manual steps. For XP-Pen and UC-Logic tablets, you may rely on the digimend-kernel-drivers package (or its newer equivalents) and ensure the kernel module supports your device. If your tablet matches a model such as the UC-Logic TABLET 1060N, it may be labeled accordingly in the system’s device listings.
For users choosing software-based configuration, the xinput and xsetwacom tooling provide the means to adjust transformation matrices, button mappings, and other device-specific properties. If you are using Wayland, libinput governs devices and direct xsetwacom/xinput-based tweaks may not apply; in Wayland environments, OpenTabletDriver or DE-provided tablet settings are typically the path forward.
Initial setup and identification
After connecting the tablet via USB (or Bluetooth), it should appear in dmesg when run as root and in /proc/bus/input/devices. For USB devices, lsusb helps confirm presence. The product name may appear as UC-Logic TABLET 1060N or similar, with the vendor/product IDs matching those seen on the DIGImend site or in kernel driver logs. If you see multiple devices with the same name (for example three UC-Logic TABLET 1060N entries), you should rely on IDs rather than names when scripting configurations.
In practice, you can use xinput to list devices and find the stylus and pad IDs. Note that xinput may assign different IDs across plug-in events, so robust configurations parse IDs dynamically rather than hardcoding them. If you need to map a tablet drawing area to a specific monitor region, the Coordinate Transformation Matrix property can be adjusted via xinput set-prop or via startup scripts that run after each hot-plug.
Coordinate Transformation Matrix: mapping to screen space
The Coordinate Transformation Matrix is a primary lever to change how the tablet’s active area maps to screen coordinates. For example, a tested command may look like: xinput set-prop "device name" --type=float "Coordinate Transformation Matrix" 0.5 0 0 0 1 0 0 0 1, which confines the active area to the left half of the screen. This approach is useful to adjust aspect ratio or to prune the drawing area to match a display setup.
Important notes:
- The device name can be ambiguous if multiple devices share the same label. Use the device ID in scripts to disambiguate, or use the XInput device list to extract IDs dynamically.
- After hot-plug events or reboots, runtime changes via xinput will not persist unless they are applied in a static Xorg configuration file or via startup scripts that run after each login or boot.
- You can craft a script that enumerates devices, identifies the correct tablet input, and applies a tailored matrix. This approach scales across new devices, sidestepping hard-coded IDs.
When you apply an initial matrix, you may also need to tweak offsets to align the top/bottom edges with the screen, though some users find vertical offsets less critical than horizontal scaling. If a matrix alone does not satisfy alignment, you can combine matrix adjustments with offsets derived from measured screen coordinates and desired mapping.
Custom xorg.conf.d and runtime scripts
To preserve settings across hot-plug events and reboots, you can place static configurations into /etc/X11/xorg.conf.d/ files. The idea is that Xorg reads these files at startup, applying the desired X input behavior consistently. If you rely on runtime xinput commands, you will want a startup script (systemd user unit or a session script) that runs after the X server starts to reapply the matrix and other properties for any newly connected tablet device.
Runtime scripts can be used to adjust settings after a hot-plug. However, there is dialogue around whether these runtime changes survive log-offs or restarts. The recommended approach is to implement a static configuration for the core properties (e.g., Coordinate Transformation Matrix, button mappings) in an xorg.conf.d fragment, complemented by a startup script that re-applies dynamic properties that cannot be captured statically.
For example, a static Xorg fragment may declare the device and its driver usage, while the runtime script uses xinput to set the matrix for discovered devices. When multiple identical devices appear, you can filter by the device’s persistence (e.g., using serial or vendor/product IDs) in the script to reconfigure the correct device instance after each connection.
Button remapping, app-specific workflows, and integration with desktop environments
Wacom-like button remapping can be performed through xsetwacom for devices supported by the wacom driver, or through xinput/uinput-based methods for non-Wacom devices. Note that xsetwacom recognizes devices by name or ID, but button IDs can differ across devices and sessions. If xsetwacom cannot locate a suitable output or device, xinput offers alternative pathways to re-map inputs or apply transformation matrices.
Some users wire tablet button presses to key sequences via tools such as Xbindkeys or sxhkd, enabling custom shortcuts that trigger external utilities (e.g., window manager commands, drawing app functions). It is possible to remap tablet buttons to function keys or mouse buttons that are otherwise unavailable on the device, as long as the desktop environment supports their integration with keyboard shortcuts or scripting hooks.
Drawing applications and tablet compatibility
Several DAWs and drawing applications interact with tablets differently depending on the environment (Xorg vs Wayland). In Xorg environments, you can typically configure tablets via xsetwacom, xinput, or libwacom-generated profiles. Krita, GIMP, OpenToonz, Inkscape, MyPaint, and Pencil2D have varying levels of pressure sensitivity support, with libmypaint-based tools generally adapting to the configured input device. When using Wayland, libinput governs device behavior and xsetwacom is not applicable; in this case, rely on desktop environment settings or OpenTabletDriver as appropriate.
libwacom provides model-specific identification, useful for mapping features to the correct device and ensuring proper hotplug behavior across sessions. For internal tablet devices or cases where autodetection misaligns surfaces, a static Xorg setup can stabilize inputs and mappings, particularly when multiple displays or high-DPI setups complicate the coordinate space.
Practical workflow examples
Example 1: Persisting a left-half mapping after each reboot
- Identify device by vendor/product IDs with dmesg and lsusb.
- Create an xorg.conf.d snippet declaring the tablet device and xsetwacom as the driver glue, if applicable.
- Write a startup script that enumerates devices via xinput list, selects the correct UC-Logic tablet by matching IDs, and applies a Coordinate Transformation Matrix corresponding to the left-half mapping (0.5 0 0 0 1 0 0 0 1).
- Ensure the script runs after the X server starts (e.g., via a systemd user unit or a desktop environment autostart entry).
Example 2: Dynamic mapping with a script that adjusts to new devices
- Parse xinput list output to identify devices named UC-Logic TABLET 1060N or equivalent.
- Use the device ID to apply a matrix, and fall back to a default if the device ID changes after reconnect.
- Update the matrix to fit your screen setup, potentially using a small configuration file that contains matrix presets for common configurations.
Potential pitfalls and troubleshooting tips
- Device IDs changing across USB plug-in events means scripts should rely on IDs parsed at runtime rather than hard-coded IDs.
- If multiple identical devices appear, use a combination of vendor/product IDs and event device naming when possible to identify the correct one for configuration.
- Wayland users may need to rely on desktop environment tools or OpenTabletDriver rather than xsetwacom/xinput-based methods.
- When using coordinate transforms, small misalignments can occur; iterative tuning of the matrix values helps achieve a precise mapping.
- Ensure your kernel driver supports the device-Digimend and HID-BPF are evolving projects; check for recent updates or AUR packages if you need the latest fixes.
Tying it together: a minimal practical setup outline
1) Install and verify drivers
- Ensure digimend-kernel-drivers or HID-BPF support for your device, and install necessary packages (e.g., udev-hid-bpf if using HID-BPF).
- Confirm device presence in dmesg and lsusb after connection.
2) Create a robust identification and mapping script
- Script should enumerate devices with xinput, select the appropriate UC-Logic tablet by vendor/product IDs, and apply a Coordinate Transformation Matrix that matches your screen setup.
- Script should be resilient to ID changes and include a fallback for when the device cannot be found.
3) Persist critical settings via Xorg fragment
- Place an /etc/X11/xorg.conf.d/ fragment that sets up the tablet device with the driver and basic properties.
4) Optional: runtime prep for hot-plug events
- Use a systemd user unit or autostart script to re-run the mapping script after login or on Xorg startup.
Визуальные и инфографические элементы
DRAWING TABLET on LINUX! [OpenTabletDriver]
Ключевые изображения помогут объяснить взаимосвязь между устройством, драйвером и экраном, а также демонстрировать процесс трансформации матрицы и конфигурацию xorg.conf.d. Видео может наглядно показать пошаговую настройку скриптов и проверку результатов в xinput/xsetwacom.