From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

Linux Users

cancel
Showing results for 
Search instead for 
Did you mean: 

can't run updateNIDrivers 2.6.27.21-170.2.56.fc10.x86_64

Hi,

I'm having trouble running updateNIDrivers with the latest Fedora 10 kernel. updateNIDrivers falls back to the previous kernel, without explaining why. Here's the output:

[root@pekkala NIKAL-1.9]# uname -a
Linux pekkala 2.6.27.21-170.2.56.fc10.x86_64 #1 SMP Mon Mar 23 23:08:10 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux


[root@pekkala NIKAL-1.9]# updateNIDrivers 2.6.27.21-170.2.56.fc10.x86_64
******************************** ERROR ****************************************
* The version of gcc in the path does not match the version of gcc used to    *
* compile the currently running kernel.  This can cause unpredictable         *
* behavior in kernel drivers and should be fixed.                             *
* gcc version: 4.4.0                                                          *
* kernel compiled with: 4.3.2                                                 *
******************************** ERROR ****************************************
Removing NI-KAL (nikal): done
/bin/rm -rf objects
Updating NI-KAL:
NI-KAL successfully updated.
warning: configured for kernel version 2.6.27.19-170.2.35.fc10.x86_64
warning: which is not the currently running kernel
Updating client modules:
/usr/local/natinst/nikal/src
nipalk.ko successfully updated.
/usr/local/natinst/nikal/src
ni488k.ko successfully updated.
/usr/local/natinst/nikal/src
ni488lock.ko successfully updated.
/usr/local/natinst/nikal/src
NiViPxiK.ko successfully updated.
/usr/local/natinst/nikal/src
NiViPciK.ko successfully updated.
National Instruments kernel drivers have been successfully installed.
You can now use your NI products when you boot into kernel 2.6.27.21-170.2.56.fc10.x86_64.

(Running against the earlier kernel generates the same gcc warning, but it works.)

Running LabView causes a crash, of course:

[mjclab@pekkala ~]$ labview /fileserver/mjcfiles/op1b/labview/AVTTCAL.llb
libnipalu.so failed to initialize
Perhaps you need to run updateNIDrivers
Aborted


It isn't a "MODVERSION" issue:

[root@pekkala ~]# grep MODVERSIONS /boot/config-2.6.27.*
/boot/config-2.6.27.15-170.2.24.fc10.x86_64:# CONFIG_MODVERSIONS is not set
/boot/config-2.6.27.19-170.2.35.fc10.x86_64:# CONFIG_MODVERSIONS is not set
/boot/config-2.6.27.21-170.2.56.fc10.x86_64:# CONFIG_MODVERSIONS is not set

Any suggestions?

- Mike

0 Kudos
Message 1 of 3
(5,587 Views)

The /boot/config* files are exactly the same, actually, except for version info.

0 Kudos
Message 2 of 3
(3,252 Views)

Hi Mike,

I'd need to take a closer look at the updateNIDrivers script to figure out why it says it is configured for your older kernel.  It may simply be because NI-KAL is erroring out with your current kernel, so it falls back to the old one.  I'm guessing you really just want it to work with your current kernel.

avtechmjc wrote:


******************************** ERROR ****************************************
* The version of gcc in the path does not match the version of gcc used to    *
* compile the currently running kernel.  This can cause unpredictable         *
* behavior in kernel drivers and should be fixed.                             *
* gcc version: 4.4.0                                                          *
* kernel compiled with: 4.3.2                                                 *
******************************** ERROR ****************************************

Actually this error means exactly what it says.  The version of your C compiler, gcc 4.4.0, is different from the version of the C compiler used to build the latest kernel, gcc 4.3.2.  Since NI-KAL is a small C kernel module, it should be compiled with the same version of gcc as your kernel.  The only way I know to fix this is upgrade/downgrade your kernel or gcc versions until they match.  So if you are running the latest Fedora 10 kernel, then you may need to downgrade gcc to version 4.3.2.  You can always file a bug report to Fedora since these versions should always match or you can't build external kernel modules.

Shawn Bohrer

National Instruments

Use NI products on Linux? Come join the NI Linux Users Community
0 Kudos
Message 3 of 3
(3,252 Views)