[ipxe-devel] Error "Could not select: Exec format error (2e008081)" while loading EFI images via HTTP/TFTP
shouldbeq931 at gmail.com
Mon Sep 9 14:17:13 BST 2019
On Mon, Sep 9, 2019 at 1:35 PM Felix Jacobi <felix.jacobi at iserv.eu> wrote:
> Dear iPXE developers,
> I am currently testing iPXE with a notebook which seems to be unable to
> chainload EFI images via HTTP and TFTP. I tried loading a Linux kernel
> with an EFI stub included and the EFI binary of SYSLINUX.
> Both attempts results in the error message which you can see in the
> first screenshot:
As per your screenshot, the error code given is in a URL
The error provides a URL http://ipxe.org/err/2e008081
> I used the following iPXE script snippet to load the Linux kernel:
> kernel http://felix.mein-iserv.de/tftpboot/efi64/install ||
> initrd http://felix.mein-iserv.de/tftpboot/efi64/miniroot.bz2 ||
> imgargs install dn=i.local panic=5 initrd=miniroot.bz2 lang=de
> video=vesa:ywrap,mtrr vga=791 service=felix.mein-iserv.de pckey=
> consoleblank=3600 rootpwd=<redacted> hn=win-10-64-01 ||
> boot ||
> I also compiled an iPXE binary with enabled EFI basic debug facilities.
> I shot a second picture with the resulting output:
If a BIOS iPXE is able to be chainloaded, then it would indicate that it is
BIOS mode rather than UEFI mode, and this may be why it will not chain load
a UEFI iPXE
> The issue could maybe related to secure boot. In any case, I did not not
> found settings related to it in the firmware settings. On the other hand
> the iPXE binary which is also unsigned was loaded without any problem.
> So I guess for now that secure boot isn't enabled.
> Any help would be appreciated. If you need additional information please
> let me know.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ipxe-devel