bart at nexus.carleton.ca
Fri Jan 12 07:29:00 EST 2001
That's pretty much it. Make sure that your module - when compiled - uses
the proper kernel include tree (ie: /usr/src/linux-2.4.00-test8/include).
More specifically /usr/src/linux*/include/linux/version.h contains the
version info of that kernel.
It is recomened that CONFIG_MODVERSIONS is set in the kernel .config file
if you have modules compiled that come from outside of the kernel
tree. This option makes kernel modules less dependant on the version of
the kernel. You can read more about this in Documentation/Configure.help
under CONFIG_MODVERSIONS and Documentation/modules.txt.
Even if you use CONFIG_MODVERSIONS, I would be surprised that you would
not need to recompile your module between 2.2.x and 2.4.x. A lot of
functions became macros and visa versa. That makes function lookups for
some things imposible.
On Fri, 12 Jan 2001, Vic Gedris wrote:
> On Fri, 12 Jan 2001 Tom_Linux at sohu.com wrote:
> > Hi,
> > I have written an usb driver under RedHat 6.2 & kernel-2.4.0-test8.
> > Now I update to RedHat7.0, but the driver can not be insmoded(under
> > test8, 11). The insmod reports kernel version mismatch. Can you tell
> > me why, and what can I do? Thank you!
> Did you re-compile the module after upgrading to the new kernel?
> Alternately, you can tell your kernel not to check module version
> numbers (I don't remember the exact option, but it's there!).
More information about the OCLUG