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

Re: Problem: wacom - Partial Sol'n



On Wed, 25 Oct 2006 15:31 -0400, Thomas H. George wrote:
> I forgot that I had encountered a problem when I first attached the
> wacom pad which I ultimately solved by editing the xorg.conf file to add
> the following sections:
> 
> Section "InputDevice"
> 	Identifier	"stylus"
> 	Driver		"wacom"
> 	Option		"Device"		"/dev/input/wacom"
> 	Option		"type"			"stylus"
> 	Option		"USB"			"on"
> EndSection
> 
> Section "InputDevice"
> 	Identifier	"eraser"
> 	Driver		"wacom"
> 	Option		"Device"		"/dev/input/wacom"
> 	Option		"type"			"eraser"
> 	Option		"USB"			"on"
> EndSection
> 
> Section "InputDevice"
> 	Identifier	"cursor"
> 	Driver		"wacom"
> 	Option		"Device"		"/dev/input/wacom"
> 	Option		"type"			"cursor"
> 	Option		"USB"			"on"
> EndSection
> 
> Section "InputDevice"
> 	Identifier	"pad"
> 	Driver		"wacom"
> 	Option		"Device"		"/dev/input/event0"
> 	Option		"type"			"pad"
> 	Option		"USB"			"on"
> EndSection
> 
> and added the following lines in the Section "Server Layout":
> 
> 	InputDevice	"stylus"	"SendCoreEvents"
> 	InputDevice	"eraser"	"SendCoreEvents"
> 	InputDevice	"cursor"	"SendCoreEvents"
> 	InputDevice	"pad"
> 
> With these changes the pad is working again but with a time delay when
> moving the cursor.  The module evdev is loaded but there must be some
> other configuration which I have overlooked.  Still searching.

hmmm, I don't see a time delay with the cursor... my set up is pretty
much like yours except I have 
Option          "Device"                "/dev/input/wacom"

for "pad" and I'm using the debian packaged kernel 2.6.16-2-k7.

In my case, xorg was not loading 
/usr/lib/xorg/modules/input/wacom_drv.so 

...it complained about a version mismatch or something.  I got
linuxwacom-0.7.6-1.tar.bz2 from http://linuxwacom.sourceforge.net ,
compiled it and replaced /usr/lib/xorg/modules/input/wacom_drv.so (I
know it's probably not the "right" way to do fix that) and then it works
except for the mouse problem you've described in your other email.

Mike




Reply to: