Re: Problem with kernel-module version mismatch

From: Richard B. Johnson (
Date: Tue Feb 13 2001 - 09:15:06 EST

On Tue, 13 Feb 2001, Marcus Ramos wrote:

> Hello,
> After compiling files "ttime.c" and "ttime.h", I try to load them into
> the kernel using the command /sbin/insmod ttime.o. However, the
> following message suggests that a version conflict has prevented the
> loading to be performed correctly:
> "kernel-module version mismatch. ttime.o was compiled for kernel
> 2.4.0-0.26 while this kernel is version 2.2.16-22".
> My question is: since the source has been compiled on the same kernel as
> it is going to be loaded into, how come this message ? What do I have to
> do in order to avoid such problem ? Change the source code ? Where did
> it learn about 2.4.0-0.26 if I am using 2.2.16-22 (Red Hat 7.0) ?
> Thanks in advance,
> Marcus.

`uname -r` shows the currently executing kernel version. The version
of the kernel you compiled is in the top of the Makefile (first 3 lines).

To see if you are lucky, you can "force" the module loading with
`insmod -f ttime.o`.

FYI, it looks like you thought you installed a new kernel after you
compiled it, but didn't.

Dick Johnson

Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).

"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

This archive was generated by hypermail 2b29 : Thu Feb 15 2001 - 21:00:21 EST