Booting wds without wimboot

[chmeyer]

Okay, I tried the testing procedure: http://ipxe.org/dev/driver

1. link detection (IMO seems okay):
iPXE> ifstat
net0: xx:xx:xx:xx:xx:xx using 82547ei on PCI02:01.0 (closed)
[Link: down, TX:0 TXE:0 RX:0 RXE:0]
[Link status: Dp#own (http://ipxe.org/38086101)]
iPXE> ifopen net0
INTEL 0xbddc4 ring 03800 is at [1f64bf00,1f64c000)
INTEL 0xbddc4 ring 02800 is at [1f64c000,1f64c100)
INTEL 0xbddc4 link status is 00000383
INTEL 0xbddc4 link status is 00000383
iPXE> ifstat (with cable connected):
net0: xx:xx:xx:xx:xx:xx using 82547ei on PCI02:01.0 (open)
[Link:up, TX:0 TXE:0 RX:42 RXE:27]
[RXE: 16 x "Operation not supported (http://ipxe.org/3c086003)"]
[RXE: 9 x "The socket is not connected (http://ipxe.org/380f6001"]
[RXE: 2 x "Error 0x440e6003 (http://ipxe.org/440e6003)"]
-> disconnect cable
iPXE> INTEL 0xbddc4 link status is 00000381
ifstat
net0: xx:xx:xx:xx:xx:xx using 82547ei on PCI02:01.0 (open)
[Link:down, TX:0 TXE:0 RX:85 RXE:62]
[Link status: Down (http://ipxe.org/38086101)]
[RXE: 24 x "Operation not supported (http://ipxe.org/3c086003)"]
[RXE: 36 x "The socket is not connected (http://ipxe.org/380f6001"]
[RXE: 2 x "Error 0x440e6003 (http://ipxe.org/440e6003)"]
-> reconnect cable
iPXE> INTEL 0xbddc4 link status is 00000383
ifstat
net0: xx:xx:xx:xx:xx:xx using 82547ei on PCI02:01.0 (open)
[Link:up, TX:0 TXE:0 RX:99 RXE:73]
[RXE: 26 x "Operation not supported (http://ipxe.org/3c086003)"]
[RXE: 45 x "The socket is not connected (http://ipxe.org/380f6001"]
[RXE: 2 x "Error 0x440e6003 (http://ipxe.org/440e6003)"]

2. basic DHCP (IMO seems okay):
dhcp net0
Configuring (net0 xx:xx:xx:xx:xx:xx)... ok
iPXE> route
net0: 172.16.0.114/255.255.0.0 gw 172.16.0.1

3. close and reopen:
ifclose
INTEL 0xbddc4 MAC reset (ctrl 003c0261)
iPXE> dhcp net0
INTEL 0xbddc4 ring 03800 is at [1f64bf00,1f64c000)
INTEL 0xbddc4 ring 02800 is at [1f64c000,1f64c100)
INTEL 0xbddc4 link status is 00000383
INTEL 0xbddc4 link status is 00000383
Configuring (net0 xx:xx:xx:xx:xx:xx)... ok
iPXE> route
net0: 172.16.0.114/255.255.0.0 gw 172.16.0.1

4. large file transfer correctness:
iPXE> imgfetch tftp://172.16.0.123/512mb
tftp://172.16.0.123/512mb... No space left on device (http://ipxe.org/34012006)
iPXE> imgfetch http://172.16.0.123/512mb
http://172.16.0.123/512mb... Connection reset

Ooops. Seems that the machine has not enough RAM. I will update it later but this is not the main problem since the different machine (x64 instead of x86) with rtl8168 driver which fails, too has 8GB RAM.
Is there a problem so far? I don't see any.

Christian