You are not logged in.
Hi, everyone.
This is my very first post here, and I'd like to say hello, first.
Now, I just set up Arch on my system on a drive on its own, with systemd-boot (I absolutely adore its simplicity compared to GRUB's bloat), and I have Windows 10 Education, already installed on another NVMe drive. My notebook (a Dell Precision 7530) has Secure Boot enabled, and I'm not really willing to disable it (because Windows), so I used the instructions for PreLoader on the Arch Wiki. Now, however, I receive this strange boot screen, with a single white line across the lower part of the screen:
https://i.imgur.com/1B3UL8R.mp4
I'm not exactly sure what's causing this. I can use the arrow keys, and the white line moves down. There are apparently three options: the highest one corresponds to the systemd-boot loader to boot Arch, the middle one loads Windows Boot Manager, and the last one reboots to the UEFI setup menu.
I suppose there is some (mis-)configuration, that can be remedied. Has anyone experienced this, or does anyone have a solution? Thanks much in advance!
Last edited by SRSR333 (2019-08-17 10:19:40)
Offline
I'd like to update this post, and mark it solved. I narrowed down the problem to the fact that the boot resolution was wrong, and that was courtesy of PreLoader. I also found the need to re-sign the bootloader on every kernel update rather annoying, so I wanted another way, that had more work initially but automates everything later.
I chose to generate and sign my own keys and certificates, and then sign the linux kernel and the systemd UEFI executable using those keys. I then enrolled those keys in my UEFI firmware. Instructions here.
A note: setting the Precision's UEFI firmware in Setup mode ('Audit Mode' within the firmware settings) for some reason does not clear the Windows keys, unlike what the guide above mentions. Hence, although I performed the steps to sign Windows' bootloader, bootmgfw.efi too, it was ultimately unnecessary as the Precision's firmware has options to append the generated key files, and this made things simpler. I also used sbupdate-git to automate the signing of the kernel and bootloader executables after a pacman update.
I hope this helps someone else.
Offline