Happy Holidays & Happy New Year everyone! This month’s update is a smaller one but marks the start of a cleanup effort that will end with us synchronizing with a number of other projects in the Linux Gaming space, sharing resources and patch sets wherever possible. We’ll have much more to share on this in the near future.
Changes in this update include:
Moved IWD to be the default wireless connection handler in Bazzite for improved wifi speed and connection stability
This will reset your Wireless Connections one time - we promise it’s worth it,
Promoted the Live ISOs to the default for future Bazzite installs
Implemented Greenboot which will automatically rollback in the event of a problem after updating.
You can see the status of this system in the terminal MOTD.
Replaced BTRFS duperemove with bees - a faster and more stable solution for file deduplication.
Fixed performance issues with the Legion GO 2 when using auto-vram
Added VRR support for the UGREEN DisplayPort to HDMI 2.1 adapter.
This update also brings the latest version of Bazaar, which now offers the ability to log in to Flathub and favorite applications among numerous other bug fixes and improvements.
Thanks again for being with us throughout 2025, and we’re very excited to bring you further improvements in 2026!
Why does the change log list both 590 and 580 Nvidia drivers?
Nvidia
580.95.05-1 590.44.01-1
Nvidia LTS
580.95.05-1
After the update I got 590, which is what I wanted, but out of curiosity, is 580 also part of the image, or is it accessible via a rebase, or something?
Also worth noting that both ScopeBuddy and ls-iommu are now packages so their version changes can now be tracked in the bazzite changelog going forward.
Bees being included is awesome. That’s one of the couple of layered packages I have on my system. Most COPR repos don’t seem to have v0.11.0, which you kind of need for reasonable performance instead of v0.10.x. I used the spec file in Kyle Gospo’s bees repo to locally build a v0.11.0 package like 6 months ago and it’s worked great.
Can you elaborate more on this? Does this workaround the limitation in AMD drivers that can’t support HDMI 2.1? Does this adapter have some model number or something?
I’m not so sure. I would expect for such an adapter to be active, not passive like these. Passive adapters rely on the device ability to send HDMI native signal over DP port, so called “Dual-Mode DisplayPort”… but the issue with AMD drivers is that they cannot generate HDMI 2.1 signal at all (with VRR and all). Am I missing something or is there some cheating involved in the background?
I wonder how future-proof the switch to IWD will turn out to be, now that Intel basically abandonded the project:
(…) I’ve been holding out hope that it was just a brief pause, but now here we are three months later without any Git activity to this very practical open-source project. I’m awaiting to hear from Intel with any official word on the status of the project, but it doesn’t look good as another open-source setback at the company. That last Git activity just occurred before word of Intel shifting their open-source focus to make their contributions more directly benefit them rather than their competitors. (…)
Yeah, things seem kinda shaky tbh. The stability seems weaker if anything, the pickup range seems to be slightly lower as my 5g channel hovered between 1 and 2 bars and now just disconnects occasionally, though my 2.4g is working alright.
Waydroid is screwed. Whatever protocols were changed made it so none of the apps installed after the fact, like from Google Playstore, work, they try to connect to their servers and just die as far as I can tell. I switched back to the previous connection protocol as that’s still a toggle-able option, but none of the sensors were working and I still had the issue with waydroid, which means its something else that was done with the update that screwed that up.
Someone else on the discord chimed in with their xbox controller not connecting and a third talked about their fresh install not actually installing, though not sure when they made that so it could be something else.
Almost none of what you’re reporting as issues has anything to do with IWD.
IWD is currently in active use in SteamOS and is being patched by Collabora. It’s an open source project and does not need Intel’s involvement to continue.