Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET
hi i have a little Problem with a Tablet.
it is the same Problem as here
http://comments.gmane.org/gmane.linu...ers.wacom/6127
and it seems to be solved.
But i don't know how to do this:
"
You may also be able to redirect this tablet to use xf86-input-evdev instead. You'll lose ability to treat eraser as a different input device but it may at least work.
"
Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET
Hi Wasabi2007,
Welcome to Ubuntu forums!
Some more information would be helpful. What release of Ubuntu are you using? Also the output of some commands run in a terminal would be good. For example:
will have a line in the output with the tablet in it and that will give us the manufacturer and model ID. And:
will tell us the "device name" the tablet is using.
Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET
Sorry for my harsh and short post. And Thank you for your welcome.
At first I can not post the needed information at the moment, because it was a Laptop from a friend of mine and he needed it back.
I wanted to make him this set-up but his tablet was not detected. So tried the Wizardpen Drivers and see there the tablet is detected.
But the tablet didn't send any feedback. So i searched for that problem and found this mailing list conversation.
It is the same Tablet device and the same error and it seemed to be solved by replacing the the "xf86-input-wacom" driver through "xf86-input-evdev".
Unfortunately i have not enough linux/(k)ubuntu in deep knowledge to know were i have to replace the driver.
Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET
Not a problem at all.
I followed your link, but I really want to verify the Vendor ID = 172f = Waltop and the Product ID = 0502 from the lsusb.
Code:
Bus 002 Device 012: ID 172f:0502 Waltop International Corp. Sirius Battery Free Tablet
See from Nick's site: http://digimend.sourceforge.net/ that Waltop model isn't included yet in the kernel: http://digimend.git.sourceforge.net/...=COMPATIBILITY And that is what they are saying on that thread you link too.
Nick offers to add it to the kernel if the usbhid-dump information his site requests is sent to him and his kernel patch/driver is tested.
You see the Waltop tablets are suppose to use the Wacom driver now, and tablets that don't use the Wacom X driver are suppose to use evdev. And that is suppose to happen automatically if the tablet is in the kernel. What you are asking about is the xorg.conf.d .conf (configuration) files. For the distribution the files would be in /usr/share/X11/xorg.conf.d. Custom .conf files by the user are suppose to go in /etc/X11/xorg.conf.d. Here's some more information on xorg.conf.d .conf files: http://sourceforge.net/apps/mediawik...le=Xorg.conf.d
But you should not have to make a custom file, it should happen automatically. It looks like the problem is that model of Waltop tablet is not yet in the kernel. In which case I don't think pressure, despite what is reported on that thread, would be working. Unless some generic hid kernel driver I don't know about processes unclaimed Waltop tablets. They are just transitioning to this system having just dropped the WizardPen driver for the evdev driver. And unfortunately a number of tablets are not in the kernel yet. They mainly seem to be KYE Systems tablets though.
Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET
I think at Saturday or Sunday, I can deliver the device information.
I hope we get that tablet to fly ^^
And I hope there is some day in the Linux Future where are no driver Issues with new devices.
Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET
Finalay I have the Laptop again ^^
so here is the lsusb output:
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 003: ID 413c:8184 Dell Computer Corp. F3607gw v2 Mobile Broadband Module
Bus 002 Device 004: ID 172f:0502 Waltop International Corp. Sirius Battery Free Tablet
edit:
sorry i forgot the xinput list result:
Code:
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)]
⎜ ↳ WALTOP Batteryless Tablet stylus id=15 [slave pointer (2)]
⎜ ↳ WALTOP Batteryless Tablet eraser id=16 [slave pointer (2)]
⎜ ↳ WALTOP Batteryless Tablet pad id=17 [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=12 [slave keyboard (3)]
↳ Dell WMI hotkeys id=14 [slave keyboard (3)]
Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET
sorry i clicked on quote rather than on edit
Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET
Good. Now what does the tablet do? Does the stylus get recognized? In other words does the pointer arrow track the stylus tip?
Although the 502 model is not in Nick's compatibility tablet (i.e. not yet in the kernel) the Wacom X driver xf86-input-wacom is picking the tablet up. That's why you see stylus, eraser, and pad appended to the device name in xinput list.
You can verify that by posting the ouput in a terminal of:
Code:
xinput list-props 15
And you should also see the tablet setting up on the Wacom driver in Xorg.0.log in /var/log.
Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET
Ok xinput list-props 15 delivers me that:
Code:
Device ' WALTOP Batteryless Tablet stylus':
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 (252): 0
Device Accel Constant Deceleration (253): 1.000000
Device Accel Adaptive Deceleration (254): 1.000000
Device Accel Velocity Scaling (255): 10.000000
Wacom Tablet Area (509): 0, 0, 20000, 12000
Wacom Rotation (510): 0
Wacom Pressurecurve (511): 0, 0, 100, 100
Wacom Serial IDs (512): 1282, 0, 2, 0
Wacom Capacity (513): -1
Wacom Pressure Threshold (514): 27
Wacom Sample and Suppress (515): 2, 4
Wacom Enable Touch (516): 0
Wacom Hover Click (517): 0
Wacom Enable Touch Gesture (518): 0
Wacom Touch Gesture Parameters (519): 50, 20, 250
Wacom Tool Type (520): "STYLUS" (412)
Wacom Button Actions (521): "Wacom button action 1" (529), "Wacom button action 2" (528), "Wacom button action 3" (527), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0)
Wacom Debug Levels (522): 0, 0
Wacom button action 1 (529): 1572865
Wacom button action 2 (528): 1572866
Wacom button action 3 (527): 1572867
And the Tablet doesn't do anything visual Noticiable. The only thing that happens is that the tablet get automatically register. The stylus or the Tablet integrate Buttons doesn't seems to do anything.
Re: HOWTO INSTALL WIZARDPEN DRIVER FOR iball TABLET
From my understanding of how things are currently suppose to work and what you've showed it appears to me everything is working correctly.
The 50-wacom.conf is correctly picking up the WALTOP keyword and configuring your tablet on the Wacom X driver which it is suppose to. As I said Waltops go to Wacom and the other tablets that used the former WizardPen driver are picked up by the 10-evdev.conf. So it is all happening as it should.
The problem is of course your tablet's usb descriptor is not in the kernel. So values like ABS_PRESSURE or ABS_Z or whatever it is the Wacom driver is looking for are null. That's why there is no reaction to the stylus tip. No tracking, left click, and pressure.
So to get it working you need to go to Nick's DIGImend sourceforge site and send in the information he requests on the link at the bottom of the site. You can see an example of the information on this post by viktoria.s, which she recently sent in for another tablet. Nick will tell you if the information is good or if he needs anything else. Then he'll make patches for the kernel and ask you to test them and if they are good he will submit them to the kernel so your tablet model is included for now on. So you get to help with linux kernel development! :)
Patching the kernel sounds a little daunting but it isn't actually that hard and Nick will walk you through it. And I will try to help if you need me to.
And by the way the hotkeys on the tablet don't work. No one has yet written code to get them working as far as I know. Maybe Nick is thinking about doing that at some point?