Re: [ipxe-devel] Error "Could not select: Exec format error (2e008081)" while loading EFI images via HTTP/TFTP
On Tue, 10 Sep 2019 at 13:25, Felix Jacobi wrote: > > Hi Christian, > > > My guess is that your server returns something other than what you > > expect it to - maybe because it is ipxe, and not a browser, and your > > server detects this. or something similar which "corrupts" the data. > > I checked that the URL is correct, it definitely serves a Linux kernel > image: > > felix.mein-iserv.de ~ # wget -q > https://felix.mein-iserv.de/tftpboot/efi64/install > felix.mein-iserv.de ~ # file install > install: Linux kernel x86 boot executable bzImage, version > 5.0.0-27-generic (buildd@lgw01-amd64-016) #28-Ubuntu SMP Tue Aug 20 > 19:53:07 UTC 2019, RO-rootFS, swap_dev 0x8, Normal VGA > > > use imgstat before boot > > verify that it says that it is an EFI image. > > Also verify that the filesize is correct. > > And that you have the correct url (that install is the actual image) > > Also used imgfetch and imgstat to verify that the image has the > correct size in bytes: > > Broken notebook: > https://community.iserv.eu/upload/faepiegho7oosh9ut8zieshe2PhaavieVohF0cooxi8ahgho8aic6Aicee4eikee/broken.jpg > Other working device: > https://community.iserv.eu/upload/faepiegho7oosh9ut8zieshe2PhaavieVohF0cooxi8ahgho8aic6Aicee4eikee/working.jpg > > Image on boot server: > > felix.mein-iserv.de ~ # ls -la /srv/tftpboot/efi64/install > > lrwxrwxrwx 1 root root 35 Sep 3 13:20 /srv/tftpboot/efi64/install -> > ../opsi-linux-bootimage/x64/vmlinuz > felix.mein-iserv.de ~ # ls -la > /srv/tftpboot/opsi-linux-bootimage/x64/vmlinuz > lrwxrwxrwx 1 root root 24 Sep 3 13:20 > /srv/tftpboot/opsi-linux-bootimage/x64/vmlinuz -> vmlinuz-5.0.0-27-generic > felix.mein-iserv.de ~ # ls -la > /srv/tftpboot/opsi-linux-bootimage/x64/vmlinuz-5.0.0-27-generic > -rw-r--r-- 1 root root 8,4M Aug 20 21:25 > /srv/tftpboot/opsi-linux-bootimage/x64/vmlinuz-5.0.0-27-generic > felix.mein-iserv.de ~ # du --bytes > /srv/tftpboot/opsi-linux-bootimage/x64/vmlinuz-5.0.0-27-generic > 8711928 /srv/tftpboot/opsi-linux-bootimage/x64/vmlinuz-5.0.0-27-generic > > > in your last image you can see that your imagefetch is not able to > > detect the fileformat. > > The interesting point is that the broken notebook seems to does not > detect the image as EFI binary. The working reference device seems to > doesn't have this problem. > > > And yes, disable secure boot, unless you have both ipxe, and the > > kernel signed by a certificate that has been added inside firmware > > config. > > Yeah, I will try to research on that point. As already mentioned before > there is no such option in the firmware. That either implies that there > is no support for secure boot or secure boot is always active. I am not > sure if the latter case is even possible, as the iPXE binary itself is > loaded without problems at the beginning. > > > You can follow the link to see each place in the sourcecode where this > > error can come from. (also, always include the link that are shown > > together with the error message to get help easier) > > I will include the link to the error code here afterwards to ease > comprehending this thread for other ones: > > http://ipxe.org/err/2e0080 > > Thank you for your time. > > Regards, Felix > > -- > Best regards, > > Felix Jacobi > > IServ GmbH > Bültenweg 73 > 38106 Braunschweig > > Phone: 0531-2243666-0 > Fax:0531-2243666-9 > E-mail: felix.jac...@iserv.eu > Web:https://www.iserv.eu > Tax ID: DE265149425 > Executive directors:Benjamin Heindl, Martin Hüppe, Jörg Ludwig > Principles on privacy: https://www.iserv.eu/privacy > > Verify my identity: https://github.com/FelixJacobi/gpg-keys > I'm starting to suspect firmware here, You might want to start an efi shell instead, from USB or similar, and try to boot the kernel from there. ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
Re: [ipxe-devel] Error "Could not select: Exec format error (2e008081)" while loading EFI images via HTTP/TFTP
On 10-09-2019 16:25, Felix Jacobi wrote: > Mailing list subscriber wrote > > > The original posting, IIRC, had || at the end of each line in the > > iPXE script. > > I did read the || as "or" and did ignore it. > > Yeah, that's correct. I don't remember the exact reason why I added the > || , but it seems to prevent iPXE from exiting immediately if an error > like the "Exec format error" one occurs. If remove trailing || from the > commands, iPXE just hands over the control over the boot process to the > firmware after the error is raised by the boot command. > > > How does iPXE script of OP behave without those ||? > > Exactly the same behavior as before except for that the subsequently > commands also complaining about the exec format error with the same message. Time to visit https://community.iserv.eu/upload/eitae6OhM9oos0EyefeiNaxathoLoo4PhohPheijaiPiphoofeix5thoo3ogah8j/Picture%202.jpg again, it reveals http://ipxe.org/err/7f048182 Cheers I.P. P.S. I'm subscribed to mailinglist, no need to CC me ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
Re: [ipxe-devel] Error "Could not select: Exec format error (2e008081)" while loading EFI images via HTTP/TFTP
On 10-09-2019 15:40, Felix Jacobi wrote: > Geert wrote: > >> >> So back to Error "Could not select: Exec format error (2e008081)" while >> loading EFI images via HTTP/TFTP >> >> My educated guess is with Christian Nilssons posting from yesterday >> the file gets damaged during transport >> >> Please pursuit this interresting problem > > I compiled an iPXE binary with the DIGEST_CMD option included as > described in http://ipxe.org/dev/drvtest/md5sum. > > The output of the md5sum command looks fine compared to the test on the > boot server: > > felix.mein-iserv.de ~ # md5sum /srv/tftpboot/efi64/install > 577a82ef6530d4a17c651617cfdd98a2 /srv/tftpboot/efi64/install > > https://community.iserv.eu/upload/pahquei9agohmeekahcesaimoiG9Eg9keathawaev5lei2ieQuaiwee3au9Avaqu/md5sum.jpg > > So I guess that the file is transferred undamaged as already implied by > the byte size comparison. Mmm. Interresting. The original posting, IIRC, had || at the end of each line in the iPXE script. I did read the || as "or" and did ignore it. How does iPXE script of OP behave without those ||? Regards Geert Stappers DevOps engineer at Hendrikx ITC ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
Re: [ipxe-devel] Error "Could not select: Exec format error (2e008081)" while loading EFI images via HTTP/TFTP
Hi Geert, > > So back to Error "Could not select: Exec format error (2e008081)" while > loading EFI images via HTTP/TFTP > > My educated guess is with Christian Nilssons posting from yesterday > the file gets damaged during transport > > Please pursuit this interresting problem I compiled an iPXE binary with the DIGEST_CMD option included as described in http://ipxe.org/dev/drvtest/md5sum. The output of the md5sum command looks fine compared to the test on the boot server: felix.mein-iserv.de ~ # md5sum /srv/tftpboot/efi64/install 577a82ef6530d4a17c651617cfdd98a2 /srv/tftpboot/efi64/install https://community.iserv.eu/upload/pahquei9agohmeekahcesaimoiG9Eg9keathawaev5lei2ieQuaiwee3au9Avaqu/md5sum.jpg So I guess that the file is transferred undamaged as already implied by the byte size comparison. Regards, Felix -- Best regards, Felix Jacobi IServ GmbH Bültenweg 73 38106 Braunschweig Phone: 0531-2243666-0 Fax:0531-2243666-9 E-mail: felix.jac...@iserv.eu Web:https://www.iserv.eu Tax ID: DE265149425 Executive directors:Benjamin Heindl, Martin Hüppe, Jörg Ludwig Principles on privacy: https://www.iserv.eu/privacy Verify my identity: https://github.com/FelixJacobi/gpg-keys ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
Re: [ipxe-devel] Error "Could not select: Exec format error (2e008081)" while loading EFI images via HTTP/TFTP
On 10-09-2019 13:36, Felix Jacobi wrote: > On 10.09.19 at 13:25, Felix Jacobi wrote: >> > http://ipxe.org/err/2e0080 > >> Yeah, I will try to research on that point. As already mentioned before >> there is no such option in the firmware. That either implies that there >> is no support for secure boot or secure boot is always active. I am not >> sure if the latter case is even possible, as the iPXE binary itself is >> loaded without problems at the beginning. > > I installed a Windows manually on the broken notebook, Windows says via > the system information program that secure boot isn't active. So back to Error "Could not select: Exec format error (2e008081)" while loading EFI images via HTTP/TFTP My educated guess is with Christian Nilssons posting from yesterday the file gets damaged during transport Please pursuit this interresting problem Regards Geert Stappers ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
Re: [ipxe-devel] Error "Could not select: Exec format error (2e008081)" while loading EFI images via HTTP/TFTP
On 10.09.19 at 13:25, Felix Jacobi wrote: > Yeah, I will try to research on that point. As already mentioned before > there is no such option in the firmware. That either implies that there > is no support for secure boot or secure boot is always active. I am not > sure if the latter case is even possible, as the iPXE binary itself is > loaded without problems at the beginning. I installed a Windows manually on the broken notebook, Windows says via the system information program that secure boot isn't active. Regards, Felix -- Best regards, Felix Jacobi IServ GmbH Bültenweg 73 38106 Braunschweig Phone: 0531-2243666-0 Fax:0531-2243666-9 E-mail: felix.jac...@iserv.eu Web:https://www.iserv.eu Tax ID: DE265149425 Executive directors:Benjamin Heindl, Martin Hüppe, Jörg Ludwig Principles on privacy: https://www.iserv.eu/privacy Verify my identity: https://github.com/FelixJacobi/gpg-keys signature.asc Description: OpenPGP digital signature ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
Re: [ipxe-devel] Error "Could not select: Exec format error (2e008081)" while loading EFI images via HTTP/TFTP
Hi Christian, > My guess is that your server returns something other than what you > expect it to - maybe because it is ipxe, and not a browser, and your > server detects this. or something similar which "corrupts" the data. I checked that the URL is correct, it definitely serves a Linux kernel image: felix.mein-iserv.de ~ # wget -q https://felix.mein-iserv.de/tftpboot/efi64/install felix.mein-iserv.de ~ # file install install: Linux kernel x86 boot executable bzImage, version 5.0.0-27-generic (buildd@lgw01-amd64-016) #28-Ubuntu SMP Tue Aug 20 19:53:07 UTC 2019, RO-rootFS, swap_dev 0x8, Normal VGA > use imgstat before boot > verify that it says that it is an EFI image. > Also verify that the filesize is correct. > And that you have the correct url (that install is the actual image) > Also used imgfetch and imgstat to verify that the image has the correct size in bytes: Broken notebook: https://community.iserv.eu/upload/faepiegho7oosh9ut8zieshe2PhaavieVohF0cooxi8ahgho8aic6Aicee4eikee/broken.jpg Other working device: https://community.iserv.eu/upload/faepiegho7oosh9ut8zieshe2PhaavieVohF0cooxi8ahgho8aic6Aicee4eikee/working.jpg Image on boot server: felix.mein-iserv.de ~ # ls -la /srv/tftpboot/efi64/install lrwxrwxrwx 1 root root 35 Sep 3 13:20 /srv/tftpboot/efi64/install -> ../opsi-linux-bootimage/x64/vmlinuz felix.mein-iserv.de ~ # ls -la /srv/tftpboot/opsi-linux-bootimage/x64/vmlinuz lrwxrwxrwx 1 root root 24 Sep 3 13:20 /srv/tftpboot/opsi-linux-bootimage/x64/vmlinuz -> vmlinuz-5.0.0-27-generic felix.mein-iserv.de ~ # ls -la /srv/tftpboot/opsi-linux-bootimage/x64/vmlinuz-5.0.0-27-generic -rw-r--r-- 1 root root 8,4M Aug 20 21:25 /srv/tftpboot/opsi-linux-bootimage/x64/vmlinuz-5.0.0-27-generic felix.mein-iserv.de ~ # du --bytes /srv/tftpboot/opsi-linux-bootimage/x64/vmlinuz-5.0.0-27-generic 8711928 /srv/tftpboot/opsi-linux-bootimage/x64/vmlinuz-5.0.0-27-generic > in your last image you can see that your imagefetch is not able to > detect the fileformat. The interesting point is that the broken notebook seems to does not detect the image as EFI binary. The working reference device seems to doesn't have this problem. > And yes, disable secure boot, unless you have both ipxe, and the > kernel signed by a certificate that has been added inside firmware > config. Yeah, I will try to research on that point. As already mentioned before there is no such option in the firmware. That either implies that there is no support for secure boot or secure boot is always active. I am not sure if the latter case is even possible, as the iPXE binary itself is loaded without problems at the beginning. > You can follow the link to see each place in the sourcecode where this > error can come from. (also, always include the link that are shown > together with the error message to get help easier) I will include the link to the error code here afterwards to ease comprehending this thread for other ones: http://ipxe.org/err/2e0080 Thank you for your time. Regards, Felix -- Best regards, Felix Jacobi IServ GmbH Bültenweg 73 38106 Braunschweig Phone: 0531-2243666-0 Fax:0531-2243666-9 E-mail: felix.jac...@iserv.eu Web:https://www.iserv.eu Tax ID: DE265149425 Executive directors:Benjamin Heindl, Martin Hüppe, Jörg Ludwig Principles on privacy: https://www.iserv.eu/privacy Verify my identity: https://github.com/FelixJacobi/gpg-keys signature.asc Description: OpenPGP digital signature ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
Re: [ipxe-devel] Error "Could not select: Exec format error (2e008081)" while loading EFI images via HTTP/TFTP
Hi Arne, Thank you for your reply. On 09.09.19 at 15:17, should be q931 wrote: > As per your screenshot, the error code given is in a URL > > The error provides a URL http://ipxe.org/err/2e008081 Yeah, I am aware of the error page and checked the list from the additional notes. That's the reason I wrote that the Linux kernel is compiled with the CONFIG_EFI_STUB option. I am also definitely sure that the kernel image isn't corrupted in some way as it works seamlessly with other hardware in UEFI mode. The same applies for the iPXE binary itself which works on other hardware, too. > 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 notebook has definitely no BIOS legacy mode, it just boots in UEFI mode. The iPXE EFI binary itself is loaded correctly by the firmware via HTTP with the URL supplied by DHCP. Chainloading further iPXE scripts works correctly, but iPXE is unable to load subsequent EFI binaries. Regards, Felix -- Best regards, Felix Jacobi IServ GmbH Bültenweg 73 38106 Braunschweig Phone: 0531-2243666-0 Fax:0531-2243666-9 E-mail: felix.jac...@iserv.eu Web:https://www.iserv.eu Tax ID: DE265149425 Executive directors:Benjamin Heindl, Martin Hüppe, Jörg Ludwig Principles on privacy: https://www.iserv.eu/privacy Verify my identity: https://github.com/FelixJacobi/gpg-keys signature.asc Description: OpenPGP digital signature ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
Re: [ipxe-devel] Error "Could not select: Exec format error (2e008081)" while loading EFI images via HTTP/TFTP
Hi Felix, On Mon, Sep 9, 2019 at 1:35 PM Felix Jacobi 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: > > https://community.iserv.eu/upload/eitae6OhM9oos0EyefeiNaxathoLoo4PhohPheijaiPiphoofeix5thoo3ogah8j/Picture%201.jpg 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: > > #!ipxe > > 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= 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: > > https://community.iserv.eu/upload/eitae6OhM9oos0EyefeiNaxathoLoo4PhohPheijaiPiphoofeix5thoo3ogah8j/Picture%202.jpg 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. > Cheers Arne ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
