[syslinux] PXELINUX 4.10-pre*

Gene Cumm gene.cumm at gmail.com
Sat May 7 05:55:45 PDT 2011


On Thu, May 5, 2011 at 00:03, H. Peter Anvin <hpa at zytor.com> wrote:
> On 05/04/2011 08:08 PM, Gene Cumm wrote:
>>>
>>>  if (!(undi_iface.ServiceFlags & PXE_UNDI_IFACE_FLAG_IRQ))
>>>    pxe_irq_vector = 0; /* Interrupts not supported */
>>
>> Matches speed of 4.0x on tftp but failing on HTTP still
>> (netconn_connect error -5).
>>
>
> OK, that's odd.  -5 is the expected value for when the receiver is
> "deaf" (meaning it could not make a connection.)  Could you do a packet
> trace with the patch applied, please?

Trace sent privately.

Also, on ESXi (at least), I can make it use a different NIC.  Using
the Intel e1000 instead of the standard Flexible NIC (in vlance mode)
I have:

Network boot from Intel E1000
Copyright (C) 2003-2008  VMware, INC.
Copyright (C) 1997-2000  Intel Corporation

UNDI code segment at 9E95 len 0BDC
UNDI data segment at 98FF len 5960

UNDI: baseio 2000 int 11 MTU 1514 type 1 "DIX+802.3" flags 0xcc1b

This one works well with PXELINUX 4.10-pre13 but it appears that HTTP
URLs are not qualified with the client's domain (netconn_connect error
-6).

Another that works:
Network boot from VMware VMXNET3
Copyright (C) 2003-2008  VMware, INC.
Copyright (C) 1997-2000  Intel Corporation

UNDI code segment at 9E95 len 0CF0
UNDI data segment at 983F len 6560

UNDI: baseio 5000 int 10 MTU 1514 type 1 "DIX+802.3" flags 0xcc1b

VMware products make the choice of virtual NIC based on the target OS
for the VM.  Seeing as I chose "Other 2.6x Linux (32-bit)", it choose
an older card that's more likely to have a driver available (although
I'd think the e1000 should be standard for 2.6 over the
Flexible/vlance NIC).

In VMware Server 2.0.2, if I choose RHEL 5 64-bit, I get the e1000 NIC.

Summary:

1) 4.10-pre13 runs DEFAULT even though "PROMPT 1" is used and no
"TIMEOUT" or "TOTALTIMEOUT" directive is used.  Using both doesn't
change the behavior.

2) Names in an HTTP URL are not qualified with the domain handed out by DHCP.

3) Using a vlance/flexible NIC in a VMware VM requires a minor change to work.

-- 
-Gene




More information about the Syslinux mailing list