Comment 7 for bug 1313620

Well that explains it!

Of course Image isn't an EFI application! It's a regular kernel. And if
someone gets around to adding efistub to linux linaro, surely Image would
still not be an EFI application and there would be another file in there
that had the stub? (ie. we'd have both a regular kernel Image file AND an
EFI stubbed kernel)

On 7 May 2014 04:20, "Roy Franz" <email address hidden> wrote:
>
> "Image" isn't a shell command, but rather the name of the EFI
> application that is being run - in this case it should be a kernel built
> with the EFI stub.
>
> I have seen this error message in 3 different situations:
> 1) The file trying to be run is not an EFI application
> 2) The EFI application is of a different architecture (arm32 vs arm64)
> 3) Something wrong with the EFI header. We shouldn't be hitting this
now, but during development I saw this when I didn't have the header right.
>
> In this case that this is failing, have we confirmed what kind of file
> "Image" is? I think we'd get a different error message if the file was
> completely missing, so I think something was there with the right name.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1313620
>
> Title:
> Image shell command not supported
>
> Status in UEFI Support in Linaro:
> New
>
> Bug description:
> When UEFI runs, it attempts to autorun the "startup.nsh" script. This
> script contains the command "Image <params>".
>
> However, "Image" is not a valid UEFI shell command, so it an error is
> reported, thus:
>
> "Error reported: Unsupported"
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linaro-uefi/+bug/1313620/+subscriptions