Yes, IK WBM is not the problem here. My systems don't show a logo at all, and they don't have a "hide logo" options.
yum13241
joined 1 year ago
I never bought my current machines. Funnily enough, they don't show any logos on bootup, (Windows Boot Manager is smth else)
Not until I can have my pretty screensavers. Yes, I care. When my laptops are on battery they don't need to S3 sleep, nor s0idle. They just show pretty animations that prompt for a password and let me in, without waiting ten years for it to wake up from its slumber
I'm a teenager and I don't talk like that.
Just:
Capitalize your sentences Stop spamming emoticons, emojis, and exclamation marks Don't be naive Use common sense
And you'll be fine.
Hardy har har.
I installed Linux Mint in a VM when I was like, 10
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.
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.
That's just bad program design.