Re: make error, unresolved symbols, berlios driver

Hi,

On Wed, 19 Nov 2003, Robin Edman wrote:

> Ok, 'uname -r' always points to my current kernel.
> I've tested with 2.4.19, 2.4.20 and 2.4.21. modprobe
> gives me a message that my kernel version doesn't match the version the
> driver was compiled for, and depmod complains about unresolved symbols
> in the module files. When I tried 2.4.19 _all_ my drivers had unresolved
> symbols, when I tried the later versions only the Berlios driver's files
> had unresolved symbols.

I didn't ask about the result of 'uname -r', but the location
the link /lib/modules/`uname -r`/build points to:

> > Please check where the symbolic link
> > /lib/modules/`uname -r`/build
> > points to. The Makefile assumes this to be
> > the root of the kernel sources to build for.

Or to put it another way:

egrep "UTS_RELEASE" \
 /lib/modules/`uname -r`/build/include/linux/version.h

must return the version string of the kernel you want to compile the
Berlios driver for. Please check this.

Did you still get the "kernel version mismatch" error from modprobe?

Furthermore the kernel sources there must be correctly configured to match
the running kernel in order to get the right _R suffices for symbols (IMHO
a correct .config file in the rootdir and a call to "make oldconfig"
should be enough).

/Jörg