On 3/27/06, Dave M G <[EMAIL PROTECTED]> wrote:
> Andy,
>
> I think I have narrowed down the problem somewhat. First, as you
> suggested, I think that my Wacom tablet is on event1, not event0. So I
> have updated my xorg.conf file to reflect this.
>
> Second, my guess is that the reason I'm having trouble getting
> control of my Wacom device is because Ubuntu keeps trying to find a
> mouse device, and it keeps interpreting the Wacom signals as mouse
> signals. Sorry for my untechnical description.
>
> I thought I read on the Linuxwacom web site that one could edit
> xorg.conf so that the mouse used "mouse1" as it's driver. So I tried
> this, and X crashed.
>
> The error output revealed something in it's output log, which is
> that it could not find any driver named "wacom". I am puzzled by this,
> as I not only have followed every instruction given, but also because in
> the Ubuntu boot screen, it says "doing wacom setop... ok". So there must
> be some kind of wacom driver roaming around.
>
> My theory is that when I moved the mouse driver from "mice" to
> "mouse1", then X looked to the wacom device, couldn't find a driver,
> then crashed. Would that be correct?
>
> Because I have been up and down the configurations by this point,
> I'm a little lost as to the status of my wacom driver configuration.
>
> Can anyone help me to know what I might do to determine what my
> current status is, and what I need to do to go from this point?
>
> I have included some information about my system below. If it does
> not paint enough of a picture, please let me know what information is
> needed.
>
> [EMAIL PROTECTED]:~$ more /etc/udev/rules.d/10-wacom.rules
> # udev rule for wacom tablets.
>
> KERNEL="event*", SYSFS{idVendor}="056a", NAME="input/%k",
> SYMLINK="input/wacom%e"
>
> [EMAIL PROTECTED]:~$ more /proc/bus/usb/devices
> /proc/bus/usb/devices: No such file or directory
> [EMAIL PROTECTED]:~$ xsetwacom list
> [EMAIL PROTECTED]:~$ grep -i wacom /var/log/messages | tail
> Mar 27 11:46:03 localhost kernel: [4294683.840000] input: Wacom
> Graphire3 as /class/input/input1
> Mar 27 11:46:03 localhost kernel: [4294683.847000] usbcore: registered
> new driver wacom
> Mar 27 11:46:03 localhost kernel: [4294683.847000]
> drivers/usb/input/wacom.c: v1.44:USB Wacom Graphire and Wacom Intuos
> tablet driver
> Mar 27 11:52:13 localhost kernel: [4295060.197000] usbcore:
> deregistering driver wacom
> Mar 27 11:53:23 localhost kernel: [4295130.367000] input: Wacom
> Graphire3 as /class/input/input2
> Mar 27 11:53:23 localhost kernel: [4295130.375000] usbcore: registered
> new driver wacom
> Mar 27 11:53:23 localhost kernel: [4295130.375000]
> drivers/usb/input/wacom.c: v1.44:USB Wacom Graphire and Wacom Intuos
> tablet driver
> Mar 27 11:57:01 localhost kernel: [4294686.362000] input: Wacom
> Graphire3 as /class/input/input1
> Mar 27 11:57:01 localhost kernel: [4294686.370000] usbcore: registered
> new driver wacom
> Mar 27 11:57:01 localhost kernel: [4294686.370000]
> drivers/usb/input/wacom.c: v1.44:USB Wacom Graphire and Wacom Intuos
> tablet driver
Did you unplug it and plug it back in again? There's a couple minutes
delay there, and when it is replugged it came back as event2. Once you
unplug it, X won't find it any more, since it comes back on a
different device.
> [EMAIL PROTECTED]:~$ more /proc/bus/input/devices
> I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
> N: Name="AT Translated Set 2 keyboard"
> P: Phys=isa0060/serio0/input0
> S: Sysfs=/class/input/input0
> H: Handlers=kbd event0
> B: EV=120013
> B: KEY=4 2000000 3802078 f840d001 f2ffffdf ffefffff ffffffff fffffffe
> B: MSC=10
> B: LED=7
>
> I: Bus=0003 Vendor=056a Product=0013 Version=0314
> N: Name="Wacom Graphire3"
> P: Phys=
> S: Sysfs=/class/input/input1
> H: Handlers=mouse0 event1 ts0
> B: EV=f
> B: KEY=1c43 0 70000 0 0 0 0 0 0 0 0
> B: REL=100
> B: ABS=3000003
The mouse0 handler is not a good sign. Check /proc/bus/usb/devices as
well; this will say what driver is in use.
> [EMAIL PROTECTED]:~$ xsetwacom set Stylus mode relative
> Error (2): WacomConfigOpenDevice: No such device
> Set: Failed to open device 'Stylus'
>
> [EMAIL PROTECTED]:more /etc/X11.xorg.conf
> Section "Module"
> Load "i2c"
> Load "bitmap"
> Load "ddc"
> Load "dri"
> Load "extmod"
> Load "freetype"
> Load "glx"
> Load "int10"
> Load "type1"
> Load "vbe"
> EndSection
I think you may need Load "wacom" in there as well.
> Section "InputDevice"
> Driver "wacom"
> Identifier "stylus"
> Option "Device" "/dev/input/event1" # USB ONLY
> Option "Type" "stylus"
> Option "USB" "on" # USB ONLY
> EndSection
>
> Section "InputDevice"
> Driver "wacom"
> Identifier "eraser"
> Option "Device" "/dev/input/event1" # USB ONLY
> Option "Type" "eraser"
> Option "USB" "on" # USB ONLY
> EndSection
>
> Section "InputDevice"
> Driver "wacom"
> Identifier "cursor"
> Option "Device" "/dev/input/event1" # USB ONLY
> Option "Type" "cursor"
> Option "USB" "on" # USB ONLY
> EndSection
...
> Section "ServerLayout"
> Identifier "Default Layout"
> Screen "Default Screen"
> InputDevice "Generic Keyboard"
> InputDevice "Configured Mouse"
> InputDevice "stylus" "SendCoreEvents"
> InputDevice "eraser" "SendCoreEvents"
> InputDevice "cursor" "SendCoreEvents"
> EndSection
If you change all occurences of /dev/input/event1 to /dev/input/wacom,
you might have more success. But make sure /dev/input/wacom actually
exists. udev should create it for you.
--
The Pythonic Principle: Python works the way it does
because if it didn't, it wouldn't be Python.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Linuxwacom-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
