Re: Module problems!
On Mon, Jul 05, 1999 at 09:06:23AM +0530, Ramakrishnan M wrote:
> I had been reading the Linux Device Drivers,and tried running the
> first program.
> #define KERNEL
> #include ...
> when I do insmod prog.o it says the program has been compiled to run on
> kernel 2.2.5 and the running kernel is 2.2.10. Sure! I have 2.2.10 kernel
> running but I am not able to understand the 2.2.5 business. Itried
> installing an older kernel and recompiled it,with no useful result.Please
> Ramakrishnan M
> World Wide Web: http://www.ee.iitm.ernet.in/~ee98m09
> "A designer knows he has achieved perfection not when there is nothing
> left to add, but when there is nothing left to take away."
> Unsubscribe? mail -s unsubscribe firstname.lastname@example.org < /dev/null
/usr/include/linux is usually a symbollic link to /usr/src/linux/include/linux
But, in Debian, for reasons I've forgotten, /usr/include/linux is a copy of
the headers for whatever kernel the package maintainer had installed at the
time. I think the line of reasoning is that very few programs really care
about the version of the kernel headers.
Unfortunately, you've got module versioning as an option in the kernel, so
it is going to check the version.h the module was compiled against with
the one in the kernel. I'd suggest recompiling your module with
"-I/usr/src/linux/include/linux", provided you have the kernel source
webmaster - http://www.mschess.org