Kwe're busting ass to replace it
Kat this point I'm looking at the GNOME OS installer of all things
KLooks customizable enough that we could make it do what we need
JI recall there being work done on a new Fedora installer
Kit's nowhere near ready sadly
J
Jits been 2 years since iwe had a peek at that
JI wonder if its caused by Red Hat cutting funding again
Nyeah, we've been working on options. we know it's a pain point.
Aoh, removing generate-drm-mode seems to have fixed the unified slider. it's now showing 144hz
Abut 30fps 60hz bug is still there
NI'm actually still investigating a potential option right now.
Alet's try rebooting now, maybe 144hz unified slider will work now, even with generate-drm-mode
Ahrm nope, still shows 60hz. how weird.
Kif you rebooted it's back to fixed being there, no?
KI'm kicking off another build w/ fixed removed from the session
Ksounds like it's not needed period
Ayeah, i rebooted so it's back. what's odd is that i know that i previously tested the testing branch without modifying the gamescope args
Aand i was able to confirm the unified slider was working
Athat's what confuses me.
Aunless the drm-mode was added to a newer testing build, and I tested the previous one?
Kshould have all been added same time
Amaybe steam was caching something then ¯\_(ツ)_/¯
Kbuilders go brr
Abut i can confirm that, at least on my device,
generate-drm-mode seems unnecessaryKanyways we'll look more into that 30fps thing here next
Kthat affects the SDOLED as well, so we really want it dead
Apin stable to 6.6
Ano need to rush to 6.7
Ais there a way i could pull in the latest gamescope while on 6.6? that could at least confirm the unified slider is fixed and separate from the 30fps issue.
KYou might be able to override install our gamescope rpm while on an older release
KCan get jt from copr
Aaight, let me try to find it + install it then. I guess there's always a possibility that the bug is gamescope related, not kernel related
Abetter to check to be safe
Aits not gamescope related, i verified it works on 6.6 by porting the patches
Aoh yeah, true
Ayou already tested on 6.6 w/ gamescope + patches
Jso, it worked on 6.6.14 but not on 6.7
KYeah, likely some changes to DRM in 6.7
KIt's not specifically your kernel
Jik, just asking in general
Jusing the time it takes for bazzite to install onto an SD to look through commits
Jyknow what would be neat?
If Bazzite could detect that you are installing it alongside SteamOS so it doesn't end up changing the UEFI default
If Bazzite could detect that you are installing it alongside SteamOS so it doesn't end up changing the UEFI default
Awouldn't that just be manual partitioning with a separate efi partition?
Jit would still end up meddling with EFI entries
Ahrm, didn't know that. good to know
Jin a good world
EFI entries were files based
EFI entries were files based
Jthey aren't
and thus we must suffer
and thus we must suffer
Aunrelated side note, I'm debating about maybe installing bazzite on my productivity laptop 
Arpm-ostree is more robust than I expected, it could probably meet most of the workloads I need to do
