• dingdongitsabear@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 year ago

    yeah, if you don’t have an encrypted drive (which I’m gonna do on a laptop NEVER) on some OEMs this can look semi-seamless.

    here’s what it looks like on a laptop:

      1. OEM logo
      1. screen goes blank, backlight off
      1. light on, OEM logo
      1. blank screen
      1. decrypt password
      1. blank screen
      1. loading spinner with OEM logo
      1. gdm/sddm login screen
      1. blank screen
    • 9a. (sddm) loading animation
    • 9b. (sddm) jerk when fractional scaling kicks in
      1. and finally there’s the desktop

    with additional mode switching interjected and occasionally the horror that is GRUB inserts a ‘Loading blah blah’ text message; thankfully we’re getting rid of that.

    • yum13241@lemm.ee
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      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.