Cisco Systems 5709 Manual De Usuario

January 2010

Document

ENGSRVT52-CDUM100-R

Unloading/Removing the Linux Driver

Page  127

•

•

•

The examples used in this procedure refer to the bnx2 driver, but also apply to the bnx2x driver.

•

On 2.6 kernels, it is not necessary to bring down the eth# interfaces before unloading the driver module.

•

If the cnic driver is loaded, unload the cnic driver before unloading the bnx2 driver.

•

Prior to unloading the bnx2i driver, disconnect all active iSCSI sessions to targets.

To unload the driver, use ifconfig to bring down all eth# interfaces opened by the driver, and then type the following:

rmmod bnx2

If the driver was installed using rpm, do the following to remove it:

rpm -e netxtreme2

NOTE: The examples used in this procedure refer to the bnx2 driver, but also apply to the bnx2x and bnx2i drivers.

If the driver was installed using make install from the tar file, the bnx2.o or bnx2.ko driver file has to be manually deleted from
the operating system. See 

 for the location of the installed driver.

NOTE: The examples used in this procedure refer to the bnx2 driver, but also apply to the bnx2x and bnx2i drivers.

For hardware detection utilities such as Red Hat kudzu to properly identify bnx2 supported devices, a number of files
containing PCI vendor and device information may need to be updated.

Apply the updates by running the scripts provided in the supplemental tar file. For example, on Red Hat Enterprise Linux,
apply the updates by doing the following:

./patch_pcitbl.sh  /usr/share/hwdata/pcitable pci.updates 

/usr/share/hwdata/pcitable.new bnx2

./patch_pciids.sh /usr/share/hwdata/pci.ids pci.updates 

/usr/share/hwdata/pci.ids.new