[syslinux] PXE EFI booting - 2 issues!

Gene Cumm gene.cumm at gmail.com
Sun Nov 17 10:15:55 PST 2013

On Sun, Nov 17, 2013 at 12:29 PM, Andrew Rae <A.M.Rae at leeds.ac.uk> wrote:
> Hi Gene,
> (some text snipped throughout)

No problems.

>> > issue #1:
>> > I can only get this working on 6.02-pre16 and before back to 6.01-pre2,
>> > but definitely not working for me on the latest precompiled 6.02 zip & tar.gz.
>> http://bugzilla.syslinux.org/show_bug.cgi?id=35 although my current
>> branch needs just a little more work for the cross-subnet case.
> Thanks for that, I'll give that a read.

Just did another push onto my branch for 79157457 which should finish it out.

>> > issue #2:
>> > the client just seems to go back to the menu after downloading the file.
>> The troubleshooting key is to not use "UI menu.c32" or "DEFAULT
>> menu.c32" with "TIMEOUT 0" to prevent it from auto-launching again and
>> hiding the error.
> okay, thanks for the tips.
> If I move the files I'm trying to load into the root folder for testing, and try without the menu...
> At the 'boot:' prompt if I enter "/bootmgfw.efi", I get the reply : "Loading /bootmgfw.efi... failed: No such file or directory"
> but on the tftpd side of things, and in  packet capture, I can see that it requested, in this order:
> /bootmgfw.efi.c32, img, bss, bin, bs, 0 -> 'not found', and then finally /bootmgfw.efi
> to which the server replies "Option Acknowlegement, tsize\000=1604952\000, blksize\000=1408\000
> and then the client says "Error Code, Code: Not defined, Message: No error, file close"

Yep, we saw that along the way.  Someone else actually made the fix.
Commit dddd53bd should solve that.

> If I rename bootmgfw.efi -> bootmgfw.0 and try again:
> "Too large for a boostrap (need LINUX instead of KERNEL?)" [note: found a typo - boostrap / bootstrap]

It shouldn't do this; it should really refuse the file since this file
type is not EFI-compatible.

> Even if I try to chain to another (windows WDS) server and type
> ".pxe y.y.y.y::boot\x64\bootmgfw.efi" - I get nothing, just back to the boot: prompt, and no acknowledgement on the WDS TFTP server logs

Is that ".pxe" inside menu.c32 or at the prompt?  At the prompt, it'll
try loading a file called ".pxe".

> I guess my question is, am I doing something daft - is it actually possible when using the EFI versions of PXELINUX to 'chain' to another EFI bootloader (and/or to another PXE/TFTP server...)

It should be possible.

> what would be the methods to do these ? the same as in pxelinux.0 ?


More information about the Syslinux mailing list