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

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.

> 
> 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.
> 
 
Dell Server PowerEdge BIOS R730/R730-xd Version 1.3.6
23 Jun 2015

It includes several updates; among them:

_ Removed unused setup options.
_ Fixed an issue where Mellanox network card would not commit PXE boot in UEFI
mode
on Port 2.


I am not saying updating this firmware (still being call "BIOS" by
Dell) will solve
any particular problem. It is just intended to show, once again, that checking
for
firmware updates might be relevant when regards to booting.

Regards,
Ady.

On 7/1/2015 12:56 PM, Ady via Syslinux wrote:
> Dell Server PowerEdge BIOS R730/R730-xd Version 1.3.6
> 23 Jun 2015
>
> It includes several updates; among them:
>
> _ Removed unused setup options.
> _ Fixed an issue where Mellanox network card would not commit PXE boot in
UEFI mode
> on Port 2.
>
>
> I am not saying updating this firmware (still being call "BIOS"
by Dell) will solve
> any particular problem. It is just intended to show, once again, that
checking for
> firmware updates might be relevant when regards to booting.
>
> Regards,
> Ady.
You are correct the version was checked with Dell's Lifecycle Management 
tool however that is not in sync with the latest they have on their 
downloads.  BIOS is version 1.3.6, problems still persist.

On 7/1/2015 12:00 PM, Nelson, Ryan M. (ARC-TI)[SGT, INC] via Syslinux
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. 
I've replaced the files from ones grabbed from GIT and now the boot 
fails quickly stating:

--snip console--
Boot Failed: PXE Device 3: Integrated NIC 1 Port 1 Partition 1
--end console--

It now looks as if it doesn't ask for the ldlinux.e64 file:

--snip messages--
Jul  1 14:54:27 aid in.tftpd[7075]: connect from 172.20.0.1
Jul  1 14:54:27 aid in.tftpd[7075]: RRQ from 172.20.0.131 filename 
X86PC/linux/syslinux.efi
Jul  1 14:54:27 aid in.tftpd[7075]: tftp: client does not accept options
Jul  1 14:54:27 aid in.tftpd[7076]: connect from 172.20.0.1
Jul  1 14:54:27 aid in.tftpd[7076]: RRQ from 172.20.0.131 filename 
X86PC/linux/syslinux.efi
--end messages--

Ryan

On 7/1/2015 3:04 PM, Nelson, Ryan M. (ARC-TI)[SGT, INC] via Syslinux
wrote:
> I've replaced the files from ones grabbed from GIT and now the boot 
> fails quickly stating:
>
> --snip console--
> Boot Failed: PXE Device 3: Integrated NIC 1 Port 1 Partition 1
> --end console-- 
For troubleshooting I put a Netgear switch in place and connected all 
network connections to the same network and enabled all NICs for UEFI 
PXE boot.  Still same problem but 4 x now ;)

Is there any debugging options I can enable for spitting out more info 
and try to determine where in the code the boot is dying at?

Thanks,
Ryan