plustek: unresolved symbols
Subject:
Re: unresolved symbols
From:
####@####.#### (G. Jaeger)
Date:
15 Oct 2000 10:33:21 -0000
Message-Id: <13kl8i-0d27QuC@fwd04.sul.t-online.com>
On Sat, 07 Oct 2000 02:27:06 +0200, Jorge Nerin wrote:
>Hello I have a Colorado Direct 9600, wich BTW I don't know if it's
>supported by plustek module, bu t my problem is that:
>
>after downloading and compiling sane-1.0.3 and
>plustek-sane-0_36_35.tar.gz, when I try to insmod the module pt_drv in
>my system I get this:
>
>modprobe pt_drv
>/lib/modules/2.4.0-test9/misc/pt_drv.o: unresolved symbol get_user_ret
>/lib/modules/2.4.0-test9/misc/pt_drv.o: unresolved symbol put_user_ret
>/lib/modules/2.4.0-test9/misc/pt_drv.o: insmod
>/lib/modules/2.4.0-test9/misc/pt_drv.o failed
>/lib/modules/misc/pt_drv.o: unresolved symbol get_user_ret
>/lib/modules/misc/pt_drv.o: unresolved symbol put_user_ret
>/lib/modules/misc/pt_drv.o: insmod /lib/modules/misc/pt_drv.o failed
>/lib/modules/misc/pt_drv.o: insmod pt_drv failed
>
>My kernel is 2.4.0-test9 (SMP compiled and uncomented in the Makefile),
>but either way I can't insmod the driver.
>
>--
>Jorge Nerin
####@####.####
>
Hi Jorge,
I have tested at least with 2.4.0-test7 and there it works.
I decided to stop testing for Kernel 2.4 until there is an "official"
version available, because each new test-release has some
changes, that affect the driver. I always thought, that the test
Kernels
a prereleases of the upcomming new version to fix the last bugs, but
even during
the test phase they accept large patches and change system-structures
so it's necessary to patch a kernel-mode driver each time a
test-version
has been released.
I hope you understand my point of view. As far as there's a stable
version 2.4
available, there will be a plustek-driver.
Gerhard
----------------------------------------
####@####.####
----------------------------------------
