What is Bazzite Linux’s Deck 44 release, and how does it complete the Fedora 44 transition and reunify the desktop and handheld editions while overhauling the handheld software stack to align with SteamOS—including the roles of InputPlumber, SteamOS Manager, PowerStation, and Ope

The practical change is that handheld controls—including TDP—move into Steam’s Quick Access Menu (QAM) rather than living primarily in a separate handheld utility.

Important compatibility caveat

On the original Lenovo Legion Go, fan control and gyro support are temporarily absent in this transition. That is a known trade-off of replacing the old handheld stack, rather than a claim that all device-specific features are already complete. Insufficient evidence in the supplied sources establishes a restoration date.

Kernel, graphics, and display changes

The release advances the core platform to the Open Gaming Collective Linux 7.2 kernel and Mesa 26.2.1.

• It includes scheduler improvements backported from newer upstream kernel work.
• The kernel carries the VRAM-overcommit and dmem cgroup work, intended to improve how graphics memory is prioritized and managed under pressure.
• AMD users can optionally enable HDMI 2.1 features—FRL, ALLM, and VRR—rather than receiving them as an unconditional default.

Updates and administration

Deck 44 adds a system updater usable directly in Steam Game Mode with a gamepad, reducing the need to enter Desktop Mode for normal system updates. Bazzite’s Portal is also redesigned as the graphical place to manage optional platform features, including the optional graphics/display capabilities.

Bazzite’s Steam Gaming Mode is intended to boot directly into the console-style Steam session while retaining a Desktop Mode, so the new updater better matches the handheld workflow.

What reunification means

The desktop and handheld editions had been temporarily separated while Deck-specific Fedora 44 work was stabilized. With Deck 44, Bazzite says that separation is over and updates should again arrive simultaneously across images. That should reduce feature/version skew and make release maintenance more predictable, though device-specific fixes can still land on their own schedule.

Advice for Deck 43 users

This is a large, foundational migration—not a routine package update. Deck 43 users who depend on current device behavior should pin their present deployment before upgrading, so they retain a known-good bootable version and can roll back if a device-specific regression affects them. That precaution is especially sensible for original Legion Go owners while fan and gyro support are absent.