Thanks for the suggestion of textual representation of all uefi error codes.
Well that seems interesting, however this kinda error handling I found
in a lot of places in the grub UEFI part. So i don't think it is
ideal, if i do then there must be a large set of modifications in the
entire UEFI par
Thanks for the suggestion of textual representation of all uefi error codes.
Well that seems interesting, however this kinda error handling I found
in a lot of places in the grub UEFI part. So i don't think it is
ideal, if i do then there must be a large set of modifications in the
entire UEFI par
On linux command also it requires to improve the way `StartImage and
`LoadImage` is checked.
But first there is things i need to point, while currently the command
is did well by printing the hex value of the status of `StartImage`
however some UEFI status code documentation is bad and not well
do
I think it would be better if we had a table of strings with the
textual representation of all UEFI status codes and have that printed
instead of unreadable hex salad.
Mate
On Fri, Apr 25, 2025 at 1:18 PM khaliid caliy wrote:
>
> This patch addresses some undescriptive error messages that grub
>
This patch addresses some undescriptive error messages that grub
chainloader command returns when issue encountered, specifically
during the loading of the uefi image or starting the image.
As per uefi UEFI specification (2.11) boot service functions
`StartImage()` and `LoadImage` return error cod
