How this works
Plug and Tux doesn't test hardware by hand. It reads the device lists that already exist in the Linux ecosystem, combines them, and turns them into one page per device. Everything is rebuilt automatically every night.
Where the data comes from
- Linux kernel
- OpenRazer
- HeadsetControl
- Solaar
- libratbag + Piper
- OpenRGB
- ckb-next
- libwacom
- Repology and Launchpad for distro kernel versions and packages
- usb.ids for vendor and product names
Thanks to all of these projects: they do the actual work of making hardware work on Linux.
What "supported" means
A feature is listed when the project that provides it says it supports that device, for example a headset in HeadsetControl's device list or a mouse in the kernel's driver tables. We don't claim every feature has been tested on every setup.
The distro table
For Arch Linux, Fedora 44, Fedora 43, openSUSE Tumbleweed, Ubuntu 26.04 LTS, Ubuntu 24.04 LTS, Ubuntu 22.04 LTS, Debian 13, Debian 12, we compare the release's kernel with the first kernel version that includes the device's driver, and check whether each needed tool is in that release's repositories. Distros sometimes backport drivers to older kernels, so a ⚠️ isn't always a no.
Is this my device?
Every device has a USB ID like 1038:2202. Run lsusb to see yours, or paste its
output into the search on the home page.
Found a mistake?
Use the report form (every device page links to it with the device filled in). Reports go straight to the maintainer; fixes go live with the next nightly update.