Date: Tue, 16 Jun 2009 12:09:01 +0200 From: "Eric" <ericd@free.fr> To: "David Christensen" <davidch@broadcom.com>, <freebsd-drivers@freebsd.org> Subject: Re: Broadcom NetXtreme II BCM5709 Gigabit Ethernet Dell 610 and Dell Message-ID: <F15354576A78441A98D53C4F9F96F340@PCdeEricDHEM> In-Reply-To: <5D267A3F22FD854F8F48B3D2B523819339EBCC774C@IRVEXCHCCR01.corp.ad.broadcom.com> References: <5E42C46B1EB84E55963EC55EF515B4A0@PCdeEricDHEM> <5D267A3F22FD854F8F48B3D2B523819339EBCC774C@IRVEXCHCCR01.corp.ad.broadcom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks David. If it may help other : a bootable iso image of cdrom with tools is available here : http://www.broadcom.com/support/ethernet_nic/driver-sla.php?driver=NX2-diag Having someone going to datacenter tomorrow and then let you know result. ;=) Have a nice day. Eric. ----- Original Message ----- From: "David Christensen" <davidch@broadcom.com> To: "Eric" <ericd@free.fr>; <freebsd-drivers@freebsd.org> Sent: Tuesday, June 16, 2009 3:47 AM Subject: RE: Broadcom NetXtreme II BCM5709 Gigabit Ethernet Dell 610 and Dell > Does any one find solution to this problem as we have same, > try a proposed patch but still have problem and don't find > anywhere the solution? I've worked with a few people off list and it seems there is an issue with the way the management firmware loaded on the 5709C enables packet reception before the FreeBSD driver has an opportunity to load. I haven't been able to find a driver only workaround that works with the "production" firmware on the Dell systems. (I don't have any reason to believe this issue is limited to just the Dell systems but I simply haven't been able to test I on other systems yet.) The only reliable workaround at present is to disable the management firmware on the 5709C. You should have a DOS based "uxdiag.exe" utility on the driver disks you recevied from Dell. If you run the commands "C:\>uxdiag.exe -c 1 -mfw 0" "C:\>uxdiag.exe -c 1 -mfw 0" You will disable the management firmware on both devices. I have tested an unreleased version of firmware which does seem reliably resolve the problem but we could be a month on more away from releasing it. Dave
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F15354576A78441A98D53C4F9F96F340>