And googling it on my phone got me basically nuffin 😄
And googling it on my phone got me basically nuffin 
VQuite new approaches/tech, google can be patchy on info
VIf in doubt just ask here 
KWell, yes, the issue was that so far as I could tell, I couldn't ask here as my PC couldn't boot (Well, until I ctrlaltdel and loaded the older image, so go immutable! 
)
)VIt's a learning experience, I'll say that much lmfao
VBefore using Bazzite I was already on Fedora Kinoite so it's been a while since I went through the motions of being at the beginning of it all. Definitely still nowhere near an expert on it tho lol
Nsending it now, gonna try daily driving bazzite, hope it sticks and i can actually move to linux
Nlast night testrun was pretty great so i feel like it's a good time for me to jump on
Wwow, that grey sure is purple
Nviewing angles aren't great
Wnaw, they're prrrfect, I love me some purple.
Ni need to calibrate them one of these days but i feel like the monitor is gonna give out before then lol
A@Jan disable
CONFIG_SECURITY_LOCKDOWN_LSM_EARLY maybe? It's off in the arch kernel and when it's on it disables disabling lockdownAprobably should be done upstream too
Rbazzite / fedora are peak linux if ya ask me
Rso hopefully you enjoy your stay
Ni enjoy fedora on my laptop a lot
Nthough i never tried silverblue/kinoite
QI'd love to use kinoite as my Linux install, but I had too many annoyances with dev tools so I'm using regular Fedora KDE for now
QI'm sure stuff like that will be worked out eventually though
RHas anybody had any opportunity to test Bazzite/Bluefin on Tuxedo computers? I have one of their laptops on the way to me (Pulse 14 gen 3). From what I'm aware, they have kernel drivers/dkms located at https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers
VUsing aurora on my laptop
A@Kyle Gospo so good news and bad news on the LGO with the gamescope fix. It does fix the refresh rate slider, but the latest testing branch seems to introduce the 60hz 30fps cap bug. I suspect maybe it's due to kernel 6.7?
Nhuh so that's why i had to raise my cap for fh4 to 120 to get 60
Aanyways, reverting back to stable branch for now
Nthe post install has begun :Yay:
Agah, should've reverted back to my prior version, instead of deploying stable again
Astable is on 6.7
Atime to find the last version of bazzite on 6.6
Mhttps://github.com/ublue-os/bazzite/pkgs/container/bazzite-deck you can look at the manifests to see which kernel each built images uses
GitHub
GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 420 million projects.
JI'm kinda against it, because having the lockdown module loaded ahead of time could prevent fiddling with things ahead of time, plus I am unsure if this will really allow you to disable it
Jbut I can look into it
Abazzite supports rolling back to builds from specific dates, i'm trying to track down which date was the last build with 6.6
e.g.
e.g.
Jany build older than 2 days
Anice, thank you. looks like it's
39-20240205Aarch does not have that option compiled and has the other ones
Ain any case, up to you. But I can not use that kernel with that option on and Im sure im not the only one
JYes, but Fedora isn't arch and they do these kind of decisions in isolation
JI'll first have to dig out why this decision was made, what recommended fixes for hibernation and so on are etc.
Jwhat you actually want is
CONFIG_LOCK_DOWN_IN_EFI_SECURE_BOOT turned offJits a custom config included in kernel-ark (upstream Fedora kernel) which forces lockdown on if secure boot is enabled
Ai dont think so, right now my memory policy is strict
Aand thats not a problem
JThis will let you find the kernel version on a given image
skopeo inspect docker://ghcr.io/ublue-os/bazzite:39-20240210 | grep ostree.linuxJlet me make sure I understand the problem right
Jthe kernel is in lockdown mode which prevents you from doing various things, correct?
Ain integrity mode
Aspecifically
Jit doesn't really matter which one it is
JSince I run kernel-fsync myself (though only on a vanilla Fedora system) I dont think
CONFIG_SECURITY_LOCKDOWN_LSM_EARLY or similar configs are the problemJlockdown is not enabled for me at all
