Syslinux - Mar 2014 - Very slow download with pxelinux > 4.07 on specific hardware

Le 11/03/2014 00:56, Gene Cumm a ?crit :
> On Mon, Mar 10, 2014 at 7:55 PM, Gene Cumm <gene.cumm at gmail.com>
wrote:
>> On Mon, Mar 10, 2014 at 7:15 PM, Gene Cumm <gene.cumm at
gmail.com> wrote:
>>> On Mon, Mar 10, 2014 at 6:52 PM, Schlomo Schapiro <schlomo at
schapiro.org> wrote:
>>>> Hi,
>>>>
>>>> On 10 March 2014 18:13, Eric PEYREMORTE <eric.peyremorte at
iut-valence.fr>wrote:
>>>>
>>>>> Ok i give up. I will stick with the old version version
(4.07) which works
>>>>> well with dell 380 and 790.
>>>>>
>>>>> I tried to understand what happened between 4.07 and 5 but
i don't have
>>>>> the skill to understand low level c.
>>>>>
>>>>> Seems that the memory management changed a lot, maybe the
culprit. But as
>>>>> many other things changed this is not obvious...
>>>>>
>>>> sad to say, we have exactly the same problem. With HTTP
downloads it is
>>>> much worse, we could not find a stable and reliable version
after 4.x.
>>>> Sadly nobody wanted to fix our syslinux problem, even as paid
development.
>>>>
>>>> I very much hope that the syslinux project will overcome these
obstacles.
>>>> It would be sad to see all the new development stay unused
because if this.
>>> It's also a balance of time.  While working on
4.10-pre*/5.10-pre*, I
>>> found that some hardware misreports its behavior.  "Sure,
Interrupts
>>> work" but they don't is but one that I worked around on
specific
>>> hardware.
>>>
>>> --
>>> -Gene
>> Simple test (and boot failure is an option as long as the core's
>> messages are intact).  Could both of you try fetching
>> Syslinux-4.10-pre22 (zip versus tar is your choice), extract out
>> core/pxelinux.0 and boot with it then record the 4-digit value for
>> flags (in the "UNDI: baseio" line) and the first 3 octets (6
hex
>> digits including 0s) of the MAC address and take a reasonable screen
>> shot (I find a cell phone against a solid object to be pretty decent
>> when angled to reduce glare and distanced for proper focus) but
don't
>> bother sending the picture yet.  It's possible that the workaround
I
>> utilized can either be having a negative impact or needs to be
>> extended to more hardware.
>>
>> Attached you'll find an image with the two pieces highlighted.
>>
>> --
>> -Gene
First, 4.10-pre22 works as well as 4.07 on my dell optiplex 380. It is 
slow as hell from v5 to 6.03.
I also tried to put a 3com NIC inside, and the result was the same. But 
when i put the nic in an optiplex
740 it boots fine.

CLIENT MAC ADDR: B8 AC 6F
UNDI : baseio 0000 int 11 MTU 1500 type 1 "DIX+802.3" flags 0x1c1b

Ps : sorry for the capture quality i had to make a movie and extract a 
picture cause it was booting too fast.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Capture.JPG
Type: image/jpeg
Size: 138779 bytes
Desc: not available
URL:
<http://www.zytor.com/pipermail/syslinux/attachments/20140311/d427c3e3/attachment-0001.jpe>

Le 11/03/2014 10:32, Eric PEYREMORTE a ?crit :
> Le 11/03/2014 00:56, Gene Cumm a ?crit :
>> On Mon, Mar 10, 2014 at 7:55 PM, Gene Cumm <gene.cumm at
gmail.com> wrote:
>>> On Mon, Mar 10, 2014 at 7:15 PM, Gene Cumm <gene.cumm at
gmail.com> wrote:
>>>> On Mon, Mar 10, 2014 at 6:52 PM, Schlomo Schapiro 
>>>> <schlomo at schapiro.org> wrote:
>>>>> Hi,
>>>>>
>>>>> On 10 March 2014 18:13, Eric PEYREMORTE 
>>>>> <eric.peyremorte at iut-valence.fr>wrote:
>>>>>
>>>>>> Ok i give up. I will stick with the old version version
(4.07)
>>>>>> which works
>>>>>> well with dell 380 and 790.
>>>>>>
>>>>>> I tried to understand what happened between 4.07 and 5
but i
>>>>>> don't have
>>>>>> the skill to understand low level c.
>>>>>>
>>>>>> Seems that the memory management changed a lot, maybe
the
>>>>>> culprit. But as
>>>>>> many other things changed this is not obvious...
>>>>>>
>>>>> sad to say, we have exactly the same problem. With HTTP
downloads
>>>>> it is
>>>>> much worse, we could not find a stable and reliable version
after
>>>>> 4.x.
>>>>> Sadly nobody wanted to fix our syslinux problem, even as
paid
>>>>> development.
>>>>>
>>>>> I very much hope that the syslinux project will overcome
these
>>>>> obstacles.
>>>>> It would be sad to see all the new development stay unused
because
>>>>> if this.
>>>> It's also a balance of time.  While working on
4.10-pre*/5.10-pre*, I
>>>> found that some hardware misreports its behavior.  "Sure,
Interrupts
>>>> work" but they don't is but one that I worked around
on specific
>>>> hardware.
>>>>
>>>> -- 
>>>> -Gene
>>> Simple test (and boot failure is an option as long as the
core's
>>> messages are intact).  Could both of you try fetching
>>> Syslinux-4.10-pre22 (zip versus tar is your choice), extract out
>>> core/pxelinux.0 and boot with it then record the 4-digit value for
>>> flags (in the "UNDI: baseio" line) and the first 3 octets
(6 hex
>>> digits including 0s) of the MAC address and take a reasonable
screen
>>> shot (I find a cell phone against a solid object to be pretty
decent
>>> when angled to reduce glare and distanced for proper focus) but
don't
>>> bother sending the picture yet.  It's possible that the
workaround I
>>> utilized can either be having a negative impact or needs to be
>>> extended to more hardware.
>>>
>>> Attached you'll find an image with the two pieces highlighted.
>>>
>>> -- 
>>> -Gene
>
> First, 4.10-pre22 works as well as 4.07 on my dell optiplex 380. It is 
> slow as hell from v5 to 6.03.
> I also tried to put a 3com NIC inside, and the result was the same. 
> But when i put the nic in an optiplex
> 740 it boots fine.
>
> CLIENT MAC ADDR: B8 AC 6F
> UNDI : baseio 0000 int 11 MTU 1500 type 1 "DIX+802.3" flags
0x1c1b
>
> Ps : sorry for the capture quality i had to make a movie and extract a 
> picture cause it was booting too fast.
>
Some news here. I didn't test with 5.01 yet (didn't see that one sorry).
With 5.01 i don't have any problem. Problems begin with
5.10.
>
>
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>

-- 
Eric PEYREMORTE
Technicien Informatique - CRI
http://www.iut-valence.fr
T: 04.75.41.88.37

> Le 11/03/2014 10:32, Eric PEYREMORTE a ?crit :
> Some news here. I didn't test with 5.01 yet (didn't see that one
sorry).
> With 5.01 i don't have any problem. Problems begin with 5.10.
> -- 
> Eric PEYREMORTE
 
Hello Eric:

To sum up your report:
_ 4.0x works;
_ 4.10-pre22 (lwip branch) works;
_ 5.01 (elflink branch) works;
_ 5.10 (lwip merge into elflink) fails;

I wonder if testing 6.03-pre5 (which is *not* the latest) pre-built 
binaries (look under the bios/ directory) would work OK for you.

If you happen to test it, please remember to use the pre-built 
binaries already included in the official archive (as oppose to 
rebuilding them, which could introduce undesirable interactions), and 
to use all c32 files from the same 6.03-pre5 version (instead of 
mixing files from different versions), specially including 
ldlinux.c32, all lib*.c32 and all the rest of c32 modules (from the 
same archive from which you take pxelinux.0, under some subdiretory 
under "bios/").

TIA,
Ady.