You are not logged in.
Pages: 1
Hello
I installed the cachyos kernel as a test, but since it did not meet my expectations, I deleted it again. Strangely enough, the system is still trying to sign the kernel data, even though I've installed it everywhere. Anyway, I think that's what I have.
Signing /boot/EFI/Linux/arch-linux-fallback.efi
✓ Signed /boot/EFI/Linux/arch-linux-fallback.efi
==> Post processing done
(5/9) Führe Skript aus, um bestimmte .desktop-Dateien zu entfernen
(6/9) Compiling GSettings XML schema files...
(7/9) Updating icon theme caches...
(8/9) Updating the desktop file MIME type cache...
(9/9) Signing EFI binaries...
Generating EFI bundles....
failed signing /boot/EFI/Linux/arch-linux-cachyos-fallback.efi: /boot/EFI/Linux/arch-linux-cachyos-fallback.efi does not exist
failed signing /boot/EFI/Linux/arch-linux-cachyos.efi: /boot/EFI/Linux/arch-linux-cachyos.efi does not exist
File has already been signed /boot/EFI/Linux/arch-linux-fallback.efi
File has already been signed /boot/EFI/Linux/arch-linux.efi
File has already been signed /boot/EFI/systemd/systemd-bootx64.efi
✓ Signed /boot/vmlinuz-linux
✓ Signed /usr/lib/systemd/boot/efi/systemd-bootx64.efi.signed
File has already been signed /boot/EFI/BOOT/BOOTX64.EFI
Last edited by Tealk (2024-10-24 16:52:45)
Offline
Try removing the entries with sbtcl remove-file ?
(see man sbctl for details)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Thanks, I didn't realize that sbctl has its own database
Offline
Pages: 1