I suppose that NVK vs proprietary driver is still slower on 4xxx cards?
I suppose that NVK vs proprietary driver is still slower on 4xxx cards?
KIn some very specific workloads it's faster, but I would wait another year for true parity and/or improvement
KAnd on some laptops it will always be slower due to Nvidia's blob STILL locking off the highest clock speed
KEvil company
THow do I roll back to a version of bazzite with stable sleep for the legion go? And which version would that be ?
TStill having issues
Ais the steam deck oled fix still coming tommorow?
KNo guarantee it's tomorrow, release is based on testing
Kbut definitely soon
Asoon
KUniversal Blue
Yes it is true for all of them, however I mostly focus on documentation on the Bazzite image which is why it’s here. Desktop images of Bazzite follow the same automatic update style that the main images follow. However, there’s also the -deck images that do not follow this which is why I wanted to differentiate between them. As for pinning, w...
KUse 0406
TTy
ZIs it already possible to use Bazzite with Fedora 40 in testing on deck oled, or are there already known issues preventing its use? I seem to have read that the kernel is not ready yet
Knot ready yet
Akinda funny how the LGO is, in a lot of ways, a more linux-compatible device than the Steam Deck itself
ALGO basically had all important hardware usable from day 1 with no additional kernel patches
NLenovo is pretty good with their hardware not being completely linux-hostile
MI’m still mad that they threadlocked the damn SSD on the 512gb unit I tested a while back
Mfirst time I’ve seen that on an SSD
THow do I select 0406? Which method
TI only have like 0415
PMaybe some day there will be a gui drop down pulling that list to select 
Nthat would be pretty neat honestly.
Nmaybe that will be @NerdsRun's next project? 
Taru made this script:
https://github.com/aarron-lee/legion-go-tricks/blob/main/bazzite-rollback-helper
not a GUI sadly
https://github.com/aarron-lee/legion-go-tricks/blob/main/bazzite-rollback-helper
not a GUI sadly
Tthere was also this prototype image switcher way before bazzite/bluefin/aurora existed:
https://github.com/atimeofday/image-switcher
but it was only for switching between all of the 'main/base' images
https://github.com/atimeofday/image-switcher
but it was only for switching between all of the 'main/base' images
T
K
N@Kyle Gospo is there any reason we aren't considering having this in Bazzite itself?
Pwhat's the spike?
KHasn't been PR'd, I'm open to it
Kthough I also want to make a GUI for it
KTitus, most likely
Aoh should I PR the helper?
Ktotally open to it
Ahadn't thought about that for some reason
ANLooking at the code, it looks pretty straight forward. Always worth giving it a second look. Something like this would be helpful to users I think.
Ai'd probably want to make the helper be able to determine the currently active bazzite image
Aright now it defaults to
bazzite-deckAso it's easy to accidentally rebase to the wrong image if you're not on bazzite-deck
Noh yeah, that would definitely need to change.
NYou can grab the image information like we do in our just scripts.
Ae.g.
bazzite-rollback-helper rebase 39-20240220 would default to bazzite-deck:39-20240220KI think deck is the more likely rollback candidate anyway, given the hardware requirements of that image
Kso if you want to simplify your load you could PR it just to the deck images
Kbasically curl it into /usr/bin/ when building -deck
Kand chmod +x it
NI mean, determining the image isn't hard though?
