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
Previous revision
err:2e0080 [2014/07/29 13:32]
mcb30
err:2e0080 [2017/09/20 18:44]
nikize
Line 8: Line 8:
   * 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 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 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 load a Linux kernel, make sure it is build with ''​CONFIG_EFI_STUB''​ and that it is a working EFI binary.
     * If you are trying to display a pxelinux menu then you may want to investigate iPXE's native [[:​cmd:​choose|menuing]] capabilities.     * 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.
 +    * 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 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.+
  
err/2e0080.txt · Last modified: 2017/09/20 18:44 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 http://ipxe.org
References to "iPXE" may not be altered or removed.