libnipalu.so failed to initialize error for all NI related commands

[soheil08]

Dear friends,

Already, I’ve installed two DAQ cards on PCI slots of a computer with a Centos 6.9 32-bit operating systems with the kernel version 2.6.32-754.2.1.el6.i686. The first one is PCI-6225 and the second is PCI-6509. I’ve followed all the steps of the instruction to update the Kernel and install the DAQmx802f0.iso driver successfully. However, now when I try to execute a command to verify the installation I just receive some errors. In more detail, I’ll elaborate on this issue as follows:

[user@localhost ~]$ nilsdev
libnipalu.so failed to initialize
Perhaps you need to run updateNIDrivers
Aborted

Unfortunately, I've run updateNIDrivers and it has been executed successfully, the problem isn't solved though.

Here are some outputs of NI routine commands:

[user@localhost ~]$ lsmod | grep ni
nikal                  55889  0 

[user@localhost ~]$ /etc/init.d/nipal start
/etc/init.d/nipal: line 81: /tmp/nipalk-load.log: Permission denied
FATAL: Error inserting nipalk (/lib/modules/2.6.32-754.2.1.el6.i686/kernel/natinst/nipal/nipalk.ko): Kernel does not have module support
 
error: nipalk failed to load
possible causes: 
   nipalk was not versioned for this kernel (2.6.32-754.2.1.el6.i686)
   modules are not enabled for this kernel (CONFIG_MODULES)
   unresolved symbols
possible solution: 
   if you recently installed a new kernel or have rebooted to
   a different kernel from one you were previously running then run
   /usr/local/bin/updateNIDrivers
   to version your NI drivers for kernel 2.6.32-754.2.1.el6.i686

Please help me to resolve this problem.

[GabeJ · Accepted solution]

NI recently released its July 2018 drivers for Linux.  I'd recommended uninstalling your current NI software and installing ni-daqmx version 18.1 instead.

[szewczak]

---

@GabeJ wrote:

NI recently released its July 2018 drivers for Linux.  I'd recommended uninstalling your current NI software and installing ni-daqmx version 18.1 instead.

---

I can confirm this solved a similar issue for me soheil08

[soheil08]

Thanks, I Installed NI-DAQmx 8.0.2 - RedHat, SUSE and NI-DAQmx Base 3.5 - RedHat, Scientific Linux, SUSE. You mean I should uninstall both of them and just install the new Linux driver version 18.1 using Linux Repos.? 

[SundarS]

---

@soheil08 wrote:

Thanks, I Installed NI-DAQmx 8.0.2 - RedHat, SUSE and NI-DAQmx Base 3.5 - RedHat, Scientific Linux, SUSE. You mean I should uninstall both of them and just install the new Linux driver version 18.1 using Linux Repos.? 

---

NI's July 2018 release of drivers should support both the 6221 and the 6509. Unless you had a pressing need for DAQmx Base 3.5, I'd recommend uninstalling both and installing NI DAQmx from the July 2018 release.

[charli22]

I tried to solve this problem installing the drivers update but I don´t solve the issue.

We installed NI-VISA 15.0 on CENTOS7 with labview 201732 bit. When running our application, the following error message appeared and the program aborted.

libnipalu.so failed to initialize

Perhaps you need to run updateNIDrivers

Do VISA 16, 17 or drivers 2018 support centos7 32 bit?

Could be possible to use LabVIEW 2017 with visa 15 without problems?

thanks in advance

[AlexRg]

I have had the same issue but mine was due to kernel not letting ni services start correctly.

I did:

    ftp.ni.com/support/softlib/visa/NI-VISA

    unzip NILinux2023Q3DeviceDrivers.zip

    sudo dpkg -i NILinux2023Q3DeviceDrivers/ni-ubuntu2004-drivers-2023Q3.deb

    sudo apt-get install -f

    reboot

When rebooting I got

    systemd[1]: nipal.service: Control process exited, code=exited, status=1/FAILURE

    systemd[1]: nipal.service: Failed with result 'exit-code'.

    systemd[1]: Failed to start LSB: NI Core Driver Services.

    In the session I could see that it was not started correctly

    :~$ sudo systemctl status nipal.service

    × nipal.service - LSB: NI Core Driver Services

         Loaded: loaded (/etc/init.d/nipal; generated)

         Active: failed (Result: exit-code) since Thu  UTC; 5min ago

           Docs: man:systemd-sysv-generator(8)

        Process: 966 ExecStart=/etc/init.d/nipal start (code=exited, status=1/FAILURE)

            CPU: 6ms

    systemd[1]: Starting LSB: NI Core Driver Services...

    nipal[977]: modprobe: ERROR: could not insert 'nipalk': Operation not permitted

    nipal[966]:

    nipal[966]: error: nipalk failed to load

    nipal[966]: error: Consult the product documentation for support

    nipal[966]: error: Or search for solutions on ni.com.

    systemd[1]: nipal.service: Control process exited, code=exited, status=1/FAILURE

    systemd[1]: nipal.service: Failed with result 'exit-code'.

    systemd[1]: Failed to start LSB: NI Core Driver Services.

From BIOS Enabling the UEFI 3rd party driver load

And disabling the secure boot, solved the issue

    :~$ sudo systemctl status nipal.service

    ● nipal.service - LSB: NI Core Driver Services

         Loaded: loaded (/etc/init.d/nipal; generated)

         Active: active (running) since Thu  UTC; 21min ago

           Docs: man:systemd-sysv-generator(8)

        Process: 955 ExecStart=/etc/init.d/nipal start (code=exited, status=0/SUCCESS)

          Tasks: 2 (limit: 8876)

         Memory: 3.8M

            CPU: 45ms

         CGroup: /system.slice/nipal.service

                 ├─1002 /bin/bash /usr/sbin/nipalps /dev/nipalk

    /var/lib/nipal/nipalps.bin

                 └─1004 cat /dev/nipalk

    systemd[1]: Starting LSB: NI Core Driver Services...

    systemd[1]: Started LSB: NI Core Driver Services.

[GabeJ]

Yes, kernel modules that are not part of the kernel tree, including NI's modules, generally don't get signed for Secure Boot automatically.  The documentation on NI's site points to RHEL's docs, which also apply to openSUSE, on signing modules manually.

I actually think Ubuntu is more advanced in its Secure Boot support, but I don't have any experience with Secure Boot there yet.