Re: [Linuxwacom-discuss] aiptek on wacom

[Peter H. <pet...@wh...>]

please don't remove the list from the CC, re-adding.

On 28/07/10 17:22 , steve wrote:
> On Wednesday 28 July 2010 01:42:06 you wrote:
>> On Tue, Jul 27, 2010 at 11:09:29AM +0200, steve wrote:
>>> Hi
>>>
>>> I'd like to try the wacom driver with my aiptek 12000U
>>>
>>> Here is my  /etc/X11/xorg.conf.d/20-wacom.conf
>>>
>>>> Section "InputClass"
>>>>
>>>>        Identifier "Wacom Tablet"
>>>>        MatchVendor     "Wacom|WALTOP|WACOM|Aiptek|aiptek"
>>>>        Driver  "wacom"
>>>>
>>>> EndSection
>>>
>>> It works but as soon as the pen touches the pad, you have to keep the pen
>>> in contact with it to make the cursor move.
>>
>> does the aiptek do proximity?
>>
>>> Looking at it with GIMP it always choose the aiptek driver.
>>
>> the Xorg.log shows what driver is being used, GIMP has no say in the driver
>> selection. With the configuration above it should pick the wacom driver but
>> the only way to make sure is if you provide your Xorg.log.
>>
>> Cheers,
>>    Peter
>
> Hi
>
> THanks fr the reply.
> Here is the log. Any clues?
>
>    359.873] (II) config/udev: Adding input device Aiptek (/dev/input/mouse1)
> [   359.873] (**) Aiptek: Applying InputClass "LocalKeyboard"
> [   359.873] (EE) No input driver/identifier specified (ignoring)
> [   359.879] (II) config/udev: Adding input device Aiptek (/dev/input/event5)
> [   359.879] (**) Aiptek: Applying InputClass "evdev pointer catchall"
> [   359.879] (**) Aiptek: Applying InputClass "evdev keyboard catchall"
> [   359.879] (**) Aiptek: Applying InputClass "evdev tablet catchall"
> [   359.879] (**) Aiptek: Applying InputClass "LocalKeyboard"
> [   359.879] (**) Aiptek: always reports core events
> [   359.879] (**) Aiptek: Device: "/dev/input/event5"
> [   359.879] (II) Aiptek: Found 3 mouse buttons
> [   359.879] (II) Aiptek: Found scroll wheel(s)
> [   359.879] (II) Aiptek: Found relative axes
> [   359.879] (II) Aiptek: Found x and y relative axes
> [   359.879] (II) Aiptek: Found absolute axes
> [   359.879] (II) Aiptek: Found x and y absolute axes
> [   359.879] (II) Aiptek: Found absolute tablet.
> [   359.879] (II) Aiptek: Found keys
> [   359.880] (II) Aiptek: Configuring as tablet
> [   359.880] (II) Aiptek: Configuring as keyboard
> [   359.880] (**) Aiptek: YAxisMapping: buttons 4 and 5
> [   359.880] (**) Aiptek: EmulateWheelButton: 4, EmulateWheelInertia: 10,
> EmulateWheelTimeout: 200

this is the evdev driver hooking onto your device. try MatchProduct 
instead of MatchVendor in your config snippet.

Cheers,
   Peter


> [   359.880] (II) XINPUT: Adding extended input device "Aiptek" (type:
> KEYBOARD)
> [   359.880] (**) Option "xkb_rules" "evdev"
> [   359.880] (**) Option "xkb_model" "evdev"
> [   359.880] (**) Option "xkb_layout" "es"
> [   359.880] (WW) Aiptek: touchpads, tablets and touchscreens ignore relative
> axes.
> [   359.880] (II) Aiptek: initialized for absolute axes.
>
>