Hello all, trying to run updateNIDrivers on fedora 26. Having trouble building nikal for kernel 4.11.11-300. First error is initialization from incompatible pointer type ......
Thanks so much!
Forget about it. The kernel blob (piece of binary code loaded into the kernel) won't fit.
It's a Russian roulette game. Nobody knows what kind of damage it could do.
Unfortunately, NI still keeps the specs as secret as nuclear launch codes, so we can't develop proper drivers (w/o expensive reverse engineering). So, there won't
be actually usable drivers anytime soon.
Perhaps just sell off the stuff at ebay and get some decent HW instead.
I'm work with Centos 7 and Labview 15 and 16 and ni-visa 15 - 16 and '17 without any single fail.
I have a good experience with labview and Linux ( much, much better than windows).
Including many applications with python and labview with very nice success.
Please don't give up. I Can help you....
Last I remember, I worked with Kernel 4.4.x and Was able to compile NIKAL with just one error (GPL License Error || On ubuntu 14.04 64-bit). Following are few options but not the last:
1. Try to get the latest package of Nikal if provided by NI.
2. Try to debug Nikal's code to make it compatible with your kernel (90% it will work).
3. Worst : Switch to another distribution like Ubuntu or CentOS
Using most current version of NIKAL
I am not tied at all to fedora, i have been running mint, and had visa working fine with it. Was having trouble getting the NI-RIO to install though so thought fedora might be easier.
I can try out centos as well.
Thanks for the replies everyone. Attached is a screenshot.
This code was written for an pretty old kernel. Lots of internal functions and data structures have changed over the years. One of the reasons why OOT-modules are *NOT* suited for production - it's just a convenience helper for *experienced* kernel hackers.
Looking at their code (eg. nikal.c), we're dealing w/ rookies here. (oh, also look at their configure scripts - that's really weird and clearly reveals their helplessness).
Sorry, but this is far, far from professional. Do *NOT* use that in production.