so i'm on windows 10 for now, im waiting for NVK to get more mature, basically until it can support
so i'm on windows 10 for now, im waiting for NVK to get more mature, basically until it can support vulkan 1.3 for dxvk/vkd3d
KCan't wait for NVK to get good
Qah yeah that makes sense then
Bif i rebase from bazzite gnome to bazzite kde is there anything i should do beforehand?
KThat's not supported upstream, expect anything to break
Bill just make sure i have a bootable usb at the ready then 
KDifferent images are fine, different desktop environments are not
Bis that because configuration is in the user directory so doesnt get touched?
Bmeaning any defaults aren't set
Qppd.conf apparently didn't work either, bleh
KDid you try the GUI?
Tyea + other issues
TKDE and GNOME do not have the same standards when it comes to files and that can break stuff
Qnot yet, doing that on a TV is pretty awkward so I wanted to just do it over ssh
Vanyone have any problems with gnome-vrr?
Bguess its time to see if my dotfiles are truly portable
QOkay setting it in the GUI sticks but with tuned-adm it does not
Qthat’s…pretty unintuitive
Qbut well it seems to have fixed it, thanks for the pointers
KTuned was primarily designed for RHEL servers, so it's likely poor documentation
KWhat did you need to change btw?
KTrying to understand the issue
QI changed the profile to latency-performance - the issue I’m having seems to be that the CPU will clock so low in the balanced profile that the system ends up with major stuttering
Qit would eagerly drop to 800MHz as soon as possible
Awtf, theres a chance steam nuked led settings
A
Aupdated to the beta version and well, leds are broken but the ui is there
KSounds like a genuine steam beta moment to me
Atried to verify this
Athey also changed the controller name
AIts PlayStation 5 controller now
BInstaller stuck on deployment starting...it did fail earlier but attempt #2...will let you know any errors
KNew installer hopefully coming very soon
BWhat's the mok password?
Publue-os
BThat seemed to work but now I get bad shim signature error indicating that it didn't
Pyour uefi might have a setting for secureboot for locking it down. I think my desktop mobo, I had to change a setting for secureboot from windows-only to be able to enroll mok. I don't remember exactly what it was called now
RRAnyone experiencing this bug after resuming from sleep?
When I also apply an update it always take a supposed 20 minutes and stucks at 99%
When I also apply an update it always take a supposed 20 minutes and stucks at 99%
BHmm I'll look, how would I re-import the mok without reinstalling
Pujust enroll-secure-boot-key
KThere's a ujust command for this
KThe progress is faked, for most people it takes 20 minutes so we simply count up to 20 minutes
KIt's still doing something even if it's stuck at 99, it's just taking longer than our guess
RYeah I assumed it was faked, should I just let it hang then?
KIt's an issue with RPM ostree not reporting download progress
KYep, let it sit
KYou can also update from desktop mode it's the same thing
KThat will at least show you the output while it's doing it's thing
BI can't boot now...so will I need to disable secure boot so that I can boot to enable secure book 
