NI-KAL in SuSE Linux 11.4

[Gòl·lum]

Here it goes.

In nipal.txt I dumped the output of grep nipal /var/log/messages. I see that there are some lines claiming that more than 4 GB of memory have been detected. Well I just happen to have 4 GB installed, so I don't know about the extra memory...

[JoeFriedchicken]

See my response in the other libnipalu.so thread 😉

Installtion and libnipalu.so problems

https://decibel.ni.com/content/message/26189#26189

Your report shows this for /proc/iomem:

100000000-11fffffff : System RAM

which is above 4 GB.

[Gòl·lum]

Well, thanks. That solved the issue with libnipalu.so. Now I can start gpibexplorer. Now the problem is that the USB interface does not appear in the list. According to the manual, there is not much to do for USB, just plug the thing and all is done. That is what I get in /var/log/messages upon connection of the usb adapter:

Aug 25 16:12:22 pc6113 kernel: [  626.360040] usb 1-1: new high speed USB device using ehci_hcd and address 3

Aug 25 16:12:22 pc6113 kernel: [  626.475777] usb 1-1: New USB device found, idVendor=3923, idProduct=709b

Aug 25 16:12:22 pc6113 kernel: [  626.475782] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

Aug 25 16:12:22 pc6113 kernel: [  626.475786] usb 1-1: Product: GPIB-USB-HS

Aug 25 16:12:22 pc6113 kernel: [  626.475789] usb 1-1: Manufacturer: National Instruments

Aug 25 16:12:22 pc6113 kernel: [  626.475791] usb 1-1: SerialNumber: 0147A1BF

Aug 25 16:12:22 pc6113 mtp-probe: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-1"

Aug 25 16:12:22 pc6113 mtp-probe: bus: 1, device: 3 was not an MTP device

Any idea?

Thanks.

[Steven_T]

I believe that Linux kernels 2.6.25 and later do not load USB kernel drivers that are not GPL-ed.  Since this version is a couple years old, it is almost certain that your current kernel is one of the affected kernels.  NI PCI/PCIe and ENET GPIB products should work.  Do you have any of these on hand?

[Gòl·lum]

Unfortunately not. However, there must be some way of forcing the kernel to load whatever driver i tell him to load right? I mean, the kernel is working for me, not the other way arround. It would be like not letting me load the propietary nvidia drivers because they are not gpl.

[irwan]

It's a bit different. The USB symbols in the kernel are marked GPLONLY

http://www.kernel.org/pub/linux/docs/lkml/#s1-19

[Gòl·lum]

(Facepalm)

[DiBosco]

I think I'm getting similar problems with Mandriva 2011 (I got this working in on 2010.0, but support has just run out for it).  I have use the kical.c file posted above and got it all compiled and installed. However, I get the good old

"libnipalu.so failed to initialize Perhaps you need to run updateNIDrivers" error when I try to run visaconf.

When I run updateNIDrivers I also get lots of errors such as:

~include/generated

/usr/local/natinst/nikal/src/client/nipalk-interface.c:20:31: fatal error: linux/autoconf.h: No such file or directory

I am guessing I need to run this "make cloneconfig && make modules_prepare" but I can't work out where to run it from or exactly where ~include/generated and ~include/linux directories are. To me ~ means my home directory, but there are no such directories in mine.

My kernel, FWIW, is 2.6.38.7.

Thanks.

[irwan]

I don't know what the deal is with ~include stuff, that's weird, I haven't seen that before.

However, it looks like you might not have kernel header or kernel source installed maybe ? I don't know what package you need to install on Mandriva for that. Every distribution is different.

[DiBosco]

I've definitely got headers and kernel source installed, the  ./INSTALL works fine other than nikcal - which is fixed with the patch on page one of this thread. It's when libnipalu.so fails to initialise and I try to run updateNIDrivers that I get these errors.

On page one there are instructions for this error (it seems to me) but I don't understand where and how to run the make cloneconfig. The error is in the linux/autoconf.h: No such file or directory bit. I suspect if I knew where to run make cloneconfig and what ~ means in this case I woud stand a better chance of solving it.