Driver Kernel Module Error in Linux Desktop in the NI Hardware Configuration Utility

Issue Details

After connecting an NI device to my computer with Linux desktop operating system, I receive the following error in the NI Hardware  Configuration Utility:

A driver Kernel module is installed but not running on your system. if you have recently installed new drivers, run "sudo dkms autoinstall" and reboot.

Or loading the module with modprobe results in:

modprobe: ERROR: could not insert '<module>': Key was rejected by service 

Solution

This error can be caused due driver compatibility depending on the Linux distribution. To solve this you can verify the points:

• Check the NI Hardware and Software Operating System Compatibility to confirm your module is compatible with the Linux desktop distribution you have, and also that the corresponding driver version is compatible as well (which is installed by the Linux Device drivers).
• This issue could be caused by corrupted software or a bad installation of the drivers. If running the command suggested by the error message doesn't fix the problem, you can try to reinstall the driver of your corresponding NI hardware manually:
  • This article explains how to install a driver depending on your Linux Distribution: Installing NI Drivers and Software on Linux Desktop.
• You can also test the hardware in a different computer to isolate the problem to this particular computer.

Another known cause for this error is when the Secure Boot is unable to validate a kernel module. When signing the module consider the following points:

• NI drivers on Linux are installed by [External] Dynamic Kernel Module System (DKMS), a standard for supporting third-party kernel modules on Linux.  DKMS signs each kernel module during installation. For Secure Boot to validate the module signature, the signing key must be enrolled with the system firmware. Typically, the signing key is /var/lib/dkms/mok.pub. On Ubuntu, the key is /var/lib/shim-signed/mok/MOK.der.  
• To enroll this key with the firmware, follow the instructions provided by DKMS on [External] Secure Boot. Key enrollment is a one-time event, after which Secure Boot will permit existing and newly-added signed third-party modules.