Package: grub2-common Version: 2.04-10 `grub-install` fails to install properly when run on a system using U-Boot's implementation of the EFI protocol (potentially also effects package grub-efi-arm64, perhaps this should be against src:grub2).
Since a Tianocore-based implementation of the EFI protocol is also available, I can provide more imformation. A useful distinction is U-Boot's EFI implementation does NOT implement EFI variables. This seems a plausible method to distinguish U-Boot's partial EFI implementation from Tianocore's complete EFI implementation. On the U-Boot implementation grubaa64.efi needs to be installed as /boot/efi/EFI/BOOT/bootaa64.efi instead. Roughly akin to --bootloader-id=BOOT, plus an extra rename. I suspect I may be filing other bugs soon. (the platform is a Raspberry Pi 4B, the Tianocore implementation is quite workable except too many pieces of software assume device-tree on ARM and won't work with ACPI) -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | ehem+sig...@m5p.com PGP 87145445 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
