Translated from the Japanese original
A new effort to support handheld and home game consoles has begun in the Linux distribution Debian. On November 12, 2026, Debian Maintainer Aryan Karamtoth announced on the official mailing list the launch of the “Debian Gaming Hardware Team,” which will investigate hardware compatibility for gaming devices. The team will run Debian on actual devices such as the Steam Deck and ASUS ROG Ally and record which features work and which problems occur. Where necessary, it also plans to consider patches and workarounds for hardware issues.
The initiative stems from a concern that, even as the Linux gaming environment expands, Debian is not well recognized as an operating system for gaming devices. Karamtoth pointed out that while Fedora-based distributions such as Bazzite and Nobara, and Arch Linux-based ones such as CachyOS, are drawing attention for gaming, Debian is rarely mentioned. The effort is not about immediately building a new gaming-specific OS. Its aim is first to find out how far the existing Debian runs on gaming devices and to share the results.
Testing Hardware Compatibility on the Steam Deck and ROG Ally
The new team covers three areas: handheld game consoles, devices used for game emulation, and home game consoles. The team’s official wiki names Valve’s Steam Deck and the ASUS ROG Ally as specific devices, and also lists the Linux-based home console Steam Machine as an example. These are devices presented as testing targets, not an announcement that testing on each model has been completed.
The Steam Deck uses SteamOS 3, which Valve developed based on Arch Linux. Valve’s official specifications also state that the OS is Arch Linux-based. A dedicated OS allows hardware and software to be tuned together, whereas installing Debian, a general-purpose distribution, requires verifying operation on the same device under a different configuration.
For handheld consoles, simply booting the OS is not enough. A device is usable as a game console only when multiple functions work properly: 3D rendering on the integrated GPU, input from the gamepad and touchscreen, audio, wireless connectivity, sleep and resume, and power management. Operation after resuming from sleep and power management in particular bear directly on the usability of a handheld, which differs from a desktop PC. These are examples of items to check in compatibility testing, not official test items defined by the new team.
Hardware compatibility must also be distinguished from game software compatibility. On Linux, Windows games can be run using tools such as Valve’s Proton, but how well a game runs also depends on the compatibility layer and anti-cheat mechanisms. What the new team will tackle for now is mainly testing to get Debian and the gaming hardware working properly together; it does not plan to work toward supporting all Windows games.
How It Differs from the Existing Debian Games Team
Debian has long had a “Debian Games Team” responsible for managing game-related packages. That team handles packaging and maintaining game software and addressing shared technical issues.
The newly formed Debian Gaming Hardware Team, by contrast, focuses on the compatibility of the consoles themselves and on hardware-specific problems. In his launch announcement, Karamtoth made clear that the team’s purpose does not overlap with the existing team’s, and said that for now it will not take on packaging or maintenance except where directly necessary for its own activities. The work is divided between bringing game software into Debian and getting Debian to run properly on specific consoles.
The Challenge of Running the Latest Consoles on Stable Debian
One key issue the new team lists for future discussion is how to get new game consoles working on Debian’s stable release.
Debian uses a release model that emphasizes stability. According to the official release information, as of November 2026 the stable release is Debian 13 “trixie,” published on August 9, 2025. Meanwhile, “testing,” which is on the path to the next stable release, is called “forky” and contains newer software than stable.
This difference affects support for new consoles. On Linux, in addition to the Linux kernel that controls the hardware, components such as the Mesa drivers for using the GPU and the firmware that runs inside the device are needed. If support for a new chip or peripheral is added later, some features may be unavailable with the software in stable but may improve in newer versions.
Comparing Debian’s official package listings shows a large difference between the software offered in stable and in Backports. Backports is a mechanism that rebuilds newer packages, such as those in testing, for the stable release.
| Software | Debian 13 stable | trixie-backports |
|---|---|---|
| Linux kernel (linux-image-amd64) | 6.12.117 | 7.3.4 |
| Mesa Vulkan drivers | 25.0.7 | 26.1.6 |
| AMD GPU firmware | 20250410 | 20260916 |
The above are versions from Debian’s official package listings checked on November 20, 2026; the Linux kernel and Mesa values are for amd64. Thenel, Mesa Vulkan drivers, and AMD GPU firmware
These differences indicate that there is room to update the software needed for hardware support while keeping the stable release. For example, the Linux kernel contains the drivers that control peripherals, and Mesa provides the functionality for using the GPU through graphics APIs such as Vulkan. The AMD GPU firmware is also managed as a separate package, so test results can vary depending on which components were updated.
Since Debian 12, official installation images have also included distributable non-free firmware. According to the Debian 13 installation guide, the installer can detect the firmware needed and, where available, install the corresponding packages. However, even if firmware is available, not all of a device’s functions can necessarily be used unless the corresponding kernel drivers and user-space software are sufficient.
Can Backports Be a Way to Support New Consoles?
In its Backports usage instructions, Debian recommends selecting and installing only the packages you need. Backports packages are, in principle, not installed automatically; users specify them as needed. Its appeal is that new kernels and drivers can be adopted while keeping the base configuration of stable.
On the other hand, Backports packages are not tested to the same degree as stable, and support is on a best-effort basis. Compatibility when combining packages of different versions also needs attention, and Debian does not recommend installing Backports wholesale without conditions.
Karamtoth lists how to run new hardware on stable Debian as a topic for future discussion, but has not announced that Backports will be adopted as the new team’s standard approach. If testing on real devices can distinguish features that work in the standard stable configuration from those requiring newer packages or individual fixes, it would provide concrete material for deciding on an approach.
Building a Compatibility Database and Issue Tracking
The new team aims to consolidate verification results from real devices into a compatibility database and link them to bug reports and fixes.
On Debian’s GitLab-based development platform Salsa, a Debian Gaming Hardware Team group has already been set up. A dedicated project for reporting hardware problems was also created on November 12, 2026. The launch announcement and wiki state collecting compatibility information and fixing problems as goals, but detailed per-model test results and standardized test procedures have not yet been presented.
To make compatibility data practical, it is important not only to record whether something works, but also to make clear the OS and package configuration used and the features tested. For example, even on the same Steam Deck, the kernel and GPU driver versions may differ between the standard Debian 13 configuration and one with Backports added. Distinguishing the results of the two makes it easier to see what was confirmed under which configuration.
Device compatibility information can be organized into the following stages.
| Verification stage | What is checked |
|---|---|
| Standard Debian 13 configuration | How much works in the standard configuration: OS boot, GPU, input devices, wireless, power management |
| Configuration with Backports added | Packages and versions added, and features confirmed after the update |
| Device-specific fix candidates | Conditions for reproducing the problem, the fix, and verification results after applying it |
| Formal adoption of fixes | Whether the fix has been incorporated into Debian packages or upstream projects |
This table does not represent officially decided test items; it is an organization based on the new team’s goals and Debian’s package management approach. In actual testing, factors such as the model number, firmware version, and test conditions also bear on how results are interpreted.
Accumulating this information will make it easier for users to choose which Debian configuration to try on their own devices. For developers, it provides clues for reproducing reported bugs and determining whether a problem lies in the kernel, drivers, or firmware. If behavior improves after installing newer packages, recording the test conditions also makes it possible to track the changes and their results.
People who are not official Debian developers or maintainers can also join the team. The OFTC IRC channel “#debian-gaming-hw” has been set up as a point of contact, and the wiki also lists a Matrix channel bridged to IRC. This structure lets ordinary users who own the devices report problems from their real usage environments and help build up compatibility information.
A Debian Configuration for Console Makers Is a Future Idea
Karamtoth also mentions creating a “Debian Pure Blend” that game console makers and DIY users could use. However, this is a future idea; for now the priority is hardware compatibility testing.
Debian Pure Blends are a mechanism that combines software for particular users or purposes to make installation and configuration easier. Rather than creating an independent derivative distribution separate from Debian, they prepare purpose-specific configurations using existing Debian packages. Examples already exist, such as Debian Edu for education, Debian Science for scientific research, and Debian Games for game software.
The Pure Blend now envisioned would not merely bundle game software but is intended to make it easier for makers and DIY users to install the software configuration needed for handheld and home consoles. If realized, it could serve as a common foundation for installing Debian at the stage of manufacturing or assembling a device and pre-combining the necessary software. However, the specific package composition and timing of availability have not been announced.
The new team’s activities begin not by immediately delivering a dedicated distribution for game consoles, but by using Debian’s existing development infrastructure to investigate compatibility on real devices. How per-model information for devices such as the Steam Deck and ROG Ally accumulates in Salsa’s issue-tracking project and compatibility database, and how reported problems lead to fixes, will be the measure of the effort’s progress.