Closed mmstick closed 6 years ago
Yes, I believe we are interested in using EFISTUB in some fashion. I need to learn more about systemd-boot.
@jackpot51 It's rather simple. Basically, you specify each boot option as a conf
file within /boot/efi/loader/entries
, and an entry looks like so:
title Solus 3
linux /EFI/com.solus-project/kernel-com.solus-project.current.4.14.8-41
initrd /EFI/com.solus-project/initrd-com.solus-project.current.4.14.8-41
options root=PARTUUID=647b989d-b034-4e81-8891-b6e2065b354f quiet loglevel=3 splash systemd.show_status=false rw radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=/dev/sda2 rw quiet rootflags=subvol=@arch
Then in /boot/efi/loader/loader.conf
, you can specify the timeout value and default entry.
timeout 3
default Solus-current-4.14.8-41
And that's it. I know that Solus is also using clr-boot-manager in combination with systemd-boot for vendoring and garbage collection of kernels and entries.
Seeing that we have made the switch to systemd-boot I am going to close this issue/question.
Will there be plans to support selecting systemd-boot as a simpler/faster alternative to GRUB for EFI installs?