Comment 74 for bug 1865515
Revision history for this message
| Julian Andres Klode (juliank) wrote | #74 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
To the best of our knowledge this issue has been worked around in shim 15.4-0ubuntu1
shim (15.4-0ubuntu1) hirsute; urgency=medium
[ Dimitri John Ledkov ]
* deiban/rules: start using DISABLE_
chainloading shim to shim, and shim to kernel.efi.
so it should no longer be affecting anyone.
But then recent comments shifted to an entirely different topic where the kernel was loaded successfully and then failed to boot, and I think the bug is not meaningful to continue discussing on because we're now talking about vastly different things.
If you/the customers still see issues, I'd advise filing a new bug.
The advise about using exit instead of chainloading is still, and increasingly moreso, valid, as MAAS's approach of chainloading is inappropriate as it breaks all the measurements of TPM, TDX, etc and so becomes increasingly less useful.