xserver-xorg-input-wizardpen for natty?
Hello, any chance to get xserver-
Question information
- Language:
- English Edit question
- Status:
- Answered
- For:
- Wizardpen Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Related bugs
Related FAQ:
None Link to a FAQ
Revision history for this message
|
#1 |
I've added a patch against trunk to the #715904 bug that makes it work on natty. but the request of getting natty support on the ppa remains.
Revision history for this message
|
#2 |
mnemoc, how would a person go about installing this patched version? I'm fine with installing things from the terminal, but I'm not very familiar with bzr or dealing with development patches.
Revision history for this message
|
#3 |
Follow https:/
patch -p1 < ~/wizardpen-
Revision history for this message
|
#4 |
sorry, too much git on my head, it's patch -p0 < ~/wizardpen-
Revision history for this message
|
#5 |
Most of the tablets supported by WizardPen should be supported by Natty kernel (2.6.38) and xserver-
Please report if that isn't the case.
Revision history for this message
|
#6 |
@Nikolai: if it would have worked out of the box with xserver-
Revision history for this message
|
#7 |
@Alejandro: Could you please tell which tablet(s) didn't work on Natty? Would you be able to help adding kernel support for them? I would be happy to do it within the DIGImend project (http://
Revision history for this message
|
#8 |
I can confirm that the following tablet did NOT work in natty without installing the latest wizardpen driver from this site
Monoprice TWA60 Pen Table.
Also labeled as the 160-TWA60-990
The following line is the pertinent information from lsusb:
ID 5543:0064 UC-Logic Technology Corp. Aiptek HyperPen 10000U
This tablet functions perfectly with the driver from this site and a proper configuration file.
Revision history for this message
|
#9 |
@Stephen: Thank you. This tablet shouldn't be supported indeed. I'm working on it right now. The kernel patch should be ready this evening.
Would you be able to test it if I provide you with a patched kernel package? It will take some time to build it in VM though, so it could only be ready tomorrow or the day after.
This is the information I have on this tablet so far:
http://
Meanwhile, could you please provide me with an output of "sudo lsusb -d5543:0064 -v"?
Revision history for this message
|
#10 |
I can, and I'd be happy to. First though, let me give you one or two details that 'may' be important here.
First and foremost, I'm running 64bit. The only other technical detail that is likely to matter is that I already have the package from here installed, but I can purge that easily enough.
The one non-technical issue is that I'm getting married in less than 3 weeks, so free time is at a minimum. Not having it available for a day or two will be fine, as long as you understand it will likely take me another day or two to test it and report back.
Revision history for this message
|
#11 |
Bus 001 Device 011: ID 5543:0064 UC-Logic Technology Corp. Aiptek HyperPen 10000U
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x5543 UC-Logic Technology Corp.
idProduct 0x0064 Aiptek HyperPen 10000U
bcdDevice 0.00
iManufacturer 1 UC-LOGIC
iProduct 2 TWA60
iSerial 0
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurat
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 1
bInterfac
bInterfac
bInterfac
iInterface 2 TWA60
HID Device Descriptor:
bLength 9
bcdHID 1.10
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
Transfer Type Interrupt
Synch Type None
Usage Type Data
bInterval 5
Device Status: 0x0000
(Bus Powered)
Revision history for this message
|
#12 |
@Stephen:
> I can, and I'd be happy to.
Great! Thank you :)
> First and foremost, I'm running 64bit.
That would complicate the matter a bit, but is not a problem in the end :)
> The one non-technical issue is that I'm getting married in less than 3 weeks, so free time is at a minimum.
Congratulations :)! No problem, I can wait and maybe someone else will also be able to test it.
Revision history for this message
|
#13 |
Well, send it along when you can anyway. If you're able to send it on Friday, there's a very good chance of a same day turn-around.
Revision history for this message
|
#14 |
@Stephen:
I built the packages, but unfortunately my server in my other home went down and I have nowhere to upload them.
Do you have anywhere where I could put them? Sending them via e-mail would be problematic.
Revision history for this message
|
#15 |
@Stephen:
Please disregard the last message. I just remembered about one place.
These are the packages that should support the tablet:
http://
http://
The patches will be published soon.
Revision history for this message
|
#16 |
You nailed it in one shot as far as I can tell. I did the following:
1. Used synaptic to purge the wizardpen driver.
2. Installed your kernel package through the software center. (I just double clicked the .deb)
3. Installed your header package the same way.
4. Reboot.
5. Plugged in my tablet.
6. Win.
The tablet works great, including the calibration which came out exceedingly close to perfect with no help needed. I fired up MyPaint to make sure pressure sensitivity is functioning as intended, and it does. All of my other USB devices appear to be unnafected in any way, which is as it should be.
The full output of lsusb with the tablet connected is as follows:
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0bda:0151 Realtek Semiconductor Corp. Mass Storage Device (Multicard Reader)
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 010: ID 5543:0064 UC-Logic Technology Corp. Aiptek HyperPen 10000U
Bus 001 Device 009: ID 0a5c:2148 Broadcom Corp.
Bus 001 Device 008: ID 0a5c:4503 Broadcom Corp.
Bus 001 Device 007: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface Subclass)
Bus 001 Device 006: ID 045e:0745 Microsoft Corp.
Bus 001 Device 005: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 001 Device 004: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 001 Device 003: ID 041e:4071 Creative Technology, Ltd
Bus 001 Device 002: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
If there is any specific testing you'd like me to do, just let me know. Beyond that, just post back when this becomes default in Ubuntu so I can stay updated with keeping my kernel at the current version.
Revision history for this message
|
#17 |
I'm sure you already know this, but for anyone following, there was no configuration of any kind for this. It "just works."
Revision history for this message
|
#18 |
@Stephen:
Glad to hear that, and thanks for testing :)!
Here is the draft patch for now, in case anyone wishes to build their own kernel (which isn't hard at all on Ubuntu):
http://
I will try to get it into 3.1 kernel.
Meanwhile, you could build your own kernel like this, approximately:
# Get build dependencies
sudo apt-get build-dep linux-image-`uname -r`
# Clone the kernel repo
git clone git://kernel.
cd natty-kernel
# This checked out Ubuntu-2.6.38-8.42 branch for my current kernel
git checkout Ubuntu-`apt-cache policy linux-image-\`uname -r\` | awk '/Installed:/ {print $2}`
# Apply the patch
patch -p1 < ~/wp1062_
# Clean and generate some files
fakeroot debian/rules clean
# Build
AUTOBUILD=1 NOEXTRAS=1 fakeroot debian/rules binary-generic
# The packages will be output to the parent directory
Note: there could be a typo in there somewhere :)
There is a good article on Ubuntu kernel building: https:/
I also have an untested patch for Waltop Q Pad (Aiptek HyperPen Mini, NGS Flexi Style, VisTablet PenPad, iVistaTablet Q Flex Pad, Bravod Q-PD65-S) here:
http://
Does anyone have any of these?
Now when Ubuntu is running a newer kernel we could turn these patches into proper DKMS packages.
Anyone up to the task?
Revision history for this message
|
#19 |
@Stephen:
One last request before I submit the patches to the kernel:
could you please measure the vertical size of the tablet working area?
Is it 6.25" as advertised, or 6.583" as the tablet itself tells?
Checking horizontal size to be 10" would also be good.
Thank you :)
Revision history for this message
|
#20 |
The size reported by the tablet is correct.
The reason for the extra 1/4" and change is that along the top of the tablet there is a row of "soft keys." These are 100% software driven. That strip along the top with icons screen printed on the tablet is fully functional tablet space without the windows software.
If you take a look at the product photos here: http://
Revision history for this message
|
#21 |
@Stephan:
Thank you :) I forgot about these "buttons" for a moment :)
Revision history for this message
|
#22 |
Is there any update on when this custom module might either become a working dkms module or find it's way into the Ubuntu kernel? You mentioned 3.1, which sounds like a year or more to me, given that we're currently on 2.9
For right now I've gone back to the wizartpen PPA since it's working in natty, and I just don't want to have to recompile my kernel every time there's a bug fix or security update to the Ubuntu kernel.
Revision history for this message
|
#23 |
@Steohen Michael Coons:
Hey, I've had trouble configuring my monoprice twa60 with the ppa version, and recompiling the kernel seems daunting. I was wondering if you could share the format of your config file with me.
Revision history for this message
|
#24 |
@Steohen Michael Coons:
Hey, I've had trouble configuring my monoprice twa60 with the ppa version, and recompiling the kernel seems daunting. I was wondering if you could share the format of your config file with me.
Revision history for this message
|
#25 |
I'll post my config, but please be aware that I'm not using it any more. As of Ubuntu 11.10, this is fully operational in the default kernel with zero configuration. I did a clean install of 11.10, and all I had to do to get my tablet fully functional, including sensitivity, was plug it in.
If you're using an older Ubuntu, and need my config, here you go:
#Save this file as /usr/share/
Section "InputClass"
Identifier "WizardPen class"
MatchIsTablet "on"
MatchVendor "UC-LOGIC|KYE Systems|Ace Cad"
MatchDevicePath "/dev/input/event*"
Driver "wizardpen"
Option "TopX" "93"
Option "TopY" "701"
Option "BottomX" "19936"
Option "BottomY" "13165"
EndSection
Section "InputClass"
Identifier "wizardpen ignore mouse dev"
MatchDevicePath "/dev/input/mouse*"
MatchTag "wizardpen"
Driver "mouse"
Option "MouseSpeed" "16"
Option "ignore" "true"
EndSection
Revision history for this message
|
#26 |
Thanks, I'm actually using linux mint 11, the one based on natty. Ubuntu fixes typically work, so, hopefully this wll.
Revision history for this message
|
#27 |
Your config works great. I'm always surprised to see how responsive the linux community is! again, thank you.
Can you help with this problem?
Provide an answer of your own, or ask Alejandro Mery for more information if necessary.