Bug#988876: grub-efi-amd64: outb command no longer works

UEFI Secure Boot is disabled. The machine is a Macbook8,3 converted to a pure Linux box, however. So, the EFI firmware might be damaged. Thank you for the clarification. In order to disable the (not properly supported) discrete graphics card, I need to execute the mentioned outb commands. Indee

Bug#988876: grub-efi-amd64: outb command no longer works

Package: grub-efi-amd64 Version: 2.02+dfsg1-20+deb10u4 Severity: important Tags: d-i After a fresh install of debian buster a grub.cfg containing an outb command throws the error "outb command not found" (and, in my case, cannot start lightdm thereafter). This problem does not appear when downgr

Bug#984520: error : symbol 'grub_register_command_lockdown' not found

Hi Dieter, the same error message for the update of grub-pc instead of grub-efi-amd64 has already been reported before this as bug #984426 . -- Marco signature.asc Description: This is a digitally signed message part.

Bug#984520: 'error: symbol "grub_register_command_lockdown" not found' and then lightdm fails to start

Package: grub-efi-amd64 Version: 2.02+dfsg1-20+deb10u4 Severity: critical Tags: d-i Justification: breaks unrelated software Hi, after the recent update to grub2/202+dfsg1-20+deb10u4, during boot the mentioned error is thrown. After that, boot continues but lightdm cannot be started anymore. Th

Bug#984426: grub suddenly does not boot and ends up with "grub_register_command_lockdown not found"

I have the same error message after the update to grub2/2.02+dfsg1- 20+deb10u4, but with grub-efi-amd64* instead of grub-pc. After pressing the "arbitrary key", Debian boots but fails to start lightdm. Should I report a new bug? Marco -- codecivil Dr. Marco Kühnel ICT Services, V