Secure Boot is just Bootloader Signature Enforcement controlled by M$, it's not gonna prevent Superfish 2.0 from happening.
Unfortunately, I don't have a coreboot-able system. When I move out I'll make that a priority.
yum13241
joined 2 years ago
That's called CSM, and Intel removed it in late 2020. I'm not sure if AMD still has it, but they still have S3 sleep afaik. Go Team Red for your next buy, I am too.
My HP crapbook doesn't have this OEM logo bullshit. Only the windows bootloader shows it, and the logo file is stored in the BGRT. So I don't think I'm affected unless the WBM or systemd-boot have this vuln.
Mine:
1. Screen turns on
2. I pick EndeavorOS in systemd-boot
3. It starts spitting out logs (I love this behavior)
4. It switches modes once the backlight is loaded
5. I log in
6. KDE loads
I will never understand people who install Plymouth, it just adds complexity in the boot process. If your distro installs this then I understand why: so it doesn't look like you're "hacking the government". If your distro doesn't install it and you install it then you probably picked the wrong distro.
Mine only switches modes once, on load save backlight.
Secure Boot is an utter piece of bullshit from the depths of hell.
Switch v2, modded? I thought that was impossible.
Pros: giving the finger to Nintendo
Cons: you'll lose online.
I know of one Fox, and he is Fox McCloud.
The funny thing is, there was this guy on YouTube who did the exact same thing, before Bing AI did. SunnyV2 made a video about it.
Basically, the Manjaro team has no idea what they're doing.
The ManjarNO sheep can fuck off to Reddit for all I care.
I installed Linux Mint in a VM when I was like, 10