DHCP seems to be working properly - returning the correct boot file for the architecture of the PXE client, but when I try to boot syslinux.efi, it gets the file then keeps requesting ldinux.e64 over and over again. The file is there and available. A wireshark trace shows it keeps requesting the file, followed by the server responding to the blksize and tsize options, but then the client just continues requesting the file. After a few dozen failed attempts it then tries to get the boot\x64\/boot/isolinux/ldlinex.e64 file for a few dozen more tries. Is it possible this is a timing issue? The TFTP server is running on a 10G NIC so it may be responding faster than expected? I did see the file downloaded properly once so this is the only thing I can think of. Any help greatly appreciated. Aaron -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5949 bytes Desc: not available URL: <http://www.zytor.com/pipermail/syslinux/attachments/20141107/0f0904d6/attachment.p7s>
> DHCP seems to be working properly - returning the correct boot file for the > architecture of the PXE client, but when I try to boot syslinux.efi, it gets > the file then keeps requesting ldinux.e64 over and over again. The file is > there and available. A wireshark trace shows it keeps requesting the file, > followed by the server responding to the blksize and tsize options, but then > the client just continues requesting the file. After a few dozen failed > attempts it then tries to get the boot\x64\/boot/isolinux/ldlinex.e64 file > for a few dozen more tries. >I am not sure what you meant with "returning the correct boot file for the architecture of the PXE client". A UEFI IA32 client (architecture-type = 00:06) should look for the syslinux.efi file from efi32 (which then looks for ldlinux.e32), and similarly for UEFI x86_64 (syslinux.efi + ldlinux.e64). The file can be renamed (e.g. to bootia32.efi, bootx64.efi) if the dhcp configuration is also changed accordingly. What I mean is that the syslinux.efi file _is_ the "boot file", so what "boot file for the architecture of the PXE client" you are referring to?. Regarding the path you mentioned, the "isolinux" part seems strange. There is no "isolinux" in UEFI. I have seen such misunderstanding before, so you are not the only one. I am not saying that you cannot use such pathprefix, but I would suggest avoiding such potential confusion. FWIW, there is also a typo in your report (ldlinex.e64 should be ldlinux.e64). And the most important detail... Are you using Syslinux 6.03 final? Or is this a pre-prelease? Are you using the official upstream pre-built binaries downloaded from kernel.org? Or are you using some distro package? Or perhaps your own build? Please try the official upstream pre-built binaries from version 6.03 final, and remember that any version mismatch (e.g. between syslinux.efi and ldlinux.e64 and additional c32 files) shall be avoided. Regards, Ady.
>> DHCP seems to be working properly - returning the correct boot file >> for the architecture of the PXE client, but when I try to boot >> syslinux.efi, it gets the file then keeps requesting ldinux.e64 over >> and over again. The file is there and available. A wireshark trace >> shows it keeps requesting the file, followed by the server responding tothe blksize and tsize options, but then>> the client just continues requesting the file. After a few dozen failed >> attempts it then tries to get the boot\x64\/boot/isolinux/ldlinex.e64 > file for a few dozen more tries. >>>I am not sure what you meant with "returning the correct boot file for thearchitecture of the PXE client". A UEFI IA32 client (architecture-type 00:06) should look for the syslinux.efi file from efi32 (which then looks for ldlinux.e32), and similarly for UEFI>x86_64 (syslinux.efi + ldlinux.e64). The file can be renamed (e.g. tobootia32.efi, bootx64.efi) if the dhcp configuration is also changed accordingly. What I mean is that the syslinux.efi file _is_ the "boot file", so what "boot file for the architecture of the PXE client" you are referring to?. I have DHCP policies set up to return a different bootfile name depending on the VCI advertised by the client. E.g. When the client reports DHCP Option 60 as "PXEClient:Arch:00007:UNDI:003016" the DHCP server returns Option 67 as "\boot\x64\syslinux.efi">Regarding the path you mentioned, the "isolinux" part seems strange. >There is no "isolinux" in UEFI. I have seen such misunderstanding before,so you are not the only one. I am not saying that you cannot use such pathprefix, but I would suggest avoiding such potential confusion. Understood - It looks like the .efi image tries [path to syslinux.efi containing folder]ldlinux.e64 . If that fails, then it tries [path to syslinux.efi containing folder]/ldlinux.e64. If that fails then it tries the isolinux file previously mentioned. This is from a wireshark capture and TFTP server log.>FWIW, there is also a typo in your report (ldlinex.e64 should beldlinux.e64). Sorry about that - eyes glazing over after hours of troubleshooting :)>And the most important detail... Are you using Syslinux 6.03 final? >Or is this a pre-prelease? Are you using the official upstream pre-builtbinaries downloaded from kernel.org? Or are you using some distro package? Or perhaps your own build?>Yes - downloaded from https://www.kernel.org/pub/linux/utils/boot/syslinux/syslinux-6.03.zip> >Please try the official upstream pre-built binaries from version 6.03final, and remember that any version mismatch (e.g. between syslinux.efi and ldlinux.e64 and additional c32 files) shall be avoided.> >Regards, >Ady.Thanks for the response, Aaron -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5949 bytes Desc: not available URL: <http://www.zytor.com/pipermail/syslinux/attachments/20141107/b1095925/attachment.p7s>