Syslinux - Jul 2015 - UEFI/EFI booting and constantly asking for ldlinux.e64

I'm setting up UEFI booting and got to the point of having the system 
talk to the dhcpd/tftpd server, grab the first image files 
(syslinux.efi) and then continuously request the secondary image file 
(ldlinux.e64).

I'm wondering if I'm missing something or if someone can point me in the
right direction of trouble shooting this.

The tftp root has all the files to boot a BIOS type system with syslinux 
menu system setup.   Then I copied the files from a syslinux tar ball 
for EFI/UEFI booting.

--snip /var/log/messages--
Jun 30 19:32:04 aid dhcpd: DHCPDISCOVER from ec:f4:bb:db:2e:20 via p1p2
Jun 30 19:32:05 aid dhcpd: option_space_encapsulate: option space 'TFTP'
does not exist, but is configured.
Jun 30 19:32:05 aid dhcpd: DHCPOFFER on 172.20.0.131 to 
ec:f4:bb:db:2e:20 via p1p2
Jun 30 19:32:08 aid dhcpd: DHCPREQUEST for 172.20.0.131 (172.20.0.1) 
from ec:f4:bb:db:2e:20 via p1p2
Jun 30 19:32:08 aid dhcpd: option_space_encapsulate: option space 'TFTP'
does not exist, but is configured.
Jun 30 19:32:08 aid dhcpd: DHCPACK on 172.20.0.131 to ec:f4:bb:db:2e:20 
via p1p2
Jun 30 19:32:08 aid xinetd[16150]: START: tftp pid=28110 from=172.20.0.131
Jun 30 19:32:08 aid in.tftpd[28111]: connect from 172.20.0.1
Jun 30 19:32:08 aid in.tftpd[28111]: RRQ from 172.20.0.131 filename 
X86PC/linux/syslinux.efi
Jun 30 19:32:08 aid in.tftpd[28111]: tftp: client does not accept options
Jun 30 19:32:08 aid in.tftpd[28112]: connect from 172.20.0.1
Jun 30 19:32:08 aid in.tftpd[28112]: RRQ from 172.20.0.131 filename 
X86PC/linux/syslinux.efi
Jun 30 19:32:08 aid in.tftpd[28113]: connect from 172.20.0.1
Jun 30 19:32:08 aid in.tftpd[28113]: RRQ from 172.20.0.131 filename 
X86PC/linux/ldlinux.e64
Jun 30 19:32:09 aid in.tftpd[28114]: connect from 172.20.0.1
Jun 30 19:32:09 aid in.tftpd[28114]: RRQ from 172.20.0.131 filename 
X86PC/linux/ldlinux.e64
Jun 30 19:32:09 aid in.tftpd[28115]: connect from 172.20.0.1
Jun 30 19:32:09 aid in.tftpd[28115]: RRQ from 172.20.0.131 filename 
X86PC/linux/ldlinux.e64
Jun 30 19:32:10 aid in.tftpd[28116]: connect from 172.20.0.1
Jun 30 19:32:10 aid in.tftpd[28116]: RRQ from 172.20.0.131 filename 
X86PC/linux/ldlinux.e64
....
Jun 30 19:36:51 aid in.tftpd[28208]: RRQ from 172.20.0.131 filename 
X86PC/linux//boot/isolinux/ldlinux.e64
Jun 30 19:36:51 aid in.tftpd[28208]: sending NAK (1, File not found) to 
172.20.0.131
Jun 30 19:36:54 aid in.tftpd[28209]: connect from 172.20.0.1
Jun 30 19:36:54 aid in.tftpd[28209]: RRQ from 172.20.0.131 filename 
X86PC/linux//boot/isolinux/ldlinux.e64
Jun 30 19:36:54 aid in.tftpd[28209]: sending NAK (1, File not found) to 
172.20.0.131
Jun 30 19:36:58 aid in.tftpd[28211]: connect from 172.20.0.1
Jun 30 19:36:58 aid in.tftpd[28211]: RRQ from 172.20.0.131 filename 
X86PC/linux//boot/isolinux/ldlinux.e64
--end /var/log/messages--

--snip cmd-line--
  ls -l /tftpboot/X86PC/linux/ldlinux.e64
-rw-r--r-- 1 -UID GID REMOVED- 140720 Jun 30 18:25 
/tftpboot/X86PC/linux/ldlinux.e64
[root at aid log]# ls -l /tftpboot/X86PC/linux/syslinux.efi
-rw-r--r-- 1 -UID GID REMOVED- 187944 Jun 30 16:03 
/tftpboot/X86PC/linux/syslinux.efi
--end cmd-line--

Thanks for any help,
Ryan

On Tue, Jun 30, 2015 at 10:55 PM, Nelson, Ryan M. (ARC-TI)[SGT, INC]
via Syslinux <syslinux at zytor.com> wrote:
> I'm setting up UEFI booting and got to the point of having the system
talk
> to the dhcpd/tftpd server, grab the first image files (syslinux.efi) and
> then continuously request the secondary image file (ldlinux.e64).
So it appears to go deaf.
> I'm wondering if I'm missing something or if someone can point me
in the
> right direction of trouble shooting this.
1) What version? In the 8 months since 6.03, there have been numerous
commits that might resolve this.  Let me know if you need a set of
test binaries.

2) What's the system?  The sole system I have confirmation of a
remaining EFI64 issue is a VMware VM with the e1000e NIC, in fact with
similar symptoms.
> The tftp root has all the files to boot a BIOS type system with syslinux
> menu system setup.   Then I copied the files from a syslinux tar ball for
> EFI/UEFI booting.
Sounds good here.

-- 
-Gene

On 7/1/2015 2:58 AM, Gene Cumm wrote:
>> I'm setting up UEFI booting and got to the point of having the
system talk
>> >to the dhcpd/tftpd server, grab the first image files
(syslinux.efi) and
>> >then continuously request the secondary image file (ldlinux.e64).
> So it appears to go deaf.
>
>> >I'm wondering if I'm missing something or if someone can
point me in the
>> >right direction of trouble shooting this.
> 1) What version? In the 8 months since 6.03, there have been numerous
> commits that might resolve this.  Let me know if you need a set of
> test binaries.
It is version 6.03.  I will attempt to use the latest from the repo and 
report back.
>
> 2) What's the system?  The sole system I have confirmation of a
> remaining EFI64 issue is a VMware VM with the e1000e NIC, in fact with
> similar symptoms.
>
The system is a Dell PowerEdge R730xd with 4 NICs:
Intel(R) Ethernet 10G 4P X520/I350 rNDC
Intel(R) Gigabit 4P X520/I350 rNDC

Current connection on the 10G port.

I have noticed something else a little weird via the UEFI setting for 
the NIC's.  I seem to have to enable two NICs for PXE booting to even 
successfully PXE boot.  When I do this the first NIC fails to boot and 
the second works right away.  Doesn't matter which interface boots first 
or which is plugged in.  I will probably open a ticket about this with 
Dell, just thought it was a little weird.