Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

NI488.2 linux installation problem

Hi, I am using Scientific Linux 6.5 32bit and I try to install NI-488.2 to talk with NI PCI-GPIB.

 

I downloaded http://www.ni.com/download/ni-488.2-2.9.1/3186/en/ and followed the installation instructions.

When I try to run gpibexplorer under /usr/local/natinst/ni4882/bin it says

libnipalu.so failed to initialize, Perhaps you need to run updateNIDrivers.

I run updateNIDrivers but nothing changes.

 

Also, when I run gpibtsw it says NI488.2 Software is not correctly installed on your system. Please restart the system and reinstall NI488.2 software. Which I did several times (with first uninstalling it completely as well) but nothing changed.

 

Can I get any help on this?

 

 

0 Kudos
Message 1 of 4
(4,797 Views)

Hello,

 

Unfortunately the 488.2 driver is not supported on Scientific Linux 6.5; it only goes up to Scientific Linux 6 (as it was made in 2012). I'm sorry for any inconveneince this may cause.

Rahul B.
0 Kudos
Message 2 of 4
(4,727 Views)

Hi,

 

On your 32-bit Scientific Linux 6.5 system, does it have more than 4 GB of memory? If so, this FAQ from the readme should help fix the problem if you are running on a system with over 4 GB:

 

Q11: When launching GPIB Explorer on 32 bit Linux with 4GB of memory or more, I
     get an error message about "libnipalu.so failed to initialize. Perhaps you
     need to run updateNIDrivers. Aborted".

A11: The NI-488.2 core driver is not able to run on a 32-bit system with more
     than 4GB of addressable memory. The work around for this problem is to
     limit the usable memory in the system to 4GB of addressable space.

     To limit the system memory, complete the following steps:
        1. In the grub boot menu, select the Linux version and press 'e' to edit
           the commands.
        2. Append "mem=4GB", with space before the option, to the Linux kernel
           executable (vmlinuz) line.
        3. Boot the Linux OS.

 

Hope this helps.

 

gpibtester

0 Kudos
Message 3 of 4
(4,707 Views)

This is where I am also.

 

I went into the boot logger and did this edit but I'm still getting the same error.

 

My system is Scientific Linux 6.5 32 bit

 

Any other steps to fixing this problem would be helpful.

0 Kudos
Message 4 of 4
(4,352 Views)