[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Wacom graphics tablet: make error for wacom.o




On Sat, Jan 11, 2003 at 03:33:38PM +0800, Arne Goetje wrote......

> > I'm trying to install a Wacom Intuous2 Graphics Tablet USB on my Debian
> > 2.4.20 and am getting stuck during the make process for the wacom.o
> > driver.
> 
> > /usr/src/kernel-source-2.4.20-2.4.20/include/linux/devfs_fs_kernel.h: In
> > function `devfs_unregister_blkdev':
> > /usr/src/kernel-source-2.4.20-2.4.20/include/linux/devfs_fs_kernel.h:260:
> > warning: implicit declaration of function `unregister_blkdev'
> > {standard input}: Assembler messages:
> > {standard input}:2011: Error: symbol `read_lock' is already defined
> > make[2]: *** [wacom.o] Error 1
> > make[2]: Leaving directory `/home/kosuke/downloads/linuxwacom-0.2.1/src'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/home/kosuke/downloads/linuxwacom-0.2.1'
> > make: *** [all] Error 2
> 
> Did you try just to use the wacom.o module in the debian kernel-source 
> package? I run 2.4.19 and it works fine. I just enabled wacom in the USB 
> section and compiled the kernel. You seem to use a seperate module, right?
 
I was under the impression that one needed to use a more updated driver
- namely one from the site that I've been using to guide me through this
process ...

http://linuxwacom.sourceforge.net

It seems that you're saying that the stock module wacom.o that's a part
of 2.4.19 (and 2.4.20) will work right out of the box so to speak.

If so, then great, but then I wonder why I'm stuck with my tablet not
working (not the tablet, it works fine on that other OS) on my Debian
box.

Quick question:  To make this work, must one compile one's own kernel
with the wacom.o module?  I've not done that yet, but have instead used
modprobe wacom to add in the module on my very stock kernel.

Thanks
Kevin

-- 
Kevin Coyner
mailto: kevin@rustybear.com
GnuPG key: 1024D/8CE11941

Attachment: pgpQwohelMp0j.pgp
Description: PGP signature


Reply to: