package grub-efi-amd64
found 984760 2.02+dfsg1-20+deb10u4
thanks
Hello,
I also had this issue when upgrading from stretch to buster.
For me the BIOS allowed be to select the EFI image to boot, so I was
able to boot into the system that way, then the fix was to:
1) run again update-grub2 and
2)
On 7/17/21 10:09 AM, Ryan Thoryk wrote:
On 7/17/21 9:44 AM, Steve McIntyre wrote:
I found that I was using an older ARM image from last year, but that
doesn't mean the issue was fixed later. In AWS's community AMI section,
the main one I tried is listed as "debian-10-arm64-20200511-260".
On 7/17/21 9:44 AM, Steve McIntyre wrote:
Hi Ryan,
So when you say "spin up a new Debian ARM VM on AWS", what exact image
are you using here? It sounds like the build process for that image
needs to be fixed to DTRT for the platform. Then you and other users
won't be bitten by this problem...
Hi Ryan,
On Sat, Jul 17, 2021 at 09:19:22AM -0500, Ryan Thoryk wrote:
>On 7/17/21 8:18 AM, Steve McIntyre wrote:
>> On Sat, Jul 17, 2021 at 07:57:48AM -0500, Ryan Thoryk wrote:
>> EFI/debian is *NOT* wrong, it's the correct location for a system that
>> has working firmware which supports setting
On 7/17/21 8:18 AM, Steve McIntyre wrote:
On Sat, Jul 17, 2021 at 07:57:48AM -0500, Ryan Thoryk wrote:
EFI/debian is *NOT* wrong, it's the correct location for a system that
has working firmware which supports setting UEFI boot variables. If
you *also* need to write a copy of grub (etc.) to the
On Sat, Jul 17, 2021 at 07:57:48AM -0500, Ryan Thoryk wrote:
>On Sat, 10 Jul 2021 23:15:15 +0100 Colin Watson wrote:
>> In general, this means that grub-install is not installing to the place
>> that your firmware is actually booting from, which causes the core image
>> (installed to a file under
On Sat, 10 Jul 2021 23:15:15 +0100 Colin Watson wrote:
In general, this means that grub-install is not installing to the place
that your firmware is actually booting from, which causes the core image
(installed to a file under /boot/efi/ on UEFI systems) to be out of sync
with the modules
Processing control commands:
> tag -1 moreinfo
Bug #984760 [grub-efi-amd64] grub-efi-amd64: upgrade works, boot fails (error:
symbol `grub_is_lockdown` not found)
Added tag(s) moreinfo.
--
984760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984760
Debian Bug Tracking System
Contact
Control: tag -1 moreinfo
Sorry for our long delay in replying to this.
On Mon, Mar 08, 2021 at 02:20:08PM +1100, Anand Kumria wrote:
> grub went into grub rescue mode and displayed:
>
> error: symbol `grub_is_lockdown` not found
In general, this means that grub-install is not installing to the
Package: grub-efi-amd64
Version: 2.04-16
Severity: critical
Justification: breaks unrelated software
X-Debbugs-Cc: akum...@gmail.com
Dear Maintainer,
* What led up to the situation?
A Toshiba laptop with a single disk, with GPT partitions, a few days ago
performed a normal upgrade:
...
10 matches
Mail list logo
