Rev 1.8
30
Mellanox Technologies
5.1.2.2 Installation Results
5.1.2.3 Installation Logging
While installing MLNX_OFED, the install log for each selected package will be saved in a
separate log file.
The path to the directory containing the log files will be displayed after running the installation
script in the following format:
"Logs dir: /tmp/MLNX_OFED_LINUX-<version>.<PID>.logs"
.
Example:
5.1.2.4 Driver Load Upon System Boot
Upon system boot, the Mellanox drivers will be loaded automatically.
To prevent automatic load of the Mellanox drivers upon system boot:
Step 1.
Add the following lines to the
"/etc/modprobe.d/mlnx.conf"
file.
Software
• Most of MLNX_OFED packages are installed under the “/usr” directory except
for the following packages which are installed under the “/opt” directory:
• openshmem, bupc, fca and ibutils
• The kernel modules are installed under
• /lib/modules/`uname -r`/extra/mlnx-ofa_kernel on RHEL and other RedHat
like Distributions
• /lib/modules/`uname -r`/updates/dkms/ on Ubuntu
Firmware
• The firmware of existing network adapter devices will be updated if the following
two conditions are fulfilled:
• The installation script is run in default mode; that is, without the option
‘--without-fw-update’
• The firmware version of the adapter device is older than the firmware version
included with the Mellanox OFED ISO image
Note:
If an adapter’s Flash was originally programmed with an Expansion
ROM image, the automatic firmware update will also burn an Expansion
ROM image.
• In case your machine has an unsupported network adapter device, no firmware
update will occur and the error message below will be printed.
-I- Querying device ...
-E- Can't auto detect fw configuration file: ...
Please contact your hardware vendor for help on firmware updates.
Logs dir: /tmp/MLNX_OFED_LINUX-x.x-x.logs
blacklist mlx4_core
blacklist mlx4_en
blacklist mlx5_core