Hi, Luca Boccassi wrote: > You can build such an image with the default configuration,
Will try to learn from the man pages. (Nevertheless an ISO would be faster to grasp and also avoid any configuration differences.) > you'll see that there is no grub.cfg in there, hence this bug report. A first attempt to understand https://salsa.debian.org/bluca/live-build/blob/master/scripts/build/binary_grub-efi leads me to https://salsa.debian.org/bluca/live-build/blob/master/scripts/build/efi-image where i believe to see the production of BOOTX64.EFI in line 65 grub-mkimage -O "$platform" -m "$memdisk_img" \ -o "$workdir/boot$efi_name.efi" -p '(memdisk)/boot/grub' \ search iso9660 configfile normal memdisk tar part_msdos part_gpt fat Reading man grub-mkimage i miss in above command the option -c, --config=FILE embed FILE as an early config which seems to be used for the BOOOTX64.EFI of debian-cd or live-wrapper. Regrettably i failed to find the corresponding spot in live-wrapper where its BOOTX64.EFI is created. (But i see the result in the ISOs.) So: Does strings $FAT_MOUNT_POINT/efi/boot/bootx64.efi | less report any GRUB configuration at the end of the output ? If not, then one should find out why debian-cd and live-wrapper do it that way instead of having a grub.cfg in the EFI System Partition. Have a nice day :) Thomas
