===========
R E A D M E
===========
Broadcom Ethernet Controller WMI provider for Windows
Copyright (c) 2009 Broadcom Corporation
All rights reserved.
Table of Contents
-----------------
1. Overview
2. Limitation
3. Files
4. Dependency
5. Known Limitations
6. Troubleshooting
1. Overview
-----------
Broadcom ethernet controller WMI provider for Windows is deisgned
to provide information and basic diagnostics functions for Broadcom
made ethernet controllers.
Implementation of the provider uses BMAPI to collect information and
perform actual diagnostics functions for network controllers.
2. Limitation
-------------
The provider supports i386 architecture based CPU. The following is
the list of supported OS:
Windows 2000 Server/Workstation GA-SP4
Windows 2003 GA-SP1 (32 bit and 64 bit)
Windows 2003 R2 (32 bit and 64 bit)
Windows XP GA-SP2 (32 bit and 64 bit)
Windows Vista (32 bit and 64 bit)
Please also refer to 'Dependency' section for more information.
3. Files
--------
bmapi.dll BMAPI share library
BrcmUtils.dll BRCM_CIM provider library
BmapiObjServices.dll BRCM_CIM provider library
BnxWmiProvider.dll BRCM_CIM provider library
BnxAdapter.mof MOF file
BnxCDM.mof MOF file
BnxWmiProvier.mof MOF file
BnxWmiProvierW2K.mof MOF file
CIM_Core.mof MOF file
CIM_Device.mof MOF file
CIM_Interop.mof MOF file
CIM_Network.mof MOF file
CIM_Physical.mof MOF file
CIM_System.mof MOF file
CIM_System_Device.mof MOF file
readme.txt this file
release.txt release information
4. Dependency
------------------
a. Broadcom network adapters running the following driver versions:
For 4401 devices: driver version 3.46.
For NetXtreme devices: NDIS driver version >= 6.34.
For NetXtremeII devices: VBD driver version >= 2.5.2.
Please refer to README.TXT of the target driver for installation
instruction.
b. BMAPI
bmapi version >= 7.16.0.
c. CIM Studio
This provider package is tested with CIM Studio.
5. Software Update Profile
---------------------------
For Software Update Profile, CIM_SoftwareInstallationService.InstallFromURI()
method is implemented to support firmware upgrade. This function takes the
following parameters:
1. URI - the USRI corresponding to the new firmware image to be used.
2. Target - reference to the CIM_SoftwareIdentity corresponding to the
device and firmware to be upgraded.
3. InstallOptions - supports options "defer reset" (2), "force" (3),
"update" (5), "reboot" (7) and Broadcom specific
values 32768 and 32769.
4. InstallOptionsValues - if Broadcom specific values 32768 or 32769 are used in
InstallOptions array, there should be an entry in
InstallOptionValues array with the same index of the Broadcom
specific value in the InstallOptions array.
e.g. if the 2nd entry of InstallOptions contains 32768, then
the 2nd entry of InstallOptionsValue should contain an option
string accordingly.
"-p" to upgrade iSCSI configuration program along with iSCSI
firmware.
For iscsi firmware upgrade, the following 2 entries in InstallOptions/InstallOptionsValues
are supported:
InstallOptions InstallOptionsValues Required Purpose
-----------------------------------------------------------------------------------------------
1. 32768 "-p" No upgrade iscsi config program
along with iscsi firmware
2. 32769 "ipv4", "ipv6", or "ipv4n6" Yes specify the iscsi configuration
for the upgrade
If option 32769 and the corresponding value is not specified when upgrading iscsi firmware,
InstallFromURI() method will return error.
6. Known Limitations
----------------------
No known limitation.
7. Troubleshooting
-------------------
Problem: Cannot enumerate any BRCM classes
Possible cause: Provider software is not installed properly.
Solution: Reinstall provider software and make sure the BnxWmiProvider,
BmapiObjServices, and BrcmUtil libraries are in the library
search path.
Possible cause: Bmapi library is not in the library search path, or the wrong
version of Bmapi library is installed.
Solution: Make sure a supported version of Bmapi library is in the library
search path. Refer to Dependency section for supported versions
of Bmapi.
Problem: No Broadcom devices are enumerated.
Possible cause: Device driver of supported version is not installed or not loaded.
Solution: Make sure the device driver is installed and loaded properly.
Ethtool should be able to enumerate the device if driver is installed.
Refer to Dependency section for supported versions of device drivers.
Problem: Only loopback tests fail while other tests pass.
Possible cause: Fad.sys and fadxp32.sys are required for MAC and physical loopback
tests. These files are required to be in the search path.
Solution: Make sure these 2 files provided in the installation are in the
search path.
Problem: RunDiagnostic failed
Possible cause: Ran out of disk/memory space.
Solution: Free up disk/memory space and try again.
Possible cause: No admin privileges to run the tests.
Solution: Login as administrator and try again.
Possible cause: Device is already in diagnostic state.
Solution: Wait until the current diagnostic to finish and try again.
If the problem can't be solved by any of the above, and it is persistent,
try using a different version of driver or software and repeat the test to
rule out the possibility of faulty software.
If the problem still persists, contact support personnel and ask for support.
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.