[SOLVED] Configering wacom -> cant 'unclick'

GalacticArachnid · 2010-07-07 17:26:06

So, here I hope this big switch away from hal on arch will actually result in a system the I can use for photo editing!

I want to use my waltop tablet with my arch system. Driver stuff works fine. its detected and i can move the pointer, but i have to list my hand like 20 cm after i press/click to move the pointer again. Thats unusable! Does anyone know a way to fix this thing?

I have tried playing around with the threshold and pressure curve, but cant seem to get this thing to work.

Edit: it all works now, heres a copy of the bottom post resolving the issue (because I forgot to put the info in the OP at the time)

--
Fix:

1) Remove anything wacom related, and performa a clean up-to-date install on an updated system. The new drivers remove a lot of issues.

2) Add a "10-local.rules " file to /etc/udev/rules.d/ This is the step detailed in the wiki that I forgot. Quite necessary though as it allows tablet events to be passed to the driver.

heres mine, but refer to wiki too. First line is for the tablet. Second for usb mice.

KERNEL=="event*", SYSFS{idVendor}=="172f", NAME="input/%k", SYMLINK="input/wacom"
KERNEL=="mouse*", SYSFS{idProduct}=="046e", NAME="input/%k", SYMLINK="input/mouse_udev

3) Configure via "/etc/X11/xorg.conf.d/50-wacom.conf". This may or may not be necessary, again refer to the wiki. But heres mine for example (if its any help at all):

Section "InputClass"
    Identifier "Wacom class"
# WALTOP needs a patched kernel driver, that isn't in mainline lk yet,
# so for now just let it fall through and be picked up by evdev instead.
    MatchProduct "Wacom|WALTOP|WACOM"
#    MatchProduct "Wacom|WACOM"
    MatchDevicePath "/dev/input/event*"
    Driver "wacom"
#    Option        "Device"       "/dev/input/wacom"
    Option        "Type"         "stylus"
    Option        "USB"          "on"                 # USB ONLY
    Option        "Mode"         "Absolute"
    Option        "Vendor"       "WACOM"
    Option        "Threshold"    "5"
EndSection

Section "InputClass"
    Identifier "Wacom serial class"
    MatchProduct "Serial Wacom Tablet"
    Driver "wacom"
EndSection

Section "InputClass"
        Identifier "Wacom serial class identifiers"
        MatchProduct "WACf|FUJ02e5|FUJ02e7"
        Driver "wacom"
EndSection


# N-Trig Duosense Electromagnetic Digitizer
Section "InputClass"
    Identifier "Wacom N-Trig class"
    MatchProduct "HID 1b96:0001|N-Trig Pen"
    MatchDevicePath "/dev/input/event*"
    Driver "wacom"
    Option "Button2" "3"
EndSection

Last edited by GalacticArachnid (2010-09-11 15:07:15)

ralvez · 2010-07-07 17:33:14

Post your configuration file /etc/X11/xorg.conf see if we can help you find what's wrong.
Also in /etc/X11/xorg.conf.d there is a file named "10-evdev.conf" that may have some relevant information.

R.

GalacticArachnid · 2010-07-07 19:30:06

Cheers dude,

heres my xorg.conf.d/50-wacom.conf

Section "InputClass"
    Identifier "Wacom class"
# WALTOP needs a patched kernel driver, that isn't in mainline lk yet,
# so for now just let it fall through and be picked up by evdev instead.
#    MatchProduct    "Wacom|WALTOP|WACOM"
    MatchProduct    "Wacom|WACOM"
    MatchDevicePath "/dev/input/event*"
    Driver          "wacom"
#    Option          "PressCurve"        "10, 0, 100, 100"
    Option          "Threshold"         "5"
EndSection

Section "InputClass"
    Identifier      "Wacom serial class"
    MatchProduct    "Serial Wacom Tablet"
    Driver          "wacom"
    Option          "ForceDevice" "ISDV4"
EndSection

Section "InputClass"
    Identifier      "Wacom serial class identifiers"
    MatchProduct    "WACf|FUJ02e5|FUJ02e7"
    Driver          "wacom"
    Option          "ForceDevice" "ISDV4"
EndSection


# N-Trig Duosense Electromagnetic Digitizer
Section "InputClass"
    Identifier "Wacom N-Trig class"
    MatchProduct "HID 1b96:0001"
    MatchDevicePath "/dev/input/event*"
    Driver "wacom"
EndSection

10-evdev.conf:

# Catchall classes for input devices
# We don't simply match on any device since that also adds accelerometers
# and other devices that we don't really want to use. The list below
# matches everything but joysticks.

Section "InputClass"
        Identifier "evdev pointer catchall"
        MatchIsPointer "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Section "InputClass"
        Identifier "evdev keyboard catchall"
        MatchIsKeyboard "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
    Option "XkbLayout" "gb"
EndSection

Section "InputClass"
        Identifier "evdev touchpad catchall"
        MatchIsTouchpad "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Section "InputClass"
        Identifier "evdev tablet catchall"
        MatchIsTablet "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Section "InputClass"
        Identifier "evdev touchscreen catchall"
        MatchIsTouchscreen "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

I have not modified xorg.conf for wacom purposes -> it works as is and since my tablet is usb I want hotplug support xD

Maybe this is no longer the case with the new architecture, in which case let me know!

GalacticArachnid · 2010-07-09 08:55:01

Bump

ptepid · 2010-07-09 11:17:56

I'm using a Wacom Bamboo and I'm having the same issue. I hadn't used my tablet in a while, in fact I have no entries for it in xorg.conf, or xorg.conf.d. I just plugged it in today after an upgrade and it was auto-detected by Xorg and started working just fine.

... Except for this problem. Seems to me that touching the pen to tablet disables the hover until the pen is "lost". Basically the "hover" functionality works perfectly fine until I actually touch the pen to "click". The pointer updates and works fine for click-and-drag, but it won't hover again until I lift the pen well off the tablet and bring it back down.

I've tested this in xev. After I lift the pen it receives this event:

ButtonRelease event, serial 40, synthetic NO, window 0x3e00001,
    root 0x15b, subw 0x3e00002, time 277314278, (56,53), root:(761,896),
    state 0x100, button 1, same_screen YES

And after that, no more MotionNotify events appear until I move the pen well away and bring it back.

GalacticArachnid · 2010-07-09 20:52:08

ptepid, have you tried playing about with the threshold and pressure curve options? Im going to give them a go again today -> who knows, maybe i did something wrong the last 10 times! xD

ptepid · 2010-07-12 02:11:15

Fixed for me. All I had to do was: pacman -S xf86-input-wacom . I restarted X and it auto-detected the device, and now I can click and hover just fine. I forgot I hadn't downloaded the wacom Xorg driver since switching to 64bit Arch.

Hopefully it's something that simple for you too GalacticArachnid.

GalacticArachnid · 2010-07-15 23:39:12

Well, I just got home and had a chance to play around with this again, unfortunately no luck at all!

I tried re-installing xf86-input-wacom but the problem is still there :'(

Anyone?

ptepid · 2010-07-16 01:56:36

Have you tried commenting out/removing the Wacom specific config information in xorg.conf/xorg.conf.d? See if the autodetect fixes it.

It could also be that it was fixed in a recent update. I'm using:
xf86-input-wacom 0.10.6-2
xf86-input-evdev 2.4.0-1
xorg-server 1.8.1.902-1

Perhaps a pacman -Syu is in order?

Just some ideas.

GalacticArachnid · 2010-07-17 09:34:17

Yeah man, system and all packages are up to date. Ill see if removing xorg.conf/d/50-wacom.conf will help.

Cheers friend

Edit: Nope, no effect. :C

Last edited by GalacticArachnid (2010-07-17 09:36:36)

GalacticArachnid · 2010-07-20 19:07:41

Bump

EdgarButan · 2010-07-23 17:58:09

I'm having the same problem. But I'm using linuxwacom-bamboo-cth-ctl from the AUR as I have got a Bamboo CTH-460, standard xf86-input-wacom doesn't work for this model.
It used to be working with older versions of that driver (but I don't know exactly which ones; I haven't used it for a while).

Buttons on the pen don't seem to work either; buttons on the tablet itself however do.

Last edited by EdgarButan (2010-07-23 18:06:07)

GalacticArachnid · 2010-08-04 15:56:04

Well guys by the looks of it, it may be an upstream problem.

My tablet works completely with Debian 5.0, all the buttons movement etc, so I'm assuming they're either using an older version or a patched package unlike us.

I have tested xf86-input-wacom on a number of different machines to make sure, and the latop has been tested with both Arch (i686, and x64) as well as deb 5.0 (i686).

So, the question is now to work out what package Deb is using and if its patched, how to port it to arch

Last edited by GalacticArachnid (2010-08-04 16:03:32)

Wutzara · 2010-09-09 00:35:44

I actually had the same problem. I'm not sure if that solve everyone's problem but my tablet worked after i added the xorg.conf configuration from the wiki (wacom article). Then restart and the problem was gone. No udev configuration or something. And i installed xf86-input-wacom-git from the AUR (before the xorg.conf configuration)

sctincman · 2010-09-09 12:34:24

Did you check the wiki? Apparently a patch is needed for waltop tablets

http://wiki.archlinux.org/index.php/Wac … om_drivers

Wutzara · 2010-09-09 14:41:05

btw - i have to restart X with plugged tablet to work properly

GalacticArachnid · 2010-09-11 15:04:19

Ahh, sorry people, been away for a while, busy sorting out accomodation for next year of uni xD

Anyway, I have solved this issue. Quite trivial actually and as always, down to my own stupidity! Also some parts of the wiki are quite outdated indeed (like the patch part).

Fix:

1) Remove anything wacom related, and performa a clean up-to-date install on an updated system. The new drivers remove a lot of issues.

2) Add a "10-local.rules " file to /etc/udev/rules.d/ This is the step detailed in the wiki that I forgot. Quite necessary though as it allows tablet events to be passed to the driver.

heres mine, but refer to wiki too. First line is for the tablet. Second for usb mice.

KERNEL=="event*", SYSFS{idVendor}=="172f", NAME="input/%k", SYMLINK="input/wacom"
KERNEL=="mouse*", SYSFS{idProduct}=="046e", NAME="input/%k", SYMLINK="input/mouse_udev

3) Configure via "/etc/X11/xorg.conf.d/50-wacom.conf". This may or may not be necessary, again refer to the wiki. But heres mine for example (if its any help at all):

Section "InputClass"
    Identifier "Wacom class"
# WALTOP needs a patched kernel driver, that isn't in mainline lk yet,
# so for now just let it fall through and be picked up by evdev instead.
    MatchProduct "Wacom|WALTOP|WACOM"
#    MatchProduct "Wacom|WACOM"
    MatchDevicePath "/dev/input/event*"
    Driver "wacom"
#    Option        "Device"       "/dev/input/wacom"
    Option        "Type"         "stylus"
    Option        "USB"          "on"                 # USB ONLY
    Option        "Mode"         "Absolute"
    Option        "Vendor"       "WACOM"
    Option        "Threshold"    "5"
EndSection

Section "InputClass"
    Identifier "Wacom serial class"
    MatchProduct "Serial Wacom Tablet"
    Driver "wacom"
EndSection

Section "InputClass"
        Identifier "Wacom serial class identifiers"
        MatchProduct "WACf|FUJ02e5|FUJ02e7"
        Driver "wacom"
EndSection


# N-Trig Duosense Electromagnetic Digitizer
Section "InputClass"
    Identifier "Wacom N-Trig class"
    MatchProduct "HID 1b96:0001|N-Trig Pen"
    MatchDevicePath "/dev/input/event*"
    Driver "wacom"
    Option "Button2" "3"
EndSection

Arch Linux

#1 2010-07-07 17:26:06

[SOLVED] Configering wacom -> cant 'unclick'

#2 2010-07-07 17:33:14

Re: [SOLVED] Configering wacom -> cant 'unclick'

#3 2010-07-07 19:30:06

Re: [SOLVED] Configering wacom -> cant 'unclick'

#4 2010-07-09 08:55:01

Re: [SOLVED] Configering wacom -> cant 'unclick'

#5 2010-07-09 11:17:56

Re: [SOLVED] Configering wacom -> cant 'unclick'

#6 2010-07-09 20:52:08

Re: [SOLVED] Configering wacom -> cant 'unclick'

#7 2010-07-12 02:11:15

Re: [SOLVED] Configering wacom -> cant 'unclick'

#8 2010-07-15 23:39:12

Re: [SOLVED] Configering wacom -> cant 'unclick'

#9 2010-07-16 01:56:36

Re: [SOLVED] Configering wacom -> cant 'unclick'

#10 2010-07-17 09:34:17

Re: [SOLVED] Configering wacom -> cant 'unclick'

#11 2010-07-20 19:07:41

Re: [SOLVED] Configering wacom -> cant 'unclick'

#12 2010-07-23 17:58:09

Re: [SOLVED] Configering wacom -> cant 'unclick'

#13 2010-08-04 15:56:04

Re: [SOLVED] Configering wacom -> cant 'unclick'

#14 2010-09-09 00:35:44

Re: [SOLVED] Configering wacom -> cant 'unclick'

#15 2010-09-09 12:34:24

Re: [SOLVED] Configering wacom -> cant 'unclick'

#16 2010-09-09 14:41:05

Re: [SOLVED] Configering wacom -> cant 'unclick'

#17 2010-09-11 15:04:19

Re: [SOLVED] Configering wacom -> cant 'unclick'

Board footer