[syslinux] UEFI: Failed to load ldlinux.e64/ldlinux.e32

[Ashish, Shivendra]

Gene wrote:
> On Wed, Oct 7, 2015 at 7:58 AM, Ashish, Shivendra <shivendra.ashish at hpe.com> wrote:
>> Still getting error
>>
>> Disable uderdefault address
>
> 1) I'm presuming this is actually "disable UseDefaultAddress"
>
>> Core_udp_sento: udp->configure unsuccessful
>>
>> This message lopping in console
>
> Not entirely surprising (for now) though I'd expect more output than 
> just that and the rest of those messages would likely tell me exactly 
> what the return codes are.
>
> More importantly, you didn't mention what else you observed or any 
> details about your test.  I thought you just said the previous binary 
> had initially good outlook on a DL380 G9?  Details like which machines 
> work, which don't, and the basic layout of your PXE system would be 
> helpful, including:
>
> - Make/model of system
> - UEFI firmware revision
> - What NIC type and port number?
> - UEFI extension agents (struggling to recall the proper term; 
> comparable to a BIOS PXE OROM for add-in cards)
> - Was a proxyDHCP/PXE server involved in addition to DHCP?

> - TFTP or HTTP transfer
> - TFTP/HTTP on a unique server or on the DHCP server or proxyDHCP/PXE server?

- Where do the DHCP server, proxyDHCP/PXE server, and TFTP/HTTP server live relative to the client and each other (ie different subnets)?

> - What precisely did you observe?  On the screen?  booting behavior?
> - Have you performed any packet captures, preferably an tap/packet 
> mirror capture?

> In your case, the only obvious thing is that it seems like it's TFTP transfer.


It seems with the binaries you had given, initrd image is not loading.
It wait for some time to load initrd image and then reboots the machine.

Here is the snapshot Untitled12.png attached.
Here is the output from tftp server

Oct  8 20:49:22 foreman in.tftpd[5383]: RRQ from 192.168.103.41 filename efi64/syslinux.efi
Oct  8 20:49:22 foreman in.tftpd[5383]: tftp: client does not accept options
Oct  8 20:49:22 foreman in.tftpd[5384]: RRQ from 192.168.103.41 filename efi64/syslinux.efi
Oct  8 20:49:22 foreman in.tftpd[5387]: RRQ from 192.168.103.41 filename efi64/ldlinux.e64
Oct  8 20:49:22 foreman in.tftpd[5389]: RRQ from 192.168.103.41 filename efi64/pxelinux.cfg/37313930-3631-5347-4834-353058385048
Oct  8 20:49:22 foreman in.tftpd[5390]: RRQ from 192.168.103.41 filename efi64/pxelinux.cfg/01-38-63-bb-43-b7-d4
Oct  8 20:49:22 foreman in.tftpd[5392]: RRQ from 192.168.103.41 filename efi64/pxelinux.cfg/C0A86729
Oct  8 20:49:22 foreman in.tftpd[5393]: RRQ from 192.168.103.41 filename efi64/pxelinux.cfg/C0A8672
Oct  8 20:49:22 foreman in.tftpd[5394]: RRQ from 192.168.103.41 filename efi64/pxelinux.cfg/C0A867
Oct  8 20:49:22 foreman in.tftpd[5395]: RRQ from 192.168.103.41 filename efi64/pxelinux.cfg/C0A86
Oct  8 20:49:22 foreman in.tftpd[5396]: RRQ from 192.168.103.41 filename efi64/pxelinux.cfg/C0A8
Oct  8 20:49:22 foreman in.tftpd[5397]: RRQ from 192.168.103.41 filename efi64/pxelinux.cfg/C0A
Oct  8 20:49:22 foreman in.tftpd[5398]: RRQ from 192.168.103.41 filename efi64/pxelinux.cfg/C0
Oct  8 20:49:22 foreman in.tftpd[5399]: RRQ from 192.168.103.41 filename efi64/pxelinux.cfg/C
Oct  8 20:49:22 foreman in.tftpd[5400]: RRQ from 192.168.103.41 filename efi64/pxelinux.cfg/default
Oct  8 20:49:22 foreman in.tftpd[5401]: RRQ from 192.168.103.41 filename efi64/menu.c32
Oct  8 20:49:22 foreman in.tftpd[5401]: tftp: client does not accept options
Oct  8 20:49:22 foreman in.tftpd[5402]: RRQ from 192.168.103.41 filename efi64/menu.c32
Oct  8 20:49:22 foreman in.tftpd[5403]: RRQ from 192.168.103.41 filename efi64/libutil.c32
Oct  8 20:49:22 foreman in.tftpd[5406]: RRQ from 192.168.103.41 filename efi64/pxelinux.cfg/default
Oct  8 20:49:30 foreman in.tftpd[5573]: RRQ from 192.168.103.41 filename efi64/boot/vmlinuz0
Oct  8 20:49:36 foreman in.tftpd[5677]: RRQ from 192.168.103.41 filename efi64/boot/initrd0.img

- Make/model of system - HP DL380 Gen9 server
- UEFI firmware revision - P89 v1.50 (07/20/2015)
- What NIC type and port number? - HP Ethernet 1Gb 4-port 331i Adapter - NIC
- UEFI extension agents (struggling to recall the proper term; comparable to a BIOS PXE OROM for add-in cards)
- Was a proxyDHCP/PXE server involved in addition to DHCP? - yes
- TFTP or HTTP transfer - tftp
- TFTP/HTTP on a unique server or on the DHCP server or proxyDHCP/PXE server? All on same server
- Where do the DHCP server, proxyDHCP/PXE server, and TFTP/HTTP server live relative to the client and each other (ie different subnets)? Same subnet, server is 192.168.0.1 and clinet is 192.168.103.41 on 192.168.0.0/16 network
- What precisely did you observe?  On the screen?  booting behavior? Mentioned above wit snapshot
- Have you performed any packet captures, preferably an tap/packet mirror capture? Not yet, if you want I can do that. Please mention the steps. I think you need tcp dump from server at the time of client network boot ?


Thanks & Regards,
Ashish Shivendra