Bazzite Pins Firmware After Handheld Issues, Adds One More Handheld Support
The Linux gaming distro Bazzite shipped a modest new stable build, 44.20260916, on September 16. It's not a feature drop. It's a surgical fix: the project rolled back and locked its linux-firmware to an older version after the latest build started breaking some handhelds, and it taught the OS to recognize one more device it had been misreading.
Built on Fedora's atomic desktop images by the Universal Blue project, Bazzite pushes stable images nearly every day. Most are small. This one is worth looking at because it's the kind of conservative, reversible patch that only matters if you actually run a third-party handheld on Linux.
Why Bazzite reached for the rollback switch
The headline change is a firmware pin. Lead maintainer Kyle Gospodnetich reverted linux-firmware from version 20260910-1 down to 20260810-1 and locked it there. His commit message is blunt about the reason: fix: Allow firmware pinning, pin to old version of firmware due to issues with the latest on some handhelds
Rather than simply dropping the newer firmware from the image, Bazzite added the ability to pin firmware in the first place. A new build argument, LINUX_FIRMWARE_VERSION, and a matching dnf5 install step now hold both linux-firmware and linux-firmware-whence at that snapshot.
The upshot is straightforward. Any Bazzite image built from here ships the August 10 firmware instead of the September 10 one, and the version won't drift forward on its own.
The exact failures aren't spelled out in the auto-generated changelog, but the pattern is well documented in the project's issue tracker. Firmware bumps have repeatedly triggered handheld regressions, most notably audio glitches. Issue #4366, filed for the Xbox Ally X, describes left and right speaker glitching that started the moment linux-firmware moved from 20260221-1 to 20260309-1, and it's still open.
Similar firmware-sensitive problems show up across the handheld ecosystem. An RDNA2 desktop card, an RX 6650 XT, reportedly took a severe FPS hit after a 20260810 amdgpu firmware landed (#5576), and a grab bag of AYANEO and OneXPlayer devices have traced suspend, fan, and input quirks back to firmware revisions.
Rolling back to a snapshot that predates the September 10 changes is a conservative, reversible move. Because Bazzite is image-based, anyone who prefers the newer firmware can still rebase or roll forward themselves.
The SuiPlay0X1 finally gets the right label
The third commit in this release, a709f26, lands a community contribution ( PR #5830) from archlinuxbits that teaches Bazzite about a device it had been getting wrong.
The SuiPlay0X1, described by the contributor as an Ayaneo 2S rebadge made by Mysten Labs, Inc., slipped through the cracks in a subtle but annoying way. InputPlumber already had a device profile for it, yet Bazzite's hardware setup classified it as an HTPC instead of a handheld. That meant InputPlumber got masked, the handheld category flag came back false, and the device lost its proper controller mapping in Gaming Mode.
The fix adds the device's DMI product and vendor strings so InputPlumber stays enabled. The device reports non-valve-handheld-hardware as exit 1, confirming it belongs in the third-party handheld bucket that Bazzite handles through InputPlumber rather than Steam's native Deck input.
A companion commit bumps bazzite-hardware-setup, the package that does this detection, so the new logic is actually present in the build. Otherwise the entire package set is unchanged from the previous day's 44.20260915 image. Firmware is the only thing that moved, and it only moved one direction.
Keeping the current stack intact
What 44.20260916 retains from 44.20260915 is as important as what it changed. The whole modern gaming and desktop stack shipped earlier in the week is fully intact: UMU Launcher for non-Steam Windows games, the Wi-Fi power-saving-off latency fix, Mesa 26.2.2, Gamescope 3.16.28 with a September 12 session, MangoHUD 0.8.4, both Nvidia driver lines, and GNOME 50.4 and KDE Plasma 6.7.5.
The kernel sits at 7.2.4-ogc3.1, with the Nvidia LTS line holding at 6.18.49-ogc1.1. One smaller image did advance, with the hid-fanatecff Fanateus controller firmware blob bumping from a May build to a September 15 one.
It's a targeted stability patch on top of an otherwise current image, not a step backward for the rest of the system.
Bazzite tracks slightly ahead of its Fedora 44 base, which shipped GNOME 50 and KDE Plasma 6.6. The project sits under Universal Blue, which applies rpm-ostree and Atomic Desktops to the Linux desktop. Because updates are atomic, the previous image stays on your machine after each update, and you can boot into it or rebase to any of the last 90 days from the terminal. That safety net is exactly what makes a firmware pin like this one low-risk: even with the version locked into the image, affected users keep full rollback capability.
The GitHub repo sits at roughly 9,100 stars and 1,100 forks, which says something about how much people lean on this thing for hardware that doesn't officially ship with Linux.
Grabbing the update
For existing users on the stable branch, the recommended path is a rebase rather than a clean reinstall:
bazzite-rollback-helper rebase stable
To pin this exact build:
bazzite-rollback-helper rebase 44.20260916
New users can pick their hardware, GPU vendor, and preferred desktop from the download form on bazzite.gg to get a tailored ISO link. Existing Fedora Atomic Desktop users can rebase in place, though it's advised to keep the same desktop environment when you do.
Those who specifically want the newer September 10 firmware can still roll forward through the standard rpm-ostree tooling, since the older image remains on disk.
It's a small release, and it's arguably doing exactly what it should: prioritizing a working gaming experience over running the newest code, if you care about handhelds at all. The pinning mechanism is the real takeaway here, since it lets the project hold firmware at a known-good version without the package manager silently pulling it forward. Everything else just stays current.
