Chapter 4: Installing the Linux Drivers
58
Apply the updates by running the scripts provided in the supplemental tar
file. For example, on Red Hat Enterprise Linux, apply the updates by
entering the following commands:
./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
Next, back up the old files and the rename the new files by entering the
following copy commands:
cp /usr/share/hwdata/pci.ids /usr/share/hwdata/
old.pci.ids
cp /usr/share/hwdata/pci.ids.new /usr/share/hwdata/
pci.ids
cp /usr/share/hwdata/pcitable /usr/share/hwdata/
old.pcitable
cp /usr/share/hwdata/pcitable.new /usr/share/hwdata/
pcitable
NetworkInstallations
For network installations through NFS, FTP, or HTTP (using a network
boot disk or PXE), a driver disk that contains the bnx2 driver may be
needed. The driver disk images for the most recent Red Hat and SuSE
versions are included. Boot drivers for other Linux versions can be
compiled by modifying the Makefile and the make environment. Further
information is available from the Red Hat website, http://www.redhat.com.
Setting Values forOptionalProperties
You can set values for optional properties for the bnx2 and bnx2i Linux
drivers. See the following:
“Setting Optional Properties for the bnx2 Driver” on page58
“Setting Optional Properties for the bnx2i Driver” on page59

Setting Optional Properties for the bnx2 Driver

The disable_msi optional property can be supplied as a command line
argument to the insmod or modprobe command. The property can also be
set in the modprobe.conf command. See the man page for more
information. All other driver settings can be queried and changed using the
ethtool utility. See the ethtool man page for more information. The ethtool
settings do not persist across a reboot or module reload. The ethtool
commands can be put in a startup script such as /etc/rc.local to preserve
the settings across a reboot.