09-12-2011 06:15 PM
Hi I have Scientific Linux 6 installed and am trying to install NI Visa 5.1.1 it seems to have installed but I also get the libnipalu.so problems. I've done uninstall /INSTALL a few times and the same problem, I ran updateNIDrivers as root and it seemed to work, but I still get the libnipalu.so problem when I try to run visaconf
I'm not a linux person, I'm a MAC guy i know some unix commands but it's better to give me step by step instructions, how should I troubleshoot this?
I've looked at this thread http://forums.ni.com/t5/Multifunction-DAQ/libnipalu-so-failed-to-initialize/td-p/707700
i think my version of gcc was indicated to be .x.x.1 version behind the one that created the install script but i don;t think that should be the source of the problem is it?
for example i followed this
You'll usually receive this error if the kernel modules are not loaded. You mentioned that you ran updateNIDriver, but did it succeed? Were there any errors or warnings? The output of of niSystemReport could be useful as well. As root try something like:
niSystemReport > system.log
gzip system.log
And attach the result
but now where do i find that file to attach?
also for > rpm -qa|grep ^ni i get this
niiotracei-3.0.0-f0.i386
nivisa-devel-5.1.1-f0.i386
nivisak-5.1.1-f0.i386
nipali-2.7.0-f0.i386
nikali-2.2.0-f0.noarch
nivisa-config-5.1.1-f0.i386
nispyi-2.8.0-f0.i386
nidimi-1.10.0-f0.i386
nipalki-2.7.0-f0.i386
nivisaserver-5.1.0-f0.i386
nimdnsresponder-1.6.0-f3.i386
nivisa-5.1.1-f0.i386
niorbi-1.9.3-f0.i386
nicvirte-8.0-7.i386
nirpci-4.2.0-f0.i386
nipxirmi-1.6.0-f0.i386
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
I uninstalled and then reinstalled
*****************************************************************************
NI-VISA for Linux
version 5.1.1f0 for Linux
*****************************************************************************
National Instruments products support the following Linux distributions:
openSUSE
Red Hat Enterprise Linux Desktop + Workstation
Refer to README.txt for the latest information at the time of release.
Refer to www.ni.com/linux for the most recent information about Linux
support at National Instruments.
Continue? [Yn] y
Checking required install tools...
Checking installer tool versions...
dpkg Not found in current path
rpm 4.8.0 can be used with a default installation path
tar 1.23
Checking dependencies...
glibc 2.12
Unpacking install files to /tmp/nivisa-5.1.1f0.install...
******************************** WARNING **************************************
* The version of gcc in the path does not match the version of gcc used to *
* compile the currently running kernel. This can cause unpredictable *
* behavior in kernel drivers and should be fixed. *
* gcc version: 4.4.4 *
* kernel compiled with: 4.4.5 *
******************************** WARNING **************************************
NATIONAL INSTRUMENTS SOFTWARE LICENSE AGREEMENT (LINUX DRIVER SOFTWARE)
NI-VISA for Linux version 5.1.1f0
is about to be installed using rpm at /usr/local/natinst
Would you like to continue? [Yn] y
Installing NI-VISA for Linux version 5.1.1f0...
Pre Installation .
Post Installation .
Pre Installation ....................
Preparing... ########################################### [100%]
1:labview-2009-rte ########################################### [ 6%]
2:nispyi ########################################### [ 12%]
3:nirpci ########################################### [ 18%]
4:nimdnsresponder ########################################### [ 24%]
5:nikali ########################################### [ 29%]
6:nicvirte ########################################### [ 35%]
7:nipalki ########################################### [ 41%]
8:nipali ########################################### [ 47%]
9:niorbi ########################################### [ 53%]
10:nidimi ########################################### [ 59%]
11:nivisak ########################################### [ 65%]
12:nivisa ########################################### [ 71%]
13:nivisa-config ########################################### [ 76%]
14:nivisa-devel ########################################### [ 82%]
15:nivisaserver ########################################### [ 88%]
16:nipxirmi ########################################### [ 94%]
17:niiotracei ########################################### [100%]
Post Installation ....................
Updating modversions database to include newly installed drivers...
FOR PATENTS COVERING NATIONAL INSTRUMENTS PRODUCTS, REFER TO
THE PATENTS.txt FILE ON /mnt/disk AND/OR
www.ni.com/patents
******************************************************************************
* A reboot is required before attempting to use the
* NI-VISA for Linux software.
******************************************************************************
Would you like to reboot now? [yes|no
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
followed by
> visaconf
libnipalu.so failed to initialize
Perhaps you need to run updateNIDrivers
Aborted
~]# updateNIDrivers
******************************** WARNING **************************************
* The version of gcc in the path does not match the version of gcc used to *
* compile the currently running kernel. This can cause unpredictable *
* behavior in kernel drivers and should be fixed. *
* gcc version: 4.4.4 *
* kernel compiled with: 4.4.5 *
******************************** WARNING **************************************
Configuring for linux kernel version 2.6.32-131.12.1.el6.i686.
********************************* NOTE *********************************
Using kernel headers found in /lib/modules/2.6.32-131.12.1.el6.i686/source.
If this does not correspond to the location of the 2.6.32-131.12.1.el6.i686 headers,
then define KERNELHEADERS in your environment to point to the location
of the kernel headers, define KERNELTARGET as the version of the
kernel for which to compile, and then rerun ./configure.
********************************* NOTE *********************************
Kernel has reparent_to_init(): no
Number of arguments for do_munmap(): 3
pte_offset function: pte_offset_kernel()
Levels in page table: 4
Kernel has remap_pfn_range: yes
Kernel has kzalloc: yes
Kernel has chained SGL support: yes
USB altsetting name: cur_altsetting
Kernel has usb_get_intf(): yes
Kernel has intf_cache member in usb_host_config: yes
Kernel has ep[] members in usb_device: yes
Kernel exports usb_set_configuration(): no
Units of USB_CTRL_GET_TIMEOUT: msec
Kernel has owner member in usb_driver: no
Kernel has put_page_testzero(): yes
Kernel has mutex method: yes
Kernel has wait_for_completion_interruptible: yes
Kernel has config.h: no
Kernel has ioctl32.h: no
IRQ handlers have pt_regs: no
Kernel has work_struct and delayed_work: yes
Kernel supports fault method in vm_operations_struct: yes
Storing configuration in Makefile.in
If the values stored are incorrect they can be changed before running make.
Installing NI-KAL:
NI-KAL successfully updated.
Updating client modules:
nipalk.ko successfully updated.
NiViPciK.ko successfully updated.
niorbk.ko successfully updated.
nidimk.ko successfully updated.
NiViPxiK.ko successfully updated.
nipxirmk.ko successfully updated.
Rebooting is required to ensure that National Instruments drivers
have been successfully updated.
Would you like to reboot now? [yes|no]
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
even after running the driver update it's still the same problem
09-13-2011 08:57 AM
Have you tried limiting addressable kernel memory?
Installation and libnipalu.so problems
https://decibel.ni.com/content/message/26189#26189
Joe Friedchicken
NI Configuration Based Software Get with your fellow OS users
[ Linux ] [ macOS ]Principal Software Engineer :: Configuration Based Software
Senior Software Engineer :: Multifunction Instruments Applications Group (until May 2018)
Software Engineer :: Measurements RLP Group (until Mar 2014)
Applications Engineer :: High Speed Product Group (until Sep 2008)
09-13-2011 12:05 PM
How do I make the change or check the setting.
I only have a single 2GB module, in system monitor it says 1.9GiB
So I DO NOT get that message ([nipal] More than 4GB of addressable memory detected.)
09-13-2011 01:53 PM
Send us system.log file. You'll have to generate it yourself. The instruction was written as part of the message above: "As root, try something like..." You'll have to do it manually.
09-13-2011 04:12 PM
youmean this step right?
As root try something like:
niSystemReport > system.log
gzip system.log
And attach the result
if so, then I've attached the file.
09-13-2011 04:25 PM
The output from dmesg says:
/bin/dmesg:
...
[nipal] More than 4GB of addressable memory detected.
[nipal] This configuration is not supported. Check the release notes for more information.
And even though you only have 2GB of physical RAM, the kernel mapped it above the 4GB boundary:
/proc/iomem:
...
100000000-1005fffff : System RAM
100600000-103ffffff : RAM buffer
So, add mem=4096M to your kernel boot parameter list, and you should be fine.
Joe Friedchicken
NI Configuration Based Software Get with your fellow OS users
[ Linux ] [ macOS ]Principal Software Engineer :: Configuration Based Software
Senior Software Engineer :: Multifunction Instruments Applications Group (until May 2018)
Software Engineer :: Measurements RLP Group (until Mar 2014)
Applications Engineer :: High Speed Product Group (until Sep 2008)
09-13-2011 04:58 PM
how do I do that? again I'm not a regular linux user, so I'm not sure which file or it's relative location I just use gedit to add it? anywhere in the file? or it already exists and I just need to change it?
09-15-2011 07:07 AM
Depending on the boot manager you chose for your installation, modifying boot parameter is a little different. The boot managers:
* lilo -- old, most probably not used in your distrib
* grub 1 -- maybe this is the one you have?
* grub 2
There are various sites out there that give instructions on how to modify kernel boot parameters. Here's some examples:
http://www.thinkwiki.org/wiki/Kernel_parameters
http://grumpymole.blogspot.com/2007/05/ubuntu-how-to-edit-grub-boot-parameters.html
http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/configure-kernel-grub.html
NOTE: Keep in mind that different linux distribution does things a little differently. You may/may not touch grub config directly. Most probably that's the right way to go, but I don't know for sure.
09-15-2011 01:49 PM
that doesn't work all it does it make the system unbootable says Error 28: Selected item cannot fit into memory.
Again the box oly physically has 2GB ram so that ca't be it, also tried with mem=2048M and still the same error.
09-15-2011 03:23 PM
JCKey wrote:
Again the box oly physically has 2GB ram so that ca't be it, also tried with mem=2048M and still the same error.
The amount of physical RAM you have is irrelevant. The computer is free to remap it how it sees fit, and in fact, I mispoke: it wasn't the kernel that took some RAM and gave it new addresses above 4 GB, but your BIOS:
/bin/dmesg:
...
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009ec00 (usable)
BIOS-e820: 000000000009ec00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000020000000 (usable)
BIOS-e820: 0000000020000000 - 0000000020200000 (reserved)
BIOS-e820: 0000000020200000 - 0000000040000000 (usable)
BIOS-e820: 0000000040000000 - 0000000040200000 (reserved)
BIOS-e820: 0000000040200000 - 000000007a061000 (usable)
BIOS-e820: 000000007a061000 - 000000007a0ac000 (ACPI NVS)
BIOS-e820: 000000007a0ac000 - 000000007a0b4000 (ACPI data)
BIOS-e820: 000000007a0b4000 - 000000007a3cb000 (reserved)
BIOS-e820: 000000007a3cb000 - 000000007a3cc000 (usable)
BIOS-e820: 000000007a3cc000 - 000000007a3dc000 (reserved)
BIOS-e820: 000000007a3dc000 - 000000007a3ea000 (ACPI NVS)
BIOS-e820: 000000007a3ea000 - 000000007a410000 (reserved)
BIOS-e820: 000000007a410000 - 000000007a453000 (ACPI NVS)
BIOS-e820: 000000007a453000 - 000000007a68e000 (reserved)
BIOS-e820: 000000007a68e000 - 000000007a800000 (usable)
BIOS-e820: 000000007b000000 - 000000007f200000 (reserved)
BIOS-e820: 00000000fed1c000 - 00000000fed20000 (reserved)
BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved)
BIOS-e820: 0000000100000000 - 0000000100600000 (usable)
The part in bold shows that your RAM has been given new addresses above the 4 GB boundary by the system's BIOS.
So, perhaps your BIOS can be set to not map above the 4 GB bondary. I'm curious to understand how "mem=2048M" didn't work for you -- if you do this again, please post your system report.
Joe Friedchicken
NI Configuration Based Software Get with your fellow OS users
[ Linux ] [ macOS ]Principal Software Engineer :: Configuration Based Software
Senior Software Engineer :: Multifunction Instruments Applications Group (until May 2018)
Software Engineer :: Measurements RLP Group (until Mar 2014)
Applications Engineer :: High Speed Product Group (until Sep 2008)