Release
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Release as PDF for free.
More details
- Words: 3,418
- Pages: 18
============================ R E L E A S E N O T E S ============================ Broadcom 440x 10/100 Integrated Controller Driver For Microsoft Windows Operating Systems Copyright (c) 2000-2004 Broadcom Corporation All Rights Reserved. Version 4.23 INF Update (August 19, 2004) -------------1. Problem (CQ#10779) 4401: Add multiple A1 and B0 device support for OEM to v4.23 driver. Cause: OEM Request to add new IDs to old certified driver. Change: Added new IDs to old driver installation file. Impact: Correct CQ#10779 issue.
Version 4.23 (September 26, 2003) -------------1. Problem (CQ#8525) 4401: OID_GEN_RCV_ERROR - remove fragmented packets Cause: Driver included Packet fragment count in RX Error count statistic OID_GEN_RCV_ERROR. Change: Driver changed to exclude Packet fragment count for RX Error statistic OID_GEN_RCV_ERROR. Impact: Correct CQ#8525 issue.
Version 4.22 (September 23, 2003) -------------1. Problem (CQ#8479) 4401-B0: HP INF file references to project names Cause: Driver installation inf file had project names. Change: Removed project names from driver installation inf Impact: Correct CQ#8479 issue.
file.
Version 4.21 (September 22, 2003) -------------1. Problem (CQ#8499) 4401: Rx Symbol Error when connected to Fujitsu LH 1108C HUB during file transfers resulting into low performance throughput. Cause:
The 4401 These RX ultimate This can
with Change: flagged
PHY hardware reports RX Symbol Errors due to collisions. Symbol Errors can be ignored because the CRC Check is the decision maker if a packet should be dropped or not. be considered a software workaround to remedy operations
particular HUBs that are not compliant to IEEE Specifications. A Registry key has been created for accepting packets that have been
by PHY hardware with RX Symbol Error condition. The default behavior is to implement this Software workaround. Impact: Correct CQ#8499 issue. 2. Problem (CQ#8502) 4401: Rx Symbol Error Accounting Cause: Due to CQ 8499 we had to modify driver error accounting. Change: Modified Driver to account for RX fragmented packets for RX total error statistics. Impact: Correct CQ#8502 issue.
Version 4.20 (September 19, 2003) -------------1. Problem (CQ#8392) 4401: PME Enable setting in conjunction with WOL Cause: Request to reduce power consumption during low power to zero amps. Change: Driver enables PowerManagementEnable (PME) when WOL is not "None" in the Advanced Properties of 4401; and Windows "Allow this device to Wake up..." is also set. Impact: Correct CQ#8392 issue.
Version 4.19 (September 18, 2003) -------------1. Problem (CQ#8482) 4401-B0: WinXP - 'Allow only management stations ...' doesn't stick when Advanced option was set to Magic Packet Cause: For 4401-B0 Driver was not reporting Magic Packet support during service of OID_PNP_CAPABILITIES. Change: Corrected Driver handling of OID_PNP_CAPABILITIES for B0 chip. Impact: Correct CQ#8482 issue.
Version 4.18 (September 18, 2003) -------------1. Problem (CQ#8472) 4401 B0 does not show 'Both' in Wakeup capabilities in Win 98/Me Cause: Driver installation inf file did not specify correct options for WOL for 4401 B0. Change: Corrected Driver installation inf file for proper 4401 B0 WOL support. Impact: Correct CQ#8472 issue. 2. Problem (CQ#8479) 4401-B0: HP INF file references to project names Cause: Driver installation inf file had project name. Change: Driver installation inf file project name was removed. Impact: Correct CQ#8479 issue. 3. Problem (CQ#8482) 4401-B0: WinXP - 'Allow only management stations ...' doesn't stick Cause: For 4401-B0 Driver was not reporting Magic Packet support during service of OID_PNP_CAPABILITIES. Change: Corrected Driver handling of OID_PNP_CAPABILITIES for B0 chip. Impact: Correct CQ#8482 issue.
Version 4.17 (September 15, 2003) -------------1. Problem (CQ#8392) 4401: PME Enable setting in conjunction with WOL Cause: Request to reduce power consumption during low power to zero amps. Change: Driver enables PowerManagementEnable (PME) when WOL is not "None" in the Advanced Properties of 4401; and Windows "Allow this device to Wake up..." is also set. Impact: Correct CQ#8392 issue.
Version 4.16 (September 15, 2003) -------------1. Problem (CQ#8463) 4401 B0 failed to wake up with MagicPacket when local administered address advanced option was set to a custom value.
Cause: WOL instead Change: use permanent Impact:
4401 Driver was always using permanent address to setup MagicPacket of the optional local administered address. 4401 Driver was modified to use local administered address if set; or address if local administered is not specified. Correct CQ#8463 issue.
Version 4.15 (September 10, 2003) -------------1. Problem 4401: Installation .inf file update to support OEM. Cause: New 4401 PCI Device Identification. Change: 4401 Driver installation .inf file was updated. Impact: None.
Version 4.14 (September 9, 2003) -------------1. Problem (CQ#8441) 4401: Failed WHQL HCT 11.2 ChkInf test procedure. Cause: 4401 Driver installation .inf file was missing a string definition for DriverOEMVersion Change: 4401 Driver installation .inf file was updated to have this string definition. Impact: Correct CQ#8441 issue.
Version 4.13 (September 3, 2003) -------------1. Problem (CQ#8325) 4401: Rpt2.0SI- Windows XP Event Viewer error: PSched: The netcard driver failed the query: OID_GEN_LINK_SPEED. This error occured when cable was disconnected. Cause: 4401 Driver was waiting seven seconds for Link up prior to handling of the above OID. Change: Modified 4401 Driver to wait maximum of 3.9 seconds and then complete the above OID when cable has been disconnected and link was not established. Impact: Correct CQ#8325 issue.
2. Problem (CQ#8358) 4401-B0, NDIS5.1 Intermittently Fails to Wake Up from The Standby Sleep State Cause: 4401 Driver setup for case of Both Magic Packet & WakeUp Frame WOL was not correct. Change: Corrected 4401 Driver setup for case of Both Magic Packet & WakeUp Frame WOL. Impact: Correct CQ#8358 issue. 3. Problem (CQ#8393) 4401 B0 halts NDIS tester during 2m_WOLMagicPacket script in Win2k WHQL Tests. Cause: 4401 Driver setup for case of Magic Packet WOL was not correct. Change: Corrected 4401 Driver setup for Magic Packet WOL. Impact: Correct CQ#8393 issue. 4. Problem (CQ#8412) 4401-B0 Drops Network Connection Once Awaken from Standby, via Magic Packet. Cause: 4401 Driver setup for case of Magic Packet WOL was not correct. Change: Corrected 4401 Driver setup for Magic Packet WOL. Impact: Correct CQ#8412 issue.
Version 4.12 (August 29, 2003) -------------1. Problem (CQ#8392) 4401: PME Enable setting in conjunction with WOL Cause: Request to reduce power consumption during low power to zero amps. Change: Driver would only enable PowerManagementEnable (PME) when WOL is not "None" in the Advanced Properties of 4401. Impact: Correct CQ#8392 issue. 2. Problem (CQ#8391) 4401 fails WHQL 2m_wolPattern test with Windows XP NDIS tester Cause: Driver setup of WOL Patterns when WOL Both option was selected. Change: Corrected Driver setup of WOL Patterns when WOL Both option is selected.
Impact: Correct CQ#8391 issue.
Version 4.11 (August 22, 2003) -------------1. Problem (CQ#8358) BCM4401-B0: Intermittently Fails to Wake Up from Standby/Hibernate/Shutdown. Cause: Incorrect driver setup of Magic Packet WOL operation for 4401 B0. Change: Corrected driver setup of 4401 B0 chip for Magic Packet WOL operation. Impact: Correct CQ#8358 for proper WakeOnLan operation of Magic Packets and Interesting Packets.
Version 4.10 (August 18, 2003) -------------1. Problem (CQ#8306) CQ#8306 4401: Locally administered MAC Network Address. Cause: Not implemented in prior 4401 Drivers. Change: Add Locally administered MAC Network Address to 4401 Driver. Impact: Correct CQ#8306 issue.
Version 4.00 (August 13, 2003) -------------Added support for 4401 B0 Hardware and increased driver version to 4.00
Version 3.64 (August 6, 2003) -------------Fixes: ========= 1. Problem (CQ#8224) CQ#8224 4401: function. Cause: 4401 Driver had power mode. Change: 4401 Driver was mode setup. Impact: Correct CQ#8224
Magic Packet wake-up with multicast packet did not not enabled Multicast during its process to go to low modified to enable Multicast as part of its low power issue.
2. Problem (CQ#8178) CQ#8178 4401:
CRC RX Error Statistics reported was not as expected. 4401: Private Statistics reported during OID: T3_OID_GET_STATISTICS_COUNTERS not
accumulative. Cause: resulting
statistics. Change: Impact:
4401 Driver reported sum of two CRC error counters with same value, in CRC count that was twice as actual errors. 4401 Driver during handling of OID: T3_OID_GET_STATISTICS_COUNTERS did not use the "accumulative" method of keeping and reporting of 4401 Driver was modified to gather and send the proper statistics. Correct CQ#8178 issue.
Version 3.63 (June 30, 2003) -------------Fixes: ========= 1. Problem (CQ#8101) CQ#8101 BCM4401-A1 NIC/LOM Intermittently fails to retain correct line speed when Advanced Option is set to 10Half Mbps; and running BACS Diagnostics. Cause: 4401 Driver did not reinitialize the PHY options after going in and out of Diagnostic mode; as a result of driver change for CQ#8027. Change: 4401 Driver was modified to reinitialize the PHY options when Diagnostic mode is done. Impact: Correct CQ#8101 issue.
Version 3.62 (June 24, 2003) -------------Fixes: ========= 1. Problem (CQ#8085) CQ#8085 4401: 802.1p Priority Tagging not as expected. Cause: 4401 always generated 802.1p Priority marked packets, when its Advanced Option was set to Enable 802.1p. Change: Modified driver to generate 802.1p Priority marked packets only when packet priority is non zero; per Windows XP Device Driver Kit documentation. Impact: Same 8021.p Priority Tagging as Broadcom 570x Adapters.
Version 3.61 (June 18, 2003) -------------Fixes: ========= 1. Problem (CQ#8027, CQ#7976, CQ#7806) CQ#8027 - 4401: WinXP - connectivity issue when changing speed/duplex with 802.1p option set and QoS Packet Sheduler enabled. CQ#7976 - 4401: Intermittently Loses Network Connection upon Change in Line Speed/Duplex CQ#7806 - 4401: IP address gets lost after changing from 10HDX->AUTO>100HDX Cause: 4401 Driver was taking longer than 3 seconds to respond to OID_GEN_MEDIA_CONNECT_STATUS; which caused Microsoft NDIS component "QoS Packet Scheduler" to disable IP address of 4401. Change: Modified driver to respond to OID_GEN_MEDIA_CONNECT_STATUS quicker, by increasing the frequency of Phy Link status check. Impact: Resolve connectivity issues CQ#8027, CQ#7976, CQ#7806 2. Problem (CQ#7842) 4401: Link activity reported by driver included Broadcast and Multicast Packets Cause: Original implementation. Change: Modify driver to report only Unicast Packets when polled for Link activity. Impact: None. 3. Problem (CQ#7788) 4401: The Power Management Tab for 4401 disappears intermittently Cause: Operating System Suspected. Change: Modified driver to wait 50 milliseconds before returning the result of PlugNPlay Power Management Query OIDs. Impact: None.
Version 3.60 (May 15, 2003) -------------Fixes: ========= 1. Problem (CQ#7796)
4401: BACS Diagnostics does not finish MAC- LoopBack test at 10 Half Duplex.
Cause:
Change:
Reported Link Down to NDIS while running this test. Keep Link Status Up while running this MAC LoopBack test.
Impact:
Resolve the problem of the MAC LoopBack diagnostic not finishing.
Version 3.59 (May 9, 2003) -------------Fixes: ========= 1. Problem (CQ#7699) 4401: Slow boot time when network cable unplugged Cause: 4401 Initial report for OID_GEN_MEDIA_CONNECT_STATUS was Link Up when Network Cable was disconnected. Part of Microsoft Workaround for Pushing Policy issue. Change: 4401 driver pends this request and determines link connection status first and then indicates results to caller of OID_GEN_MEDIA_CONNECT_STATUS. Impact: Improve boot time and resolve this issue. 2. Problem (CQ#7700) 4401: NDIS Tester 3.91 failure in function 1c_ginfo.leth Cause: 4401 Initial report for OID_GEN_MEDIA_CONNECT_STATUS was Link Up when Network Cable was disconnected. Part of Microsoft Workaround for Pushing Policy issue. Change: 4401 driver pends this request and determines link connection status first and then indicates results to caller of OID_GEN_MEDIA_CONNECT_STATUS. Impact: Resolve NDIS Tester 3.91 failure in function 1c_ginfo.leth 3. Problem (CQ#7669) 4401: BACS LoopBack PHY diagnostic runs indefinitely when testing at 10Half Duplex. Cause: Reported Link Down to NDIS while running this test. Change: Keep Link Status Up while running this PHY LoopBack test. Impact: Resolve the problem of the LoopBack PHY diagnostic not finishing.
Version 3.58 (April 26, 2003) -------------Fixes: ========= 1. Problem (CQ#7095) 4401: Spurious connection drops when connected at 100Half with Dell 5224 Switch and DHCP mode. Cause: 4401 driver did PHY isolate prior to setting forced 100Half Duplex mode. Change: 4401 driver no longer doing PHY isolate prior to setting 100Half Duplex mode. Impact: Proper operation with Dell 5224 switch at 100Half and DHCP mode.
2. Problem (CQ#7606) Operating System crash while running BACS diagnostics and pinging out in Windows NT 4. Cause: 4401 driver did NdisMSendComplete for discarded and or modified packets during diagnostics. Change: 4401 driver updated to flush modified packets. Impact: No Operating System crash during BACS Diagnostics while pinging out.
Version 3.57 (April 24, 2003) -------------Fixes: ========= 1. Problem (CQ#7324) 4401 equipped systems had link issues with Dell 5224 Switch in DHCP mode at 100 Half Duplex. Cause: 4401 driver handling of 100 Half Duplex setting. Change: 4401 driver proper setting of 100 Half Duplex. Impact: Correct link issues with Dell 5224 Switch in DHCP mode at 100 Half Duplex. 4. Problem (CQ#7596) 4401 Not doing WOL from S5 Shutdown when 'wake up frame' is selected. Cause: Original design. Change: Modified 4401 driver to do WOL with Magic Packet when 'wake up frame' is selected for
Dell SubVendor programmed device ID. Impact:
4401 Dell SubVendor device will now do WOL from S5 Shutdown when magic packet is sent to it.
Version 3.56 (April 21, 2003) -------------Fixes: ========= 1. Problem (CQ#7537) 4401 equipped systems in Win98 cannot connect using only NetBeui protocol. Cause: 4401 driver initialization and first link indication Change: 4401 device reports Link down until finished initialization and negotiations. Impact: Correct problem of running only NetBeui protocol. 2. Problem (CQ#7451) 4401 equipped systems in Win2k switching from TCP/IP to Netbeui resulted in losing connection. Change: 4401 device reports Link down until finished initialization and negotiations. Impact: Correct problem of losing mapped drive when only Netbeui protocol is running. 3. Problem (CQ#7473) BACS 6.10 does not display Bus / Device Number correctly in WinNT 4.0 for 4401 device Cause: Driver was not setting this information. Change: 4401 driver was modified to get and set this information. Impact: Correct display of Bus / Device in BACS. 4. Problem (CQ#7596) 4401 Not doing WOL from S5 Shutdown Cause: Original Marketing Requirements for Change: Modified 4401 driver to do WOL with is selected. Impact: 4401 device will now do WOL from S5 sent to it.
when 'wake up frame' is selected. this product specified this. Magic Packet when 'wake up frame' Shutdown when magic packet is
---------------------------------------------------------------------------------------------------------------Version Release Date ======= ============ 3.55 03/25/03 driver
a. Corrected SQA Bug# 7327:
Wrong spelling for Broadcom name shown during
installation in Windows NT.
3.54
03/18/03
a. Corrected SQA Bug#7095: 4401: Intermittent connection down when connected at 100Half with Dell PowerConnect switch models 5224 and 5012.
3.53 Bar
03/18/03 a. Corrected SQA Bug#7229: upon Disabling/Enabling
BCM4401 Reported wrong line speed in the Task of device.
b. Corrected SQA Bug#4794: Broadcom Advanced Control Suite (BACS) NT 4 did not show Vital Sign information for 4401 adapters.
3.52
03/10/03
a. Corrected SQA Bug#6963: 4401 did not pad small packets with zeros. b. Corrected issue of Group Policy "Windows Startup Script" and "Logon Script" not being applied to 4401 equipped user station. c. Corrected SQA Bug#6095: 4401 BACS does not retain network speed setting after "Diagnostic Test". d. Corrected SQA Bug#7151: PHY Mode On/Off OID support for 4401 APIs. 3.51
12/17/02
a. Corrected SQA Bug#6424: running 4401 Diagnostics caused system lock up. 3.50
Shared Interrupt with Audio device and
12/04/02
a. Corrected SQA Bug#6236: 4401 Did Wake On LAN with Interesting Packet (ping) when OS check box "Allow this device" was not checked.
b. Corrected wrong LED operation after Wake On LAN from S3 Standby state on laptops using battery.
3.49
11/04/02
a. Corrected SQA Bug#5802: 4401 Win2K/XP speed change from 10Mb Half Duplex to 100Mb Half Duplex failed to work b. Corrected SQA Bug#5860: Asustek P4GE MotherBoard 3.48 test:
3.47
4401 WinME Shutdown - System Rebooted on
09/10/02 a. Corrected driver issue of not logging Link Speed during Windows XP WHQL WHQLCheckConfig
08/30/02
a. Corrected LED display initialization in driver after wake from Standby or Hibernate.
3.46
08/22/02 a. Submit 4401 NDIS Drivers to SQA for Microsoft WHQL HCT Testing.
3.45
08/19/02
a. Corrected Windows XP and Windows 2000 Link Indications after wake from Standby/Hibernate.
3.44
08/19/02
a. Corrected SQA logged bug#4512 No cable attached, 4401 shows a link in Windows at 10mb, after going into sleep mode and waking. b. Corrected SQA logged bug#4162 4401 Cable disconnect, put in Standby, connect cable, wake, connection to network lost. 3.43
08/06/02 a. Corrected SQA logged bug#4830 BACS reports wrong statistic counters for
4401.
b. Corrected SQA logged bug#4511 After running "Internal Memory" diag test in BACS,
the statitics displays wrong statistic counters. c. Corrected SQA logged bug#4799 4401 version 3 board locks up during hibernation at 100HD d. Corrected SQA logged bug#4987 4401 Received packet counter displays "0" and does not increment.
3.42
07/18/02
a. Corrected SQA logged bug#4814 NDIS5.1 driver v3.41 fails 2c_LoadUnload in XP32 Pro
3.41
07/18/02
a. Corrected SQA logged bug#4811: Win2k Infchecker test fails with 4401 Ndis5 driver v3.40 3.40
07/17/02 a. Added support for Broadcom 440x OEM device and subsystem IDs.
3.39
07/16/02
a. Changed Driver to correct reporting of CRC and CRC_Align errors with OID_GEN_RCV_CRC_ERROR and general RX errors with OID_GEN_RCV_ERROR.
3.38
07/11/02 a. Added Windows XP 32 and Windows NT 4 Driver support.
3.37
07/02/02
a. Resolved SQA Logged Bug#4652 Win2K WHQL Signability test reports error with 4401 Ndis5 driver.
3.36
06/17/02 a. Resolved SQA Logged Bug#4413 Netmon statistics support added. b. Resolved SQA Logged Bug#4303 802.3 and BACS statistics added.
c. Resolved SQA Logged Bug#4412 directed and broadcast packets statistics added.
d. Resolved SQA Logged Bug#4411 Frames RXed with alignment error statistics added. e. Resolved SQA Logged Bug#3881 System locks up with 4401 during NDIS Testing in Win2K. f. Resolved SQA Logged Bug#3910 System stop during Win2K Certification. g. Resolved SQA Logged Bug#4066 System hangs during Win2k certs with 4401.
3.35
06/06/02
a. Resolved SQA Logged Bug#4160 from Standby/Hibernate. b. Resolved SQA Logged Bug#4151 lost. c. Resolved SQA Logged Bug#4186 Windows at 10mb, after going into sleep d. Resolved SQA Logged Bug#4382 Netmon. e. Resolved SQA Logged Bug#4395 to come out of standby"
Mapped Drive not available after wake up Cable disconnect in sleep state/connection No cable attached, 4401 shows a link in mode CRC error count not supported using Power management option "Allow this device is grayed out when
Dell Magic Packet is set. 3.34
Driver.
05/30/02 a. Resolved SQA Logged Bug#4324 wrong version in BACS displayed for NDIS b. Updated WOL Advanced Options.
3.33
05/17/02
a. Resolved SQA Logged Bug#4154 WOL at S5 sleep state did not work on all ACPI compliant systems.
3.32
05/16/02
a. Set FlowControl Default Option to Enabled per Dell Software Requirements. b. Set Default WakeOnLan Advanced Option to "Wake Up Frame" for WHQL Certification. c. Corrected SQA Bug#4183 Win2K Certification test 1c_ginfo failure. 3.31
05/08/02 a.
Set WakeOnLan Default Option to Both (Magic Packet and Wake Pattern)
3.30 Suite.
05/08/02 a.
Resolved SQA Logged Bug#4077
b. Resolved SQA Logged Bug#4078 Control Suite. c. Resolved SQA Logged Bug#4053 packet enabled. 3.29
Driver Version Display in BACS Control Driver Statistics Display in BACS System Wake on Ping When only Magic
05/03/02 a.
3.27
Modified driver for performance and submit to Broadcom SQA.
04/30/02 a. b.
3.26
Corrected Windows System Shutdown issue noted as prior errata. Corrected Win2K WHQL Test 1c_ginfo.tst failures. 04/24/02
a. b. "Shutdown"
Added Flow Control advanced option. Corrected failing WHQL 2m_WOLPattern test. Errata 1: Some systems may experience power shutdown problems when requested from the Windows Start button. In this situation please press the Reset button of the
system first and then
3.25
press the system Power button.
04/22/02
a. Resolved warnings encountered during 1c_64BitOids Windows XP Certification Tests. b. Added Advanced Adapter Options Key for Wake On LAN choices. c. Added Dell/Broadcom DTWOL Magic Packet Wake On LAN support. Errata 1: Some systems may experience power shutdown problems when "Shutdown" requested from the Windows Start button. In this situation please press the Reset button of the system first and then press the system Power button. 3.24
04/12/02 a.
3.23
Updated driver settings for duplex performance. 04/11/02
a.
Submit to Broadcom SQA for XP and Win2K Certification.
3.22
04/03/02
a. Adapters.
Resolve Bug#3774
3.21
03/27/02
a. Resolve Bug#3525 disable/enable
3.20
Wrong Driver version in BACS for 4401 NIC
-
The NIC option 802.1P "Priority Handling" for WHQL HCT
test 2m_prior.
02/27/02 a.
3.19 testing;
-
Resolve Bug#3281
-
Control Suite Failure while testing MAC and PHY Loopback tests.
02/27/02 a.
Resolve Bug#3427
-
Signability test in Windows ME Certification
b.
Resolve Bug#3426
-
missing Catalog file entry added. Inchecker test in Windows 2000; BASEDRIVERFILEVERSION entry added.
-
Device name under Event Viewer corrected. Logging of Link Status and Speed for Windows XP
3.18
02/22/02 a. b.
Resolve Bug#3326 Resolve Bug#3336
and
Windows 2000 Pro and Server.
3.17
02/19/02 a.
3.16
Change Adapter name to "Broadcom 440X Fast Ethernet Controller" 02/19/02
a. b. c. 3.15
Resolve Bug#3291 Resolve Bug#3286 Resolve Bug#3282
-
Device Name to 4401 InfChecker issue with unreferenced name Forced and Auto Speed Setting Correction
02/14/02 a.
3.14
Change Advanced Options display text to match other Broadcom driver. 02/14/02
a.
Initial Release of 4401 Driver
Version 4.23 (September 26, 2003) -------------1. Problem (CQ#8525) 4401: OID_GEN_RCV_ERROR - remove fragmented packets Cause: Driver included Packet fragment count in RX Error count statistic OID_GEN_RCV_ERROR. Change: Driver changed to exclude Packet fragment count for RX Error statistic OID_GEN_RCV_ERROR. Impact: Correct CQ#8525 issue.
Version 4.22 (September 23, 2003) -------------1. Problem (CQ#8479) 4401-B0: HP INF file references to project names Cause: Driver installation inf file had project names. Change: Removed project names from driver installation inf Impact: Correct CQ#8479 issue.
file.
Version 4.21 (September 22, 2003) -------------1. Problem (CQ#8499) 4401: Rx Symbol Error when connected to Fujitsu LH 1108C HUB during file transfers resulting into low performance throughput. Cause:
The 4401 These RX ultimate This can
with Change: flagged
PHY hardware reports RX Symbol Errors due to collisions. Symbol Errors can be ignored because the CRC Check is the decision maker if a packet should be dropped or not. be considered a software workaround to remedy operations
particular HUBs that are not compliant to IEEE Specifications. A Registry key has been created for accepting packets that have been
by PHY hardware with RX Symbol Error condition. The default behavior is to implement this Software workaround. Impact: Correct CQ#8499 issue. 2. Problem (CQ#8502) 4401: Rx Symbol Error Accounting Cause: Due to CQ 8499 we had to modify driver error accounting. Change: Modified Driver to account for RX fragmented packets for RX total error statistics. Impact: Correct CQ#8502 issue.
Version 4.20 (September 19, 2003) -------------1. Problem (CQ#8392) 4401: PME Enable setting in conjunction with WOL Cause: Request to reduce power consumption during low power to zero amps. Change: Driver enables PowerManagementEnable (PME) when WOL is not "None" in the Advanced Properties of 4401; and Windows "Allow this device to Wake up..." is also set. Impact: Correct CQ#8392 issue.
Version 4.19 (September 18, 2003) -------------1. Problem (CQ#8482) 4401-B0: WinXP - 'Allow only management stations ...' doesn't stick when Advanced option was set to Magic Packet Cause: For 4401-B0 Driver was not reporting Magic Packet support during service of OID_PNP_CAPABILITIES. Change: Corrected Driver handling of OID_PNP_CAPABILITIES for B0 chip. Impact: Correct CQ#8482 issue.
Version 4.18 (September 18, 2003) -------------1. Problem (CQ#8472) 4401 B0 does not show 'Both' in Wakeup capabilities in Win 98/Me Cause: Driver installation inf file did not specify correct options for WOL for 4401 B0. Change: Corrected Driver installation inf file for proper 4401 B0 WOL support. Impact: Correct CQ#8472 issue. 2. Problem (CQ#8479) 4401-B0: HP INF file references to project names Cause: Driver installation inf file had project name. Change: Driver installation inf file project name was removed. Impact: Correct CQ#8479 issue. 3. Problem (CQ#8482) 4401-B0: WinXP - 'Allow only management stations ...' doesn't stick Cause: For 4401-B0 Driver was not reporting Magic Packet support during service of OID_PNP_CAPABILITIES. Change: Corrected Driver handling of OID_PNP_CAPABILITIES for B0 chip. Impact: Correct CQ#8482 issue.
Version 4.17 (September 15, 2003) -------------1. Problem (CQ#8392) 4401: PME Enable setting in conjunction with WOL Cause: Request to reduce power consumption during low power to zero amps. Change: Driver enables PowerManagementEnable (PME) when WOL is not "None" in the Advanced Properties of 4401; and Windows "Allow this device to Wake up..." is also set. Impact: Correct CQ#8392 issue.
Version 4.16 (September 15, 2003) -------------1. Problem (CQ#8463) 4401 B0 failed to wake up with MagicPacket when local administered address advanced option was set to a custom value.
Cause: WOL instead Change: use permanent Impact:
4401 Driver was always using permanent address to setup MagicPacket of the optional local administered address. 4401 Driver was modified to use local administered address if set; or address if local administered is not specified. Correct CQ#8463 issue.
Version 4.15 (September 10, 2003) -------------1. Problem 4401: Installation .inf file update to support OEM. Cause: New 4401 PCI Device Identification. Change: 4401 Driver installation .inf file was updated. Impact: None.
Version 4.14 (September 9, 2003) -------------1. Problem (CQ#8441) 4401: Failed WHQL HCT 11.2 ChkInf test procedure. Cause: 4401 Driver installation .inf file was missing a string definition for DriverOEMVersion Change: 4401 Driver installation .inf file was updated to have this string definition. Impact: Correct CQ#8441 issue.
Version 4.13 (September 3, 2003) -------------1. Problem (CQ#8325) 4401: Rpt2.0SI- Windows XP Event Viewer error: PSched: The netcard driver failed the query: OID_GEN_LINK_SPEED. This error occured when cable was disconnected. Cause: 4401 Driver was waiting seven seconds for Link up prior to handling of the above OID. Change: Modified 4401 Driver to wait maximum of 3.9 seconds and then complete the above OID when cable has been disconnected and link was not established. Impact: Correct CQ#8325 issue.
2. Problem (CQ#8358) 4401-B0, NDIS5.1 Intermittently Fails to Wake Up from The Standby Sleep State Cause: 4401 Driver setup for case of Both Magic Packet & WakeUp Frame WOL was not correct. Change: Corrected 4401 Driver setup for case of Both Magic Packet & WakeUp Frame WOL. Impact: Correct CQ#8358 issue. 3. Problem (CQ#8393) 4401 B0 halts NDIS tester during 2m_WOLMagicPacket script in Win2k WHQL Tests. Cause: 4401 Driver setup for case of Magic Packet WOL was not correct. Change: Corrected 4401 Driver setup for Magic Packet WOL. Impact: Correct CQ#8393 issue. 4. Problem (CQ#8412) 4401-B0 Drops Network Connection Once Awaken from Standby, via Magic Packet. Cause: 4401 Driver setup for case of Magic Packet WOL was not correct. Change: Corrected 4401 Driver setup for Magic Packet WOL. Impact: Correct CQ#8412 issue.
Version 4.12 (August 29, 2003) -------------1. Problem (CQ#8392) 4401: PME Enable setting in conjunction with WOL Cause: Request to reduce power consumption during low power to zero amps. Change: Driver would only enable PowerManagementEnable (PME) when WOL is not "None" in the Advanced Properties of 4401. Impact: Correct CQ#8392 issue. 2. Problem (CQ#8391) 4401 fails WHQL 2m_wolPattern test with Windows XP NDIS tester Cause: Driver setup of WOL Patterns when WOL Both option was selected. Change: Corrected Driver setup of WOL Patterns when WOL Both option is selected.
Impact: Correct CQ#8391 issue.
Version 4.11 (August 22, 2003) -------------1. Problem (CQ#8358) BCM4401-B0: Intermittently Fails to Wake Up from Standby/Hibernate/Shutdown. Cause: Incorrect driver setup of Magic Packet WOL operation for 4401 B0. Change: Corrected driver setup of 4401 B0 chip for Magic Packet WOL operation. Impact: Correct CQ#8358 for proper WakeOnLan operation of Magic Packets and Interesting Packets.
Version 4.10 (August 18, 2003) -------------1. Problem (CQ#8306) CQ#8306 4401: Locally administered MAC Network Address. Cause: Not implemented in prior 4401 Drivers. Change: Add Locally administered MAC Network Address to 4401 Driver. Impact: Correct CQ#8306 issue.
Version 4.00 (August 13, 2003) -------------Added support for 4401 B0 Hardware and increased driver version to 4.00
Version 3.64 (August 6, 2003) -------------Fixes: ========= 1. Problem (CQ#8224) CQ#8224 4401: function. Cause: 4401 Driver had power mode. Change: 4401 Driver was mode setup. Impact: Correct CQ#8224
Magic Packet wake-up with multicast packet did not not enabled Multicast during its process to go to low modified to enable Multicast as part of its low power issue.
2. Problem (CQ#8178) CQ#8178 4401:
CRC RX Error Statistics reported was not as expected. 4401: Private Statistics reported during OID: T3_OID_GET_STATISTICS_COUNTERS not
accumulative. Cause: resulting
statistics. Change: Impact:
4401 Driver reported sum of two CRC error counters with same value, in CRC count that was twice as actual errors. 4401 Driver during handling of OID: T3_OID_GET_STATISTICS_COUNTERS did not use the "accumulative" method of keeping and reporting of 4401 Driver was modified to gather and send the proper statistics. Correct CQ#8178 issue.
Version 3.63 (June 30, 2003) -------------Fixes: ========= 1. Problem (CQ#8101) CQ#8101 BCM4401-A1 NIC/LOM Intermittently fails to retain correct line speed when Advanced Option is set to 10Half Mbps; and running BACS Diagnostics. Cause: 4401 Driver did not reinitialize the PHY options after going in and out of Diagnostic mode; as a result of driver change for CQ#8027. Change: 4401 Driver was modified to reinitialize the PHY options when Diagnostic mode is done. Impact: Correct CQ#8101 issue.
Version 3.62 (June 24, 2003) -------------Fixes: ========= 1. Problem (CQ#8085) CQ#8085 4401: 802.1p Priority Tagging not as expected. Cause: 4401 always generated 802.1p Priority marked packets, when its Advanced Option was set to Enable 802.1p. Change: Modified driver to generate 802.1p Priority marked packets only when packet priority is non zero; per Windows XP Device Driver Kit documentation. Impact: Same 8021.p Priority Tagging as Broadcom 570x Adapters.
Version 3.61 (June 18, 2003) -------------Fixes: ========= 1. Problem (CQ#8027, CQ#7976, CQ#7806) CQ#8027 - 4401: WinXP - connectivity issue when changing speed/duplex with 802.1p option set and QoS Packet Sheduler enabled. CQ#7976 - 4401: Intermittently Loses Network Connection upon Change in Line Speed/Duplex CQ#7806 - 4401: IP address gets lost after changing from 10HDX->AUTO>100HDX Cause: 4401 Driver was taking longer than 3 seconds to respond to OID_GEN_MEDIA_CONNECT_STATUS; which caused Microsoft NDIS component "QoS Packet Scheduler" to disable IP address of 4401. Change: Modified driver to respond to OID_GEN_MEDIA_CONNECT_STATUS quicker, by increasing the frequency of Phy Link status check. Impact: Resolve connectivity issues CQ#8027, CQ#7976, CQ#7806 2. Problem (CQ#7842) 4401: Link activity reported by driver included Broadcast and Multicast Packets Cause: Original implementation. Change: Modify driver to report only Unicast Packets when polled for Link activity. Impact: None. 3. Problem (CQ#7788) 4401: The Power Management Tab for 4401 disappears intermittently Cause: Operating System Suspected. Change: Modified driver to wait 50 milliseconds before returning the result of PlugNPlay Power Management Query OIDs. Impact: None.
Version 3.60 (May 15, 2003) -------------Fixes: ========= 1. Problem (CQ#7796)
4401: BACS Diagnostics does not finish MAC- LoopBack test at 10 Half Duplex.
Cause:
Change:
Reported Link Down to NDIS while running this test. Keep Link Status Up while running this MAC LoopBack test.
Impact:
Resolve the problem of the MAC LoopBack diagnostic not finishing.
Version 3.59 (May 9, 2003) -------------Fixes: ========= 1. Problem (CQ#7699) 4401: Slow boot time when network cable unplugged Cause: 4401 Initial report for OID_GEN_MEDIA_CONNECT_STATUS was Link Up when Network Cable was disconnected. Part of Microsoft Workaround for Pushing Policy issue. Change: 4401 driver pends this request and determines link connection status first and then indicates results to caller of OID_GEN_MEDIA_CONNECT_STATUS. Impact: Improve boot time and resolve this issue. 2. Problem (CQ#7700) 4401: NDIS Tester 3.91 failure in function 1c_ginfo.leth Cause: 4401 Initial report for OID_GEN_MEDIA_CONNECT_STATUS was Link Up when Network Cable was disconnected. Part of Microsoft Workaround for Pushing Policy issue. Change: 4401 driver pends this request and determines link connection status first and then indicates results to caller of OID_GEN_MEDIA_CONNECT_STATUS. Impact: Resolve NDIS Tester 3.91 failure in function 1c_ginfo.leth 3. Problem (CQ#7669) 4401: BACS LoopBack PHY diagnostic runs indefinitely when testing at 10Half Duplex. Cause: Reported Link Down to NDIS while running this test. Change: Keep Link Status Up while running this PHY LoopBack test. Impact: Resolve the problem of the LoopBack PHY diagnostic not finishing.
Version 3.58 (April 26, 2003) -------------Fixes: ========= 1. Problem (CQ#7095) 4401: Spurious connection drops when connected at 100Half with Dell 5224 Switch and DHCP mode. Cause: 4401 driver did PHY isolate prior to setting forced 100Half Duplex mode. Change: 4401 driver no longer doing PHY isolate prior to setting 100Half Duplex mode. Impact: Proper operation with Dell 5224 switch at 100Half and DHCP mode.
2. Problem (CQ#7606) Operating System crash while running BACS diagnostics and pinging out in Windows NT 4. Cause: 4401 driver did NdisMSendComplete for discarded and or modified packets during diagnostics. Change: 4401 driver updated to flush modified packets. Impact: No Operating System crash during BACS Diagnostics while pinging out.
Version 3.57 (April 24, 2003) -------------Fixes: ========= 1. Problem (CQ#7324) 4401 equipped systems had link issues with Dell 5224 Switch in DHCP mode at 100 Half Duplex. Cause: 4401 driver handling of 100 Half Duplex setting. Change: 4401 driver proper setting of 100 Half Duplex. Impact: Correct link issues with Dell 5224 Switch in DHCP mode at 100 Half Duplex. 4. Problem (CQ#7596) 4401 Not doing WOL from S5 Shutdown when 'wake up frame' is selected. Cause: Original design. Change: Modified 4401 driver to do WOL with Magic Packet when 'wake up frame' is selected for
Dell SubVendor programmed device ID. Impact:
4401 Dell SubVendor device will now do WOL from S5 Shutdown when magic packet is sent to it.
Version 3.56 (April 21, 2003) -------------Fixes: ========= 1. Problem (CQ#7537) 4401 equipped systems in Win98 cannot connect using only NetBeui protocol. Cause: 4401 driver initialization and first link indication Change: 4401 device reports Link down until finished initialization and negotiations. Impact: Correct problem of running only NetBeui protocol. 2. Problem (CQ#7451) 4401 equipped systems in Win2k switching from TCP/IP to Netbeui resulted in losing connection. Change: 4401 device reports Link down until finished initialization and negotiations. Impact: Correct problem of losing mapped drive when only Netbeui protocol is running. 3. Problem (CQ#7473) BACS 6.10 does not display Bus / Device Number correctly in WinNT 4.0 for 4401 device Cause: Driver was not setting this information. Change: 4401 driver was modified to get and set this information. Impact: Correct display of Bus / Device in BACS. 4. Problem (CQ#7596) 4401 Not doing WOL from S5 Shutdown Cause: Original Marketing Requirements for Change: Modified 4401 driver to do WOL with is selected. Impact: 4401 device will now do WOL from S5 sent to it.
when 'wake up frame' is selected. this product specified this. Magic Packet when 'wake up frame' Shutdown when magic packet is
---------------------------------------------------------------------------------------------------------------Version Release Date ======= ============ 3.55 03/25/03 driver
a. Corrected SQA Bug# 7327:
Wrong spelling for Broadcom name shown during
installation in Windows NT.
3.54
03/18/03
a. Corrected SQA Bug#7095: 4401: Intermittent connection down when connected at 100Half with Dell PowerConnect switch models 5224 and 5012.
3.53 Bar
03/18/03 a. Corrected SQA Bug#7229: upon Disabling/Enabling
BCM4401 Reported wrong line speed in the Task of device.
b. Corrected SQA Bug#4794: Broadcom Advanced Control Suite (BACS) NT 4 did not show Vital Sign information for 4401 adapters.
3.52
03/10/03
a. Corrected SQA Bug#6963: 4401 did not pad small packets with zeros. b. Corrected issue of Group Policy "Windows Startup Script" and "Logon Script" not being applied to 4401 equipped user station. c. Corrected SQA Bug#6095: 4401 BACS does not retain network speed setting after "Diagnostic Test". d. Corrected SQA Bug#7151: PHY Mode On/Off OID support for 4401 APIs. 3.51
12/17/02
a. Corrected SQA Bug#6424: running 4401 Diagnostics caused system lock up. 3.50
Shared Interrupt with Audio device and
12/04/02
a. Corrected SQA Bug#6236: 4401 Did Wake On LAN with Interesting Packet (ping) when OS check box "Allow this device" was not checked.
b. Corrected wrong LED operation after Wake On LAN from S3 Standby state on laptops using battery.
3.49
11/04/02
a. Corrected SQA Bug#5802: 4401 Win2K/XP speed change from 10Mb Half Duplex to 100Mb Half Duplex failed to work b. Corrected SQA Bug#5860: Asustek P4GE MotherBoard 3.48 test:
3.47
4401 WinME Shutdown - System Rebooted on
09/10/02 a. Corrected driver issue of not logging Link Speed during Windows XP WHQL WHQLCheckConfig
08/30/02
a. Corrected LED display initialization in driver after wake from Standby or Hibernate.
3.46
08/22/02 a. Submit 4401 NDIS Drivers to SQA for Microsoft WHQL HCT Testing.
3.45
08/19/02
a. Corrected Windows XP and Windows 2000 Link Indications after wake from Standby/Hibernate.
3.44
08/19/02
a. Corrected SQA logged bug#4512 No cable attached, 4401 shows a link in Windows at 10mb, after going into sleep mode and waking. b. Corrected SQA logged bug#4162 4401 Cable disconnect, put in Standby, connect cable, wake, connection to network lost. 3.43
08/06/02 a. Corrected SQA logged bug#4830 BACS reports wrong statistic counters for
4401.
b. Corrected SQA logged bug#4511 After running "Internal Memory" diag test in BACS,
the statitics displays wrong statistic counters. c. Corrected SQA logged bug#4799 4401 version 3 board locks up during hibernation at 100HD d. Corrected SQA logged bug#4987 4401 Received packet counter displays "0" and does not increment.
3.42
07/18/02
a. Corrected SQA logged bug#4814 NDIS5.1 driver v3.41 fails 2c_LoadUnload in XP32 Pro
3.41
07/18/02
a. Corrected SQA logged bug#4811: Win2k Infchecker test fails with 4401 Ndis5 driver v3.40 3.40
07/17/02 a. Added support for Broadcom 440x OEM device and subsystem IDs.
3.39
07/16/02
a. Changed Driver to correct reporting of CRC and CRC_Align errors with OID_GEN_RCV_CRC_ERROR and general RX errors with OID_GEN_RCV_ERROR.
3.38
07/11/02 a. Added Windows XP 32 and Windows NT 4 Driver support.
3.37
07/02/02
a. Resolved SQA Logged Bug#4652 Win2K WHQL Signability test reports error with 4401 Ndis5 driver.
3.36
06/17/02 a. Resolved SQA Logged Bug#4413 Netmon statistics support added. b. Resolved SQA Logged Bug#4303 802.3 and BACS statistics added.
c. Resolved SQA Logged Bug#4412 directed and broadcast packets statistics added.
d. Resolved SQA Logged Bug#4411 Frames RXed with alignment error statistics added. e. Resolved SQA Logged Bug#3881 System locks up with 4401 during NDIS Testing in Win2K. f. Resolved SQA Logged Bug#3910 System stop during Win2K Certification. g. Resolved SQA Logged Bug#4066 System hangs during Win2k certs with 4401.
3.35
06/06/02
a. Resolved SQA Logged Bug#4160 from Standby/Hibernate. b. Resolved SQA Logged Bug#4151 lost. c. Resolved SQA Logged Bug#4186 Windows at 10mb, after going into sleep d. Resolved SQA Logged Bug#4382 Netmon. e. Resolved SQA Logged Bug#4395 to come out of standby"
Mapped Drive not available after wake up Cable disconnect in sleep state/connection No cable attached, 4401 shows a link in mode CRC error count not supported using Power management option "Allow this device is grayed out when
Dell Magic Packet is set. 3.34
Driver.
05/30/02 a. Resolved SQA Logged Bug#4324 wrong version in BACS displayed for NDIS b. Updated WOL Advanced Options.
3.33
05/17/02
a. Resolved SQA Logged Bug#4154 WOL at S5 sleep state did not work on all ACPI compliant systems.
3.32
05/16/02
a. Set FlowControl Default Option to Enabled per Dell Software Requirements. b. Set Default WakeOnLan Advanced Option to "Wake Up Frame" for WHQL Certification. c. Corrected SQA Bug#4183 Win2K Certification test 1c_ginfo failure. 3.31
05/08/02 a.
Set WakeOnLan Default Option to Both (Magic Packet and Wake Pattern)
3.30 Suite.
05/08/02 a.
Resolved SQA Logged Bug#4077
b. Resolved SQA Logged Bug#4078 Control Suite. c. Resolved SQA Logged Bug#4053 packet enabled. 3.29
Driver Version Display in BACS Control Driver Statistics Display in BACS System Wake on Ping When only Magic
05/03/02 a.
3.27
Modified driver for performance and submit to Broadcom SQA.
04/30/02 a. b.
3.26
Corrected Windows System Shutdown issue noted as prior errata. Corrected Win2K WHQL Test 1c_ginfo.tst failures. 04/24/02
a. b. "Shutdown"
Added Flow Control advanced option. Corrected failing WHQL 2m_WOLPattern test. Errata 1: Some systems may experience power shutdown problems when requested from the Windows Start button. In this situation please press the Reset button of the
system first and then
3.25
press the system Power button.
04/22/02
a. Resolved warnings encountered during 1c_64BitOids Windows XP Certification Tests. b. Added Advanced Adapter Options Key for Wake On LAN choices. c. Added Dell/Broadcom DTWOL Magic Packet Wake On LAN support. Errata 1: Some systems may experience power shutdown problems when "Shutdown" requested from the Windows Start button. In this situation please press the Reset button of the system first and then press the system Power button. 3.24
04/12/02 a.
3.23
Updated driver settings for duplex performance. 04/11/02
a.
Submit to Broadcom SQA for XP and Win2K Certification.
3.22
04/03/02
a. Adapters.
Resolve Bug#3774
3.21
03/27/02
a. Resolve Bug#3525 disable/enable
3.20
Wrong Driver version in BACS for 4401 NIC
-
The NIC option 802.1P "Priority Handling" for WHQL HCT
test 2m_prior.
02/27/02 a.
3.19 testing;
-
Resolve Bug#3281
-
Control Suite Failure while testing MAC and PHY Loopback tests.
02/27/02 a.
Resolve Bug#3427
-
Signability test in Windows ME Certification
b.
Resolve Bug#3426
-
missing Catalog file entry added. Inchecker test in Windows 2000; BASEDRIVERFILEVERSION entry added.
-
Device name under Event Viewer corrected. Logging of Link Status and Speed for Windows XP
3.18
02/22/02 a. b.
Resolve Bug#3326 Resolve Bug#3336
and
Windows 2000 Pro and Server.
3.17
02/19/02 a.
3.16
Change Adapter name to "Broadcom 440X Fast Ethernet Controller" 02/19/02
a. b. c. 3.15
Resolve Bug#3291 Resolve Bug#3286 Resolve Bug#3282
-
Device Name to 4401 InfChecker issue with unreferenced name Forced and Auto Speed Setting Correction
02/14/02 a.
3.14
Change Advanced Options display text to match other Broadcom driver. 02/14/02
a.
Initial Release of 4401 Driver
