[DIGImend-users] Fwd: Aiptek Media Tablet 14000u worked instantly (and almost complete) in linux 3.
Brought to you by:
spb_nick
Menu
▾
▴
[DIGImend-users] Fwd: Aiptek Media Tablet 14000u worked instantly (and almost complete) in linux 3.3.2
|
From: Eduardo H. S. <hob...@gm...> - 2012-04-29 21:46:51
|
---------- Forwarded message ---------- From: Eduardo H. Silva <hob...@gm...> Date: 2012/4/29 Subject: Re: [DIGImend-users] Aiptek Media Tablet 14000u worked instantly (and almost complete) in linux 3.3.2 To: "Favux ..." <fav...@gm...> 2012/4/29 Favux ... <fav...@gm...>: > On Sun, Apr 29, 2012 at 7:35 AM, Eduardo H. Silva <hob...@gm...> wrote: >> >> Yep, with your new config file, the scroll wheels work, and the stylus >> has pressure. But the first button paints, and the second button >> paints while held and undos it when released. In inkscape, this 2nd >> button sometimes does a zoom in. >> >>> The wheels and mode buttons should work, but may need some configuration. >> >> After using Dave's configuration, the wheel and mode buttons work immediately. > > Good. So we have everything working with 52-waltop-custom.conf except > the two stylus side buttons. We need to find out why. Your new > Xorg.0.log shows that event10 is the stylus and is being set up by > Wacom while events 11, 12, and 13 are being claimed by evdev. I think > that is correct, Nick can tell us. On those 3 events evdev is > reporting: > ButtonMapping '1 2 3' > Event 10 on Wacom is reporting: > using pressure threshold of 27 for button 1 > which is correct. > > Still see Aiptek, so you commented out the evdev driver line but left > the matching in? Oops, I forgot I had a waltop-on-evdev.conf file which looked for identifier in /usr/share/X11/xorg.conf.d/ . I've removed it. > > With the 52-waltop-custom.conf let's try to find out what we have. > What is the output of? > xsetwacom list WALTOP International Corp. Media Tablet stylus id: 10 type: STYLUS > I'll guess that event10 was the ID # 9 on your 'xinput list' and that > hasn't changed. Let's see if we can get a button map reported in the > output of: > xinput list-props 9 > If rerunning 'xinput list' shows different ID numbers you'll have to > guess until you hit the stylus. You'll know you have the right one > when the driver in the output is wacom not evdev. xinput list-props 10: Device 'WALTOP International Corp. Media Tablet stylus': Device Enabled (134): 1 Coordinate Transformation Matrix (136): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000 Device Accel Profile (260): 0 Device Accel Constant Deceleration (261): 1.000000 Device Accel Adaptive Deceleration (262): 1.000000 Device Accel Velocity Scaling (263): 10.000000 Device Node (254): "/dev/input/event10" Wacom Tablet Area (288): 0, 0, 16383, 16383 Wacom Rotation (289): 0 Wacom Pressurecurve (290): 0, 0, 100, 100 Wacom Serial IDs (291): 1280, 1, 0, 0, 0 Wacom Serial ID binding (292): 0 Wacom Pressure Threshold (293): 27 Wacom Sample and Suppress (294): 2, 4 Wacom Enable Touch (295): 1 Wacom Hover Click (296): 1 Wacom Enable Touch Gesture (297): 0 Wacom Touch Gesture Parameters (298): 0, 0, 250 Wacom Tool Type (299): "STYLUS" (281) Wacom Button Actions (300): "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0) Device Product ID (253): 5935, 1280 Wacom Debug Levels (301): 0, 0 Hm, "Button Actions: "None"... > We can also get the assigned button values reported separately using > the xsetwacom get command. So using the stylus ID # from above: > xsetwacom get 9 Button 1 > xsetwacom get 9 Button 2 > xsetwacom get 9 Button 3 Yep, shows them as 1, 2, 3. > The other thing is to look at the gnome-settings-daemon's key values. > Since the applet isn't allowing access install dconf-editor and run > it. Then navigate to org.gnome.settings-daemon.peripherals.wacom. If > your tablet was listed there, under the tablet name would be one or > more styli. They should report a pressurecurve and the active one a > buttonmapping. Anything regarding a stylus or tablet in there? > Buttonmapping? Hmm, I don't have a wacom sections under peripherals... > >> The Gnome Wacom applet doesn't shown me options, saying that no tablet >> was detected. This with all my previous configurations, and with your >> new suggestion. Btw, I just need to restart X to have the >> configuration re-read right? > > I don't think so. As far as I know it should be run-time, changing > the gnome-settings-daemon's key values with the Wacom Tablet applet > should change behavior instantly just like a xsetwacom command. Ah, but what about adding rules in /etc/X11/xorg.conf.d/? > If it is on the Wacom driver why isn't it showing up on the tablet > applet? We know the xf86-input-wacom driver is handling the stylus > according to the Xorg.0.log and it is working because you have > pressure. But what about the last message about wacom in Xorg.0.log: UnloadModule: "wacom" ? > Libwacom does have a stylus file with a generic stylus > section. Libwacom is a Wacom tablet metadata library that was added > shortly after the initial Wacom Graphics Tablet applet came out. And > the applet was then changed to work with it. The idea was to simplify > the applet and make the library available to other applications that > might want to use the tablet metadata. So my guess is that it is > libwacom blocking recognition of the Waltop stylus, which is why you > don't see it in the applet. If so that may be also true for the > N-Trig and Hanwang tablets. Not good. I think I need to ask the LWP > about this. > > Favux |
