How to detect ARM architecture from iPXE script?
|
2018-10-31, 20:35
Post: #15
|
|||
|
|||
RE: How to detect ARM architecture from iPXE script?
Another question - why iPXE is complaining about kernel not being EFI while stock grubaa64.efi (from Ubuntu 18.04) has no problem with it? Am I missing something in iPXE setup?
>>Checking Media Presence...... Downloading NBP file... Succeed to download NBP file. iPXE initialising devices...ok iPXE 1.0.0+ (975120) -- Open Source Network Boot Firmware -- http://ipxe.org Features: DNS HTTP HTTPS iSCSI TFTP VLAN AoE EFI Menu iPXE 2018-10-25 running on arm64 architecture. Configuring (net0 d4:5df:1d:ef:f0)........... ....... ok tftp://10.20.109.97/pxelinux.cfg/01-d4-5d-df-1d-ef-f0.ipxe... No such file or directory (http://ipxe.org/2d12608e) tftp://10.20.109.97/pxelinux.cfg/default.ipxe... ok overrides.ipxe... ok MiniOS version u18.04.1-arm64 on machine (arm64). http://10.43.184.12/ims/os-profiles/mini...vmlinuz... ok Could not select: Exec format error (http://ipxe.org/2e008081) Could not boot: Exec format error (http://ipxe.org/2e008081) iPXE> According to http://ipxe.org/err/2e0080, iPXE is most probably tripping over this: Quote: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. But again, the same vmlinuz works with grub2 w/o any issues. Is iPXE missing some features that grub2 posses that allows it not to care if the kernel is EFI or not? If so, any pointers on how exactly to rebuild vmlinuz with CONFIG_EFI_STUB? Strangely enough, I'm having hard time figuring this mostly because grub2 just does not seem to care so nobody needs to rebuild their kernel, I guess. Thanks! Thanks! |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)