NI-KAL 2.0 / VISA RTE 5.0 Beta available

[mhoogend]

Bryan wrote:

I have several USB devices that I am using with LabVIEW and have to keep an older kernel for the drivers to work.  I didn't see any mention in the release notes if this version of NI-KAL allows the use of USB devices or if that restriction is in one of the other driver modules.  Is anyone aware if this will improve the use of USB devices?

Thanks.

All NI drivers that leverage USB through the kernel (while it was available) have the code in place and should still work if you are using a kernel without GPL_ONLY on the usb symbols.  We detect if that goes away and give runtime failures if you try to use a USB device on a kernel with USB symbols as GPL_ONLY.

[mhoogend]

anshuljain wrote:

I did some tinkering and managed to get it working I'd suggest that the README file be more comprehensive on how to install NI-KAL for openSUSE as it was in the earlier releases. The steps that I performed are the same as that for NI-KAL 1.10 for openSUSE 11.1. Repeating them here verbatim:-

<snip>

I'm not aware of the steps not being included in the README for NI-KAL.  You should still have that, but it does not show up in the NI-VISA README.

I then install NI-VISA 4.5.1 and it installed successfully. It did throw up some warning messages about niorb etc installed and also some messages from scripting errors. But there was no problem installing. I then rebooted the system and performed an updateNIdrivers just to be sure.

niorb warnings messages I would expect for a 64-bit kernel (but it looks like you are running 32-bit from what I can tell).  Do you still have the messages from scripting errors?

[mhoogend]

AKHuettel wrote:

While testing the installation of nikal-2.0 beta 1 with Gentoo, kernel 2.6.33-gentoo-r1, I found the following issues (which might at the moment not be relevant for "supported distros" but will be at some point for sure):

<snip>

With these changes the module compiles and installs fine. No further functionality tests done so far...

Yes, this is something that happened in later kernels than what we will be officially supporting for this release.  We do have your patch though and will make an effort to include it in this release.

[mhoogend]

Note to beta testers.  We found there are some issues where you will have to run updateNIDrivers after the installer completes.  The installer doesn't tell you this so you don't know what exactly the problem is.  Using this beta we would recommend you first try updateNIDrivers after an installation before rebooting or trying the driver out.

We are working on fixing it before release.

I believe Anshul may have run into this issue at some point.

[ninevoltz]

I tried it out on Fedora 12 yesterday with kernel 2.6.32.12-115.fc12.i686. It installed ok, but causes a kernel oops. It works fine under kernel 2.6.24.7. I'll try to get more details for you next week or so, when I get more time to tinker with it.

Thanks for working on this, I've been stuck using kernel 2.6.24.7 since 2008 because of the NI drivers. 2.6.24 doesn't have support for ext4 which creates some issues with using Fedora 12+.

There were some build messages/problems:

the program '/bin/bash' called '/sbin/udevcontrol', it should use 'udevadm control <options>', this will stop working in a future release
udevadm control commands requires the --<command> format, this will stop working in a future release

and

make: depmod: Command not found
make: *** [install] Error 127

The makefile for nikal has a call to depmod, which doesn't work.

[ninevoltz]

Here's what happens in Fedora 13, when the nipal service is started, anyone know what might fix it?

BUG: unable to handle kernel paging request at debfe000
IP: [<e3bb2ba0>] nipalk-unversioned0002875+0x294/0x4a8 [nipalk]
*pde = 00007067 *pte = 00000000
Oops: 0000 [#1] SMP
last sysfs file: /sys/devices/pci0000:00/0000:00:18.3/temp1_input
Modules linked in: nipalk(P) nikal(P) oss_usb oss_hdaudio osscore nfsd exportfs nls_utf8 cifs nfs lockd fscache nfs_acl auth_rpcgss sunrpc ipv6 fuse uinput nvidia(P) nouveau ttm drm_kms_helper forcedeth i2c_nforce2 drm i2c_algo_bit i2c_core k8temp ppdev usb_storage parport_pc parport serio_raw microcode pata_acpi ata_generic pata_amd sata_nv [last unloaded: scsi_wait_scan]

Pid: 3721, comm: cat Tainted: P           (2.6.31.5-127.fc12.i686 #1) 
EIP: 0060:[<e3bb2ba0>] EFLAGS: 00010213 CPU: 0
EIP is at nipalk-unversioned0002875+0x294/0x4a8 [nipalk]
EAX: d4bb6130 EBX: e3c55ce0 ECX: 02811a9a EDX: d4bb7598
ESI: e3c55ce0 EDI: d837a738 EBP: d4ca7ef4 ESP: d4ca7e74
DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Process cat (pid: 3721, ti=d4ca6000 task=d839d940 task.ti=d4ca6000)
Stack:
d4bb7598 00000004 e3c55ce0 00000000 00000000 d4bb6130 00000000 00000000
<0> 00000000 d837a738 e3bd6ce0 d4ca7ecc 00000000 e3c55ce0 02811a9a 00000000
<0> d4ca7ef8 e3c55ce0 ffffffff e3baa535 d4ca7ecc e3c55ce0 000a1856 d4ca7ef0
Call Trace:
[<e3bd6ce0>] ? _ZNV14tSyncAtomicU32mmEi+0x14/0x30 [nipalk]
[<e3baa535>] ? nipalk-unversioned0002590+0x55/0x7c [nipalk]
[<e3b93955>] ? nipalk-unversioned0002405+0x29/0x48 [nipalk]
[<e3b92e20>] ? nipalk-unversioned0002396+0x1b8/0x1ec [nipalk]
[<df4709d7>] ? nNIKAL100_release+0x1e/0x3b [nikal]
[<c04c1467>] ? __fput+0xed/0x184
[<c04c1516>] ? fput+0x18/0x1a
[<c04be9b9>] ? filp_close+0x56/0x60
[<c04bea23>] ? sys_close+0x60/0x8f
[<c040363c>] ? syscall_call+0x7/0xb
Code: a4 00 00 00 00 8b 5d 88 89 5d b4 c7 45 b8 00 00 00 00 8b 43 08 85 c0 89 5d c4 89 45 c8 74 27 8b 75 b4 8b 4d b8 8b 56 0c 8b 45 94 <39> 04 8a 74 2e 8d 51 01 8b 5d 88 89 55 b8 8b 43 08 39 c2 89 5d
EIP: [<e3bb2ba0>] nipalk-unversioned0002875+0x294/0x4a8 [nipalk] SS:ESP 0068:d4ca7e74
CR2: 00000000debfe000
---[ end trace c169112307b3b95c ]---
BUG: sleeping function called from invalid context at kernel/rwsem.c:21
in_atomic(): 0, irqs_disabled(): 1, pid: 3721, name: cat
Pid: 3721, comm: cat Tainted: P      D    2.6.31.5-127.fc12.i686 #1
Call Trace:
[<c042866a>] __might_sleep+0xc6/0xcb
[<c0765a02>] down_read+0x1a/0x2e
[<c0461606>] acct_collect+0x3c/0x15d
[<c0439e73>] do_exit+0x15e/0x5da
[<c0764636>] ? printk+0x14/0x16
[<c0767010>] oops_end+0x99/0xa1
[<c0420083>] no_context+0x10d/0x117
[<c04275fa>] ? sched_slice+0x76/0x9d
[<c04201ac>] __bad_area_nosemaphore+0x11f/0x127
[<c0416a0a>] ? apic_write+0x14/0x16
[<c0416c20>] ? lapic_next_event+0x14/0x18
[<c045338e>] ? clockevents_program_event+0xbf/0xcd
[<c043c0d9>] ? __do_softirq+0x148/0x157
[<c0767ead>] ? do_page_fault+0x0/0x298
[<c04201c6>] bad_area_nosemaphore+0x12/0x15
[<c0767fe1>] do_page_fault+0x134/0x298
[<c0767ead>] ? do_page_fault+0x0/0x298
[<c0766663>] error_code+0x73/0x78
[<e3bb2ba0>] ? nipalk-unversioned0002875+0x294/0x4a8 [nipalk]
[<e3bd6ce0>] ? _ZNV14tSyncAtomicU32mmEi+0x14/0x30 [nipalk]
[<e3baa535>] ? nipalk-unversioned0002590+0x55/0x7c [nipalk]
[<e3b93955>] ? nipalk-unversioned0002405+0x29/0x48 [nipalk]
[<e3b92e20>] nipalk-unversioned0002396+0x1b8/0x1ec [nipalk]
[<df4709d7>] nNIKAL100_release+0x1e/0x3b [nikal]
[<c04c1467>] __fput+0xed/0x184
[<c04c1516>] fput+0x18/0x1a
[<c04be9b9>] filp_close+0x56/0x60
[<c04bea23>] sys_close+0x60/0x8f
[<c040363c>] syscall_call+0x7/0xb

[philfour]

Hi all

I've tried to install this version on my openSuse 11.2, and I can't get it working. As I'm prety new to Linux, I'm not sure to have done all that has to be done. I've strictly followed the anshuljain's note, and after an updateNIDrivers, installed the NIDaqmx 8.01.Both installation (visa and nidaqmx) didn't returned any error messages. Everything seemed to be OK.

When I try to run the nidaqmxconfig, I've the followin message :

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

Of course, updateNIDrivers doesn't change anything.

I don't if it would be useful, but here some info about my configuration :

tcms@testbenchcb:/usr/local/bin> rpm -qa |grep ^ni
niorbi-1.9.3-f0.i386                             
nistci-1.3.3-f0.i386                             
nimxs-4.0.1-3006.i386                            
nidaqmxcapii-1.6.1-f0.i386                       
nipalki-2.5.4-b2.i386                            
nimxdfi-1.4.1-f1.i386                            
nimioi-1.7.2-f0.i386                             
nipali-2.5.4-b2.i386                             
nimxpi-1.4.1-f0.i386                             
nidaqmxcapihelp-1.6.1-f0.i386                    
niscxi-1.5.1-f0.i386                             
nimdnsresponder-1.1.0-f3.i386                    
nivisak-5.0.0-b5.i386                            
nimdbgi-1.3.1-f0.i386                            
niscarabmm-1.2.1-f0.i386                         
nidaqmxinfi-8.0.1-f0.i386                        
nidaqmxcapiexmp-1.6.1-f0.i386                    
nitimingi-1.5.2-f0.i386                          
ni653x-1.1.1-f0.i386                             
nikali-2.0.0-b1.noarch                           
nidimi-1.9.0-f0.i386                             
nidaqmxhelp-1.0.1-f0.i386                        
nidaqmxcfgi-1.4.0-f0.i386                        
nivisa-5.0.0-b5.i386                             
nimru2i-2.4.1-f0.i386                            
nidaqmxef-1.4.1-f3.i386                          
nidaqmxswitch-1.6.1-f0.i386                      
nirpci-4.2.0-d6.i386                             
nipxirmi-1.6.0-f0.i386                           
nicdigi-1.5.1-f0.i386                            
nidsai-1.5.1-f0.i386

and here the result of niSystemReport:

/usr/local/bin/niSystemReport version 2.0.0b1

********************************************************************************
/bin/uname -a:
Linux testbenchcb 2.6.31.12-0.2-desktop #1 SMP PREEMPT 2010-03-16 21:25:39 +0100 i686 i686 i386 GNU/Linux
********************************************************************************

********************************************************************************
/etc/SuSE-release:
openSUSE 11.2 (i586)
VERSION = 11.2
********************************************************************************
/usr/local/bin/niSystemReport: line 79: ./configure: Aucun fichier ou dossier de ce type

********************************************************************************
/usr/local/natinst/nikal/src make:
make: *** Pas de cibles spécifiées et aucun makefile n'a été trouvé. Arrêt.
********************************************************************************
/usr/local/natinst/nipal/bin

********************************************************************************
/usr/bin/tail --lines=25 /var/log/messages:
Jul  6 15:27:28 testbenchcb smartd[3272]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.WDC_WD3000HLFS_01G6U1-WD_WXE0C79T3276.ata.state
Jul  6 15:27:28 testbenchcb smartd[3272]: Monitoring 1 ATA and 0 SCSI devices
Jul  6 15:27:28 testbenchcb smartd[3272]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD3000HLFS_01G6U1-WD_WXE0C79T3276.ata.state
Jul  6 15:27:28 testbenchcb smartd[3538]: smartd has fork()ed into background mode. New PID=3538.
Jul  6 15:27:28 testbenchcb pidof[3582]: can't read sid from /proc/3305/stat
Jul  6 15:27:28 testbenchcb /usr/sbin/cron[3609]: (CRON) STARTUP (V5.0)
Jul  6 15:27:28 testbenchcb SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Jul  6 15:27:28 testbenchcb SuSEfirewall2: using default zone 'ext' for interface eth0
Jul  6 15:27:28 testbenchcb SuSEfirewall2: using default zone 'ext' for interface eth2
Jul  6 15:27:28 testbenchcb SuSEfirewall2: using default zone 'ext' for interface eth3
Jul  6 15:27:28 testbenchcb SuSEfirewall2: batch committing...
Jul  6 15:27:29 testbenchcb SuSEfirewall2: Firewall rules successfully set
Jul  6 15:27:29 testbenchcb kernel: [   17.958113] bootsplash: status on console 0 changed to on
Jul  6 15:27:29 testbenchcb avahi-daemon[3171]: Service "testbenchcb" (/etc/avahi/services/ssh.service) successfully established.
Jul  6 15:27:29 testbenchcb avahi-daemon[3171]: Service "SFTP File Transfer on testbenchcb" (/etc/avahi/services/sftp-ssh.service) successfully established.
Jul  6 15:27:30 testbenchcb python: hp-systray[3755]: warning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting.
Jul  6 15:27:34 testbenchcb kernel: [   23.290130] eth1: no IPv6 routers present
Jul  6 15:29:36 testbenchcb nidaqmxconfig: [libnipalu.so.2.5]  Warning: source/lib/linux/linLoadKern.cpp:168 - libKernelDriverLoad: Failed to open nipalk, errno: 2
Jul  6 15:29:36 testbenchcb nidaqmxconfig: [libnipalu.so.2.5]  Warning: source/initcln/initcln.cpp:147 - Posix: Init kInitClnPackage: kernelDriver: failed! status=-50204
Jul  6 15:29:36 testbenchcb nidaqmxconfig: [libnipalu.so.2.5]  Warning: source/package/posix/ulibEntry.cpp:179 - initialize: unable to load NI-PAL. status=-50204
Jul  6 15:30:53 testbenchcb sudo:     tcms : TTY=pts/0 ; PWD=/ ; USER=root ; COMMAND=/usr/bin/zypper install findutils-locate
Jul  6 15:32:41 testbenchcb nilsdev: [libnipalu.so.2.5]  Warning: source/lib/linux/linLoadKern.cpp:168 - libKernelDriverLoad: Failed to open nipalk, errno: 2
Jul  6 15:32:41 testbenchcb nilsdev: [libnipalu.so.2.5]  Warning: source/initcln/initcln.cpp:147 - Posix: Init kInitClnPackage: kernelDriver: failed! status=-50204
Jul  6 15:32:41 testbenchcb nilsdev: [libnipalu.so.2.5]  Warning: source/package/posix/ulibEntry.cpp:179 - initialize: unable to load NI-PAL. status=-50204
Jul  6 15:39:59 testbenchcb sudo:     tcms : TTY=pts/0 ; PWD=/usr/local/natinst/nipal/bin ; USER=root ; COMMAND=/usr/local/bin/niSystemReport
********************************************************************************
/usr/local/natinst/nikal/src/Makefile.in: File not found!!!
/usr/local/bin/niSystemReport: line 95: /usr/local/natinst/nikal/src/Makefile.in: Aucun fichier ou dossier de ce type

Thanks for any help !!

Phil.

[philfour]

Hi all,

I've solved my problem after many tries by scalling the memory amount in the GRUB configuration (mem=4096M) thanks to some other posts. I didn't think to it first because I have 4Go installed, and I thought that the problem appeared only on systems with more than 4Go of RAM....

Phil.

[mhoogend]

Yes, that is the case many times.  When you have only 4GB of physical memory installed the OS will see > 4GB of RAM since it reserves some address space below 4GB for device memory.  That results in some physical memory being addressed at above 4GB.  Depending on the hardware in your system that size will vary.