This document contains the NI Linux Device Drivers known issues that were discovered before and since the release of NI Linux Device Drivers 2023 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; see Additional Resources.
Bug Number |
Legacy ID |
Description |
Details |
---|---|---|---|
1448861, 1482726, 1482726 |
System Crashes When NI Drivers Exceed the Default Max for iNotify InstancesWhen 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:
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 HibernateNI 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 |
|
1210589, 2256290 |
DMA is not working with NI Drivers on IOMMU-enabled systemsWhen 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 |
|
NI Driver software fails to install on Linux kernel 5.16 or later with "stdbool.h: No such file or directory"When installing certain NI drivers onto a Linux system using kernel version 5.16 or later, the installation fails at the "dkms autoinstall" step with an error such as: Error! Bad return status for module build on kernel: 5.19.0-32-generic (x86_64) Consult /var/lib/dkms/xxxxx/xxx/build/make.log for more information. And the make.log file shows: stdbool.h: No such file or directory As of the 2023Q1 release, this affects the following drivers: NI-488.2 NI-Sync Workaround: After running (or equivalent yum or zypper command)
Then rerun (or equivalent yum or zypper command) |
Reported Version: NI Linux Device Drivers 2022 Q4 Resolved Version: N/A Added: Apr 27, 2023 |
Issues found in this section will not be listed in future known issues documents for this product.
There are currently no issues to list.
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