NI Linux Device Drivers 2023 Q1 Known Issues

Overview

This document contains the NI Linux Device Drivers known issues that were discovered before and since the release of NI Linux Device Drivers 2023 Q1 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; see Additional Resources.

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, 1870327, 1930911, 2044661, 2117686, 2256287, 2268371

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 2022Q4 release, this affects the following driver that depends on KAL:
NI-Serial


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 [on Ubuntu] 
sudo touch /usr/src/kernels/$(uname -r)/include/config/modversions.h [on RHEL] 
sudo touch /usr/src/linux-$(uname -r | sed -r 's/-default//')-obj/x86_64/default/include/config/modversions.h [on OpenSUSE]

Reported Version:

NI Linux Device Drivers 2021 Q4

Resolved Version:

N/A

Added:

Feb 21, 2023

1984221, 2143826

NI driver software fails to install on RHEL9 because of missing /sbin/chkconfig

When I try to install an NI driver on RHEL9, it fails with an error message indicating that chkconfig is missing. 

Many NI drivers use chkconfig in initialization of their services and will fail installation if it is not present. It was present in the base images of previous RHEL versions, but as of RHEL9 needs to be installed prior to NI drivers. The latest releases of most NI drivers will automatically install chkconfig on RHEL 9, however there are still a few that don't automatically install it. And none of the older NI driver versions prior to 2022Q4 automatically install it.

Installing chkconfig will fix this issue. However there is a chance that chkconfig may not install successfully on RHEL9 (for several reasons) see #2126697  for workarounds if installing chkconfig fails.

Workaround:

To explicitly avoid this issue, install chkconfig (which is in one of the RHEL9 default repositories) by running
sudo yum install chkconfig
prior to installing NI software on RHEL9. 

Reported Version:

NI Linux Device Drivers 2022 Q4

Resolved Version:

N/A

Added:

Sep 30, 2022

1984221, 2143826

Chkconfig fails to install on RHEL9

When running an NI installer on RHEL9, I get an error message which says
Failed:
  chkconfig-1.20-2.el9.x86_64                         Error: Transaction failed

This may occur because of this known issue with chkconfig: https://bugzilla.redhat.com/show_bug.cgi?id=1728139 which could be encountered by anyone trying to install chkconfig who has already run into #2126414.

Workaround:

1. Backup the /etc/init.d folder to somewhere

sudo mv /etc/init.d /home/<your username>/initd_backup

2. Install chkconfig
sudo yum install chkconfig

3. Restore the backup
sudo cp -u /home/<your username>/initd_backup /etc/init.d/

Reported Version:

NI Linux Device Drivers 2022 Q4

Resolved Version:

N/A

Added:

Sep 30, 2022

1976540

NI driver software fails to install on OpenSUSE 15.3+ because of missing /sbin/insserv

When I try to install an NI driver on OpenSUSE 15.3 or 15.4, it fails with an error message indicating that insserv is missing. 

Many NI drivers use insserv in initialization of their services and will fail installation if it is not present. It was present in the base images of previous OpenSUSE versions, but as of OpenSUSE Leap 15.3 needs to be installed prior to NI drivers. The latest releases of most NI drivers will automatically install insserv on OpenSUSE, however there are still a few that don't automatically install it. And none of the older NI driver versions prior to 2022Q4 automatically install it.

Installing insserv will fix this issue. 

Workaround:

To explicitly avoid this issue, install chkconfig (which is in one of the RHEL9 default repositories) by running
sudo zypper install insserv
prior to installing NI software on OpenSUSE. 

Reported Version:

NI Linux Device Drivers 2022 Q4

Resolved Version:

N/A

Added:

Sep 30, 2022

2187982

NI driver software fails to install on RHEL9 because of missing dkms dependency

During installation, NI driver software may fail to install on RedHat Enterprise Linux 9 with an error message such as:
Nothing provides dkms needed by ni-pal-dkms

Workaround:

Download and register the "Extra Packages for Enterprise Linux" (EPEL) repo provided by Fedora:
sudo yum install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
Install DKMS.
sudo yum install dkms
Proceed with installing NI Driver SW.

Reported Version:

NI Linux Device Drivers 2022 Q4

Resolved Version:

N/A

Added:

Oct 19, 2022

1210589, 2256290

DMA is not working with NI Drivers on IOMMU-enabled systems

When attempting to do DMA with an NI driver on a Linux system, memory access is restricted and the driver doesn't function. The kernel may report an error such as:
DMAR: [DMA Read NO_PASID] Request device [06:00.0] fault addr 0xb8441000 [fault reason 0x06] PTE Read access is not set


Workaround:

Disable IOMMU control from the Linux kernel bootup parameters with whichever of these applies to the system:
iommu=off 
intel_iommu=off
amd_iommu=off

Reported Version:

NI Linux Device Drivers 2020

Resolved Version:

N/A

Added:

Feb 21, 2023

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).