>> 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>
>> 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 dozenfailed>>> 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 looksfor 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 changedaccordingly. 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 dependingon 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 67as "\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 suchpathprefix, but I would suggest avoiding such potential confusion.> >Understood - It looks like the .efi image tries [path to syslinux.eficontaining 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 be >ldlinux.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-built >binaries 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.03 >final, and remember that any version mismatch (e.g. between syslinux.efiand>ldlinux.e64 and additional c32 files) shall be avoided. >> >>Regards, >>Ady. > > >Thanks for the response, >Aaron >After testing 3 different TFTP servers, I tried a different PXE system and it worked. Looks like the problem was with the Dell Latitiude E6330 I was testing with. Just upgraded the BIOS from A01 to A14 and it works now too. Thanks again for the help! 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/2e74e7e5/attachment.p7s>
> -----Original Message----- > From: Syslinux [mailto:syslinux-bounces at zytor.com] On Behalf Of Aaron > Hancock > Sent: Friday, November 7, 2014 1:24 PM > To: syslinux at zytor.com > Subject: Re: [syslinux] Can't UEFI boot PXELinux on WDS server > > After testing 3 different TFTP servers, I tried a different PXE system and it > worked. Looks like the problem was with the Dell Latitiude E6330 I was > testing with. Just upgraded the BIOS from A01 to A14 and it works now too. > > Thanks again for the help! > > AaronUpdating the BIOS is always something I forget about as well. We recently had some old Compaq/HP machines, I forget the model offhand (think they were from after HP bought out Compaq, but they were still branded Compaq, we've had some that were actually pre-dating the HP buyout that we've replaced not all that long ago too) and we have replaced them all this past summer, that would not network boot pxelinux at all. But I discovered they would boot pxelinux if I used a boot CD instead. They were on the first revision (1.0 or 1.2) of the BIOS, so I updated them to the latest (something like 2.14 or so) and that solved the issue. So it's always good to get a reminder that when having PXE problems, try updating the BIOS. -- John McDonnell Penn Cambria School District