[syslinux] Re: etherboot 5.3.14 and pxelinux keyboard problem

[Michael Brown]

On Tue, 8 Mar 2005, Quinn wrote:
> As requested, an etherboot PXE trace with pxelinux (serial output - 
> 9600,n,8,1 - captured via minicom):
> 
> <snip>
> [PXENV_UDP_WRITE 57090->10.0.0.100:32998 (4)]
> [PXENV_UDP_READ 10.0.0.100:32998->10.0.0.80:57090 (30)]
> [PXENV_UDP_WRITE 57090->10.0.0.100:32998 (4)]
> PXELINUX 2.13 2004-12-14  Copyright (C) 1994-2004 H. Peter Anvin
> [PXENV_UDP_WRITE 57091->10.0.0.100:69 (41)]
> [PXENV_UDP_READ 10.0.0.100:32998->10.0.0.80:57091 (12)]
> [PXENV_UDP_WRITE 57091->10.0.0.100:32998 (4)]
> [PXENV_UDP_READ 10.0.0.100:32998->10.0.0.80:57091 (260)]
> [PXENV_UDP_WRITE 57091->10.0.0.100:32998 (4)]
> boot:
> 
>  From here anything I type on the keyboard does not show up - and after 
> awhile the keyboard buffer gets full and beeps at me.
> Same thing via the serial console - type anything, but nothing shows up.

Thanks.  Whatever's causing the lockup, it's in pxelinux.  At the time of
the lockup, it's not in the middle of a PXE API call - you can tell
because there is no unterminated "[PXENV_" message.

Are you using the pxelinux.0 as distributed in the syslinux 3.08-pre5
tarball?  If not, please try it, since that version works for me.

Michael