> -----Original Message----- > From: Matt Fleming [mailto:matt at console-pimps.org] > Sent: 09 July 2014 19:50 > Hey Andrew, > Sorry for the delay. Could you provide the packet dumps of the network > traffic involved in the failed EFI boot? > Hopefully that will allow us to track down exactly what's going wrong.Hi Matt, Appears to all be working under 6.03-pre19 on vmware workstation 8, as well as on a series 8 Asus board I tried with an onboard Intel NIC.. That's in all 4 modes I was trying - BIOS (both pxelinux and lpxelinux), EFI32, EFI64. I used both HTTP (not in pxelinux) and TFTP to boot from to test each. (Apologies again for not getting some packet dumps done before when you'd asked !) Cheers, Andrew
Shantanu Gadgil
2014-Aug-11 13:12 UTC
[syslinux] testing out 6.03 network booting... (6.03-pre19)
Hi all, I too am getting positive results using 6.03-pre19 lpxelinux.0, for the problem that I have been facing. The symptom was that booting hangs on client side. On the server (DNSMasq TFTP) it keeps getting a request for the same (MAC address) file. OR, alternatively it just stops completely. My server: OptiPlex 755. BIOS A22 The PXE booting client: OptiPlex 960. BIOS A17 * Things are broken using 6.03-pre17 lpxelinux.0 and working correctly using 6.03-pre19 lpxelinux.0 Regards, Shantanu
H. Peter Anvin
2014-Aug-11 16:51 UTC
[syslinux] testing out 6.03 network booting... (6.03-pre19)
On 08/11/2014 06:12 AM, Shantanu Gadgil wrote:> Hi all, > > I too am getting positive results using 6.03-pre19 lpxelinux.0, for the problem that I have been facing. > > The symptom was that booting hangs on client side. > On the server (DNSMasq TFTP) it keeps getting a request for the same (MAC address) file. > OR, alternatively it just stops completely. > > My server: OptiPlex 755. BIOS A22 > The PXE booting client: OptiPlex 960. BIOS A17 > > * Things are broken using 6.03-pre17 lpxelinux.0 and working correctly using 6.03-pre19 lpxelinux.0 >Wonderful. It looks like we really hit some paydirt here. -hpa