it's always enabled so long as the game and your hardware support it
it's always enabled so long as the game and your hardware support it
Kyou actually have to use an environment variable to turn it off
Tyeah so back to this. it's KDE specific like Kyle said BUT it seemed to actually go away after a fresh installation of bazzite
Tother applications would do this too
Tit's a cosmetic thing for sure. idk try following the advice of removing the desktop file of steam link
T@B0BP4G3 to add to this, on the OLED deck, the HDR doesn't come at a cost of performance being always enabled
Tso you can always keep it on whether the game uses it or not
BWon't resolve in Desktop mode?
KNo HDR in any DE at this time
Toh yeah desktop doesnt have HDR support
Tyea
TKDE/GNOME are working on it
Texactly the same situation for steamOS
Talthough KDE is getting HDR support for wayland when Plasma 6 is released
MOh nice, my first accidental react with a glance and hand gesture :kekw:
Ceven your problems are futuristic
Mthe butt dialing of the future
Mits lowkey way more usable for basic productivity than I expected. I pushed a commit to GitHub in here which was wild.
Cwhaaat
Cdamn, sounds cool, are you using it as a remote screen for your mac?
BAmazing @Kyle Gospo that appears to have finally solved it. I closed the issue and reported the solution.
BAlso @Kyle Gospo I cannot find my original message, but you had asked for a
https://pastebin.com/Q45VmCsP
dmesg the next time I hit the "Nvidia booting to black screen" issue. Well, I just hit that issue 5 times in a row, so here is the dmesg output once I finally managed to do a proper boot:https://pastebin.com/Q45VmCsP
J
your github avatar
Hoh thats funny, leftover bazzite-arch steamlink icon 
A@j0rge hi. Thinking of something here. Do you by chance have an idea about supporting dkms modules on ublue kernels?
Kwon't work with OCI
Kyou can use kmods, but they must be build for the currently installed kernel AOT
Kand packaged as part of the image
AExactly my thoughts, this will be really weird for a rolling kernel
Kyou'd have to make a custom image
Kand build your kmods prior to the image build time
KFedora updates it's kernel constantly, we have no issues
AI'd appreciate some hand-holding here, I don't have much of a clue about how to go with that. Read here and there that it's supposed to be easy but it's not something I was considering up until... yesterday?
KTake a look at https://github.com/ublue-os/akmods/
GitHub
A caching layer for pre-built Fedora akmod RPMs. Contribute to ublue-os/akmods development by creating an account on GitHub.
AIf there is a tutorial written somewhere I can follow it and bug you only in case I hit a brick wall
KThis is where all of our kmods are built
KYou can fork this and add what you need to it, then install it in your custom bazzite image
ASounds simple but it's a little bit like that "draw an owl"/"draw a horse" joke
AI'm not that good at drawing unicorns yet 
hard to just erase the horn and be done with it hehe.
hard to just erase the horn and be done with it hehe.TTbut yeah i get it
Tit takes a little to grasp
AThanks!!
Adoes any one of you know what the stapm limit actually does?
Awhen the processor is running in stapm mode
VThere was discussion about impossibility of adding 535 nvidia driver in images because rpmfusion stopped packaging it. GloriusEggroll in nobara distribution based on fedora packages latest 535 driver. Can't you use this one to include in images?
Jgot a link to the packaging?
Kmoot point
Knext linux kernel release will force everyone to Nvidia 550
Kdue to a change in the kernel that breaks prior nvidia kmods
Ktalked to the guys at Nobara about it today
