Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET
I would love to help to Improve the Linux Driver Support but i can only inspect the Laptop and it's behaviors till Tuesday.
And I get first wired result if i try to usbhid-dump the tablet:
Code:
sudo usbhid-dump 002 004
Code:
Failed to retrieve interface #0 report descriptor: Pipe error (ERROR_PIPE)
or do i need to write the output direct into a file?
btw:
It semes that the using from the xf86-input-evdev drivers work for Mypaint, and that would be the key point for my friend. I would like to use the xf86-input-evdev driver till there is an official support for that tablet. But i still have no idea were i have to set the used driver.
Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET
I haven't used usbhid-dump before. Would it be?
Code:
sudo usbhid-dump --model=172f:0502
I get the impression that it is suppose to create a txt file and you don't need to pipe the output into one.
For a 52-waltop-on-evdev.conf you could try:
Code:
Section "InputClass"
Identifier "waltop-on-evdev class"
MatchProduct "WALTOP"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Using
Code:
gksudo gedit /etc/X11/xorg.conf.d/52-waltop-on-evdev.conf
Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET
nope your usbhid-dump command doesn't work ether.
and my ubuntu dosen't seems to have gksudo installed, but it is already late in my country so i try it tomorrow.
Thanks for your help. Big open source Community's are the best :D
Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET
ok
after i force the tablet to use the evdev driver it seems to work al right
here are some commando output's
"lsusb":
Code:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 0408:2fb1 Quanta Computer, Inc.
Bus 002 Device 005: ID 172f:0502 Waltop International Corp. Sirius Battery Free Tablet
Bus 002 Device 004: ID 413c:8184 Dell Computer Corp. F3607gw v2 Mobile Broadband Module
"xinput list":
Code:
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=14 [slave pointer (2)]
⎜ ↳ WALTOP Batteryless Tablet id=12 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Video Bus id=8 [slave keyboard (3)]
↳ Power Button id=9 [slave keyboard (3)]
↳ Sleep Button id=10 [slave keyboard (3)]
↳ Laptop_Integrated_Webcam_2HDM id=11 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)]
↳ Dell WMI hotkeys id=15 [slave keyboard (3)]
and "xinput list-props 12":
Code:
Device ' WALTOP Batteryless Tablet ':
Device Enabled (132): 1
Coordinate Transformation Matrix (134): 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
Evdev Axis Inversion (264): 0, 0
Evdev Axis Calibration (265): <no items>
Evdev Axes Swap (266): 0
Axis Labels (267): "Abs X" (256), "Abs Y" (257), "Abs Pressure" (258), "Abs Misc" (259), "Abs Misc" (259)
Button Labels (268): "Button Left" (135), "Button Middle" (136), "Button Right" (137), "Button Wheel Up" (138), "Button Wheel Down" (139), "Button Horiz Wheel Left" (140), "Button Horiz Wheel Right" (141), "Button Side" (254), "Button Extra" (255), "Button Unknown" (252), "Button Unknown" (252), "Button Unknown" (252), "Button Unknown" (252)
Evdev Middle Button Emulation (269): 0
Evdev Middle Button Timeout (270): 50
Evdev Wheel Emulation (271): 0
Evdev Wheel Emulation Axes (272): 0, 0, 4, 5
Evdev Wheel Emulation Inertia (273): 10
Evdev Wheel Emulation Timeout (274): 200
Evdev Wheel Emulation Button (275): 4
Evdev Drag Lock Buttons (276): 0
he registers even the special buttons left and right from the device.
but the Button Mapping seems to be wrong.
is there a way that i could map a button to say "shift" with that in the .conf file:
Code:
Option "ButtonMapping" "string"
if it's not gonna working, it is not that bad.
Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET
That is good news. Is pressure working with evdev? In the Xorg.0.log is it the "evdev tablet class" snippet that is picking up the tablet?
Quote:
he registers even the special buttons left and right from the device.
but the Button Mapping seems to be wrong.
Are you talking about the stylus side buttons? Does the stylus have two side buttons, i.e. a rocker switch? What is wrong with the mapping?
Quote:
Option "ButtonMapping" "string"
Yes, exactly as you can see from man evdev entered in a terminal. So we just need to know what the current button map is. Unfortunately list-props doesn't seem to tell us. Say something like:
Code:
Section "InputClass"
Identifier "waltop-on-evdev class"
MatchProduct "WALTOP"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
Option "ButtonMapping" "1,3,2"
EndSection
You could also do it through xinput. See man xinput. Be careful about the "device name" though. From previous experience the malformed one you are seeing in xinput list is what you have to use, i.e.:
Code:
" WALTOP Batteryless Tablet"
I'm pretty sure you have to include the erroneous white spaces.
Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET
Yes the Pressure sensetivity works without problems.
Tested in Gimp and Mypaint.
To the buttons.
I doesn't mean the stylus buttons.
that is the tablet device:
http://www.trust.com/products/produc...TS&artnr=16938
and it has those configurable buttons left and right.
and those buttons i want to map to "shift", "ctrl", "alt" and "r"
is that waht you wanted out of the Xorg0.log?
Code:
[ 2144.790] (II) config/udev: Adding input device WALTOP Batteryless Tablet (/dev/input/event5)
[ 2144.790] (**) WALTOP Batteryless Tablet : Applying InputClass "evdev pointer catchall"
[ 2144.790] (**) WALTOP Batteryless Tablet : Applying InputClass "evdev keyboard catchall"
[ 2144.790] (**) WALTOP Batteryless Tablet : Applying InputClass "evdev tablet catchall"
[ 2144.790] (**) WALTOP Batteryless Tablet : Applying InputClass "Wacom class"
[ 2144.790] (**) WALTOP Batteryless Tablet : Applying InputClass "waltop-on-evdev class"
[ 2144.790] (II) Using input driver 'evdev' for ' WALTOP Batteryless Tablet '
[ 2144.790] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 2144.790] (**) WALTOP Batteryless Tablet : always reports core events
[ 2144.790] (**) WALTOP Batteryless Tablet : Device: "/dev/input/event5"
[ 2144.790] (--) WALTOP Batteryless Tablet : Found 9 mouse buttons
[ 2144.790] (--) WALTOP Batteryless Tablet : Found scroll wheel(s)
[ 2144.790] (--) WALTOP Batteryless Tablet : Found relative axes
[ 2144.790] (--) WALTOP Batteryless Tablet : Found x and y relative axes
[ 2144.790] (--) WALTOP Batteryless Tablet : Found absolute axes
[ 2144.790] (II) evdev-grail: failed to open grail, no gesture support
[ 2144.790] (--) WALTOP Batteryless Tablet : Found x and y absolute axes
[ 2144.790] (--) WALTOP Batteryless Tablet : Found absolute tablet.
[ 2144.790] (--) WALTOP Batteryless Tablet : Found keys
[ 2144.790] (II) WALTOP Batteryless Tablet : Configuring as tablet
[ 2144.790] (II) WALTOP Batteryless Tablet : Configuring as keyboard
[ 2144.790] (II) WALTOP Batteryless Tablet : Adding scrollwheel support
[ 2144.790] (**) WALTOP Batteryless Tablet : YAxisMapping: buttons 4 and 5
[ 2144.790] (**) WALTOP Batteryless Tablet : EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2144.790] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input5/event5"
[ 2144.790] (II) XINPUT: Adding extended input device " WALTOP Batteryless Tablet " (type: KEYBOARD)
[ 2144.790] (**) Option "xkb_rules" "evdev"
[ 2144.790] (**) Option "xkb_model" "pc105"
[ 2144.790] (**) Option "xkb_layout" "de"
[ 2144.790] (WW) WALTOP Batteryless Tablet : touchpads, tablets and touchscreens ignore relative axes.
[ 2144.790] (II) WALTOP Batteryless Tablet : initialized for absolute axes.
[ 2144.791] (**) WALTOP Batteryless Tablet : (accel) keeping acceleration scheme 1
[ 2144.791] (**) WALTOP Batteryless Tablet : (accel) acceleration profile 0
[ 2144.791] (**) WALTOP Batteryless Tablet : (accel) acceleration factor: 2.000
[ 2144.791] (**) WALTOP Batteryless Tablet : (accel) acceleration threshold: 4
[ 2144.791] (II) config/udev: Adding input device WALTOP Batteryless Tablet (/dev/input/mouse0)
Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET
Quote:
Yes the Pressure sensetivity works without problems.
Tested in Gimp and Mypaint.
Wow, outstanding! Now how the heck is that happening? Clearly I am missing something.
With the new .conf file to put the Waltop on the evdev driver we're overriding the Wacom X driver match in the 50-wacom.conf. So now the situation is getting complicated. Some Waltops work on Wacom and others on evdev? I am confused.
Alright, tablet buttons. Thanks that link was helpful for me to see what you were talking about. Wacom calls those ExpressKeys, but since that is trademarked by Wacom in linux we call them pad or tablet buttons. The Wacom driver has a bunch of code to support those, both in the kernel driver and the X driver I believe. Then the xsetwacom code in the Wacom X driver has code to handle setting the pad buttons to modifiers and/or keys. As far as I'm aware the evdev driver has no code at all to support those, other than the keyboard stuff I suppose.
I have no idea how to set those up. You could see if they are sending a signal (button/key press and release or whatever) by either trying xev or evtest. With xev you enter xev in a terminal and then press a button and see if you get a key code. With evtest you may need to run it in a console as root and you need to know the device node the tablet is on.
If you can get a keycode then you may be able to do a keybinding with the CompizConfigurationManager (CCSM) or say Xbindkeys.
Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET
Except for the Eraser Button i get those events by xev.
and they seemed to be already mapped to the right keys.
Code:
KeyPress event, serial 34, synthetic NO, window 0x1e00001,
root 0xb7, subw 0x0, time 1458993, (242,614), root:(245,637),
state 0x0, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 34, synthetic NO, window 0x1e00001,
root 0xb7, subw 0x0, time 1459181, (242,614), root:(245,637),
state 0x1, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 34, synthetic NO, window 0x1e00001,
root 0xb7, subw 0x0, time 1461381, (242,614), root:(245,637),
state 0x0, keycode 23 (keysym 0xff09, Tab), same_screen YES,
XLookupString gives 1 bytes: (09) " "
XmbLookupString gives 1 bytes: (09) " "
XFilterEvent returns: False
KeyRelease event, serial 34, synthetic NO, window 0x1e00001,
root 0xb7, subw 0x0, time 1461525, (242,614), root:(245,637),
state 0x0, keycode 23 (keysym 0xff09, Tab), same_screen YES,
XLookupString gives 1 bytes: (09) " "
XFilterEvent returns: False
KeyPress event, serial 34, synthetic NO, window 0x1e00001,
root 0xb7, subw 0x0, time 1462385, (242,614), root:(245,637),
state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 34, synthetic NO, window 0x1e00001,
root 0xb7, subw 0x0, time 1462521, (242,614), root:(245,637),
state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 34, synthetic NO, window 0x1e00001,
root 0xb7, subw 0x0, time 1464393, (242,614), root:(245,637),
state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 34, synthetic NO, window 0x1e00001,
root 0xb7, subw 0x0, time 1464537, (242,614), root:(245,637),
state 0x4, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET
Hmmm. It sure is looking like your model Waltop tablet has support from a kernel driver somewhere. You're using Oneiric, so the 3.0 kernel, correct?
Changing a key's mapping can be done a bunch of ways. Changing the mapping in the kernel driver's code, udev, or X. And along with that keybinding. See appendix 2 of the Rotation HOW TO to get a feel for what is involved.
Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET
Dear Favux and Drkurian i tried to read almost all topics before telling you my problem because i see that you do everything you can to help us.
I have a trust/16937 tablet and i use ubuntu 10.04.I have a really bizare problem.When pc boots up i can move the pen without touching the tablet and cursor moves in screen.As soon as i touch pen in tablet or press the button the movement stops and i can move the cursor only if pen touches tablet.Iam really sorry for my bad english,Ty in advance.:p