I noticed this, this morning as well. I plan to do some debugging this
afternoon, once I get some other issues out of the way from the start of
our semester.
I'm not sure if Kevin has seen the previous post or not, but it's here:
http://lists.ipxe.org/pipermail/ipxe-devel/2012-May/001461.html .
I do want to thank the guys/gals at Broadcom who are putting an effort
into this, as it does appear to have fixed a different issue we had (If
you booted via USB, into a WinPE image, the WinPE image was not able to
use the NIC. This appears to be working as expected now).
I plan to do a DEBUG=tg3 build, so if more debugging, or another is
requested, let me know and I can include that. The machine I have for
testing does have a Serial output, so I can easily grab any console output.
Brandon Penglase
On 08/21/12 10:53, Brendon Walsh wrote:
Hi,
I just wanted to notify everyone that the recent commit with fixes for
the tg3 driver (a05871d89ad9b94248049c66f238092fc896e9aa) have not
made any noticeable difference in regards to functionality on gigabit
interfaces.
I am testing with BCM5764M and while iPXE will function properly on
100Mbit, it fails on DHCP still on a gigabit link. This behaviour is
the same as before this commit.
Thanks Kevin and all others who are working on this. I can provide any
data that may help with resolving this issue.
Brendon
_______________________________________________
ipxe-devel mailing list
ipxe-devel@lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
_______________________________________________
ipxe-devel mailing list
ipxe-devel@lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
