Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
err:2e0080 [2014/07/29 13:20]
robinsmidsrod Added info about UEFI image compatibility
err:2e0080 [2014/07/29 13:29]
mcb30
Line 6: Line 6:
     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.     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'​re ​running ​an UEFI version of iPXE then only EFI binaries can be loaded. PXE binaries ​like pxelinux.0 use legacy BIOS calling conventions ​and will never work on UEFI.+  * If you are running ​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.  You can use iPXE to directly load a Linux kernel (or other EFI binary) without needing pxelinux.0. ​ 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.   * Check that the image you are trying to boot has not been corrupted in any way.
err/2e0080.txt ยท Last modified: 2021/10/07 09:29 by nikize
Recent changes RSS feed CC Attribution-Share Alike 4.0 International Driven by DokuWiki
All uses of this content must include an attribution to the iPXE project and the URL https://ipxe.org
References to "iPXE" may not be altered or removed.