Home Support Documentation Bugs

NI Linux Device Drivers 2022 Q2 Known Issues

Created Jun 22, 2023

Overview

This document contains the NI Linux Device Drivers known issues that were discovered before and since the release of NI Linux Device Drivers 2022 Q2. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.

 

Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community.

Bug Number

Legacy ID

Description

Details
1448861, 1482726, 1482726

System Crashes When NI Drivers Exceed the Default Max for iNotify Instances

When running code that initializes NI drivers, the system crashes. This may be because the NI drivers have requested more than the 128 iNotify instances that the default Linux kernel allows. The likelihood of encountering this issue increases as the number of installed drivers increases.

Workaround:

Increase the iNotify limit from the default 128 to a larger number, such as 12288.

You can increase the iNotify limit permanently through the following:
  1. Add      
    fs.inotify.max_user_instances=<Upper Limit> to /etc/sysctl.conf 
  2. Run      
    sysctl -p
    to reload the limit     

  3. Run      
    sysctl -a | grep fs.inotify.max_user_instances
    to see that the new limit is set.


Or you can increase the iNotify limit after every restart with this command:

 
sudo sysctl -w fs.inotify.max_user_instances=<Upper Limit>
Note: <Upper Limit> can be any large number such as 12288.

Reported Version:

NI Linux Device Drivers 2021 Q3

Resolved Version:

N/A

Added:

Aug 10, 2021
1724713

NI Linux Device Drivers do not Support Sleep or Hibernate

NI device drivers may crash a Linux system if the system tries to sleep or hibernate while devices are in use.

Workaround:

There is no known workaround.

Reported Version:

NI Linux Device Drivers 2019

Resolved Version:

N/A

Added:

Nov 11, 2021
1860393, 1860393, 1930911

NI-KAL Fails to Install on Linux Kernel 5.13 or Later with Fatal Error

When installing certain NI drivers onto a Linux system using kernel version 5.13 or later, the installation fails at the NI-KAL component with the following error:

/var/lib/dkms/nikal/21.5.0f129/build/nikal.c:32:16: fatal error: config/modversions.h: No such file or directory

As of the 2022Q2 release, this affects the following drivers that depend on KAL:
NI-USRP
NI-RIO
NI-SCOPE
NI-488.2
NI-Serial
NI-SWITCH
NI-VISA

Workaround:

Reattempt the installation after adding modversions.h to the kernel headers for your current system kernel. For example:
sudo touch /usr/src/linux-headers-$(uname -r)/include/config/modversions.h

Reported Version:

NI Linux Device Drivers 2021 Q4

Resolved Version:

N/A

Added:

May 6, 2022

Final Time Issue Listed

Issues found in this section will not be listed in future known issues documents for this product.

There are currently no issues to list.

Additional Resources

Explore Support Content and Product Documentation 

 

 

Ask the NI Community

 

 

Request Support from an Engineer

 

A valid service agreement may be required, and support options vary by country

 

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).