Xorg: Wacom tablet causes conflict with synaptics touchpad

Tzolkin · 10-28-2007, 10:43 AM

Hi,

I'm running Kubuntu 7.10 Gutsy on my Laptop, a Dell Inspiron 1200. For the most part I've gotten everything working, but this has me stumped, and I've searched all over for answers but I cannot find any.

What's going on is this. During normal operation my touchpad works fine, including scroll feature. But recently I've been wanting to connect my wacom graphire4 to it as well. When I do this, and make the needed changes to xorg.conf for this to work, the tablet works fine except for a reversed scroll wheel on the mouse. But the touchpad's scroll area disappears/doesn't work.

I managed to get both to work... somehow, but it only worked once and never again. Since I use the touchpad for pointing and scrolling more than I use the tablet for that, I'd like to have both working. But apparently there's a conflict or something, because it doesn't work. I've reinstated my previous settings and the touchpad worked perfectly, then changed the settings to activate the touchpad again and it stopped working again.

The contents of my xorg.conf file is:

Code:

# xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
EndSection

Section "InputDevice"
	Identifier	"Generic Keyboard"
	Driver		"kbd"
	Option		"CoreKeyboard"
	Option		"XkbRules"	"xorg"
	Option		"XkbModel"	"pc105"
	Option		"XkbLayout"	"us"
EndSection

Section "InputDevice"
	Identifier	"Configured Mouse"
	Driver		"mouse"
	Option		"CorePointer"
	Option		"Device"		"/dev/input/mice"
	Option		"Protocol"		"ImPS/2"
	Option		"ZAxisMapping"		"4 5"
	Option		"Emulate3Buttons"	"true"
EndSection

Section "InputDevice"
	Identifier	"Synaptics Touchpad"
	Driver		"synaptics"
	Option		"SendCoreEvents"	"true"
	Option		"Device"		"/dev/psaux"
	Option		"Protocol"		"auto-dev"
	Option		"HorizEdgeScroll"	"1"
EndSection

Section "InputDevice"
	Driver		"wacom"
	Identifier	"stylus"
	Option		"Device"	"/dev/input/wacom"
	Option		"Type"		"stylus"
#	Option		"ForceDevice"	"ISDV4"		# Tablet PC ONLY
EndSection

Section "InputDevice"
	Driver		"wacom"
	Identifier	"eraser"
	Option		"Device"	"/dev/input/wacom"
	Option		"Type"		"eraser"
#	Option		"ForceDevice"	"ISDV4"		# Tablet PC ONLY
EndSection

Section "InputDevice"
	Driver		"wacom"
	Identifier	"cursor"
	Option		"Device"	"/dev/input/wacom"
	Option		"Type"		"cursor"
#	Option		"ForceDevice"	"ISDV4"		# Tablet PC ONLY
EndSection

Section "Device"
	Identifier	"Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller"
	Driver		"intel"
	BusID		"PCI:0:2:0"
EndSection

Section "Monitor"
	Identifier	"Generic Monitor"
	Option		"DPMS"
EndSection

Section "Screen"
	Identifier	"Default Screen"
	Device		"Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller"
	Monitor		"Generic Monitor"
	DefaultDepth	24
	SubSection "Display"
		Modes		"1024x768"
	EndSubSection
EndSection

Section "ServerLayout"
	Identifier	"Default Layout"
	Screen		"Default Screen"
	InputDevice	"Generic Keyboard"
	InputDevice	"Configured Mouse"

# Uncomment if you have a wacom tablet
	InputDevice     "stylus"	"SendCoreEvents"
	InputDevice     "cursor"	"SendCoreEvents"
	InputDevice     "eraser"	"SendCoreEvents"
	InputDevice	"Synaptics Touchpad"
EndSection

This is driving me nuts. Anyone know how to fix it?

--Tzolkin

Tzolkin · 10-28-2007, 05:46 PM

A little update...

I've thought about it a bit, and I think what is happening is my poor computer is treating both my touchpad and my tablet as the same device.. or same kind of device. *dizzy* When the wacom part of xorg.conf is inactive, (ie at defaults) the tablet works but more like a touchpad. And when the wacom part of xorg is active, the touchpad works but more like a tablet.

Question is, how does one fix -that-? *falls over*

Sincerely,
--Undead Tzolkin XD

Tzolkin · 10-29-2007, 01:07 AM

Additional information. This is from /var/log/Xorg.0.log:

Code:

stylus Wacom X driver grabbed event device
(==) Wacom using pressure threshold of 30 for button 1
(==) Wacom USB Graphire4 tablet speed=9600 maxX=10208 maxY=7424 maxZ=511 resX=2032 resY=2032 suppress=2 tilt=enabled
(==) Wacom device "stylus" top X=0 top Y=0 bottom X=10208 bottom Y=7424
(==) Wacom device "cursor" top X=0 top Y=0 bottom X=10208 bottom Y=7424
(==) Wacom device "eraser" top X=0 top Y=0 bottom X=10208 bottom Y=7424
Synaptics DeviceInit called
SynapticsCtrl called.
(II) Configured Mouse: ps2EnableDataReporting: succeeded
Synaptics DeviceOn called
(--) Synaptics Touchpad auto-dev sets device to /dev/input/event2
(**) Option "Device" "/dev/input/event2"
(WW) Synaptics Touchpad can't grab event device, errno=1022
(--) Synaptics Touchpad touchpad found

...Anyone know how to fix this? It works fine without the tablet...

Tzolkin · 10-29-2007, 07:48 AM

Yet more information. . I've tried manipulating the values in xorg.conf. Though nothing has worked it's given me a better understanding of what might be going on... unless I'm missing something. I hope I am..

Changing the device setting for the wacom tablet to event4 caused neither to work properly.
Changing the device setting for the wacom tablet to event0 cause the touchpad to again not scroll, and the tablet to not work well.
In both these cases both grabbed an event without error.

With the wacom driver active, Touchpad seems to like event2 as opposed to running as event3 when the wacom driver is not loaded.

Commenting out the line for 'cursor' at the end of xorg.conf caused no change from the usual lack of proper operation.

I'm thinking this is a driver problem. The Synaptics driver and Wacom driver simply don't play nice together, since it doesn't seem to help if both successfully grab an event or not. Please let me know if I'm missing something.

--Tzolkin