Further developments. Following some older advice I remembered, I downloaded the latest versions of NI-KAL and NI-VISA (1.7xxx and 4.3, respectively).
Now I have (NI-KAL) :
Installing NI-KAL version 1.7.0f0...
Pre Installation ..
Preparing... ########################################### [100%]
1:nikali ########################################### [100%]
Post Installation .
Warning: nikali post installation failed! /tmp/nikaliPostInstall.log follows:
Configuring for linux kernel version 2.6.25.9.
********************************* NOTE *********************************
Using kernel headers found in /lib/modules/2.6.25.9/source.
If this does not correspond to the location of the 2.6.25.9 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
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 kthread: 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
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.25.9/source SUBDIRS=/usr/local/natinst/nikal/src/objects modules
make[1]: Entering directory `/usr/src/rpm/BUILD/kernel-2.6.25.9'
WARNING: Symbol version dump /usr/src/rpm/BUILD/kernel-2.6.25.9/Module.symvers
is missing; modules will have no dependencies and modversions.
CC [M] /usr/local/natinst/nikal/src/objects/nikal.o
/usr/local/natinst/nikal/src/objects/nikal.c: In function ‘nNIKAL100_registerPCIDriver’:
/usr/local/natinst/nikal/src/objects/nikal.c:2802: error: ‘nLinux_pciDriver’ has no member named ‘enable_wake’
/usr/local/natinst/nikal/src/objects/nikal.c: In function ‘nNIKAL100_reserveInterrupt’:
/usr/local/natinst/nikal/src/objects/nikal.c:4114: error: ‘SA_INTERRUPT’ undeclared (first use in this function)
/usr/local/natinst/nikal/src/objects/nikal.c:4114: error: (Each undeclared identifier is reported only once
/usr/local/natinst/nikal/src/objects/nikal.c:4114: error: for each function it appears in.)
/usr/local/natinst/nikal/src/objects/nikal.c:4114: error: ‘SA_SHIRQ’ undeclared (first use in this function)
make[2]: *** [/usr/local/natinst/nikal/src/objects/nikal.o] Error 1
make[1]: *** [_module_/usr/local/natinst/nikal/src/objects] Error 2
make[1]: Leaving directory `/usr/src/rpm/BUILD/kernel-2.6.25.9'
make: *** [objects/nikal.ko] Error 2
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.
.
FOR PATENTS COVERING NATIONAL INSTRUMENTS PRODUCTS, REFER TO
THE PATENTS.txt FILE ON /media/iso AND/OR
www.ni.com/patents
NI-KAL Installation completed with errors.
I found something that appeared to be germane to this issue here :
http://forums.ni.com/ni/board/message?board.id=250&message.id=38929&query.id=10831#M38929
"
ne more update: so i noticed that some of the
errors i was getting, (SA_INTERRUPT not defined, SA_SHIRQ not defined)
were reported by people having problems with SATA drivers, and that the
recommended fix there was to recompile the kernel with the SATA drivers
compiled in, instead of as modules, so i did this, and now lsdaq
doesn't crash... it still doesn't find my boards though!"
Now, I am not using a DAQ (in fact, no hardware is currently installed on this machine - a PCIe GPIB card is about to be ordered). Does this apply in my case ? I do have SATA drives, and its quite possible that these are supported using modules.
Message Edited by m-s on
07-02-2008 06:32 PM
