01-12-2009 06:28 PM
Rne wrote:I have the same problem with OpenSuse 11.1 and NI-DAQmx.
After run INSTALL script, I try to run "updateNIDrivers" but I've the folling error :
/bin/cp nikal.c objects/nikal.c
/bin/cp nikal.h objects/nikal.h
make -C /lib/modules/2.6.27.7-9-pae/source SUBDIRS=/usr/local/natinst/nikal/src/objects modules
make[1]: entrant dans le répertoire « /usr/src/linux-2.6.27.7-9 »
CC [M] /usr/local/natinst/nikal/src/objects/nikal.o
/usr/local/natinst/nikal/src/objects/nikal.c: In function ‘nNIKAL100_initDriver’:
/usr/local/natinst/nikal/src/objects/nikal.c:875: error: ‘max_mapnr’ undeclared (first use in this function)
/usr/local/natinst/nikal/src/objects/nikal.c:875: error: (Each undeclared identifier is reported only once
/usr/local/natinst/nikal/src/objects/nikal.c:875: error: for each function it appears in.)
make[2]: *** [/usr/local/natinst/nikal/src/objects/nikal.o] Erreur 1
make[1]: *** [_module_/usr/local/natinst/nikal/src/objects] Erreur 2
make[1]: quittant le répertoire « /usr/src/linux-2.6.27.7-9 »
make: *** [objects/nikal.ko] Erreur 2
I should mention that we have not tested on openSUSE 11.1 and thus it is not officially supported. It looks like the kernel config for the pae kernel you have installed sets CONFIG_DISCONTIGMEM=y and CONFIG_NEED_MULTIPLE_NODES=y which is what causes NI-KAL to fail to compile. I'm curious is this the default kernel that openSUSE 11.1 installs, or did you manually install a different kernel either yourself or from the repositories? I mainly ask because it looks like you only have 2GB of RAM and a PAE kernel isn't really needed unless you have 4GB or more.
Since your system only has 2GB of RAM you can probably fix this problem by editing /usr/local/natinst/nikal/src/nikal.c and removing/commenting out lines 870-883. As the comment above them explains this code checks how much physically addressable memory is available, so it should be safe to remove that code on systems that have less than 3GB of RAM. After editing nikal.c you should be able to run updateNIDrivers.
Shawn Bohrer
01-13-2009 04:00 AM
Since your system only has 2GB of RAM you can probably fix this problem by editing /usr/local/natinst/nikal/src/nikal.c and removing/commenting out lines 870-883. As the comment above them explains this code checks how much physically addressable memory is available, so it should be safe to remove that code on systems that have less than 3GB of RAM. After editing nikal.c you should be able to run updateNIDrivers.
/bin/cp nikal.c objects/nikal.c
/bin/cp nikal.h objects/nikal.h
make -C /lib/modules/2.6.27.7-9-pae/source SUBDIRS=/usr/local/natinst/nikal/src/objects modules
make[1]: entrant dans le répertoire « /usr/src/linux-2.6.27.7-9 »
CC [M] /usr/local/natinst/nikal/src/objects/nikal.o
Building modules, stage 2.
MODPOST 1 modules
WARNING: modpost: module nikal.ko uses symbol 'init_mm' marked UNUSED
WARNING: "alloc_pages_current" [/usr/local/natinst/nikal/src/objects/nikal.ko] undefined!
WARNING: "node_data" [/usr/local/natinst/nikal/src/objects/nikal.ko] undefined!
WARNING: "physnode_map" [/usr/local/natinst/nikal/src/objects/nikal.ko] undefined!
CC /usr/local/natinst/nikal/src/objects/nikal.mod.o
LD [M] /usr/local/natinst/nikal/src/objects/nikal.ko
make[1]: quittant le répertoire « /usr/src/linux-2.6.27.7-9 »
Installing NI-KAL (nikal): Starting NI-KAL failed!
make: *** [install] Erreur 1
I should mention that we have not tested on openSUSE 11.1 and thus it is not officially supported. It looks like the kernel config for the pae kernel you have installed sets CONFIG_DISCONTIGMEM=y and CONFIG_NEED_MULTIPLE_NODES=y which is what causes NI-KAL to fail to compile. I'm curious is this the default kernel that openSUSE 11.1 installs, or did you manually install a different kernel either yourself or from the repositories? I mainly ask because it looks like you only have 2GB of RAM and a PAE kernel isn't really needed unless you have 4GB or more.
01-13-2009 07:48 AM
I tried to make a another test by installing the default kernel. In this case, updateNIDrivers seemed to work and I didn't have any error messages.
But when I tried to launch nilsdev, I had this error :
libnipalu.so failed to initialize
Perhaps you need to run updateNIDrivers
Abandon
I found a post about this error and I try to uninstall et reinstall the drivers but it wasn't work.
rpm -qa | grep ^ni
01-13-2009 08:43 AM
Hey Rne,
The system.log you provided with the default kernel looks like everything is installed. Did you reboot the system after running updateNIDrivers? The "libnipalu.so failed to initialize" error occurs when the nipalk.ko kernel module is not loaded and your system.log confirms that it is present but not loaded. This kernel module should load if you reboot the system.
Shawn Bohrer
National Instruments
01-13-2009 09:12 AM
Hey,
I tried to reboot many times but it doesn't work.
During the boot sequence, I saw this
FATAL: Error inserting nipalk (/lib/modules/2.6.27.7-9-default/kernel/natinst/nipal/nipalk.ko): Unknown symbol in module, or unknown parameter (see dmesg)
error: nipalk failed to load
possible causes:
nipalk was not versioned for this kernel (2.6.27.7-9-default)
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 then you were previously running then run
/usr/local/bin/updateNIDrivers
to version your NI drivers for kernel 2.6.27.7-9-default
and this with dmesg
nikal: module license 'Copyright (c) 2002-2008 National Instruments Corporation. All Rights Reserved. Any and all use of the copyrighted materials is subject to the then current terms and conditions of the applicable license agreement, which can be found at <http://www.ni.com/linux/>.' taints kernel.
Symbol init_mm is marked as UNUSED, however this module is using it.
This symbol will go away in the future.
nipalk: no symbol version for nNIKAL100_unregisterPCIDriver
nipalk: Unknown symbol nNIKAL100_unregisterPCIDriver
nipalk: no symbol version for nNIKAL100_waitForSingleUseEventTimeout
nipalk: Unknown symbol nNIKAL100_waitForSingleUseEventTimeout
nipalk: no symbol version for nNIKAL100_ioWrite16
nipalk: Unknown symbol nNIKAL100_ioWrite16
nipalk: no symbol version for nNIKAL100_unregisterUSBDriver
nipalk: Unknown symbol nNIKAL100_unregisterUSBDriver
nipalk: no symbol version for nNIKAL100_ioRead8
nipalk: Unknown symbol nNIKAL100_ioRead8
nipalk: no symbol version for nNIKAL100_usbSetConfiguration
nipalk: Unknown symbol nNIKAL100_usbSetConfiguration
nipalk: no symbol version for nNIKAL100_acquireSpinLockInterrupt
nipalk: Unknown symbol nNIKAL100_acquireSpinLockInterrupt
nipalk: no symbol version for nNIKAL100_pciConfigRead16
nipalk: Unknown symbol nNIKAL100_pciConfigRead16
....
01-14-2009 01:53 PM
HI, I swithced mu system to OpenSuse 11.0 322 bit, running with KDE 4. Although the NIDAQ mannage to install, when try (after reboot) nilsdaq, got the ususal error: nical failed to load....
I am attaching niSystemReport with this message.
Can you please help with this?
Stojan
01-14-2009 02:18 PM
Hey Stojan,
This KnowledgeBase should solve your problem. Basically you need to add mem=4096M to your kernel boot line.
Shawn Bohrer
National Instruments
01-15-2009 11:53 AM
Worked perfectly! Thanks!
Unfortunately I have another problem: when I try to do something with the card (using ansi_c examples) i get : AQmx Error: Device not available for routing. It is poss ... Status Code: -89130 (I will attach the full output).
I do check that the device number and channel numbers are ok etc..
Could you please help me with this?
S
01-15-2009 06:39 PM - edited 01-15-2009 06:39 PM
I have heard of this issue before on Linux and it seemed to have to do something with not all the services running properly. In one case I saw it had to do with nidevldu not starting. Could you run ps -A and see if nidevldu or something similar is running? Could you also run nilsdev --verbose --diag? This may provide some more clues as to what is going on.
Regards,
Neil S.
01-16-2009 03:06 PM
Hey,
I just reinstaled OpenSuse 11.0 32 bit, with gnome, puled out 1GB of memory (noe it has 3GB) and everything went fine. So I gues, this is it.
thax for the help.
S