I agree, bricks have been known to get rid of problems.

I need it for my Windows 11 install for a few games on there that require it.

That is not the purpose of Secure Boot. The purpose is to establish a chain of trust of all code running on the system from boot and as such eliminate rootkits that can hide from the OS. A classic example is the MBR bootkit. Of course that this is mostly out of the window if at some point in the chain the trusted code just runs untrusted code, like the bootloader or the OS running unsigned code. Also the implementation is terrible, a proper implementation would allow the user to use their own certificates and only their own certificates, otherwise a compromised generic certificate fucks everything up like it already happened.

To play Valorant, why else

Secure boot is in case the OS gets tainted. It only allows a signed OS to boot.

For example when new nvidia drivers are autocompiled into my Tumbleweed kernel during an update, on reboot the srcureboot asks if I want to view the new key or allow it. I then have to enter a password to add the key...otherwise it won't boot with that kernel.

You’re thinking bitlocker not secure boot

Edit: I was incorrect, see below.

I would disagree. The idea is great; eliminate preboot malware by trusting the whole boot stack. It has a place in computing and I would like to see it be something easier to work with.

Pretty much everything about how it's currently implemented is a mistake, I'll agree with.

My secure boot with hibernate works perfectly fine, or rather it did work fine before hibernate started freezing my system, secure boot or not.

Alpine is dead simple if used for what’s it’s good at. The LBU is its best feature. It’s great on shitty ARM boards that digest SD cards. I use it on NUT servers throughout my network.

Now I'm curious. What did you try that didn't work?

Yes works well for me.