Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Sanboot 0x80 (local) on EFI
2018-02-13, 06:35
Post: #2
RE: Sanboot 0x80 (local) on EFI
If your machine has 64bit efi firmware then you won't be able to boot a 32bit version of ipxe efi

So first make sure that you are referring to the correct ipxe binary and mode as to not confuse this further.

If you are using a pcbios build of ipxe then filename will do nothing.
That sanboot command will boot the first "EFI disk" with the filename you provide, so using exit 1 would do that for most cases when the disk is next in boot order. One step in trying to figure out how your system maps things would be to use a efi shell.

Also, always read and post the ipxe.org error urls. http://ipxe.org/err/2c2220 have 2 possible sources in the code, either no network device is open, or it simply can't find the disk. So make sure you have ifopen or dhcp before sanboot, and if that fails build ipxe with DEBUG=efi_block to get more details on what it fails on...
For reference commit where the --filename was implemented: https://git.ipxe.org/ipxe.git/commitdiff...e4b58cacc8

iPXE is a network boot program, not local disk boot program so booting from disk is not the intended use.

Use GitHub Discussions
VRAM bin
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: Sanboot 0x80 (local) on EFI - NiKiZe - 2018-02-13 06:35



User(s) browsing this thread: 1 Guest(s)