Successful SUSE linux and DAQmx install; nilsdev and other utilities missing.

[GreggSAO]

I am trying to install an NI PCI-6723 card into a Linux computer.

Problems:  1) Although the NI INSTALL program *says* it installed successfully,
                     I cannot find utilities such as nilsdev, or nidaqmxconfig and
                    many others.

                   /usr/local/bin is entirely empty.

               2) During the install I see this:

dpkg-query: failed to open package info file `/var/lib/dpkg/available' for reading: No such file or directory

I've listed the setup and packages used, below as well as the output from the INSTALL script as well as the dmesg differences between before INSTALL and afterward.

If anyone can help me out I'd appreciate it as I don't know what to try next.

System setup:
=============

Operating system - OpenSUSE 11.3 i586, 32 bit.
-----------------

ls /lib/modules

2.6.34.10-0.6-default 

2.6.34.10-0.6-pae
2.6.34.10-0.6-desktop 

2.6.34.10-0.6-xen

uname -r
2.6.34.10-0.6-desktop

So I'm using the Desktop version and NOT the PAE version.

Packages installed:

dpkg
make
gcc
kernel-syms
kernel-source
I also ran through the kernel configuration procedure in the README (zcat....
make cloneconfig......make modules prepare etc)


Computer:
---------

Pentium Dual Core E6700
4GB DDR3-1333 RAM
64 bits

HARDWARE:

---------------------

lspci shows:

03:01.0 Class ff00: National Instruments Device 7073

NIDAQmx version downloaded and installed:
-----------------------------------------

DAQmx802f0.iso

Ok so after installing the OS and patches, and the other packages (e.g. dpkg), and ran the kernel congiuration procedure successfuly, I then catted dmesg to a file.  

Then I copied all the files in DAQmx802f0.iso from the the DVD I burned. Put them all into one directory, became root, cd'd to the directory and ran
./INSTALL.

It said it succeeded but with the following issue (here's the output):

---------------------------------------------------------------------
.......
Checking required install tools...
Checking installer tool versions...
dpkg found
rpm        4.8.0 can be used with a default installation path
tar        1.23
Checking dependencies...
glibc      2.11.2
Unpacking install files to /tmp/nidaqmx-8.0.2f0.install...


LabVIEW 8.6 not detected
Manually specify a location for LabVIEW 8.6 support files? [yN] y
Specify the installation path for the software; a natinst/LabVIEW-8.6
subdirectory will be created at the specified location.

[Default /usr/local

LabVIEW 8.6 support will be installed to /usr/local/natinst/LabVIEW-8.6

dpkg-query: failed to open package info file `/var/lib/dpkg/available' for reading: No such file or directory
dpkg-query: failed to open package info file `/var/lib/dpkg/available' for reading: No such file or directory
dpkg-query: failed to open package info file `/var/lib/dpkg/available' for reading: No such file or directory
dpkg-query: failed to open package info file `/var/lib/dpkg/available' for reading: No such file or directory
dpkg-query: failed to open package info file `/var/lib/dpkg/available' for reading: No such file or directory
dpkg-query: failed to open package info file `/var/lib/dpkg/available' for reading: No such file or directory
Preparing...                ########################################### [100%]
   1:lvsupport86-daqmxviref ########################################### [ 33%]
   2:lvsupport86-daqmxsupp  ########################################### [ 67%]
   3:lvsupport86-daqmxexmp  ########################################### [100%]

FOR PATENTS COVERING NATIONAL INSTRUMENTS PRODUCTS, REFER TO
THE PATENTS.txt FILE ON /home/gregg/WHIPPLE/NIDRIVER AND/OR
www.ni.com/patents

NI-DAQmx for Linux Installer Distribution Installation completed successfully.
----------------------------------------------------------------

I was offered the option of installing Labviews 8.0 through 8.6.  I said yes to 8.6 even though I have no intention of using it.

FIRST ISSUE:
============

Does the fact that it cannot find /var/lib/dpkg/available cause a serious problem?

    - can I just do a touch /var/lib/dpkg/available and run UNINSTALL then INSTALL?  Or does there have to be something in the file?

Next PROBLEM:
=============

As stated above, I cannot find nilsdev on my computer, nor any of the other utilities that ConfigurationGuide.html says should be there.  Including:


the nidaqmxconfig Command-Line Utility

[GreggSAO]

I just ran UNINSTALL and got the response sown below. As you can see a LOT of untilities were not installed:

Uninstalling NI-DAQmx for Linux Installer Distribution version 8.0.2f0...
labview80-rte not installed, skipping.
lvsupport80-daqmxexmp not installed, skipping.
lvsupport80-daqmxsupp not installed, skipping.
lvsupport80-daqmxviref not installed, skipping.
lvsupport82-daqmxexmp not installed, skipping.
lvsupport82-daqmxsupp not installed, skipping.
lvsupport82-daqmxviref not installed, skipping.
lvsupport85-daqmxexmp not installed, skipping.
lvsupport85-daqmxsupp not installed, skipping.
lvsupport85-daqmxviref not installed, skipping.
ni653x not installed, skipping.
nicdigi not installed, skipping.
nidaqmxcapiexmp not installed, skipping.
nidaqmxcapihelp not installed, skipping.
nidaqmxcapii not installed, skipping.
nidaqmxcfgi not installed, skipping.
nidaqmxef not installed, skipping.
nidaqmxhelp not installed, skipping.
nidaqmxinfi not installed, skipping.
nidaqmxswitch not installed, skipping.
nidimi not installed, skipping.
nidsai not installed, skipping.
nikali not installed, skipping.
nimdbgi not installed, skipping.
nimioi not installed, skipping.
nimru2i not installed, skipping.
nimxdfi not installed, skipping.
nimxpi not installed, skipping.
nimxs not installed, skipping.
niorbi not installed, skipping.
nipali not installed, skipping.
nipalki not installed, skipping.
nipalki not installed, skipping.
nipxirmi not installed, skipping.
nirpci not installed, skipping.
niscarabmm not installed, skipping.
niscxi not installed, skipping.
nistci not installed, skipping.
nitimingi not installed, skipping.
Pre Uninstallation ...............................
NI-DAQmx for Linux Installer Distribution Uninstallation completed successfully.

[JoeFriedchicken]

It's hard to determine what could be causing this problem. The INSTALL output doesn't appear to be complete -- perhaps the forum software pruned it. If you can attach it as text file, that would be helpful.

My first suggestion in the mean time is to uninstall dpkg. The INSTALL script prefers rpm, but it will use dpkg if it finds it on the system.

[GreggSAO]

Hi Joe,

I think that solved it...not having dpkg installed. The INSTALL had a lot more output. Stuff like this:

Pre Installation ...............................
Preparing...                ########################################### [100%]
   1:niscarabmm             ########################################### [  3%]
   2:nirpci                 ########################################### [  7%]
   3:nidaqmxhelp            ########################################### [ 10%]
   4:labview80-rte          ########################################### [ 14%]
   5:nikali                 ########################################### [ 17%].....

Next Problem:

After rebooting I tried to run nilsdev. It was there but I got this response:


gregg@LEDSLED:~/WHIPPLE/NIDRIVER> nilsdev
libnipalu.so failed to initialize
Perhaps you need to run updateNIDrivers
Aborted

the library exists in /usr/local/lib.

So ok I then ran updateNIDrivers. The results feedback below. but that did not solve the problem:

LEDSLED:/home/gregg/WHIPPLE/NIDRIVER # /usr/local/bin/updateNIDrivers
 
Configuring for linux kernel version 2.6.34.10-0.6-desktop.
 
********************************* NOTE *********************************
Using kernel headers found in /lib/modules/2.6.34.10-0.6-desktop/source.
If this does not correspond to the location of the 2.6.34.10-0.6-desktop 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
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.
 niorbk.ko successfully updated.
 nidimk.ko successfully updated.
 nimxpk.ko successfully updated.
 nipxirmk.ko successfully updated.
 nimdbgk.ko successfully updated.
 nistc2k.ko successfully updated.
 nimstsk.ko successfully updated.
 nimxdfk.ko successfully updated.
 nimru2k.ko successfully updated.
 nidmxfk.ko successfully updated.
 nicdrk.ko successfully updated.
 nisdigk.ko successfully updated.
 nimsdrk.ko successfully updated.
 nistcrk.ko successfully updated.
 niesrk.ko successfully updated.
 niwfrk.ko successfully updated.
 nidsark.ko successfully updated.
 nisftk.ko successfully updated.
 nitiork.ko successfully updated.
 nixsrk.ko successfully updated.
 nissrk.ko successfully updated.
 niscdk.ko successfully updated.
 nispdk.ko successfully updated.
 niswdk.ko successfully updated.
Rebooting is required to ensure that National Instruments drivers
have been successfully updated.
Would you like to reboot now? [yes|no] yes

I rebooted and stll had the same problem. I tried to set LD_LIBRARY_PATH but that didn't help.

I see this in the listing above:

ernel has config.h: no
Kernel has ioctl32.h: no
IRQ handlers have pt_regs: no

Are these the  killers?

Can you give me a hint on this one?

thanks!

Gregg

[JoeFriedchicken]

---

GreggSAO wrote:

Next Problem:

After rebooting I tried to run nilsdev. It was there but I got this response:


gregg@LEDSLED:~/WHIPPLE/NIDRIVER> nilsdev
libnipalu.so failed to initialize
Perhaps you need to run updateNIDrivers
Aborted

<snip>

Can you give me a hint on this one?

---

Sure. What does dmesg have to say now? I bet there's something 😉

That error message prints what used to be most frequent cause for this load failure: an updated kernel without updated NI kernel modules. Now that PCs have shifted to 64-bit processors, there's a new most frequent problem: the system BIOS is also 64-bit aware and may choose to map system RAM above the 32-bit address threshold. The Linux kernel uses that map and the NI kernel modules complain about 64-bit addressable memory. If you see a message like:

[nipal] More than 4GB of addressable memory detected.
[nipal] This configuration is not supported.  Check the release notes for more information.

in dmesg, then add the following kernel boot parameter [1]:

memmap=60G$0x100000000

[1] SL 6.0 NI-VISA 5.1.1 - libnipalu.so failed to initialize

https://decibel.ni.com/content/message/26778

[GreggSAO]

Yep I see those lines in dmesg.

So where do I enter that line ( mem = .......)?

You used the term:

".......kernel boot parameter"

I did a google search on that and saw that /boot/grub/menu.lst is one possibility. I looked at it and it said:

# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
# Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader

So is that where I'd put it?

/etc/sysconfig/bootloader?

And does the position in the file matter?

thanks

[GreggSAO]

After studying the files I do believe I should put this:

memmap=60G$0x100000000

in here:

/etc/sysconfig/bootloader

There is a line in there that has parameters which show up in the /boot/grub/menu.lst file so I am surmising that position matters, and that I can add the memmap parameter to that line and it will appear in /boot/grub/menu.lst

[JoeFriedchicken]

---

GreggSAO wrote:

So where do I enter that line ( mem = .......)?

 

---

YaST will let you do this [1]. If you edit the files in /etc/sysconfig by hand, you should follow the instructions [2].

[1] openSUSE Reference: 17.2. Configuring the Boot Loader with YaST

http://doc.opensuse.org/documentation/htmlsingle/openSUSE_113/opensuse-reference.html#sec.boot.yast2...

[2] openSUSE Reference: 16.3.2. Changing the System Configuration Manually

http://doc.opensuse.org/documentation/htmlsingle/openSUSE_113/opensuse-reference.html#sec.boot.sysco...

[GreggSAO]

Many thanks I'll give it a try this afternoon.

[GreggSAO]

I got into the Yast editor and selected SYSTEM | BOOTLOADER

I then added the memmap = 60G..... command and saved.

I rebooted

Ran updateNIDrivers <kernel>

rebooted

and then ran nilsdev:

gregg@LEDSLED:~/WHIPPLE/NIDRIVER> nilsdev --verbose
NI PCI-6723: "Dev1"
    Serial Number:                      0x16B94D7
    Bus Type:                           PCI
    PCI Bus:                            0x3
    PCI Device:                         0x1
    IRQ Level:                          0x10
    Memory Range:                       0xFEBFF000-0xFEBFFFFF
    Memory Range:                       0xFEBFC000-0xFEBFDFFF

So now that works. I guess the next step is to find the sample C programs that come with the driver and run those.

thanks!

Gregg