This shows you the differences between two versions of the page.
Next revision | Previous revision Next revision Both sides next revision | ||
err:2e0080 [2010/12/08 12:01] 127.0.0.1 external edit |
err:2e0080 [2014/07/29 13:29] mcb30 |
||
---|---|---|---|
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 | * 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. | 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. 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. |