Graf Zahl wrote: ↑Mon Nov 28, 2022 1:21 am
Cacodemon345 wrote: ↑Mon Nov 28, 2022 12:03 am
There will be always ARM SBCs that aren't infested with Secure Boot bullshit, but there may not be one for x86 computers in the future.
And for the average user that will be beneficial - how?
If there are problems on the Linux side with Secure Boot, it's mainly a failing of the affected distros. The concept itself is absolutely fine for better system protection.
About this, is there any information available telling us which Intel chipsets are affected by reduced SSBO performance?
Is this something only relevant on older ones or does it still persist on current hardware?
About Secure Boot
As a concept, Secure Boot is fine. (It should
be called Bootloader Signature Enforcement because that's all it does)
The problem is M$ decided to unilaterally deny anything GPLv3 to be signed ever (shim being a notable exception, GRUB isn't even signed), and signing the bootloader and adding it to the Secure Boot database isn't straight forward.
Essentially, out of the box M$ has FULL CONTROL
over what will boot on your PC. Anything signed with their key will boot. Anything that isn't will just pop up a message designed to scare you. All they have to do is to push an update thru the universal backdoo- I mean Windows Update.
The first thing I do is turn off Secure Boot. Why? I know what I'm doing and I don't want to bother with signing the bootloader on every update (on Arch this can actually be quite frequent)
The distro I use (EndeavourOS) actually doesn't support secure boot OOTB anyway (and neither does arch
I'm not stupid enough to leave my laptop lying around in my hotel room for a
maid to try to open up my PC and replace the BIOS chip. If I caught her the first thing I'd do is sue. (read:
Every backend available in GZD right now works fine for me, GLES performing best, and the others barely hitting 60 FPS.
Also, WHY IN HELL are 4GB laptops still sold in 2022 (soon to be 2023?)
Once I found a laptop in a store that proudly said that its graphics drivers are Microsoft drivers with all these absurd claims. "High performance" etc.
I dunno about you, but MS drivers can't even play Q13K of all things, w/o screen tearing.
To answer Cacodemon: If you build it yourself you automatically know what stuff is in there. So just disable it
To add one more thing: Manjaro (an Arch derivative) isn't exactly a supportable OS. Reason being that they do all sorts of shenanigans regarding their repos and in general can't be trusted to not have their certs expire again, among other things. Since GZDoom is on the AUR AND a Flatpak, a bug could arise from Manjaro effectively being always 2 weeks out of date. (read:https://manjaro.snorlax.sh