Hi Michael! On Mon, May 13, 2019 at 10:34:46AM +0200, Michael Kesper wrote: > >Is it possible that the erroneous behaviour of grubx64.efi (not loading its >config >files when being loaded by bootnetx64.efi aka shim-signed) gets triggered by >how the shim calls grubx64? >With Debian 9, the same setup (boot the installer via UEFI PXE) worked. > >References: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928750 > https://lists.debian.org/debian-boot/2019/05/msg00076.html > https://lists.debian.org/debian-boot/2019/05/msg00084.html
Ah. Apologies, you've clearly found a bug in our setup. :-( It looks like what you're seeing is that the signed grub image is using a different $prefix setting, and now it needs help to find the grub.cfg file. The debian-installer build used to rebuild its own grub EFI image and change some config during that build (using -p "$netboot_prefix/grub"), but now we can't do that (as it would lose the signature). We need to update our netboot tree and the documentation to reflect this. -- Steve McIntyre, Cambridge, UK. st...@einval.com "Because heaters aren't purple!" -- Catherine Pitt
