Bug 437969 - Replace GRUB with systemd-bootloader
Summary: Replace GRUB with systemd-bootloader
Status: RESOLVED NOT A BUG
Alias: None
Product: neon
Classification: KDE Neon
Component: Live/Install images (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-01 20:57 UTC by Lua
Modified: 2021-06-06 21:51 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Lua 2021-06-01 20:57:32 UTC 
When encrypting the disk, GRUB:

- Decrypts the disk very, vert slowly;
- Doesn't show the blinking underscore indicating activity.

systemd-bootloader fix this issues.
Comment 1 Lua 2021-06-01 20:58:52 UTC 
- Doesn't show the blinking underscore indicating activity. Is not possible to notice if the decryption really started.*
- Enters into the rescue mode after only one wrong attempt of decrypting, which is very frustrating because the user needs to press Control Alt Del when that happens.
Comment 2 Lua 2021-06-06 21:51:47 UTC 
Whoops, systemd-boot doesn't support encryption: https://www.freedesktop.org/wiki/Software/systemd/systemd-boot/

> systemd-boot loads boot entry information from the EFI system partition (ESP), usually mounted at /efi/, /boot/, or /boot/efi/ during OS runtime, as well as from the Extended Boot Loader partition if it exists (usually mounted to /boot/). Configuration file fragments, kernels, initrds and other EFI images to boot generally need to reside on the ESP or the Extended Boot Loader partition.

(The EFI partition is unencrypted).