Differences

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

--- err:2e0080 [2017/08/16 19:20]
nikize
+++ err:2e0080 [2021/05/10 21:05]
mcb30
@@ 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 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 built with ''CONFIG_EFI_STUB'' enabled.  Most distribution kernels will already be built with ''CONFIG_EFI_STUB'' enabled.
     * 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.
+    * You can use the ''[[:cmd:imgstat]]'' command to check that the filesize is correct and that the file has been detected as the correct type.
-    * 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 have edited the script on a Windows machine, check that the script was saved using ASCII (or UTF-8) rather than UTF-16 encoding, and that your Windows editor has not inserted a byte order mark (BOM) at the start of the file.