Hardware
Diagnostics Checking
for Network Link and Activity
Checking
if Current Drivers are Loaded
Software
Problems and Solutions
 |
NOTE: For additional information, go to Broadcom Ethernet NIC Frequently Asked Questions at http://www.broadcom.com/drivers/faq_drivers.php. |
Loopback diagnostic tests are available for testing the adapter hardware. These tests provide access to the adapter internal/external diagnostics, where packet information is transmitted across the physical link (for instructions and information on running tests in an MS-DOS environment, see User Diagnostics; for Windows environments, see Diagnostics).
See Network Link and Activity Indication or Vital Sign to check the status of the network link and activity.
 |
WARNING: Before you open your computer case, review Safety Precautions. |
The following checklist provides recommended actions to take if you experience problems with your adapter.
Click the Vital Sign tab in Broadcom Advanced Control Suite 2 to see if the adapter driver is loaded. If the Driver Status line shows that the driver is loaded, compare the Driver Version and Driver Date information with the latest driver version and date information provided on the Broadcom website at http://www.broadcom.com/drivers/downloaddrivers.php.
To verify that the driver is loaded properly, type
LOAD B57.LAN FRAME_ETHERNET_II NAME=B57_1_EII
This command automatically verifies if the link is active. If the link is active, the command returns Link is up.
From the command line, type config then press ENTER. The following status information is displayed:
Broadcom NetXtreme Gigabit Ethernet Adapter
Version:
Hardware Setting:
Node Address:
Frame Type:
Board Name:
LAN Protocol: ARP (see note)
LAN Protocol: IP Addr: (see note)
|
NOTE: The LAN protocol status is displayed after an IP address is assigned to the adapter. |
To verify that the bcm5700.o driver is loaded properly, run:
lsmod
If the driver is loaded, a line similar to the one below is displayed, where
size
| Module |
Size |
Used by |
|---|---|---|
| BCM5700 |
size |
n |
In Windows environments, a cable test is run in Broadcom Advanced Control Suite 2. Go to Cable Analysis for information about running a cable length test.
|
NOTES:
|
Use the ping command to determine if the network connection is working.
|
NOTE: Network connectivity can also be tested using the Network Test feature in Broadcom Advanced Control Suite 2. |
The ping statistics that are displayed indicate whether the network connection is working or not.
Ping an IP host on the network to verify connection has been established:
From the command line, type ping IP address, and then press ENTER.
The ping statistics that are displayed indicate whether the network connection is working or not.
To verify that the Ethernet interface is up and running, run ifconfig to check the status of the Ethernet interface. It is possible to use netstat -i to check the statistics on the Ethernet interface. Go to Linux Driver Software for information on ifconfig and netstat.
Ping an IP host on the network to verify connection has been established:
From the command line, type ping IP address, and then press ENTER.
The ping statistics that are displayed indicate whether the network connection is working or not.
Problem: Microsoft Remote Installation Service (RIS) installation fails to load the Broadcom network adapter driver for both Windows 2000 and Windows XP.
Solution: Follow the procedure described below, which is based on the Microsoft Knowledge Base Article, "How to Add Third-Party OEM Network Adapters to RIS Installations" (Article 246184 applies to Windows 2000, and Article 315279 applies to Windows XP).
[Broadcom]
%OEM1_DEV5% = OEM1_DEV5.Inst, PCI\VEN_14e4&DEV_165D&SUBSYS_865d1028
.
.
%BCM5750B0F% = BCM5750B0MF.Inst, PCI\VEN_14e4&DEV_167E&SUBSYS_057D1014&REV_10
| Original | Revised |
|---|---|
[Manufacturer] |
[Manufacturer] |
[Unattended]
OemPreinstall = yes
OemPnpDriversPath = \Drivers\NIC (append if necessary)
A sample RIS answer file is shown below for a fully-unattended install that is consistent with the instructions provided above.
Filename - ristndrd.sif
-----------------------------------------------
[data]
floppyless = "1"
msdosinitiated = "1"
OriSrc = "\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"
OriTyp = "4"
LocalSourceOnCD = 1
UnattendedInstall=Yes
[SetupData]
OsLoadOptions = "/noguiboot /fastdetect"
SetupSourceDevice = "\Device\LanmanRedirector\%SERVERNAME%\RemInst\%INSTALLPATH%"
[Unattended]
OemPreinstall = Yes
OemPnPDriversPath=\Driver\Video;\Driver\Audio;\Driver\Nic
FileSystem = LeaveAlone
ExtendOEMPartition = 0
TargetPath = \WINDOWS
OemSkipEula = yes
InstallFilesPath = "\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"
LegacyNIC = 0
UnattendMode=FullUnattended
[UserData]
FullName = "%USERFIRSTNAME% %USERLASTNAME%"
OrgName = "%ORGNAME%"
ComputerName = %MACHINENAME%
ProductID=
[GuiUnattended]
OemSkipWelcome = 1
OemSkipRegional = 1
TimeZone = %TIMEZONE%
AdminPassword="*"
[Display]
BitsPerPel = 16
XResolution = 800
YResolution = 600
VRefresh = 60
[Networking]
[NetServices]
MS_Server=params.MS_PSched
[Identification]
JoinDomain = %MACHINEDOMAIN%
DoOldStyleDomainJoin = Yes
[RemoteInstall]
Repartition = Yes
UseWholeDisk = Yes
[OSChooser]
Description ="Microsoft Windows XP Professional"
Help ="Automatically installs Windows Professional without prompting the
user for input."
LaunchFile = "%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com"
ImageType =Flat
Version="5.1"
Problem: I want to be sure that my Broadcom NetXtreme 57XX network adapter works properly if I use the System Preparation utility (Sysprep.exe) to install an existing configuration on my computer.
Solution: On the Sysprep.inf file, modify the [Unattend] header as shown below:
[Unattend]
OemPnPDriversPath=Drivers\Net
The driver files for the Broadcom NetXtreme 57XX adapter must reside in this folder, which is located on the system drive (where the operating system resides). If other drivers are to be loaded, then Drivers\Net can be appended to the paths listed and separated by a semicolon:
Example
OemPnpDriversPath=Drivers\Video;Drivers\Net
For Windows XP, the driver files to be included are B57win32.inf, B57win32.cat, and B57xp32.sys.
For Windows 2000, the driver files to be included are B57win32.inf, B57win32.cat, and B57w2k.sys.
The Sysprep utility must run with the –pnp switch, which enables the system to rescan for new devices that can be added during the mini-setup.
A Sample Sysprep.inf file for Windows XP is shown below.
------------------------------------------------------------------------
;SetupMgrTag
[Unattended]
OemSkipEula=Yes
OemPreinstall=Yes
TargetPath=\Windows
UnattendedInstall=Yes
OemPnpDriversPath=Drivers\Net
[GuiUnattended]
AdminPassword="password"
EncryptedAdminPassword=NO
AutoLogon=Yes
AutoLogonCount=99
OEMSkipRegional=1
OEMDuplicatorstring="XP System"
TimeZone=4
OemSkipWelcome=1
[UserData]
FullName="User"
OrgName="Organization"
ComputerName=*
[SetupMgr]
DistFolder=C:\sysprep\i386
DistShare=whistlerdist
[Identification]
JoinDomain=workgroup
[Networking]
InstallDefaultComponents=Yes
---------------------------------------------------
Problem: Unable to obtain network settings through DHCP using PXE.
Solution: For proper operation make sure that the Spanning Tree Protocol (STP) is disabled or that portfast mode (for Cisco) is enabled on the port to which the PXE client is connected. For instance, set spantree portfast 4/12 enable.