Syslinux - Mar 2005 - Re: [Fwd: Re: etherboot 5.3.14 and pxelinux keyboard problem]

On Wed, 9 Mar 2005, Quinn wrote:
> I have now also tried etherboot on a AMD Athlon machine with a 3Com 905B
> NIC, etherboot 5.3.14 and pxelinux.0-3.08-pre5. Here is the results:
> 
> Etherboot 5.3.14 (GPL) http://etherboot.org
> Drivers: 3C90X   Images: NBI ELF PXE   Exports: PXE  
> Protocols: DHCP TFTP
> Relocating _text from: [00010420,00022880) to [5feedba0,5ff00000)
> Boot from (N)etwork or (Q)uit?
> 
> <snip>
> [PXENV_UDP_WRITE 40708->10.0.0.100:69 (41)]
> [PXENV_UDP_READ 10.0.0.100:33016->10.0.0.101:40708 (12)]
> [PXENV_UDP_WRITE 40708->10.0.0.100:33016 (4)]
> [PXENV_UDP_READ 10.0.0.100:33016->10.0.0.101:40708 (260)]
> [PXENV_UDP_WRITE 40708->10.0.0.100:33016 (4)]
> Unknown keyword in config file.
> boot:
> [PXENV_UDP_READ 0001 err]
> [PXENV_UDP_READ 0001 err]
> [PXENV_UDP_READ 0001 err]
> [PXENV_UDP_READ 0001 err]
> [PXENV_UDP_READ 0001 err]
> [PXENV_UDP_READ 0001 err]
> 
> and so on....
> 
> As you can see with etherboot 5.3.14 and pxelinux.0-3.08-pre5 on the old
> 486DX machine with the NE2000 NIC does not produce the [PXENV_UDP_READ
> 0001 err] messages at the boot prompt whereas the AMD Athlon machine
> with the 3Com 905B NIC does produce the messages.
The [PXENV_UDP_READ 0001 err] messages are correct; it's pxelinux 
repeatedly calling the UDP_READ routine in order to make sure that ARP 
queries are responded to.  The "0001 err" return status is simply 
indicating "no packet".

This proves my point that Etherboot's PXENV_UDP_READ routine is 
non-blocking, at least.

We need to isolate the cause of the problem.  Are you able to try the 
3C905B in your old 486DX machine, or the NE2000 in the Athlon?  At the 
moment you have too many variables to be able to identify a single cause.

Michael