Release Notes
=============
Broadcom NetXtreme Gigabit Ethernet Driver
For Netware 4.x, 5.x, 6.x
Copyright (c) 2000-2004 Broadcom Corporation
All rights reserved.
Version 7.63 November 23, 2004
------------------------------
Fixes
=====
1.Problem: (CQ11117) Need SERDES parameter support.
Cause: Certain 5704 designs have requested that certain bits
be set in SERDES config to non-default values.
Change: Changes made to use presupplied value for SERDES
whenever parameter is found in NVRAM.
Impact: None.
2.Problem: (CQ11088) Remove the ability to set speed & duplex on
the 150T
Cause : The switch on this nic is set to auto only. The line
speed on the 5705 must always be set to auto for proper
link to be established.
Change : Added code to check for switch nics and always set it
to auto.
Impact : None.
Enhancements
============
1. Change : GPIO2 not allowed to output on device ids for 5753.
2. Change : Added code to support more flash (and EEPROM) types.
The flash write code has been separated into buffered
and unbuffered versions. The flash and EEPROM read
code has been modified to support sub-32bit word reads.
New nvram sizing functions have been introduced.
Version 7.62 October 12, 2004
---------------------------------
Enhancements
============
Support added for devices 16dd,16f7,16fd and 16fe.
Version 7.61 June 18, 2004
---------------------------------
Fixes
=====
1.Problem: CQ#10387 NW driver Ver 7.60 causes cert system
to abend.
Cause: The new Transmit Resource Logic causes the legacy
NICs in the secondary system to crash the system
during Transmit Endurance test.
Change: Back out the new Transmit Resource Logic.
Impact: Fixes CQ10387 issue.
Enhancements
============
1. Enable capacitive coupling feature on the PHY if this
feature is administratively enabled.
Version 7.60 June 10, 2004
---------------------------------
Enhancements
============
1. Added support for the 5789.
2. Added greater support for the 5751M.
Fixes
=====
Problem:CQ9033 Flow control does not work consistantly.
Cause: When the phy is initially powered on, the default behavior
is to not advertise flow control.
Change: Restart autoneg when flow control is configured to notify
the link partner that flow control is desired.
Impact: None.
Version 7.59 May 27, 2004
-------------------------
Fixes
=====
1.Problem: CQ#10033 5700 B2 LOM with v1.3 Bootcode does not pass
traffic.
Cause: The older 5700 v1.3 Bootcode did not implement shared
memory driver-bootcode interface; so the driver would
not recognize nor initialize the PHY.
Change: Added a fallback case to driver; so that in case of
older bootcodes the driver would initialize the PHY
for proper operation.
Impact: Fixes CQ10033 issue.
2.Problem: CQ#9992 5704 nic may draw VAUX during device initialization
when only one port has been enabled.
Cause: Incorrect programming of GPIO2 when only one port has
been enabled.
Change: Corrected programming of GPIO2.
Impact: 5704 nic will not draw from VAUX during device initialization.
3.Problem: CQ#9812 Fiber NIC 5701 has intermittent connectivity
at startup.
Cause: Unsuccessful negotiation at startup with fiber switch.
Change: Increased loop attempts to negotiate with fiber switch
from two to four times and also added initialize of
negotiation state machine prior to actual negotiation
attempt.
Impact: Fixes CQ9812 issue.
Enhancements
============
Request: CQ#10193 Disable embedded cpu for 5750/5721 A3 rev parts.
Cause: Hardware errata for 5750/5721 A3 revision parts.
Change: Added cpu halt routine in device initialization for
affected parts.
Impact: Embedded cpu for affected parts will be halted.
Version 7.58 May 12, 2004
----------------------------
Enhancements:
=============
1. (CQ#9811) Added IPMI PT and ASF support to the ODI-32 driver.
2. Added support for the 5751M.
Impact: IPMI PT is supported on 5721.
Version 7.57 April 23, 2004
----------------------------
Fixes:
======
Problem: (CQ#9955)Need to remove support for an untested
controller.
Cause: The controller has not been tested for this release.
Change: PCI Device ID for non-production controller was removed
from driver.
Impact: None.
Version 7.56 April 20, 2004
----------------------------
Fixes:
======
1.Problem: (CQ#9887)Bit Error Rate reporting greater than desired
in corner case testing on 575x/5705 PHYs.
Cause: PHY settings not set to optimum setting.
Change: The driver changed the PHY settings.
Impact: None.
Enhancements:
============
Changed Link related counter strings for better clarity.
Version 7.55 April 14, 2004
----------------------------
Fixes:
======
Problem: (CQ#9116) Frame integrity test failure in Novell
certification test.
Cause: The driver ran out of transmit buffers without
notifiying the OS, causing the test to fail.
Change: The driver properly notifies the OS when it depletes
transmit resources.
Impact: None.
Version 7.54 April 2, 2004
----------------------------
Fixes:
======
1.Problem: (CQ#9695) 5705 Error counters did not increment
under negative testing.
Cause: Values were not being read properly.
Change: Added code to access registers properly before
updating stats.
Impact: None.
2.Problem: (CQ#9481) 5751 LEDs did not show correct color codes.
Cause: Controller LED config was not setup properly.
Change: Controller LEDs are setup in the driver whereas they
were setup in the firmware in v7.53.
Impact: None.
Version 7.53 March 18, 2004
----------------------------
Fixes:
======
1.Problem: (CQ#9607) PCI bus mode description displayed invalid value.
Cause: Description was changed, but not corresponding driver code.
Change: Driver displays correct value
Impact: None.
2.Problem: 5751 NIC LEDs not displaying NIC activity.
Cause: The code was not implemented for LED display
Change: LED code is implemented.
Impact: None.
Version 7.52 March 5, 2004
----------------------------
Fixes:
======
Problem: 5700 controller was not being recognized.
Cause: Driver code did not check for 5700 device id. This bug
was introduced in v7.50.
Change: Driver now checks for 5700.
Impact: None.
Version 7.51 February 27, 2004
----------------------------
Enhancements:
============
1.Support of 575x rev A1.
2.Reset delay values decreased.
3.Driver invokes a further reset subsequent to PXE usage.
Impact: None.
Version 7.50e February 4, 2004
----------------------------
Fixes:
======
Problem: (CQ#9295) PCI MODE field in Monitor displayed PCIX mode, when
controller was actually in PCIE mode.
Cause: PCIE mode display was not implemented.
Change: Added a PCIE mode.
Impact: None.
Version 7.50d January 13, 2004
----------------------------
Fixes:
======
Problem: Link occasionally not established.
Cause: Initialiazation/Reset delay was not long enough.
Change: Increased delay time in code after a initialization/reset.
Impact: None.
Version 7.50b November 26, 2003
----------------------------
Fixes:
======
Problem: Occasional dropped connection.
Cause: 802.2 HW Checking caused paddeded packets to be rejected.
Change: Turned off default 802.2 checking in HW.
Impact: None.
Version 7.50a November 25, 2003
----------------------------
Enhancements:
=============
Enhancement: Added support for 575x
Impact: New controller.
Version 7.08 February 4, 2004
----------------------------
Enhancment
==========
Request: (CQ #9141)String change.
Change: String changed as requested in CQ#9141
Impact: None.
Version 7.07 January 13, 2004
----------------------------
Fixes:
========
Problem: (CQ # 8532) The MAGICP= keyword does not function
as documented.
Cause: The code did not enable the PME bit.
Change: Code was changed to enable PME bit on shutdown when
the MAGICP= keyword is invoked.
Impact: None.
Version 7.06 January 6, 2004
----------------------------
Fixes:
========
Problem:(CQ # 8835) Client32 driver halt occurs occasionally
when running heavy stress tests.
Cause: Driver did not thoroughly replenish receive packet
resources causing the driver to reject packets.
Change: Driver modified to service packets more thoroughly.
Impact: None.
Version 7.04 December 3, 2003
----------------------------
Fixes:
========
Problem:(CQ # 8982) Use of the vlan=1 keyword on multiple adapters
displays the following message after the first adapter loads
successfully:
/enter value for vlan between - 0 - 0
Cause: The keyword was not reset properly by the driver after the
primary adapter loaded.
Change: Code properly resets the keyword after each driver load.
Impact: None.
Version 7.03 November 14, 2003
----------------------------
Enhancements:
=============
Enhancement:Turned off default hardware 802.2 Length checking.
Change: The code was changed to enable the hardware 802.2 length
checking feature when set in a keyword. Default is off.
Impact: None.
Version 7.02 October 17, 2003
----------------------------
Fixes:
========
Problem: (CQ #8588) Fiber adapter will not default to link at 1000Mbs FD
when a switch will not participate in autonegotiation.
Cause: The fall back algorithm was not implemented.
Change: A timer routine will cause a retry in the fiber link setup
which in turn allows the adapter to eventually default to
link at 1000Mbs if a connection is sensed on the fiber.
Impact: None.
Version 7.01 October 09, 2003
----------------------------
Fixes:
========
Problem: (CQ #8561) The driver would hang on Client32 if receiving
packets with VLAN tags.
Cause: The VLAN tag support was enabled allowing packets to be
received and the driver behaved as if BASP were loaded,
causing a hang.
Change: VLAN tagging is enabled only when the VLAN keyword is set.
Impact: None.
Version 7.00 August 28, 2003
----------------------------
Fixes:
========
Problem:(CQ #8389)Update readme.txt to reflect SPEED keyword
changes. Update driver version to be consistent w/other
drivers.
Change: Updated.
Impact: None.
Version 6.08 August 22, 2003
----------------------------
Fixes:
========
Problem: (CQ #7931)
Need to have a 1000FD forced autoneg option in the
driver similar to that of 10FD, 10HD, 100FD and
100HD options available in speed= parameter.
Cause: The speed would autoneg with all values due to
an error in enumeration of user input.
Change: Fixed code so that user input is passed with
correct values.
Impact: All adapters.
========
Problem: (CQ #8303)
Fiber 5704 B0 would not pass traffic properly.
Cause: Transmit code was over-writing used BDs.
Change: Changed transmit code to transmit serially.
Impact: All adapters.
Version 6.07 August 13, 2003
----------------------------
Enhancements:
=============
1. Enhancement:
Syncs up with the latest changes to support 5704 B0.
Change: Changes to hardware specific code.
Impact: None.
2. Enhancement: (CQ #7931)
Customers request a user enabled keyword that allows
setting the speed to 1000FD. Currently speed can be
forced or advertised only upto 100FD.
Change: A 1000FD is a recognized parameter for the SPEED
keyword. 1000FD is only advertised in autoneg.
Impact: All gigabit adapters.
Fixes:
========
Problem: (CQ #8095)
Cause: Spurious interrupts displayed on some NetWare systems.
Change: Driver has read back functions for each write function to the
adapter interrupt specific registers.
These functions are user keyword controlled and can be
disabled. The keyword is SPURIOUSFIX.
Impact: Slightly slower performance.
Version 6.06 May 16, 2003
-------------------------
Enhancements:
=============
1. Enhancement:
Syncs up with the latest lower module code
that has more bond id checking.
Change: Keyword check for "C32=1" to use in the DOS
Client32 environment to force initialization failure
if no link is found. Under this condition, the
following message is displayed:
"** Error:187 Link Down. Initialization Failed"
Impact:
None.
Version 6.04 May 12, 2003
-------------------------
Fixes:
========
1. Problem: (CQ #4441)
Cause: Only seen on NetWare 4.2 server & only seen on specific
machines when sharing IRQs w\multiple Broadcom Adapters:
OS occasionally loops on the wrong adapter driver entry
point. The System appears non functional.
Change: Code was added to detect this condition and allow the
OS to call a different driver entry point.
Impact: All adapters. There should be no noticeable difference
if earlier driver versions function properly.
2. Problem: (CQ #7729)
Cause: Driver displayed 570x when 5901 was loaded.
Change: The driver displays a non adapter specific string.
Impact: Same string is displayed for all adapters.
Version 6.03 April 29, 2003
-------------------------
Fixes:
========
1. Problem: (CQ #7280)
Cause: Phy Locks up when continual resets to phy occur.
Note: This a very rare condition and may not be reproducible.
Change: Check the phy after each phy reset to determine if lockup
occurs. Additional phy reset clears lockup.
Impact: The fix to this problem should not be noticeable.
Fix is activated in 5703, 5704, 5705 adapters.
03/20/03 v6.02
Added support for 5788. Removed WireSpeed keyword.
02/14/03 v6.01
Changed jumbo support from 9100 max to 9000 max. Link message is changed.
Fixed CarrierSense Counter. Added new Device IDs.
01/13/03 v5.09
Fixed cable disconnect delay for server.
01/02/03 v5.06
Fixed cable disconnect delay for Client32.
12/20/02 v5.05
Enhanced client32 support.
12/09/02 v5.04
Added PCIX mode status in custom stats.
Fixed Link mode.
11/22/02 v5.03
Fixed client32 slow connection problem. Checksum offload is default off.
11/08/02 v5.02
Fixed checksum problem found in NW6 support pack 2.
10/29/02 v5.01
Fixed rare eeprom read bug.
09/26/02 v5.00
This version has 5705 support.
09/26/02 v4.00
Fixed client32 cable disconnect bug. Took out 5705 support.
08/21/02 v3.03
Added support for 5705.
05/13/02 v3.02
Changed water marks for performance tuning.
05/13/02 v3.01
Fixed bug in tx checksum that prevented snmp events.
Fixed bug preventing completion of 72 hour stress test.
05/03/02 v3.00
Added support for 5704 controller.
05/07/02 v2.32
Fixed bug in tx checksum that prevented snmp events.
04/19/02 v2.31
Added delays in driver for initialization.
03/22/02 v2.29
Fix of Jumbo size reported to Netware certification.
03/20/02 v2.28
Added changes to control LEDs.
03/19/02 v2.27
Added two command line keywords: fiber=auto/force & MagicP=0/1.
03/14/02 v2.26
Changed driver to work in DOS CLIENT32.
VLAN support broken on older versions of BASP use only on BASP 2.09 or later.
02/25/02 v2.25
Fixed some keywords that were not being reset properly.
Added WireSpeed feature.
02/07/02 v2.24
Added Jumbo frame dynamic size. Poll mode display.
01/22/02 v2.23
Fixed dropped client problem.
01/22/02 v2.22
Further enhancement of the spurious int fix.
01/19/02 v2.21
Spurious int fix is now default on.
12/19/01 v2.20
Added code to better handle spurious interrupts on some machines.
12/06/01 v2.19
Fixed ipx vlan problem.
11/28/01 v2.18
Fixed 100 hr stress problem.
11/16/01 v2.17
Fixed multicast address size, performance improvement.
11/07/01 v2.16
Fixed backward compatibility probs.
10/30/01 v2.15
Jumbo certified.
09/18/01 v2.14
Fixed cable fault problem.
09/12/01 v2.12
Fixed FrameAlignment & ChecksumError counters.
08/24/01 v2.10
Fixed a PCIX problem.
08/17/01 v2.09
Fixed a jumbo mode problem.
08/03/01 v2.08
Fixed Perform3 problem.
07/20/01 v2.07
Improved fiber support.
07/06/01 v2.06
802.3 bug fix.
07/02/01 v2.05
Fix for fiber link.
Fix for shutdown.
06/14/01 v2.02
Fixed fiber support/performance improvements.
06/04/01 v2.01
Rebuild for new release.
05/04/01 v1.27
Added registration for advanced server program.
04/24/01 v1.25
supports 5701
04/12/01 v1.23
Reset bug fix.
03/27/01 v1.22
Jumbo frame support added.
02/26/01 v1.20
Checksum is default off.
02/15/01 v1.18
Fix for vlan bug in ipx, and min packet size with vlan.
02/08/01 v1.16
Fixed bug for 4.x primary install.
02/05/01 v1.15
Fixed new persistent driver bug, multicast bug, and basp support bug.
01/30/01 v1.12
Fix for vlans.
01/29/01 v1.10
Added changes in PCI-X support.
01/26/01 v1.09
Fixed NESL bug.
01/19/01 v1.08
Fixed persistent driver mode bug.
01/05/01 v1.07
Added persistent driver mode.
12/29/00 v1.06
Added better checksum support.
12/21/00 v1.05
Added more user info.
12/15/00 v1.04
Fixed spurious interrupt reports.
12/11/00 v1.03
Made changes for better performance.
12/08/00 v1.02
Added better ipx w/802.3 support.
12/01/00 v1.01
Added console status messages for link up/down.
11/27/00 v1.00
1st release.
11/22/00 v0.26
Real update of lower module.
11/22/00 v0.25
Updated lower module for led change.
11/22/00 v0.24
Added support for 32 minimum receive buffers.
11/18/00 v0.23
Updated lower module for better flow control. Passes Novell certification.
11/17/00 -v0.22
Upgraded the checksum off load support & receive code.
11/08/00 -v0.21
Updated lower module.
11/06/00 -v0.20
Fixed link problem and unwanted messages.
11/03/00 -v0.19
Added support for new firmware.
11/01/00 -v0.18
Fixed vlan bug for large packets.
Changed promiscuous mode support.
10/30/00 -v0.17
Added vlan support for BASP.
10/28/00 -v0.16
Added code to guard against ECB starvation. Enhanced code for speed
parameter.
10/23/00 -v0.15
Added a custom NESL event for changing the MAC address to work with
BASP.
10/20/00 -v0.14
Made adjustments for certification test.
10/16/00 -v0.13
New release.
10/13/00 -v0.12
Fortified reset code and isr.
10/6/00 - v0.11
Added support for sharing ints between multiple B57s.
Added support for "auto" within the speed keyword.
Displays line speed more consistently.
9/22/00 - v0.10
Changed allocated resources amount. Fixed bug in user defined
parameters.
9/20/00 - v0.09
Change in reset and interrupt code (checks if initialized).
9/14/00 - v0.08a
Changed interrupt enable/disable.
9/13/00 - v0.08-
First Engineering Release.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.