You are not logged in.
Pages: 1
Hey there. I did a new Arch install yesterday. The install was straightforward and things are up and running smoothly; it's not my first Arch install as I ran it as my daily driver during college. I have a post-install question that I'm hoping to get some assistance with. Bear in mind this is pretty nitpicky/niche so even if it goes unresolved it's not going to affect me at all, but it is something I'd like to get sorted out if possible.
For full(-ish) context, my setup is configured as follows:
1TB NVMe SSD partitioned into three partitions. Partition 1 is a 512MiB EFI partition, partition 3 is a 64GiB encrypted swap partition, and partition 2 is an encrypted BTRFS partition that fills the rest of the space.
Using mkinitcpio to generate kernel images.
Other hardware is AMD 5800X3D CPU, AMD 7900XTX GPU, 64GiB memory if that matters at all.
I'm running KDE Plasma/Wayland.
I attempted to use a signed UKI for Secure Boot essentially following this write-up, but am now just using a generic kernel (more info in the question below).
My question is about the UKI itself. I ended up having to switch to a generic kernel because after updating packages I could no longer boot with Secure Boot enabled as I got an invalid signature error. I set up the various pacman hooks described in the write-up above, but it seems I must have done something wrong as things just stopped working immediately. I followed that particular set-up exactly as written and still had issues. Are there any shot-in-the-dark guesses as to something I may have missed or misconfigured?
Any help is appreciated!
Offline
Pages: 1