BunsenLabs Boot Fails with EFI and dbx Signature Errors
Asked by
MapleOrbit42
I installed BunsenLabs on a 2005 HP computer, but every boot starts with "Failed to open \EFI\debian\ - Not Found." It briefly reaches the BunsenLabs boot screen, then reports "couldn't parse dbx signatures: -74" before entering emergency mode. What do these messages mean, and how can I get the system to boot normally?
Answers
The dbx message is related to Secure Boot’s forbidden-signature database. Check the firmware setup for a Secure Boot option and disable it if it exists. However, a computer from around 2005 probably predates UEFI Secure Boot, so this may instead be a firmware or boot-mode compatibility issue. Make sure the system is booting in the same mode used during installation—legacy BIOS versus UEFI—and verify that the drive’s bootloader was installed for that mode.
Reply to this answer
The missing EFI path suggests the firmware is looking for a UEFI Debian bootloader, but the installation may have been done in legacy mode or the EFI files were not created correctly. If the computer supports both modes, choose the appropriate boot entry in its boot menu and consider reinstalling with the matching mode. On a machine this old, legacy BIOS installation is usually the more reliable choice.
Reply to this answer
Add your answer
Answers are reviewed before publication.
MapleOrbit42: I couldn’t find a Secure Boot setting, which may be because this machine is too old for it. I’ll check whether the installation and firmware are using the same boot mode.