Your message dated Sun, 20 Dec 2015 20:04:33 +0000
with message-id <[email protected]>
and subject line Re: Bug#808366: grub-efi-amd64 -- error: symbol
'grub_efi_find_last_device_path' not found
has caused the Debian Bug report #808366,
regarding grub-efi-amd64 -- error: symbol 'grub_efi_find_last_device_path' not
found
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
808366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808366
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grub-efi-amd64
Version: 2.02~beta2-33
Severity: serious
dpkg -l "grub*" | egrep "^ii"
ii grub-common 2.02~beta2-33 amd64 GRand Unified Bootloader
(common files)
ii grub-efi 2.02~beta2-33 amd64 GRand Unified Bootloader,
version 2 (dummy package)
ii grub-efi-amd64 2.02~beta2-33 amd64 GRand Unified Bootloader,
version 2 (EFI-AMD64 version)
ii grub-efi-amd64-bin 2.02~beta2-33 amd64 GRand Unified Bootloader,
version 2 (EFI-AMD64 binaries)
ii grub2-common 2.02~beta2-33 amd64 GRand Unified Bootloader
(common files for version 2)
On a system that dual boots Linux and Windows 10, the latest grub-efi
gives this error:
error: symbol 'grub_efi_find_last_device_path' not found
when attempting to boot Windows 10 after an update-grub is performed.
Linux will boot correctly; however, an attempt to boot Windows 10 will
give this error and say "press any key..." and bring one back to the OS
menu.
There is a workaround, which is to downgrade back to 2.02~beta2-32, and
Windows will boot correctly.
--- End Message ---
--- Begin Message ---
On Sat, 2015-12-19 at 10:14 -0600, S. R. Wright wrote:
> On 12/19/2015 10:04 AM, Ian Campbell wrote:
> > On Sat, 2015-12-19 at 09:52 -0600, S. R. Wright wrote:
> >> Ian:
> >>
> >> Attached is the info you suggested, pre- and post-upgrade. Was
> never
> >> prompted to answer any questions or than to continue the upgrade.
> > I can't explain how it got there, but I think that this
> > Boot/bootx64.efi is what your system is booting from and it doesn't
> > appear to be being updated. I expect that the reason this is
> present
> > at all is that your BIOS is bug gy in the way the extra removable
> > option is intended to workaround, if it wasn't you could likely
> > convince your BIOS to boot thebconf-set-selections
> debian/grubx64.efi
> > by playing with efibootmgr etc but I think you best bet would be to
> > set grub2/force_efi_extra_removable=true, try (as root): echo
> > "grub-efi-amd64 grub2/force_efi_extra_removable boolean true" | de
> > bconf-set-selections and then upgrade or reconfigure the package
> and
> > it should be updated. Do you have any idea what might have happened
> at
> > 04:48 on Dec 12? Ian.
>
> Ian, your suggestion appeared to have worked. Ta!
Great.
> As far as what
> happened @ 4.48a on the 12th, I really cannot say as I was asleep.
No worries, I think since we've no idea how the binary got there in the
first place there isn't much else we can investigate or fix regarding
what caused the initial problem, so I'm closing the bug.
Ian.
--- End Message ---
