Switch to shim-systemd-boot for secure boot support. After installing this update and running clr-boot-manager update,
clr-boot-manager will auto setup shim & systemd-boot and create a new UEFI boot entry called 'Solus Linux Bootloader'
which should be able to be booted from with Secure Boot enabled after performing the one step time of enrolling the
solus certificate from the Mok Management screen.
Details
Details
- Reviewers
- None
- Group Reviewers
Triage Team - Commits
- R3347:f9a9d4baf741: clr-boot-manager: Switch to shim-systemd-boot for secure boot support
- Install this package and reboot WITHOUT running clr-boot-manager update
- If a kernel update is available: Install the kernel update and reboot
- If no kernel update is available: Run clr-boot-manager update and reboot
- Attempt to boot from the old UEFI entry
- Attempt to boot from the new 'Solus Linux Bootloader' UEFI entry
- Reboot and enable secure boot, enroll default keys if neccessary
- If your UEFI firmware provides such an option: Set the 'Image Execution Policy' to 'Deny Execute' upon secure boot violation (names may vary).
- Attempt to boot from the old UEFI entry (should fail with secure boot violation)
- Attempt to boot from the new 'Solus Linux Bootloader' entry
- This should launch Mok Manager with a warning about a security violation. Press enter to continue then choose 'Enroll Key from Disk'. Enroll 'SOLUSESP/solus-enroll-me.cer'.
- Reboot, and you should successfully boot.
Diff Detail
Diff Detail
- Repository
- R3347 clr-boot-manager
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Comment Actions
There is a bug where mmx64.efi doesn't get copied into the ESP. Seen it happen twice now.