I don't think Utah even gets enough snow for that to be relevant in most places.
I don't think Utah even gets enough snow for that to be relevant in most places.
K(where jerryrig lives, for reference)
CI think that when they launched the R5-R9 lineup they really started giving a damn for Linux, and look at it now, amazing
ZSo I enrolled secure boot
Kon?
ZAnd I entered my sudo password. Then I entered it again, and again, but it wasn't sudo lmao
ZDeck
Kdon't
Kdeck isn't a secure boot device
ZWelp
ZI got a menu that was very blue
Kthat would be the MOK enrollment
ZYea that's what it was called
ZI didn't remember what I was supposed to press so the device rebooted itself after a bit
Knot reading the notice when enrolling the key that you needed to enter the password "ublue-os" saved you here
Kenrolling that key on deck would have turned on secure boot and rendered your shit very unbootable
KBazzite isn't showing that terminal notice on deck, is it?
Kit's showing it on all builds because deck is also for HTPCs
ZYea I just didn't notice that it stopped asking for the sudo password
Koh awkward.
Kit's up to the end user to know whether or not they're using secure boot
ZBut either way, what will happen now?
Ksince not showing it for secure boot disabled could result in people not being aware of it
Ksince you failed to enroll, nothing
ZSweet
ZSaved my install :D
KI mean, I'm running Bazzite on my desktop, so I enrolled and all was fine, but if it can brick decks to do it, that'd be bad?
ZA notice for Deck users would be nice
KI'll have to be more explicit next time, notice is going away tomorrow
KHDR kernel tomorrow?
Kyep
KNice
ZIs there a notice that I missed? D;
Kthe secure boot notice
Kin the terminal
K
Kuh the fortune message isn't part of the notice obviously 
ZAh
ZI read through the readme and then I got exactly that message and was like "well, why not"
ZAnd I don't seem to recall an error message when I ran it strangely enough
Kit echos a message into the terminal about what the password for the key is
Kbut still, can't stress enouigh don't enable secure boot on deck hardware
Kdeck doesn't come with any keys, so enabling secure boot there can brick your device if you're not extremely careful
ZYea I mean the notice, not error
ZI ran it on Deck GNOME as well and there I even put in the right key, but nothing happened
Kare you on the
:testingThat was a while ago tho
Kah, perhaps not then
ANew HDR kernel as a part of a new release? Would a new release happen to include all of the OLED fixes?
ZI am not,
:latest
NI enrolled it and weirdly enough everything is fine
