============================ R E L E A S E N O T E S ============================ Broadcom Gigabit Ethernet Driver for DOS ODI Copyright (c) 2002-2003 Broadcom Corporation All rights reserved. Version 6.08 May 22, 2003 ---------------------------- Fixes: ======== 1. Problem: (CQ #7839) (CQ #7840) When connected to a hub, a momentary disconnect will cause to lose the network connection until the driver is reloaded. Cause: The NIC does not generates PHY Change Interrupt after the PHY Reset when the link is first lost. Change: Driver preserves and restores Auto-negotiation advertisement register after the PHY Reset. Impact: None. 2. Problem: User try to force 1G. Cause: Driver allows parameter to be set. Change: Driver will performs Auto-negotiation when LineSpeed is set to 1000. Impact: None. Version 6.07 May 12, 2003 ---------------------------- Fixes: ======== 1. Problem: (CQ #4981) Running PERFORM3 test with a 5703S causes the system to either hang or reboot. (CQ #7448) When using DOS ODI and ODINSUP running NetBEUI protocol, Ruthless not able to use a remote drive. (CQ #7449) Stressing a SUT running Netbeui on ODINSUP eventually hangs the machine. Cause: The timer function crupted its stack. Change: Assigned correct stack label to timer function. Impact: None 2. Problem: (CQ #7683) Intermittently slow with BCM5704 Serdes/ CIOBE Serdes. Cause: Firmware (v1.8.0) performs autonegotiation when link is up and hardware autonegotiation logic indicates AUTONEG is completed. Change: Changed the firmware (v1.9.0) so that it will not perform autonegotiation when link is up and hardware autonegotiation logic indicates AUTONEG complete. Impact: 5704 Serdes/CIOBE Serdes. 3. Problem: (CQ #7718) Link detection intermittently fails when ASF is enabled. Cause: Contention with ASF firmware polls for PHY registers during PHY reset routine with PHY lockup Work-Around. Change: Driver stops ASF firmware before accessing PHY during initialization. Impact: When ASF is enabled, link establishment will take twice as long when ASF is disabled. 4. Problem: (CQ #7648) Fixed a problem where dynamic 10/100 or 10/100/1000 PHY auto-neg advertising based on GPIO2 state might not work correctly and appears to take a long time to re-establish the link. Cause: This issue was introduced when the PHY lockup workaround was added. This problem only occurs on the platform where GPIO2 state is used for dynamic PHY auto-neg. Change: Changed the PHY lockup workaround code so that it restores AUTONEG configuration. Impact: None. 5. Problem: (CQ #7706) Fixed a problem where driver would reports the forced LineSpeed when there is no cable detected. Cause: Driver was not checking for link when LineSpeed and Duplex were forced. Change: Driver checks for link always. Impact: None. Enhancements: ============= 1. Request: Added Keywords to force LineSpeed and Duplex in NET.CFG file Change: Recognized LINESPEED and DUPLEX keyword and force the speed and duplex mode accordingly. Impact: None. Notes: ======== 1. Problem #2 to #5 are fixed carry over from NDIS2's Lower Module. Version 6.06 April 29, 2003 ---------------------------- Fixes: ======== 1. Problem: The PHY lockup problem described in v6.05 Fix #3 below theoretically can affect other PHY cores in 5703 and 5705. Cause: Hardware bug in the PHY core. Probability of lockup is extremely small. Change: Expanded the lockup detection and recovery code to 5703, 5704, and 5705. Also changed the driver to do a PHY reset on link down. Impact: 5703 and 5704. 2. Problem: Driver cannot detects link change status when driver first initialized without cable attached. Cause: When driver initialized without cable attached, driver does not enable Link Change Status Interrupt. Change: Enable Link Change Status Interrupt when initialized even without cable. Impact: None. 3. Problem: When the cable is disconnected and reconnected, its takes longer than expected to re-establish link. Cause: When the cable is reconnected, driver runs Setup PHY with long delay. Change: Reduce the delay time in Setup PHY routine. Impact: None. Version 6.05 April 25, 2003 ---------------------------- Fixes: ======== 1. Problem: (CQ #7380) Driver not functional with 5700 A and B steps devices due to the smaller memory model being used by download an exclusive firmware for 16-bit (DOS) drivers. Cause: The exclusive firmware for 16-bit (DOS) drivers prevents the internal firmware to work-around the 5700 A and B steps' Errata. Change: Added 5700 support. When driver is loading upon 5700 A and B steps, it will not download the exclusive firmware for 16-bit (DOS) drivers and allocate the additional 48KB memory. Impact: For 5700 A and B steps, the driver's memory footprint is at ~83KB. 2. Problem: (CQ #6467) Intermittently, 5704S Fiber NICs cannot pass traffic when connect 3COM SuperStack 4900sx after a system-soft reset. Cause: Auto-Negotiation timing. Change: The fix was in the firm ware that gets download during initialization. Impact: 5704S Fiber. Enhancements: ============= 1. Request: Added support for dynamic 10/100 or 10/100/1000 phy auto-neg advertising for certain platforms. Change: Added a check for the state of GPIO2 during link change events and adjust auto-neg capability advertising accordingly. Impact: None. Notes: ======== 1. The code base for this version is from v6.04 with the 5704 PHY lock up work-around and zero MAC address fixes in v6.03.2 2. The Lower Module is ported from PXE v6.2.4. Version 6.03.2 April 18, 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. Version 6.03.2 April 18, 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. 03/20/03 -v6.04 Added 5788 support. 03/06/03 -V6.03 Removed support for 5700. 02/14/03 -V6.02 Updated Device IDs. 02/07/03 - v6.00 Fixed 5704 function (FUNNUM) loading and fiber support. 01/09/03 - v5.02 Fixed the SUBVID keyword. 12/13/02 - v5.01 Fixed Keyword bugs found w/DEVNUM etc. 09/24/02 - v5.00- Fixed problem with ASF enabled. Updated with PXE's LM v3.1.14. Added support for 5705, 5901, & 5704 Fiber. 08/20/02 -v3.01 Removed support for 5705 & 5901. 08/13/02 -v3.00 Added support for 5705 & 5901. 07/23/02 -v1.22 Fixed intermittent hang during driver load. 07/12/02 -v1.21 Slight change to firmware. 07/10/02 -v1.20 Reduced size of driver to 31K. 06/18/02 -v1.19 Fixed debug screen dump. Added display of PCI adapter configuration. Suports 5704. 05/16/02 -v1.18 Fixed MAC address display. 04/18/02 -v1.17 Fixed 100 half duplex bug. 04/03/02 -v1.16 Enhanced the fiber support. 02/28/02 -v1.15 Added wirespeed feature, decreased memory footprint, added device ids. 02/04/02 -v1.14 Fixed occasional drop connection problem when using IRQ 7. 01/25/02 -v1.13 Updated phy support for 5702/3. 01/22/02 -v1.12 Fixed 8023z support. 01/21/02 -v1.11 Fiber Support added. 01/04/02 -v1.10 Added MODEL keyword to load on first found matching SVID. 12/13/01 -v1.09 Better support for 5411 phy. 12/07/01 -v1.08 Fixed other PCI-X initialization problem. 11/27/01 -v1.07 Fixed PCI-X initialization problem. 10/26/01 -v1.06 Fix for speed value in sign on message. Additional board detection. 05/25/01 -v1.05 Fix for compatability with video adapters. 05/16/01 -v1.04 Fix for interrupt sharing problem. Added BUSNUM DEVNUM keywords. 05/02/01 -v1.03 Supports integrated mac 03/23/01 -v1.02 Driver Size reduction 03/01/01 -v1.00 Modified to work with ODINSUP 12/05/00 -v0.07 Added interrupt sharing, and unload support. 12/01/00 -v0.06 Added better link support. 11/28/00 -v0.05 Added code for better performance. 11/22/00 - v0.03- Changed code to fix bugs. 11/16/00 - v0.02- 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.