ni.com checkout is currently experiencing issues.
Support teams are actively working on the resolution.
ni.com checkout is currently experiencing issues.
Support teams are actively working on the resolution.
05-23-2022 04:40 PM - edited 05-24-2022 02:12 PM
We are attempting to pxeboot a system based on our working RHEL 7.9 LabVIEW 2019 SP1 installation.
When we created the nfs image that the system uses using rsync we took everything but /proc and /sys and /home/installers (where we put package and iso images on our disconnected systems in case we need to install a package we forgot).
The system boots into RHEL 7.9 GNOME, autologin and autostart work to trigger the start of our LabVIEW EXE - but when my DAQmx device based code runs, it is telling me that the DAQmx driver basically has not been installed. I get error -52006 when DAQmx Create Task.vi is called.
Anyone have experience with the NI DAQmx LabVIEW drivers in a pxeboot system that should run a LabVIEW EXE that can shed some light?
when I run
nidaqmxconfig --export /tmp/ni-system in the disk loaded image version I get the DAQmx cards listed in Slots 6, 7, 8, and 9
When I run from the pxeboot running the NFS image
nidaqmxconfig --export /tmp/ni-system
shows
Failed
Error -52006
The requested resource was not located.
Edit to add: Coworker used the disk-booted FSP-4 system to collect all modules reported by lsmod that started with "ni" or "Ni", and created files in the rootfs on tftpboot Server for each in the directory /etc/modules-load.d/*.conf
We saw some suggestions that on systemd systems that this could work to load drivers. This did not help.
Solved! Go to Solution.
05-24-2022 02:17 PM
Which (if any) NI kernel modules are being loaded on the failing system? What happens if you try to load one manually (e.g., if nipalk is failing to load, modprobe nipalk)? Anything interesting in dmesg or in /var/log/messages or using journalctl?
05-24-2022 02:49 PM - edited 05-24-2022 03:16 PM
ah dmesg showed a failure of nikal module verification failed: signature and/or required key missing
Accordingt to NI: NI-KAL is driver software that supports the Linux driver architecture.
Seems like this could be the source of the issue.
Although lsmod shows nikal loaded....
lsmod | grep ni
ni448k
nicdcck
nicmrk
nicntdrk
nidimk
nifslk
nikal
nilmsk
nimdbgk
nimru2k
nimxdfk
niorbk
nipalk
nipxipfk
nipxirmk
nismbus
05-24-2022 03:14 PM - edited 05-24-2022 04:48 PM
nikal is a fundamental module used by nearly every other NI kernel module.
The error message means that the kernel module is not signed properly for Secure Boot. Unlike the kernel and all of the modules included with it, out-of-tree modules must be signed separately if you wish to use Secure Boot. I can see a couple of scenarios:
Edit for future readers: I was completely wrong about Secure Boot in this case. See below.
05-24-2022 03:16 PM
@RVallieu wrote:
Although lsmod shows nikal loaded....
I just saw this part. Are other NI modules also shown as loaded? Maybe the dmesg output was just a warning and not an error.
05-24-2022 03:19 PM
Was editing my prior post with the list. Its a disconnected system so I have to type it out....
The one difference in loaded packages we see is NiVipciK did not load on the pxeboot system
05-24-2022 03:28 PM
did a modprobe NiPciViK and it seems to have loaded
Doing a reboot on the pxeboot and seeing if it is persistent.
05-24-2022 03:33 PM
NiViPciK is the VISA PCI/PXI Passport. NI software should be configured to load it at boot normally.
05-24-2022 03:34 PM
It was persistent, but the DAQmx driver is still not loaded...
nidaqmxconfig --export /tmp/ni-system still shows error -52006 The requested resource was not found.
05-24-2022 03:38 PM
Looks like all of the modules shown in lsmod | grep ni from the disk booted system are now loaded when we do the pxeboot system - yet we still have the DAQmx driver error