Upgrade to grub 2.14 from 2.12 on Debian can no longer load Linux initrd

horsey_guy <[email protected]> Fri, 06 Mar 2026 02:20:49 +0000
Newsgroups gmane.comp.boot-loaders.grub.bugs
Message-ID <kzS0ABfrkbj593MAnT-UAp3K8AIk39A1oRglNsWF9Bg0ZCmo-hQhSErJdt2cooRT4AmmQZWvZwj-sEiQiD8mwayFwU4GMYDvxpG_C9G3WQU=@proton.me>
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--------1aa0e05778159087dd45bc40be4b51a60e35bb093f207a85a06dca8b2403d5c3
Content-Type: multipart/mixed;boundary=---------------------74b0b013cf34baa63294255734ec8a77

-----------------------74b0b013cf34baa63294255734ec8a77
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;charset=utf-8

I have been recommended to send this question on Unix&Linux Stackexchange =
https://unix.stackexchange.com/questions/804824/upgrade-to-grub-2-14-from-=
2-12-on-debian-can-no-longer-load-linux-initrd to here.

In summary, upgrading from 2.12 to 2.14 on Debian prevents the initrd from=
 being loaded. The errors that grub gives are:
```
error: ../../../grub-core/loader/efi/linux.c:437:failed to install protoco=
ls
error: ../../../grub-core/loader/efi/linux.c:227:cannot load image
```

The first error intermittently occurs, but the second one always occurs.

I use Debian Sid/Experimental with an LUKS2 encrypted root partition.

The answer mentions how the firmware creates the "failed to install protoc=
ols" error and "There is no way to force legacy handover protocol. You can=
 try installing older shim (pre-16.1) to see if it changes anything but it=
 is not an option in the long run."
-----------------------74b0b013cf34baa63294255734ec8a77
Content-Type: application/pgp-keys; filename="publickey - [email protected] - 0xEC8A06ED.asc"; name="publickey - [email protected] - 0xEC8A06ED.asc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="publickey - [email protected] - 0xEC8A06ED.asc"; name="publickey - [email protected] - 0xEC8A06ED.asc"

LS0tLS1CRUdJTiBQR1AgUFVCTElDIEtFWSBCTE9DSy0tLS0tCgp4ak1FYUlGTnZoWUpLd1lCQkFI
YVJ3OEJBUWRBK0RncGlib1VTWXlzS2U4bC9GOU94NGREQVB5OWNIRXcKMFZ6cEZRUjVHeEhOSzJo
dmNuTmxlVjluZFhsQWNISnZkRzl1TG0xbElEeG9iM0p6WlhsZlozVjVRSEJ5CmIzUnZiaTV0WlQ3
Q3dCRUVFeFlLQUlNRmdtaUJUYjREQ3drSENaQW15Z3VrQ1ZYRFZrVVVBQUFBQUFBYwpBQ0J6WVd4
MFFHNXZkR0YwYVc5dWN5NXZjR1Z1Y0dkd2FuTXViM0puUFErVDFnMVRsNG1NK0NGNjRNT1EKSm0r
UGljZzhSeXpHbUdQNjYyS01qeHNERlFvSUJCWUFBZ0VDR1FFQ213TUNIZ0VXSVFUc2lnYnQ3Wm5p
CmJicGpMU3dteWd1a0NWWERWZ0FBRGhVQkFPREVGMUFWbjdVOS90NE9PTnlYQXdhWWJhTjkxaE94
WmZLVgp0b0psVzNZMEFQOVFRYjZWOXltMjVwWUk2QVp3SlZGK3d6VFlsb3ZhZmI5UFdac0NnbC9h
RE00NEJHaUIKVGI0U0Npc0dBUVFCbDFVQkJRRUJCMEFRQVhoTDRxMWJVU0JWRlpic0t3ekxmTlNz
dWw3Unp0VDZNVTRWClNjNENRQU1CQ0FmQ3ZnUVlGZ29BY0FXQ2FJRk52Z21RSnNvTHBBbFZ3MVpG
RkFBQUFBQUFIQUFnYzJGcwpkRUJ1YjNSaGRHbHZibk11YjNCbGJuQm5jR3B6TG05eVovUFpwT2JJ
UHVIQkd0SFlNNFpHa0tvQlk2RXUKMm1HNStMclVyMjNaTlI3YkFwc01GaUVFN0lvRzdlMlo0bTI2
WXkwc0pzb0xwQWxWdzFZQUFILzRBUDBjCnJESytzUWl3UHFWbnh2VGE1SlNma09mdExPV0YvajVP
NXgxZ0NDdHJMd0VBNWs1Nm1CVkhsb2JjWEljWgplTnBya2hpdTZ5eFZTbVpGY1Z5dGgveHNYZ0E9
Cj1FVjdXCi0tLS0tRU5EIFBHUCBQVUJMSUMgS0VZIEJMT0NLLS0tLS0K
-----------------------74b0b013cf34baa63294255734ec8a77--

--------1aa0e05778159087dd45bc40be4b51a60e35bb093f207a85a06dca8b2403d5c3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wrsEARYKAG0FgmmqOegJECbKC6QJVcNWRRQAAAAAABwAIHNhbHRAbm90YXRp
b25zLm9wZW5wZ3Bqcy5vcmfHMAmixK4E9J4J4LY7BxAxdK0FAww27aBh6dWl
VSqRbxYhBOyKBu3tmeJtumMtLCbKC6QJVcNWAAAaJQD/WbnesIONMQ8Dc7dV
eo2IIePI1qKTBVBSFafyYAEkWdYBANHoaTw09kJ1yp+Brywc4uXbJpCMOQuS
WiyZwVsXfzYC
=k67p
-----END PGP SIGNATURE-----


--------1aa0e05778159087dd45bc40be4b51a60e35bb093f207a85a06dca8b2403d5c3--