[ipxe-devel] sanboot or exit under UEFI

[Sanjay Agrawal]

Thanks for looking into my query and the response.. Exit 1 worked for me..
The issue was that we were chain loading another script and both requires
an exit to get to the next boot device in the UEFI. i was thinking that the
exit from the second chainloaded script will get us the next boot device in
UEFI.

regards,
sanjay

On Tue, Feb 20, 2018 at 10:27 PM, Christian Nilsson <nikize at gmail.com>
wrote:

> On Mon, Feb 19, 2018 at 1:49 PM, Sanjay Agrawal <agraws at gmail.com> wrote:
> > I'm not sure if anybody has reported, but the sanboot --drive 0x80 or
> exit
> > or exit 1 doesn't relinquish the control to local disk or next boot
> device
> > in UEFI mode.
> >
> > I have tried this on both Dell and HP skylake servers. it woks perfectly
> > fine in BIOS mode. Both models are running the latest firmware.
> >
> > Any pointers will be a great help.
> >
> > thanks,
> > sanjay
> >
>
> iPXE can only "exit" and then it's up to the EFI firmware to do the
> right thing. exit 1 in EFI mode is working for most people as that
> returns "error" to the firmware and it then boots the next boot
> device.
> sanboot --drive 0x80 --no-describe as described on
> http://ipxe.org/cmd/sanboot#examples has some reported issues, this is
> due to the fact that iPXE only has support for "boot standard from
> device X" and in EFI I think that means try to find default named efi
> file on the first disk (in the case of 0x80) and then tell firmware to
> boot that.
>
> Hope that helps clarifying how it works.
>
> So for exit 1, check that next boot device is configured as expected
> in firmware, and if that is not working provide more information what
> is going on.
> for sanboot, verify that you have --no-describe on that line, and that
> the disk in question has a efi boot on it.
>
> /Christian
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20180221/baca7983/attachment.htm>