Re: [DIGImend-users] Aiptek Media Tablet 14000u worked instantly (and almost complete) in linux 3.3
Brought to you by:
spb_nick
|
From: Eduardo H. S. <hob...@gm...> - 2012-04-30 02:12:09
|
2012/4/30 Favux ... <fav...@gm...>: > On Sun, Apr 29, 2012 at 6:05 PM, Eduardo H. Silva <hob...@gm...> wrote: >> >>> The gnome-settings-daemon runs after the xorg.conf.d conf files so >>> what it says goes. And you can over ride it with an xsetwacom >>> command. So what happens if you run these commands: >>> xsetwacom set 10 Button 2 2 >>> xsetwacom set 10 Button 3 3 >>> Any change on the stylus buttons behavior? If the tablet isn't being >>> recognized maybe no gnome-settings-daemon key values are being >>> applied. >> >> It remains the same, and I've figured that: >> >> 1 - xsetwacom is working. If I assign: >> >> Button 1 1 >> Button 2 3 >> Button 3 2 >> >> , the button's behaviors switch. >> >> 2 - if I assign: >> Button 1 0 >> Button 2 2 >> Button 3 3 >> >> , the buttons are working as expected in Gimp and elsewhere, but >> pressing with the stylus doesn't work. > > Out of curiosity what happens when you assign 'Button 1 1' along with? > Button 2 2 > Button 3 3 > Still see the confusion between Button 2 and Button 1? Yep. >> Also, the broken behavior in Inkscape and throughout Gnome's interface >> is different than Gimp's. If the assignment is: >> Button 1 1 >> Button 2 2 >> Button 3 3 >> >> , button 2 does action 1 and 2 (left and middle-click) and button 3 >> does action 3 (right-click). > > So for now is it OK if you use xsetwacom to assign: > Button 2 3 > Button 3 3 > Sure they're both assigned 3 (right click), but does it avoid the > confusion with 2 (middle click) & 1? No, and now I notice that Button 3 is also linked with what is set for Button 1. >>> So if this works try uncommenting those button options from >>> earlier in the Wacom snippet and see what happens. Actually try that >>> either way I suppose. >> >> Uncommented the options and restarted X, but > > Oops, what happened? oops, should end with "...but things remained the same." > >>>> But what about the last message about wacom in Xorg.0.log: >>>> UnloadModule: "wacom" >>> >>> What, where is that in the last Xorg.0.log snippet you gave? We know >>> the stylus is on the Wacom X driver (module) from the diagnostics you >>> ran above. >> >> Ah, at the time of that diagnostic, I was only copying what seemed to >> have to do with the tablets, and may have missed the unload message. >> Also, only now I noticed that once I removed waltop-on-evdev.conf from >> /usr/share/X11/xorg.conf.d/ , makes the wheels not work. >> Sorry about this confusion. > > So now you've lost the scroll wheels. Then leave it in? Or do we > need to match to another evdev snippet, maybe? > MatchIsPointer "on" > Or else try the snippet Nick suggested for that. No, doesn't work with MatchIsPointer. with Nick's addition, and moving all of the wacom config options to the end of the /etc/X11/xor.conf.d/52-waltop-custom.conf file, I now have volume and scrolling. >> Ok, so my configuration is exactly like the one you told in your first >> reply. To make sure, it is: >> >> /usr/share/X11/xorg.conf.d/: >> Section "InputClass" >> Identifier "Wacom class" >> MatchProduct "Wacom|WACOM|WALTOP|Hanwang|PTK-540WL" >> MatchDevicePath "/dev/input/event*" >> Driver "wacom" >> # Option "Button1" "3" >> # Option "Button2" "1" >> # Option "Button3" "2" >> >> >> 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|FUJ02e9" >> 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 >> >> /etc/X11/xorg.conf.d/52-waltop-custom.conf >> Section "InputClass" >> Identifier "Waltop evdev custom" >> MatchProduct "WALTOP" >> MatchIsKeyboard "on" >> MatchDevicePath "/dev/input/event*" >> Driver "evdev" >> EndSection >> >> Section "InputClass" >> Identifier "Waltop wacom custom" >> MatchProduct "WALTOP" >> MatchIsTablet "on" >> MatchDevicePath "/dev/input/event*" >> Driver "wacom" >> Option "Button2" "2" >> Option "Button3" "3" >> EndSection >> >> >> The complete Xorg.0.log after restarting X with the tablet plugged in: >> >> [128945.868] (II) config/udev: Adding input device WALTOP >> International Corp. Media Tablet (/dev/input/event10) >> [128945.868] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "evdev tablet catchall" >> [128945.868] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "Wacom class" >> [128945.868] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "Waltop wacom custom" >> [128945.868] (II) LoadModule: "wacom" >> [128945.868] (II) Loading /usr/lib/xorg/modules/input/wacom_drv.so >> [128945.868] (II) Module wacom: vendor="X.Org Foundation" >> [128945.869] compiled for 1.11.99.901, module version = 0.14.0 >> [128945.869] Module class: X.Org XInput Driver >> [128945.869] ABI class: X.Org XInput driver, version 16.0 >> [128945.869] (II) Using input driver 'wacom' for 'WALTOP International >> Corp. Media Tablet' >> [128945.869] (**) WALTOP International Corp. Media Tablet: always >> reports core events >> [128945.869] (**) Option "Device" "/dev/input/event10" >> [128945.869] (II) WALTOP International Corp. Media Tablet: type not >> specified, assuming 'stylus'. >> [128945.869] (II) WALTOP International Corp. Media Tablet: other types >> will be automatically added. >> [128945.869] (**) Option "Button2" "2" >> [128945.869] (**) Option "Button3" "3" >> [128945.869] (--) WALTOP International Corp. Media Tablet stylus: >> using pressure threshold of 27 for button 1 >> [128945.869] (--) WALTOP International Corp. Media Tablet stylus: >> Wacom USB Bamboo tablet maxX=16383 maxY=16383 maxZ=1023 resX=53000 >> resY=88000 tilt=disabled >> [128945.869] (II) WALTOP International Corp. Media Tablet stylus: >> hotplugging dependent devices. >> [128945.869] (EE) WALTOP International Corp. Media Tablet stylus: >> Invalid type 'eraser' for this device. >> [128945.869] (EE) WALTOP International Corp. Media Tablet stylus: >> Invalid type 'cursor' for this device. >> [128945.869] (EE) WALTOP International Corp. Media Tablet stylus: >> Invalid type 'touch' for this device. >> [128945.869] (EE) WALTOP International Corp. Media Tablet stylus: >> Invalid type 'pad' for this device. >> [128945.869] (II) WALTOP International Corp. Media Tablet stylus: >> hotplugging completed. >> [128945.869] (**) Option "config_info" >> "udev:/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/input/input424/event10" >> [128945.869] (II) XINPUT: Adding extended input device "WALTOP >> International Corp. Media Tablet stylus" (type: STYLUS, id 10) >> [128945.869] (**) WALTOP International Corp. Media Tablet stylus: >> (accel) keeping acceleration scheme 1 >> [128945.869] (**) WALTOP International Corp. Media Tablet stylus: >> (accel) acceleration profile 0 >> [128945.869] (**) WALTOP International Corp. Media Tablet stylus: >> (accel) acceleration factor: 2.000 >> [128945.869] (**) WALTOP International Corp. Media Tablet stylus: >> (accel) acceleration threshold: 4 >> [128945.870] (II) config/udev: Adding input device WALTOP >> International Corp. Media Tablet (/dev/input/mouse2) >> [128945.870] (II) No input driver specified, ignoring this device. >> [128945.870] (II) This device may have been added with another device file. >> [128945.870] (II) config/udev: Adding input device WALTOP >> International Corp. Media Tablet (/dev/input/event11) >> [128945.870] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "Wacom class" >> [128945.870] (II) Using input driver 'wacom' for 'WALTOP International >> Corp. Media Tablet' >> [128945.870] (**) WALTOP International Corp. Media Tablet: always >> reports core events >> [128945.870] (**) Option "Device" "/dev/input/event11" >> [128945.870] (EE) WALTOP International Corp. Media Tablet: Invalid >> type 'stylus' for this device. >> [128945.870] (EE) WALTOP International Corp. Media Tablet: Invalid >> type 'eraser' for this device. >> [128945.870] (EE) WALTOP International Corp. Media Tablet: Invalid >> type 'cursor' for this device. >> [128945.870] (EE) WALTOP International Corp. Media Tablet: Invalid >> type 'touch' for this device. >> [128945.870] (EE) WALTOP International Corp. Media Tablet: Invalid >> type 'pad' for this device. >> [128945.871] (EE) WALTOP International Corp. Media Tablet: No type specified >> [128945.871] (EE) PreInit returned 8 for "WALTOP International Corp. >> Media Tablet" >> [128945.871] (II) UnloadModule: "wacom" > > I can't tell if that is a general wacom module/X driver unload or not. > As long as 'xsetwacom list' still shows the stylus and you see the > Wacom driver in 'xinput list-props <stylus ID #> we may not need to > worry about this. It appears to be happening to event11 not event10 > which is the stylus. But if the stylus isn't in 'xsetwacom list' etc. > then we do have a problem. > >> [128945.871] (II) config/udev: Adding input device WALTOP >> International Corp. Media Tablet (/dev/input/event12) >> [128945.871] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "evdev keyboard catchall" >> [128945.871] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "Wacom class" >> [128945.871] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "system-setup-keyboard" >> [128945.871] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "Waltop evdev custom" >> [128945.871] (II) Using input driver 'evdev' for 'WALTOP International >> Corp. Media Tablet' >> [128945.871] (**) WALTOP International Corp. Media Tablet: always >> reports core events >> [128945.871] (**) evdev: WALTOP International Corp. Media Tablet: >> Device: "/dev/input/event12" >> [128945.871] (--) evdev: WALTOP International Corp. Media Tablet: >> Vendor 0x172f Product 0x500 >> [128945.871] (--) evdev: WALTOP International Corp. Media Tablet: Found keys >> [128945.871] (II) evdev: WALTOP International Corp. Media Tablet: >> Configuring as keyboard >> [128945.871] (**) Option "config_info" >> "udev:/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/input/input426/event12" >> [128945.871] (II) XINPUT: Adding extended input device "WALTOP >> International Corp. Media Tablet" (type: KEYBOARD, id 11) >> [128945.871] (**) Option "xkb_rules" "evdev" >> [128945.871] (**) Option "xkb_model" "pc105" >> [128945.871] (**) Option "xkb_layout" "pt" >> [128945.871] (**) Option "xkb_options" "terminate:ctrl_alt_bksp," >> [128945.872] (II) config/udev: Adding input device WALTOP >> International Corp. Media Tablet (/dev/input/event13) >> [128945.872] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "evdev keyboard catchall" >> [128945.872] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "Wacom class" >> [128945.872] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "system-setup-keyboard" >> [128945.872] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "Waltop evdev custom" >> [128945.872] (II) Using input driver 'evdev' for 'WALTOP International >> Corp. Media Tablet' >> [128945.872] (**) WALTOP International Corp. Media Tablet: always >> reports core events >> [128945.872] (**) evdev: WALTOP International Corp. Media Tablet: >> Device: "/dev/input/event13" >> [128945.872] (--) evdev: WALTOP International Corp. Media Tablet: >> Vendor 0x172f Product 0x500 >> [128945.872] (--) evdev: WALTOP International Corp. Media Tablet: Found keys >> [128945.872] (II) evdev: WALTOP International Corp. Media Tablet: >> Configuring as keyboard >> [128945.872] (**) Option "config_info" >> "udev:/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/input/input427/event13" >> [128945.872] (II) XINPUT: Adding extended input device "WALTOP >> International Corp. Media Tablet" (type: KEYBOARD, id 12) >> [128945.872] (**) Option "xkb_rules" "evdev" >> [128945.872] (**) Option "xkb_model" "pc105" >> [128945.872] (**) Option "xkb_layout" "pt" >> [128945.872] (**) Option "xkb_options" "terminate:ctrl_alt_bksp," > > Assuming we don't have a driver problem and the stylus is on the Wacom > X driver I'm thinking this is a kernel driver problem. What are your > thoughts Nick? > > Favux In inkscape I can test the stylus in a special window, and it shows that pressing the tip and the buttons register differently. Eduardo |