FW: Driver Modules under linux-2.4.31 - unresolved sysmbols - sol ved

[PHILLIPS John M]

I was not paying enough attention to the default values when doing the
inital "make menueconfig" for each kernel.  For some reason in the 2.6
kernel CONFIG_MODVERSIONS defaulted to not set, but in the 2.4.31 kernel it
defaulted to "y".  Once I unset the CONFIG_MODVERSIONS, the modules loaded
correctly.

-----Original Message-----
From: uclibc-bounces at uclibc.org
To: 'uclibc at uclibc.org'
Sent: 9/15/05 9:32 AM
Subject: Driver Modules under linux-2.4.31 - unresolved sysmbols

Short form of the question:
What is required to make a load-able driver module under the later
versions
of linux 2.4.xx?

Long form of the question:
I have already build and run a linux-2.6 version of our drivers and
application. But a bug has appeared in our existing system and I need to
re-build a linux-2.4 version.  The makefiles used under linux-2.4.4 that
made simple loadable object modules no long seem to work under 2.4.31.
When
attempting "insmod <modulename>", I get unresolved symbols
__generic_copy_from_user, __release_region, reguster_chrdev, and more.
_______________________________________________
uClibc mailing list
uClibc at uclibc.org
http://busybox.net/cgi-bin/mailman/listinfo/uclibc