Differences

This shows you the differences between two versions of the page.

--- err:2e0080 [2010/12/08 12:01]
127.0.0.1 external edit
+++ err:2e0080 [2017/08/16 19:20]
nikize
@@ Line 5: / Line 5: @@
   * Check that your build of iPXE supports the type of image you are trying to boot.  You can see the list of supported image types in the iPXE start-up banner; for example:<code>    iPXE 1.0.0+ -- Open Source Network Boot Firmware -- http://ipxe.org
     Features: HTTP iSCSI DNS TFTP AoE VLAN bzImage COMBOOT ELF MBOOT PXE PXEXT</code> shows that bzImage, COMBOOT, ELF, Multiboot, and PXE images are supported in this build of iPXE.
+  * If you are running a UEFI version of iPXE then only EFI binaries can be loaded.  PXE binaries such as pxelinux.0 use legacy BIOS calls and can never work on UEFI.
+    * If you are trying to load a Linux kernel (or other EFI binary) then you can use iPXE to load it directly; there is no need to load pxelinux.0 first.
+    * If you are trying to display a pxelinux menu then you may want to investigate iPXE's native [[:cmd:choose|menuing]] capabilities.
   * Check that the image you are trying to boot has not been corrupted in any way.
+    * The filesize, what iPXE reports during download, and download the same url with browser or other client and check the size.
+    * If the size is the same it can also be a good idea to compare checksums between original file, file on server, and downloaded file with different client.
   * If you are trying to boot an iPXE script, check that the "''#!ipxe''" signature is present at the beginning of the script.
+    * If you have edited the script on a Windows machine, check that the script was saved using ASCII (or UTF-8) rather than UTF-16 encoding. (Some editors add what is known as BOM at the beginning which will cause issues)
-  * If you are trying to boot an iPXE script, and you have edited the script on a Windows machine, check that the script was saved using ASCII (or UTF-8) rather than UTF-16 encoding.