Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

Make of nikal kernel module failed

Hi,
   I am installing NI-488.2 driver on SUSE Linux 10.1, after running the command ./INSTALL, it always failed.
The following lists the failure. The log file niSystemReport.out.gz is also attached. I have searched the similar
problems posted in the forum, but helps little. Thanks for your help in advance.
 
===========================================================
 
Installing NI-488.2 Distribution version 2.5.1f0...
Pre Installation ......
Preparing...                ########################################### [100%]
   1:nikali                 ########################################### [ 20%]
   2:nipali                 ########################################### [ 40%]
/sbin/ldconfig: /usr/lib/libcomedi.so.0 is not a symbolic link
   3:labview80-rte          ########################################### [ 60%]
   4:nispyi                 ########################################### [ 80%]
/sbin/ldconfig: /usr/lib/libcomedi.so.0 is not a symbolic link
   5:ni4882i                ########################################### [100%]
/sbin/ldconfig: /usr/lib/libcomedi.so.0 is not a symbolic link
Post Installation .
Warning: nikali post installation failed! /tmp/nikaliPostInstall.log follows:
Configuring for linux kernel version 2.6.16.13-4-smp.
********************************* NOTE *********************************
Using kernel headers found in /lib/modules/2.6.16.13-4-smp/source.
If this does not correspond to the location of the 2.6.16.13-4-smp 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(): yes
Number of arguments for do_munmap(): 3
pte_offset function: pte_offset_kernel()
Levels in page table: 4
Kernel has remap_pfn_range: 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
Storing configuration in Makefile.in
If the values stored are incorrect they can be changed before running make.
Uninstalling NI-KAL (nikal): done
/bin/rm -rf objects
Updating NI-KAL:
 NI-KAL update failed.
/bin/cp nikal.c objects/nikal.c
/bin/cp nikal.h objects/nikal.h
make -C /lib/modules/2.6.16.13-4-smp/source SUBDIRS=/usr/local/natinst/nikal/src
/objects modules
make[1]: Entering directory `/usr/src/linux-2.6.16.13-4'
  CC [M]  /usr/local/natinst/nikal/src/objects/nikal.o
  Building modules, stage 2.
  MODPOST
WARNING: "_spin_lock" [/usr/local/natinst/nikal/src/objects/nikal.ko] undefined!
WARNING: "_spin_lock_irqsave" [/usr/local/natinst/nikal/src/objects/nikal.ko] un
defined!
WARNING: "del_timer_sync" [/usr/local/natinst/nikal/src/objects/nikal.ko] undefi
ned!
WARNING: "_spin_unlock_irqrestore" [/usr/local/natinst/nikal/src/objects/nikal.k
o] undefined!
WARNING: "cpu_online_map" [/usr/local/natinst/nikal/src/objects/nikal.ko] undefi
ned!
WARNING: "_spin_unlock_bh" [/usr/local/natinst/nikal/src/objects/nikal.ko] undef
ined!
WARNING: "_spin_lock_bh" [/usr/local/natinst/nikal/src/objects/nikal.ko] undefin
ed!
  CC      /usr/local/natinst/nikal/src/objects/nikal.mod.o
  LD [M]  /usr/local/natinst/nikal/src/objects/nikal.ko
make[1]: Leaving directory `/usr/src/linux-2.6.16.13-4'
Installing NI-KAL (nikal): Starting NI-KAL failed!
make: *** [install] Error 1
ERROR: make of nikal kernel module failed, not installing kernel module.
   updateNIDrivers should be called again after fixing the problem.
   Logging failure...
   Include the file /tmp/niSystemReport.out.gz when contacting
   National Instruments for support.
===========================================================
My Linux environment:
 
wujun@aft:/tmp> rpm -qa | grep -i kern
kernel-docs-2.6.16.13-4
kernel-smp-2.6.16.13-4
kernel-syms-2.6.16.13-4
kernel-source-2.6.16.13-4

wujun@aft:/tmp> cat /proc/version
Linux version 2.6.16.13-4-smp (geeko@buildhost) (g
 #1 SMP Wed May 3 04:53:23 UTC 2006
wujun@aft:/tmp> uname -a
Linux aft 2.6.16.13-4-smp #1 SMP Wed May 3 04:53:2
Linux

wujun@aft:/tmp> rpm -qa | grep -i gcc
colorgcc-1.3.2-132
gcc-c++-4.1.0-25
libgcc-4.1.0-25
gcc-info-4.1.0-25
gcc-4.1.0-25
gcc-java-4.1.0-25
 
0 Kudos
Message 1 of 4
(5,823 Views)
Interesting, I don't think I've ever seen this issue before.  Could you please try installing the latest version of NI-KAL (currently 1.6) and see if that solves the problem?  If it doesn't solve the problem the output from the KAL install and "dmesg > dmesg.log"  would be useful.

Shawn Bohrer
National Instruments
Use NI products on Linux? Come join the NI Linux Users Community
0 Kudos
Message 2 of 4
(5,806 Views)
Dear Shawn,
    Thanks for your comments very much. This problem has been resolved.
    The dmesg tells "disagrees about version of symbol struct_module" after installing the NI-KAL driver with latest
version or previous one. I searched this message through google, find this problem has something to do with my
kernel source. I run commands "make clean;make modules" under my kernel directory. Then the driver could be
successfully built, although with some flaw "nipalk: module not supported by Novell, setting U taint flag" printed by
driver. Anyway, it does work. Thanks again. If you would like to explain this flaw, I'll appreciate you more:)
 
 
WuJun
0 Kudos
Message 3 of 4
(5,790 Views)
Hey WuJun,

I'm glad you were able to install the driver.  The "nipalk: module not supported by Novell, setting U taint flag" message is normal.  All this message means is that you have installed a kernel module that was not provided by Novell.  This way if your system crashes and you call Novell for support they will see this taint flag and know that the problem may be caused by a third party driver.  This allows them to ask to you reproduce the problem without our drivers installed, or they may simple ask you to contact us for support if they believe the problem might be caused by our drivers.

Shawn Bohrer
National Instruments
Use NI products on Linux? Come join the NI Linux Users Community
0 Kudos
Message 4 of 4
(5,772 Views)