============================
R E L E A S E N O T E S
============================
Broadcom NetXtreme Ethernet Driver
for
DOS/OS2 NDIS2
Copyright (c) 2002-2004 Broadcom Corporation
All rights reserved.
Revision History
================
version 7.11 January 9, 2004
------------------------------
1. Problem:
Driver will not load when PXE is enabled.
Cause:
Driver uses of register during initialization to determine if the
NIC is in used by another instance of the driver was contaminated
when PXE is loaded.
Change:
Driver uses other register that is not conflict with PXE.
Impact:
None.
Enhancement:
=============
1. Request:
Provide work-around in the driver for version of TCPIP stack that
does not recognize the 1's compliment checksum.
Change:
Modify only valid received TCPIP frame's checksum. Add keyword
FixCheckSumOff to turn off this work-around.
Impact:
None.
version 7.10 December 18, 2003
------------------------------
1. Problem:
CQ #9018: OS2 client - Cannot connect to server when LAA (Locally
Administered Address) is used.
Cause:
Type casting was set incorrectly when written to the MAC address
registers in the Set Station function.
Change:
Set type casting correctly when write to the MAC address registers
in the Set Station function.
Impact:
None.
2. Problem:
CQ #9015: NDIS2 DOS takes anywhere between 2-8 minutes to establish
link with 3Com Superstack 3 Switch (Model #3C16468).
Cause:
Driver unnecessarily reset the PHY when performing cable auto
sensing to load upon in case of use in multiple NICs system. This
causes the auto negotiation to continue after the Driver is armed
then the PHY Link Change Interrupt services this incomplete auto
negotiation and mistaken for the link lost then reset the PHY when
the link is recovered resulting the lengthy link fluctuation on some
switch.
Change:
Driver will not perform PHY reset when sensing for cable and in the
PHY Link Change Interrupt logic to include condition when auto
negotiation is completed.
Impact:
Driver will initialize faster when use in multiple NICs system.
Enhancement:
=============
1. Request:
Banner change to include NC10xx.
Change:
Sign on banner.
Impact:
None.
version 7.09 October 27, 2003
----------------------------
1. Problem:
CQ #8743: NDIS2 DOS failed to start the download image process
when using Ghost v7.5 to download image via multicast. The
Protocol in use was Symantec's MAC/DIS to Packet Driver Converter
over TCP/IP.
Cause:
Driver filtered 48-bit on the Multicast address set by the Ghost
server while it expects communication on 23-bit filtering of the
set Multicast address.
Change:
Driver filtered 23-bit of the set Multicast address.
Impact:
None.
version 7.08 October 23, 2003
----------------------------
1. Problem:
CQ #8663: NDIS2 DOS causes Ghost v7.5 to freeze when uploading
image via multicast. The Protocol in use was Symantec's MAC/DIS
to Packet Driver Converter over TCP/IP.
Cause:
Driver miss-used Transmission Confirm Counter when deferring
the Protocol's request to transmit while in Receive Look Ahead
up call and caused the system to hang when the extra Transmit
Confirm was made.
Change:
Driver responses with "REQUEST_QUEUED" on all Transmit Requests
from the Protocol and call Transmit Confirm if required at
Transmit Complete Interrupt.
Impact:
None.
2. Problem:
None.
Change:
PCI configuration data register (0xCFC) does NOT needed to be
preserve in Driver's PCI configuration Read and Write
subroutines. Removed the preserve of PCI configuration data
register (0xCFC) that was put in v7.05.
Impact:
This would remove unnecessary I/O cycles every time the driver
accesses the PCI configuration area.
version 7.07 October 16, 2003
----------------------------
1. Problem:
CQ #8631: When attempting to force the 100/Full or Half
with LineSpeed forced in protocol.ini while the switch is
set to AutoNeg. The driver's signon message indicates
"forced", but the switch reports 100 Full when it should
reports 100 Half.
Cause:
Driver configured the NIC properly but on some switch;
it's required a "line drop" to update the duplex status.
Change:
Driver toggled the SuperIsolate bit to simulate a
"line drop" that allows the far-end to adjust to the forced
speed and duplex.
Impact:
None.
version 7.06 October 13, 2003
----------------------------
Enhancements:
=============
1. Request:
Added new device ID and displays banner properly.
Change:
Added new device ID and displays banner properly.
Impact:
None.
Version 7.05 October 03, 2003
----------------------------
Fixes:
========
1. Problem:
CQ #8528: Linespeed "Undeterminable" is displayed when driver
loads using 5705F connected to 1G Switch.
Cause:
Driver was not configure properly for 5705F.
Change:
Driver initializes correctly for 5705F.
Impact:
none.
2. Problem:
PCI configuration data register (0xCFC) was not preserve in Driver's
PCI configuration Read and Write subroutines.
Change:
Driver preserves PCI configuration data register (0xCFC) also.
Impact:
none.
version 7.04 September 23, 2003
----------------------------
Enhancements:
=============
1. Request:
Add support for 5705F and displays banner properly.
Change:
Add support for 5705F and displays banner properly.
Impact:
None.
Fixes:
========
1. Problem:
CQ #8424: 5704s will not pass traffic when "FullSize"
parameter is used.
Cause:
When "FullSize" keyword is used, the driver will not be
download its own firmware. So it is NOT needed to command
the firmware to use AUTONEG or 1000Mbps FULL for fiber NIC.
Change:
When "FullSize" keyword is used Driver is NOT to command the
firmware.
Impact:
Fiber NIC.
Version 7.03 September 03, 2003
----------------------------
Fixes:
========
1. Problem:
CQ #8407: NDIS2 OS2 - Connection is lost under heavy
IP/NetBEUI stress.
Cause:
Driver's Middle Module had some debug codes to verify its
configuration space access sequence got corrupted. These codes
added overhead to its normal timing and this additional time
caused NetBEUI to terminate its communication to the driver
while the driver is under enormous stress.
Change:
Remove the debug codes.
Impact:
None.
Version 7.02 August 29, 2003
----------------------------
Fixes:
========
1. Problem:
CQ #8402: NDIS2 DOS/OS2 - Cannot pass traffic on fiber NIC.
Cause:
Driver's Lower Module required to instruct firmware (v1.14.0)
to use AUTONEG or 1000Mbps FULL for fiber NIC.
Change:
Driver's Lower Module commands the firmware to use AUTONEG or
1000Mbps FULL for fiber NIC.
Impact:
Fiber NIC.
Version 7.01 August 29, 2003
----------------------------
Fixes:
========
1. Problem:
Driver uses zero MAC address on 5700 & 5701-based NIC/LOM
when reads it from Serial EEPROM.
Cause:
Serial EEPROM routine has a bug, which causes MAC address in
the serial EEPROM cannot be read correctly.
Change:
Fixed serial EEPROM driver so that MAC address can be read
correctly.
Impact:
None.
Notes:
========
1. This is a "theoretical problem" only.
Version 7.00 August 27, 2003
-------------------------
Fixes:
========
1. Problem:
CQ #8360: Driver will load on the first copper port that is
detected with a link. This feature does not work on fiber
NIC.
Cause:
This feature is not implement for fiber NIC.
Change:
Enable this feature for fiber NIC.
Impact:
none.
Enhancements:
=============
1. Request:
Improve bit error performance of 5703AX and 5704AX when used
with long cable lengths.
Change:
Program the phy's ADC and Gamma registers to more optimum
settings.
Impact:
None.
2. Request:
Improve Serdes drive levels on 5704s.
Change:
Programed the serdes config registers so that SerDes' drive
transmission level is 1.2V. This modification was made in the
driver download firmware v1.14.0.
Impact:
None.
Notes:
========
1. Firmware v1.14.0 is used in place of v1.9.0 was used since DOS ODI v6.07.
2. No release for v6.47-v6.99. Adjust version number for Software Rel 6.8.
Version 6.47 Aug 07, 2003
----------------------------
****************************
Enhancements:
=============
1. Request:
Enable hardware fixes in 5704_Bx parts for known 5704 Ax errata.
Change:
Added code to driver init routines to enable hardware fixes in
5704 B0 silicon. See 5704 errata for more details info about
the changes/fixes in B0 silicon.
Impact:
None.
Fixes:
========
1. Problem:
CQ #8240: NDIS2 DOS driver causes divide over flow if IRQ is
disabled in BIOS.
Cause:
Driver still loads when BIOS provided with an invalid IRQ.
Change:
Driver only loads when BIOS provided with IRQ value between
2 and 15.
Impact:
none.
2. Problem:
CQ #8205: NDIS2 OS2 driver causes system to idle approximately
1 minute after NDIS2 OS2 driver banner shows when binding
with IBM IEEE 802.2 protocol.
Cause:
IBM IEEE 802.2 protocol calls ResetMAC function after driver is
already initialized the NIC. The driver does not support this
request but returns SUCCESS.
Change:
Driver returns NOT_SUPPORTED when ResetMAC is called.
Impact:
none.
3. Problem:
CQ #8265: When OS2 is boot up from floppy, NDIS2 OS2 driver
causes the system to trap when it is connected to CISCO Catalyst
3550 switch.
Cause:
CISCO switch transmits Multicast discovery protocol packets
while the Protocol and the Driver are binding.
Change:
Driver set Multicast filtering after the binding process.
Impact:
none.
4. Problem:
NDIS2 driver uses same MAC address for both ports on 5704 NIC
when reads it from NVRAM.
Cause:
Driver uses the same offset for both ports.
Change:
Driver uses correct offset for the second port.
Impact:
none.
Version 6.46 June 25, 2003
----------------------------
Fixes:
========
1. Problem:
(CQ #8086) NDIS2 DOS intermittent failed on RPL test when
using 5702 NIC. This problem traced back to v6.40 and
v5.00-v5.22. However, V5.23-v6.30 had no problem.
Cause:
The current Download Firmware (v1.9.0) combines with Tag
Status method of handling interrupt causes the RPL Protocol
waits for a response for a packet that was transmitted while
processing the receiving packet in ReceiveLookahead.
Change:
Driver queue all transmission requests during up-call to
ReceiveLookahead and returns REQUEST_QUEUED.
Impact:
Protocol that chooses to transmit while processing a
receiving packet in ReceiveLookahead such as Netbeui and RPL.
Enhancements:
=============
1. Change:
Added NoTagStatus Keyword in the PROTOCOL.INI to set Driver NOT
to utilize the default method Tag Status of handling interrupts
for none 5700 NIC.
Impact:
Helps stabilize on certain platforms when using with protocol
such as Netbeui and RPL.
Version 6.45 June 23, 2003
----------------------------
Fixes:
========
1. Problem:
(CQ #7988) OS2 APING stress test, the APPC conversation
failed. There were two issues in this problem.
Cause 1:
Index BX register was changed while Driver copying transmit
data fragments when Protocol delivered a Physical addressed
data fragment pointer.
Change 1:
Driver disables interrupts and preserves the BX register
before makes the call to OS2 Device Helpers to map the
Physical addressed data fragment pointer to a Selector.
Impact 1:
Driver's transmission logic for OS2 only.
Cause 2:
Driver miss-handled OUT_OF_RESOURCE that was returned from
the Protocol after the ReceiveLookahead call.
Change 2:
Driver will not turns Indication Off as before but simply
continue and makes no effort to re-deliver the packet.
Impact 2:
Driver's receive logic.
2. Problem:
OS2 system crashed when using IBM TCP/IP ping a large
packet size (14500 bytes).
Cause:
Protocol delivered zero byte count in the data fragment.
Driver does not copy zero byte count data fragment but
uses the number of data fragment supplies by the Protocol.
Change:
Driver calculates the number of data fragment copied
instead of use the number delivered from the Protocol.
Impact:
Driver's transmission logic.
Version 6.44 May 21, 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:
(CQ #7843) 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.43 May 11, 2003
----------------------------
Fixes:
========
1. Problem:
(CQ #7677) OS2 system crashes when uses 5700 Ax and Bx
or FullSize mode.
Cause:
Driver provided incorrect Global Descriptor Table to OS2
when called to map to its Physical area.
Change:
Driver obtains correct Global Descriptor Table to OS2
when called to map to its Physical area during
initialization.
Impact:
5700 Ax & Bx or runs in FullSize Mode in OS2.
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.
6. Problem:
OS2 system hangs when NIC is sharing interrupts. This was
introduced since v5.29.
Cause:
Driver does EOI on other interrupt.
Change:
Driver does EOI on its own interrupt only.
Impact:
OS2 driver only.
Version 6.42 April 29, 2003
----------------------------
Fixes:
========
1. Problem:
The PHY lockup problem described in v6.35 Fix #1 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:
(CQ #7658) (CQ #7660) OS2 system crashes when uses 5703,
5703S and OS2 system cannot pass traffic with 5704, 5704S.
Cause:
Download Firmware's length was not set correct for OS2.
Change:
Set the Download Firmware's length accordingly.
Impact:
5703, 5703S, 5704 and 5704S.
3. Problem:
(CQ #7642) 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.
4. Problem:
(CQ #7648) 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.41 April 25, 2003
----------------------------
Fixes:
========
1. 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.40 with the 5704 PHY lock up work-around
and zero MAC address fixes in v6.35.
2. The Lower Module is ported from PXE v6.2.4.
Version 6.35 April 18, 2003
----------------------------
Fixes:
========
1. Problem:
In some extremely rare situations, 5704/CIOBE copper NICs may not link up
after a PHY reset.
Cause:
On some 5704/CIOBE PHY cores, there is a small probability of lock up after
a PHY reset.
Change:
Added 5704/CIOB-E copper support.
Added code to detect PHY lock up after a PHY reset and reset again if lock
up is detected.
Impact:
5704/CIOB-E copper.
Notes:
========
1. The code base for this version is from v6.34.
Version 6.34 April 18, 2003
----------------------------
Fixes:
========
1. Problem:
In some extremely rare situations, 5704/CIOBE copper NICs may not link up
after a PHY reset.
Cause:
On some 5704/CIOBE PHY cores, there is a small probability of lock up after
a PHY reset.
Change:
Removed 5704/CIOB-E copper support.
Impact:
5704/CIOB-E copper.
2. Problem:
Driver Intermittently using a MAC address of all zeros.
Cause:
In some rare timing related situations, the Firmware is behind in providing
the MAC address for the Driver at the MAC Control Registers.
Change:
Driver will get the MAC address from NVRAM when the MAC address read from the
MAC Control Registers is all zeros.
Impact:
Code size increased by 944 bytes.
Notes:
========
1. The code base for this version is from v6.33.
03/20/03 - v6.40-
Added 5788, 5704 Fiber & 5700 supports.
Support 5700 AX & BX using full size mode (48KB more-total 83KB).
Added keyword FullSize.
Added feature to detect and load on device that have cable first.
No release for v6.34-v6.39
03/05/03 - v6.33-
Removed 5700 support.
02/20/03 - v6.32-
Fixed intermittent error in EMM386 introduced since v5.25.
Fixed problem of identify the second 5704 on the same system.
Fixed loss connection during file copy with 5700 in 10MB.
Removed 5704 fiber support.
02/15/03 - v6.31-
Fixed problem with forced LineSpeed and Duplex of new PXE's LM.
02/12/03 - v6.30-
Updated with PXE's LM v6.0.3 and have following fixes:
1) Fix bug in Transmit routine that did not preserve EAX register causing
intermittent problems when running with DOS-Extender Applications.
2) Fix passing traffic problem with 5700 B0&B2.
3) Fix "security flaw" in packet padding.
4) Make some "branding" changes.
5) Add recognition of new Device IDs for 5705/5901 A2/A3.
6) Merged source code with DOS and OS2.
02/05/03 - v6.29-
Enabled 5704.
No release for v5.29-v6.18.
01/28/03 - v5.28-
Added key word NodeAddress in Protocol.ini.
Resolved duplicate name if driver loaded more than once to support multiple
adapters.
01/23/03 - v5.27-
Add Set Station Address function.
Support multiple adapters by recognize the previously loaded driver(s).
No DOS release.
01/20/03 - v5.26-
Fix a Tx/Rx HW race condition where only Tx was reported with forcing
Status Block to update periodically (every 55ms).
No OS2 release.
01/17/03 - v5.25-
EOI before handle own interrupt.
Correction releasing transmission resources logic.
Fix a Tx/Rx HW race condition where only Tx was reported.
No OS2 release.
01/02/03 - v5.24-
Remove 5704, added Fast Ethernet Banner, and enable ClockRun support
for 5705.
No OS2 release.
12/13/02 - v5.23-
Updated with PXE's LM v3.1.25 and have following fixes:
1) Firmware handles links negotiation for fiber.
2) Fix bug in ISR that will cause system to lockup when other device
shared ISR don't have share-interrupt signature. This bug was
introduced since v5.00.
3) Speed correction for 5705FE.
4) Add recognitions for 5702/3 A3 and 5782.
12/04/02 - v5.22-
Back off Tagged Status. It causes intermittent problem when running
with Netbeui.
11/25/02 - v5.21-
Fix problem with Network disconnection.
Used Tagged Status.
10/25/02 - v5.20-
Updated with PXE's LM v3.1.18.
Back off EOI before handle own interrupt.
Fix performance issue.
Fixed problem with forced LineSpeed and Duplex.
Fixed problem with EMM386 for 5705.
Fixed problem with system appeared to hang when cable was removed.
No release for v5.01-v5.19.
10/09/02 - v5.00 - OS2 only
Fixed problem with system appeared to hang when cable was removed.
09/24/02 - v5.00- DOS only
Fixed problem with ASF enabled.
Updated with PXE's LM v3.1.14.
Fixed problem with RIS Client Installation.
EOI before handle own interrupt.
Added 5704 Fiber support.
08/13/02 - v3.07-
Added 5705 & 5901 support.
Used PXE v3.1.5 's LM.
08/13/02 - v3.06-
Removed Alpha Driver Label.
08/01/02 - v3.06- Alpha Driver
Fixed problem with EMM386.
07/24/02 - v3.05- Alpha Driver
Used PXE's LM.
07/23/02 - v3.04- Alpha Driver
Clean out NIC's Status Block during initialization to prevent spur-interrupt after
initialization.
07/17/02 - v3.04- Alpha Driver
Slim down Host memory used by adpater (dropped 48K memory foot print).
Hanle Transmit Segment equal to 0 for OS2 Granite trap.
06/19/02 - v3.03-
Fixed problem with the RPL boot up, the driver hangs while downloading file image.
The Boot Block Configuration file *.cnf MUST specify in the DRV Type's second field
the additional memory (53KB-60KB) used by the driver as follows:
DRV BBLOCK\NDIS\B57.DOS ~ 53 ~
Block re-entrance during Interrupt handler loop in OS2 driver.
05/23/02 - v3.02-
Fixed a low performance problem with BCM5701 Serdes LOMs with Copper Trace
media. As in the PXE v2.1.2.
05/17/02 - v3.01-
Port number correction.
05/15/02 - v3.00-
Added support for 5704.
07/12/02 - v1.12-
Fixed problem with the RPL boot up, the driver hangs while downloading file image.
The Boot Block Configuration file *.cnf MUST specify in the DRV Type's second field
the additional memory (53KB-60KB) used by the driver as follows:
DRV BBLOCK\NDIS\B57.DOS ~ 53 ~
Block re-entrance during Interrupt handler loop in OS2 driver.
Hanle Transmit Segment equal to 0 for OS2 Granite trap.
Fixed a low performance problem with BCM5701 Serdes LOMs with Copper Trace
media. As in the PXE v2.1.2.
Port number correction.
05/10/02 - v1.11-
Minor Modification to accommodate IBM IEEE 802.2 Protocol.
04/29/02 - v1.10-
Drivers allocate system's memory for adapter use to reduce the file size.
04/22/02 - v1.09-
Removed unused adapter's specific features.
04/19/02 - v1.08-
1. Latest LM from ODI16 v1.17 that have following fixes:
a) DMA once bit with PCI-X
b) LINK polarity bit for 5703/02.
c) Removed the runt packet configuration setup.
d) The PHY ADC Decimator fix.
e) Additional delays are needed during PCI config B2B access.
f) 40us delay after GPIO access.
3. Added PortNum Keyword.
4. New banner displays other NICS present in the system (up to 8).
5. Support up to 4 adapters.
6. Os2 Traps during Fibre Auto-Negotiation.
04/03/02 - v1.07-
Removed debug statements conflict with retail OS/2 kernel.
03/27/02 - v1.06-
Fixed inconsistent Fibre Auto-Negotiation.
03/25/02 - v1.05-
Fixed high data rate Netbeui protocol's flowcontrol, Added Fiber LED control,
and fixed locked up when cable is disconnected and re-connected during file
transfer.
03/07/02 - v1.04-
Added 16a6, 16a7, 164d device ids. Drivers utilized ODI16 v1.15's LM supports
nic send bds and wirespeed.
02/25/02 - v1.03-
Added LineSpeed, Duplex, and FuncNum keywords.
02/08/02 - v1.02-
Fixed BusNum and DevNum keywords to pickup the assigned adapter when there
are more than one adapter present. Utilized ODI16 v1.14's LM modules.
02/07/02 - v1.01-
Add OS2 support. Current drivers does not support any Ax firm ware fixes.
02/06/02 - v1.00-
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.