On Wed, Feb 01, 2017 at 03:24:51PM +0100, Svante Signell wrote: >Hello, > >After as long time hesitating to upgrade grub-efi* I did that today, going from >2.00-22 to 2.03~beta3-4. That upgrade did not ask me if I wanted to install >the efi file somewhere else than the default. > >Something is maybe still wrong with the patch: grub-install-extra- >removable.patch. Looking through that patch quickly I did not see any problems >though. grub-install is never called when upgrading, only update-grub? >Especially when is the grub-install option --force-extra-removable activated? > >The efi file on my box is at: >/boot/efi/EFI/Boot/bootx64.efi >where I already had a copy of the 2.00-22 version. >The upgrade did install the efi file at: >/boot/efi/EFI/debian/grubx64.efi, nowhere else.
What does # debconf-get-selections | grep grub2/force_efi_extra_removable say for you? That's the bit that's responsible for whether or not the grub-efi-* package will call grub-install with --force-extra-removable - look in the postinst file. grub-install is absolutely called when upgrading grub binary packages - it's needed to put new binaries in place. update-grub only updates the grub config file that will be used at boot. -- Steve McIntyre, Cambridge, UK. [email protected] Getting a SCSI chain working is perfectly simple if you remember that there must be exactly three terminations: one on one end of the cable, one on the far end, and the goat, terminated over the SCSI chain with a silver-handled knife whilst burning *black* candles. --- Anthony DeBoer
