Nvidia ConnectX-6 Dx User Manual page 30

Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com. Arrow.com.
Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from Downloaded from

On Redhat and SLES distributions with errata kernel installed there is no need
to use the mlnx_add_kernel_support.sh script. The regular installation can be
performed and weak-updates mechanism will create symbolic links to the
MLNX_OFED kernel modules.

If you regenerate kernel modules for a custom kernel (using
), the packages installation will not involve automatic regeneration of
support
the initramfs. In some cases, such as a system with a root filesystem mounted
over a ConnectX card, not regenerating the initramfs may even cause the
system to fail to reboot.
In such cases, the installer will recommend running the following command to
update the initramfs:
dracut -f
On some OSs, dracut -f
can be safely ignore.
libkmod: kmod_module_new_from_path: kmod_module 'mdev' already
exists with different path
The "mlnx_add_kernel_support.sh" script can be executed directly from the
mlnxofedinstall script. For further information, please see '--add-kernel-support' option
below.

On Ubuntu and Debian distributions drivers installation use Dynamic Kernel
Module Support (DKMS) framework. Thus, the drivers' compilation will take
place on the host during MLNX_OFED installation.
Therefore, using "mlnx_add_kernel_support.sh" is irrelevant on Ubuntu and
Debian distributions.
Example: The following command will create a MLNX_OFED_LINUX ISO image for
RedHat 7.3 under the /tmp directory.
# ./MLNX_OFED_LINUX-x.x-x-rhel7.3-x86_64/mlnx_add_kernel_support.sh -m /tmp/MLNX_OFED_LINUX-x.x-x-
rhel7.3-x86_64/ --make-tgz
Note: This program will create MLNX_OFED_LINUX TGZ
All Mellanox, OEM, OFED, or Distribution IB packages will be removed.
Do you want to continue?[y/N]:y
See log file /tmp/mlnx_ofed_iso.21642.log
Building OFED RPMs. Please wait...
Removing OFED RPMs...
Created /tmp/MLNX_OFED_LINUX-x.x-x-rhel7.3-x86_64-ext.tgz
• The script adds the following lines to /etc/security/limits.conf for the userspace
components such as MPI:
• * soft memlock unlimited
• * hard memlock unlimited
• These settings set the amount of memory that can be pinned by a
userspace application to unlimited. If desired, tune the value unlimited
to a specific amount of RAM.
might result in the following error message which
for rhel7.3 under /tmp directory.
--add-kernel-
30