Hi, background: I've managed to get EFI32, EFI64 and 'BIOS' modes all booting & working from the same TFTP/DHCP server using the setup described in message #10 here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589#10 I'm running this inside VMWare 9 - switching between x86 and x86_64 to check both EFI32 and EFI64, and then another non efi VM for bios. 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. 6.02 seems to produce the same behaviour as this discussion - http://www.syslinux.org/archives/2013-June/020195.html (i checked packet capture, it changes port as described in the posts from June) I couldn't see any bugs in the bugzilla list about this... wasn't sure if I should just discuss first. issue #2: i've tried alsorts... i have a fully working pxe / windows pe boot on 'bios' mode and wanted to replicate over to EFI. how do i add Windows EFI boot to (vesa)menu ? copying the boot file(s) to the tftp server and adding a menu entry like 'KERNEL /Boot//EFI/x64/bootmgfw.efi' the client just seems to go back to the menu after downloading the file. I even tried things like an entry for 'PXE 10.10.1.1::Boot/EFI/x64/bootmgfw.efi' pointing at a windows server 2012 with WDS configured, to no avail. I admit I have searched and searched already hopefully I didn't miss something obvious...... can anyone advise something to try next? Cheers Andrew
On Sat, Nov 16, 2013 at 6:11 PM, Andrew Rae <A.M.Rae at leeds.ac.uk> wrote:> Hi, > > background: > I've managed to get EFI32, EFI64 and 'BIOS' modes all booting & working from the same TFTP/DHCP server using the setup described in message #10 here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589#10 > > I'm running this inside VMWare 9 - switching between x86 and x86_64 to check both EFI32 and EFI64, and then another non efi VM for bios. > > 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. > > 6.02 seems to produce the same behaviour as this discussion - http://www.syslinux.org/archives/2013-June/020195.html (i checked packet capture, it changes port as described in the posts from June) > I couldn't see any bugs in the bugzilla list about this... wasn't sure if I should just discuss first.http://bugzilla.syslinux.org/show_bug.cgi?id=35 although my current branch needs just a little more work for the cross-subnet case.> issue #2: > i've tried alsorts... i have a fully working pxe / windows pe boot on 'bios' mode and wanted to replicate over to EFI. > how do i add Windows EFI boot to (vesa)menu ? > copying the boot file(s) to the tftp server and adding a menu entry like 'KERNEL /Boot//EFI/x64/bootmgfw.efi' > 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. You can also try removing menu.c32 entirely from the picture and just load the label from the boot prompt -- -Gene
Hi Gene, (some text snipped throughout)> > 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.> > 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" 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] 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 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...) what would be the methods to do these ? the same as in pxelinux.0 ? Cheers Andrew