Syslinux - Jul 2014 - lpxelinux hangs under Intel Boot Agent 1.3.81 (2.1 build 089) on Dell Optiplex 990 BIOS A16

On Fri, Jul 11, 2014 at 5:49 PM, Alexander Perlis <aperlis at
math.lsu.edu> wrote:
> On 07/11/2014 04:31 PM, H. Peter Anvin wrote:
>>
>> On 07/11/2014 10:17 AM, Alexander Perlis wrote:
>>>
>>>
>>> Trace shows that lpxelinux.0 6.03-pre18 is transferred, and after
that
>>> there is only ARP traffic: a "gratuitous" ARP
announcement by the
>>> client, and then a string of ARP requests and replies in which the
>>> client is asking for the MAC of the PXE server, about every 3
seconds,
>>> for about 2 minutes [...]
>>
>>
>> So it is sending packets but not getting the response.
>
>
> Yes. To clarify my report: client is sending ARP requests, server is
sending
> ARP responses, and then either the client is totally ignoring them or
> perhaps indeed updating its ARP table but then say immediately expiring the
> ARP entry. This only happens with lpxelinux.0. Any other things I should
try
> or other data I can provide to assist?
>
> Alex
Seems like a deaf client.  Interestingly enough, the flags value is
the same as on those other Dells.

With everything else from 6.03-pre18, try this binary (xzip-compressed):

http://www.zytor.com/~genec/lpxelinux-6.03p18g3.tgz

-- 
-Gene

On 07/11/2014 09:39 PM, Gene Cumm wrote:
> With everything else from 6.03-pre18, try this binary (xzip-compressed):
> http://www.zytor.com/~genec/lpxelinux-6.03p18g3.tgz
It works! Thanks!

Anything else I should do/report on this hardware before I upgrade the 
BIOS and possibly eliminate the broken environment that exhibited the 
problem?

Alex

On Sat, Jul 12, 2014 at 3:15 PM, Alexander Perlis <aperlis at
math.lsu.edu> wrote:
> On 07/11/2014 09:39 PM, Gene Cumm wrote:
>>
>> With everything else from 6.03-pre18, try this binary
(xzip-compressed):
>> http://www.zytor.com/~genec/lpxelinux-6.03p18g3.tgz
>
>
> It works! Thanks!
>
> Anything else I should do/report on this hardware before I upgrade the BIOS
> and possibly eliminate the broken environment that exhibited the problem?
>
> Alex
Oh fun.  That's the exact same workaround just now for different
hardware.  I can't think of anything but not sure if there's anything
that someone else might think of.

-- 
-Gene