<div dir="ltr"><div>I have similar symptoms, very reproducible. <br><br>same nic, but in an HP laptop:<br><font size="3"> lspci.. 00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection <br><br></font></div>
<font size="3">apt-get install grub-ipxe <br></font><div><div><font size="3">342468 Jan 6 03:59 ipxe.lkrn<br><br></font></div><div><font size="3">update it:<br><br>vt@pc9d:/boot$ sudo wget <a href="http://boot.ipxe.org/ipxe.lkrn">http://boot.ipxe.org/ipxe.lkrn</a><br>
2014-05-02 17:24:01 (188 KB/s) - ‘ipxe.lkrn’ saved [369882/369882]<br>vt@pc9d:/boot$ ls -l ipxe.lkrn <br>-rw-r--r-- 1 root root 369882 May 2 17:00 ipxe.lkrn<br>vt@pc9d:/boot$ md5sum ipxe.lkrn <br>ca7c8c447041b40c1d65e34fbf6d0346 ipxe.lkrn<br>
<br>reboot<br><br></font></div><div><font size="3">grub menu, pick ipxe,<br></font></div><div><font size="3">iPXE 1.0.0+ (c6474)<br></font></div><div><font size="3"> see dhcp/tftp traffic, repeat a few time just to be sure all is good. Nothing seems to be wrong. <br>
<br>reboot.<br><br>grab the ubuntu net installer: <br><br> wget -N <a href="http://archive.ubuntu.com/ubuntu/dists/trusty/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/linux">http://archive.ubuntu.com/ubuntu/dists/trusty/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/linux</a><br>
wget -N <a href="http://archive.ubuntu.com/ubuntu/dists/trusty/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/initrd.gz">http://archive.ubuntu.com/ubuntu/dists/trusty/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/initrd.gz</a><br>
</font></div><div><font size="3"><br></font></div><div><font size="3">pxe boot :<br> linux ubuntu/trusty/amd64/linux<br> append initrd=ubuntu/trusty/amd64/initrd.gz root=/dev/rd/0 rw<br><br></font></div><div>
<font size="3">Enter though the defaults about keyboards and such, get to networking:<br></font></div><div><font size="3">"Configuring network with dhcp... " error.<br></font></div><div><font size="3"><br></font></div>
<div><font size="3">At this point, nothing I can do will make the nic function, even rebooting and picking ipxe, or rebooting, hitting F11 and using the stock pxe in the nic's rom.<br></font></div><div><font size="3"><br>
</font></div><div><font size="3">I have to pull power/battery from the laptop to reset it.<br></font></div><div><font size="3"><br><br></font></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 2, 2014 at 11:40 AM, Michael Brown <span dir="ltr"><<a href="mailto:mcb30@ipxe.org" target="_blank">mcb30@ipxe.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 02/05/14 11:01, Christian Hesse wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Is the datapath broken in both directions?<br>
</blockquote>
<br>
No. The Dell notebook (the one acting as client and having the problem)<br>
receives packets. I can not see a single ethernet frame on the network sent<br>
from the notebook.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Are you able to transmit ARP<br>
requests or broadcast pings, or observe received data via tcpdump?<br>
</blockquote>
<br>
tcpdump receives all types of packets on the notebook.<br>
</blockquote>
<br></div>
If you try sending a large number of packets (e.g. using arping or a broadcast ping: anything that won't wait for a reply before sending out the next packet) then what happens to the TX packet counts and error counts reported by ifconfig?<br>
<br>
Does tcpdump running on the notebook see its own transmitted packets?<div class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Did a warm reboot and tried to boot via UNDI. BIOS reported:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
PXE-E05: The LAN adapter's configuration is corupted or has not been<br>
initialized. The Boot agent cannot continue.<br>
</blockquote>
<br>
Though this is not reproducible. After a cold reboot everything ist just fine<br>
again.<br>
</blockquote>
<br></div>
Good to know, but it's probably going to be easier to try to diagnose the problem from within Linux first.<div class="HOEnZb"><div class="h5"><br>
<br>
Michael<br>
______________________________<u></u>_________________<br>
ipxe-devel mailing list<br>
<a href="mailto:ipxe-devel@lists.ipxe.org" target="_blank">ipxe-devel@lists.ipxe.org</a><br>
<a href="https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel" target="_blank">https://lists.ipxe.org/<u></u>mailman/listinfo.cgi/ipxe-<u></u>devel</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Carl K
</div>