Support us on Patreon
PayPalBazzite Linux has seen an upgrade to the just released Fedora 41, and with it comes lots of extra enhancements to their support of various PC gaming handhelds from AYANEO, ROG Ally and others.
What is Bazzite? It's "a cloud native image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices - including your favorite handheld". Basically, it's a SteamOS-like based on Fedora that can turn your Windows handhelds into a smooth Linux device.
With the Bazzite F41 update they've got an updated Linux kernel v6.11 that includes patches for Ayaneo, OneXPlayer, Ayn, basic controller support for the MSI Claw and a whole lot more goodies. Some of these changes include:
- Speaker patches for Ayaneo Geek, Geek 1S, 1S, 2, 2S, Kun, Flip KB, Flip DS, and Ayn Loki MiniPro.
- Display quirks for Ayaneo Flip DS, Neo 2S, GEEK, Founder edition and Ayaneo 2.
- ROG Ally has a new patch that "selects the correct firmware for the Ally speakers, offering superior performance for users that used the incorrect firmware previously".
- OneXPlayer X1 and X1 Mini sensors driver updated with "support for charge limiting and charge bypass" plus allowing control of the Turbo LED.
- The MSI Claw also had support added to the "Handheld Daemon, where the front OEM buttons and the controller will work properly in Steam Gaming Mode". Lots of work still needed there though as there's plenty missing like TDP controls and back buttons.
Lots of background work on the Bazzite project as a whole too. Bazzite has grown massively recently, with even the likes of Digital Foundry giving it a spin showing how it can improve on the mess of Windows on handhelds:
Direct Link
See more in their announcement and official site.
Article taken from GamingOnLinux.com.
Quoting: SamsaiGiven the actual plain meaning of the word "immutable" I think that's kind of understandable. What I find weird is deciding to go Humpty-Dumpty and use the word to mean something that's apparently completely different.Quoting: Purple Library GuyGotta say, this sounds kind of . . . mutable.Not really any more than functional programming being able to represent a changing state despite immutable values. Some people just don't have a good grasp of what immutability in this context means, because it definitely doesn't need to mean that nothing is ever allowed to change.
Quoting: Purple Library GuyGiven the actual plain meaning of the word "immutable" I think that's kind of understandable. What I find weird is deciding to go Humpty-Dumpty and use the word to mean something that's apparently completely different.And the system still works according to the plain meaning, you just need to actually look at how state change happens. Deployments are immutable unless unlocked (we will ignore overlayfs for now). What is allowed is creation of new deployments, which can add, change or remove packages. Whether the user can affect how deployments are created or not does not affect whether the system is immutable. So, nobody is going "Humpty-Dumpty" here, the terminology is consistently applied, you just have a preconceived notion of what an immutable OS is like, which doesn't match the reality on the ground. I mean, it sure would be a bit awkward if SteamOS was "immutable" in the sense that not a single bit on the root filesystem was ever allowed to change. :)
See more from me