digimend-users Mailing List for DIGImend (Page 12)
Brought to you by:
spb_nick
You can subscribe to this list here.
2012 |
Jan
|
Feb
|
Mar
|
Apr
(58) |
May
(72) |
Jun
(24) |
Jul
|
Aug
(12) |
Sep
(9) |
Oct
(10) |
Nov
(2) |
Dec
(4) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2013 |
Jan
(5) |
Feb
(23) |
Mar
|
Apr
|
May
(4) |
Jun
(7) |
Jul
(2) |
Aug
(2) |
Sep
(5) |
Oct
(7) |
Nov
(31) |
Dec
(11) |
2014 |
Jan
(13) |
Feb
(4) |
Mar
(1) |
Apr
(1) |
May
(1) |
Jun
(2) |
Jul
(12) |
Aug
(10) |
Sep
(13) |
Oct
(15) |
Nov
(49) |
Dec
(4) |
2015 |
Jan
(49) |
Feb
(62) |
Mar
(81) |
Apr
(10) |
May
(4) |
Jun
(6) |
Jul
(17) |
Aug
(3) |
Sep
(1) |
Oct
(4) |
Nov
|
Dec
(8) |
2016 |
Jan
(8) |
Feb
(5) |
Mar
(7) |
Apr
(7) |
May
(3) |
Jun
(4) |
Jul
(12) |
Aug
(8) |
Sep
(6) |
Oct
(4) |
Nov
(1) |
Dec
|
From: Christopher B. <chr...@gm...> - 2014-09-07 01:42:14
|
On Sat, 6 Sep 2014 14:53:52 -0400 Christopher Barry <chr...@gm...> wrote: >On Sat, 6 Sep 2014 13:55:43 -0400 >Christopher Barry <chr...@gm...> wrote: > >>Greetings, >> >>running v5-1-g200f0d2 >>kernel 3.14-2-amd64 on Debian Jessie @sid >> >>Bought the Huion H610 after doing a bit of research on good tablets >>for Linux. Found recommendations for your driver, saw it was already >>in the kernel, but pulled git and built anyway. >> >>The sensitivity of the pen is *really* over the top. I use three >>monitors, so it's likely 3 times as fast horizontally than in most >>setups. I really only want it to be active on one screen. That, and >>not sure how to configure the buttons. Also, the pen starts to act >>upon the tablet while about 2cm above the tablet surface, which makes >>it very difficult to use. >> >>How can I setup/adjust all these things? >> >>-- >>Regards, >>Christopher Barry >> >>Random geeky fortune: >>Dear Lord: Please make my words sweet and tender, for tomorrow I may >>have to eat them. > >Sorry to have sent prematurely - I'll see what AutoKey can do for me. > >Thanks > So, the big issue for me was that with three monitors, movement was 3 times as fast horizontally than vertically, making drawing pretty much impossible. After reading various manpages, I managed to restrict the tablet to working on a single monitor at a time. Attached is a script to selectively put the tablet on a monitor. It's coded to allow left,center, or right. Edit to suit your situation (there's a config section at the top). Yet to solve: * Getting the buttons tablet to work for me. * Adjusting the pressure required to 'click'. I'd like to have more pressure be required. If anyone can help with these, please let me know. -- Regards, Christopher Barry Random geeky fortune: You can tell the ideals of a nation by its advertisements. -- Norman Douglas |
From: Christopher B. <chr...@gm...> - 2014-09-06 18:52:22
|
On Sat, 6 Sep 2014 13:55:43 -0400 Christopher Barry <chr...@gm...> wrote: >Greetings, > >running v5-1-g200f0d2 >kernel 3.14-2-amd64 on Debian Jessie @sid > >Bought the Huion H610 after doing a bit of research on good tablets >for Linux. Found recommendations for your driver, saw it was already >in the kernel, but pulled git and built anyway. > >The sensitivity of the pen is *really* over the top. I use three >monitors, so it's likely 3 times as fast horizontally than in most >setups. I really only want it to be active on one screen. That, and not >sure how to configure the buttons. Also, the pen starts to act upon the >tablet while about 2cm above the tablet surface, which makes it very >difficult to use. > >How can I setup/adjust all these things? > >-- >Regards, >Christopher Barry > >Random geeky fortune: >Dear Lord: Please make my words sweet and tender, for tomorrow I may >have to eat them. Sorry to have sent prematurely - I'll see what AutoKey can do for me. Thanks -- Regards, Christopher Barry Random geeky fortune: Fortune favors the lucky. |
From: Christopher B. <chr...@gm...> - 2014-09-06 17:54:14
|
Greetings, running v5-1-g200f0d2 kernel 3.14-2-amd64 on Debian Jessie @sid Bought the Huion H610 after doing a bit of research on good tablets for Linux. Found recommendations for your driver, saw it was already in the kernel, but pulled git and built anyway. The sensitivity of the pen is *really* over the top. I use three monitors, so it's likely 3 times as fast horizontally than in most setups. I really only want it to be active on one screen. That, and not sure how to configure the buttons. Also, the pen starts to act upon the tablet while about 2cm above the tablet surface, which makes it very difficult to use. How can I setup/adjust all these things? -- Regards, Christopher Barry Random geeky fortune: Dear Lord: Please make my words sweet and tender, for tomorrow I may have to eat them. |
From: Nikolai K. <sp...@gm...> - 2014-08-19 12:40:27
|
Hi everyone, I've just released a v5 release of digimend-kernel-drivers package, which supersedes the huion-driver package (now deprecated), and continues its version numbering: https://github.com/DIGImend/digimend-kernel-drivers/releases/tag/v5 Important changes from the huion-driver v4 release are: * Add support for Yiynova tablets and tablet displays, including: MSP19U, MSP19U+, MVP22U+, MVP10U, MVP10U IPS, MVP10U HD IPS, DP10U, DP10U+. A big "thank you" goes to Yiynova Europe BV for initial driver hacking, testing and feedback! * Add uninstallation support. * Fix potential DMA issues on retrieving tablet parameters. All users are recommended to update. Yiynova tablet owners are encouraged to try the driver. Nick |
From: Nikolai K. <sp...@gm...> - 2014-08-16 11:29:32
|
On 08/15/2014 05:02 PM, Pierre Vuillemin wrote: > Ok, thank you for the information. > > I've finally used AutoKey to re-assign the keys to what I want depending > of the application. > It works fine and was not too complicated to set up. Great! I didn't know about that utility. Will keep it in mind. Thank you. Nick |
From: Pierre V. <co...@pi...> - 2014-08-15 16:29:48
|
Le lundi 11 août 2014 à 20:36 +0300, Nikolai Kondrashov a écrit : > Hi Pierre, > > On 08/10/2014 11:59 AM, Pierre Vuillemin wrote: > > I've just bought a Huion 610 Pro, and the pressure works fine with > > huion-driver. > > The buttons on the tablet are detected and do things but not what I > > want. > > > > So, I have tried to solve this problem by mapping the scancodes sent by > > these buttons to some unused keys like F13, etc... Then I have used > > 'xbindkeys' to call a script than will launch specific actions with > > 'xvkbd' depending on the current program (myPaint, Krita, etc.). > > > > It seems to work fine, but I was wondering if there was an > > easier/cleaner solution embedded in the digimend project that I have > > missed? > > There is none at the moment, unfortunately. > > However, there is a plan to make the Wacom X driver support generic tablets > better, which would allow to configure the keys as necessary. > > Still, it would take time and would probably mean tackling each Huion tablet > model separately. > > Nick Hi, Ok, thank you for the information. I've finally used AutoKey to re-assign the keys to what I want depending of the application. It works fine and was not too complicated to set up. Pierre |
From: Nikolai K. <sp...@gm...> - 2014-08-11 17:36:24
|
Hi Pierre, On 08/10/2014 11:59 AM, Pierre Vuillemin wrote: > I've just bought a Huion 610 Pro, and the pressure works fine with > huion-driver. > The buttons on the tablet are detected and do things but not what I > want. > > So, I have tried to solve this problem by mapping the scancodes sent by > these buttons to some unused keys like F13, etc... Then I have used > 'xbindkeys' to call a script than will launch specific actions with > 'xvkbd' depending on the current program (myPaint, Krita, etc.). > > It seems to work fine, but I was wondering if there was an > easier/cleaner solution embedded in the digimend project that I have > missed? There is none at the moment, unfortunately. However, there is a plan to make the Wacom X driver support generic tablets better, which would allow to configure the keys as necessary. Still, it would take time and would probably mean tackling each Huion tablet model separately. Nick |
From: Pierre V. <co...@pi...> - 2014-08-10 10:15:03
|
Hi all, I've just bought a Huion 610 Pro, and the pressure works fine with huion-driver. The buttons on the tablet are detected and do things but not what I want. So, I have tried to solve this problem by mapping the scancodes sent by these buttons to some unused keys like F13, etc... Then I have used 'xbindkeys' to call a script than will launch specific actions with 'xvkbd' depending on the current program (myPaint, Krita, etc.). It seems to work fine, but I was wondering if there was an easier/cleaner solution embedded in the digimend project that I have missed? Pierre |
From: Nikolai K. <sp...@gm...> - 2014-08-06 19:12:08
|
Hi Emanuele, On 07/20/2014 10:10 PM, Emanuele Olivetti wrote: > I've just installed huion-driver from github following the instructions. My > tablet Huion H610 works perfectly on Ubuntu 12.04 LTS amd64. Thanks a lot > for the great work! Great! Thank you for the feedback. > Some feedback/questions: > > - I don't know if this is related to the driver, but when using mypaint, as > soon as the tablet is plugged in, the mouse click is not effective anymore > on some items/buttons like in the brush list editor. Nevertheless, the pen > click (on the graphic tablet) works well. As soon as the tablet is > unplugged, the mouse clicks start working again where they did not. I've heard similar problems reported, but didn't try to reproduce them yet, so no answer so far. > - I don't know how to configure the buttons on the left side of the Huion > H610. Is this application dependent? It seems to me that this is not related > to the driver. It isn't configurable currently, unfortunately, and it is not really related to the driver. Nick |
From: Nikolai K. <sp...@gm...> - 2014-08-06 18:30:55
|
Hi everyone, I regretfully announce that I'm officially stopping accepting tablet diagnostics. I was unable to process them for quite a while already due to lack of time and personal issues. Now it is official. I apologise for ruined hopes of everyone who sent diagnostics and was expecting a driver for their tablets, or just a reply for that matter. I haven't managed so far to secure a job which would allow me to work on the project during working hours and I find I have very little energy and time left otherwise. However, I'll continue my attempts. If anyone wishes to employ me for that kind of work or can refer me to such an opening, see my LinkedIn profile [1] for the resume. For now, whenever I can, I'll focus on migrating our website to GitHub pages, where I have a stub already [2], as SourceForge.net hosting of MediaWiki is very slow and MediaWiki itself requires more effort to support and edit. I'll also work on drivers for tablets which I can lay my hands on personally, which is quicker, as compared to diagnosing tablets remotely, which requires more time. In parallel, I'll work on a HOWTO describing how most tablets work and how you can make drivers for them, so more technically-inclined can try to make a driver for their own tablets themselves and perhaps help others. Then, if I have any time left from that, I'll try to follow on the old mail. Thank you everyone who sent their diagnostics and exercised impossible patience waiting for my replies and, once again, please accept my apologies for unmet expectations. Sincerely, Nick [1] https://www.linkedin.com/in/spbnick [2] http://digimend.github.io/ |
From: Ashwyn F. <as...@gm...> - 2014-07-30 15:01:11
|
Hi there, hope this message isn't too annoying, but I submitted tablet diagnositcs around 6 months ago to the devel list for UC Logic tablet 5543:0782 I was just wondering if there's anything else I can do to help development on getting support for this model? Only a bit confused because I haven't seen any indication that the diagnostics were received by anyone... Thanks to everyone who puts their time into this project, just want to know if I should just give up on the tablet and get a more expensive one... Cheers, Ash. |
From: Emanuele O. <ema...@gm...> - 2014-07-20 19:10:50
|
Hi, I've just installed huion-driver from github following the instructions. My tablet Huion H610 works perfectly on Ubuntu 12.04 LTS amd64. Thanks a lot for the great work! Some feedback/questions: - I don't know if this is related to the driver, but when using mypaint, as soon as the tablet is plugged in, the mouse click is not effective anymore on some items/buttons like in the brush list editor. Nevertheless, the pen click (on the graphic tablet) works well. As soon as the tablet is unplugged, the mouse clicks start working again where they did not. - I don't know how to configure the buttons on the left side of the Huion H610. Is this application dependent? It seems to me that this is not related to the driver. Best, Emanuele |
From: Rose N. <r.n...@ho...> - 2014-07-20 17:58:14
|
Is the Yiynova MSP19U+ among the supported tablets? |
From: Nikolai K. <sp...@gm...> - 2014-07-04 21:50:16
|
Hi Stephen, On 07/04/2014 06:25 PM, stephen egts wrote: > Hi there! I have a Yiynova MSP19U and Ubuntu 14.04. I suspect it is unlikely to be supported, at least to a good extent, but it would be good to know what works and how. > I'm going to try to installing Digimend tomorrow, There's usually nothing to install from DIGImend project that could help you make your tablet supported, with the current exception of Huion tablets, as we try to contribute our drivers to upstream. There's certainly nothing from DIGImend that can help with Yiynova at the moment. > but I was wondering if you could include me on your mailing list. Sure, you can subscribe by sending an empty message with "subscribe" subject to dig...@li.... > I'll let you know how it goes and thanks in advance for all of your help! I > can't thank you enough! Thank you. We haven't done much to support these tablets yet, so there is nothing to thank us for, yet. Sincerely, Nick |
From: stephen e. <se...@gm...> - 2014-07-04 15:26:03
|
Hi there! I have a Yiynova MSP19U and Ubuntu 14.04. I'm going to try to installing Digimend tomorrow, but I was wondering if you could include me on your mailing list. I'll let you know how it goes and thanks in advance for all of your help! I can't thank you enough! All the Best Stephen Egts:) |
From: Nikolai K. <sp...@gm...> - 2014-06-20 08:31:41
|
Hi everyone, As SourceForge have finally closed their hosted application service, I've moved DIGImend wiki to a MediaWiki installation on Project Web Space. This means that all page addresses have changed from being http://sourceforge.net/apps/mediawiki/digimend/index.php?title=<TITLE> to http://digimend.sourceforge.net/wiki/<TITLE> where <TITLE> is the page title. Old page URLs currently lead to the project summary page [1]. However, I posted a ticket [2] to site support requesting setting up a redirection, which will hopefully be honored and old URLs will redirect to the new ones seamlessly. In related news, I'm currently investigating the possibility to move the project site to GitHub pages service. GitHub pages uses Jekyll, which with its Liquid template support seems to cover our needs, while at the same time providing a way to edit pages and track changes via Git commits to mostly plain text (markdown) files, which will be more convenient for developers. This would also remove the need to maintain a MediaWiki installation. [1] https://sourceforge.net/projects/digimend/ [2] https://sourceforge.net/p/forge/site-support/7943/ |
From: Mozart C. <moz...@gm...> - 2014-04-25 03:39:18
|
Hello everyone, I would like to know if the huion v3 driver can be installed on Ubuntu / Xubuntu / GnomeUbuntu 14.04 or if there is another, most current and where can I download this driver driver. Thank you. -- Mozart Couto www.mozartcouto.com.br http://blogdodesenhador.blogspot.com<http://mozartcoutoimagens.blogspot.com> |
From: Jake <ha...@ou...> - 2014-03-10 12:41:52
|
Hello there, I'm running Fedora 20, and I've just checked the project out and found out that my newly purchased tablet is in testing. "5543:0781 UC-Logic Tablet TWHA60" Could I ask for some directions to installing digimend along with the test driver for this product? As you can tell, I'm not a wizard at getting around linux at the minute. Thanks! |
From: Timmy . <omi...@ho...> - 2014-02-14 03:20:29
|
Hello I own a Yiynova MSP19u Tablet monitor and I would love to test some drivers for it if there are any. I would love to help in any way I can to get this great tablet running on Linux. 12.4 Please let me know if there is anything I can do. |
From: Andrew H. <job...@gm...> - 2014-02-03 14:35:30
|
Further to this thread ( http://sourceforge.net/mailarchive/message.php?msg_id=31884990): My previous post focused on HID_QUIRK_MULTI_INPUT, which splits the tabletinto multiple devices, one of which (almost) works as a pointer device. The main problem with MULTI_INPUT is that this pointer device has no pressure information. Maybe that's easy to fix. However, I've figured out some more information regarding the tablet without the quirk applied, which I will describe in the rest of this post. AFAICS, the reason that the pen doesn't drive the cursor is that the ABS_X and ABS_Y channels are being reported to evdev as ABS_Z and ABS_RX. Others have had similar problems. This thread seems very relevant, with code snippets: https://bugzilla.redhat.com/show_bug.cgi?id=473144 (especially comments 11, 28 and 42). See also http://www.mail-archive.com/xo...@li.../msg09730.html. The gist of these posts is that the device in question registered two different sets of axes. The first two axes took up channels ABS_X and ABS_Y, leaving only ABS_Z and ABS_RX for the true axes. It's worth noting that ABS_PRESSURE and other messages seem to be handled correctly. In the present case (of the UC-LOGIC TWHA60), the false axes described in the HID header claim to have resolution 40000x25000. The working axes claim 2048x2048. IIRC, there is some known weirdness on this tablet regarding the activation of a proprietary mode with enhanced resolution. If this enhanced mode is not being activated then even after we solve the axis problem, there may be more work to do. Perhaps that should take precedence? Apologies for the lack of copy/pasted debug info in this post. Will provide it either today or tomorrow, so you can get it straight from the horse's mouth (not interpreted through the mind of a newbie :) ). If I haven't updated in the mean-time, please feel free to ask for specific read-outs! It's worth noting that I now have access to a Windows machine, so could capture Windows USB traffic if that sounds useful. Cheers, Andrew |
From: Viktoria S. <vik...@fr...> - 2014-01-31 08:48:37
|
Hi, making Krita compatible with the evdev driver is currently in progress. I don't really know if this is include in the 2.8 pre alpha version, but according to my best knowledge if you compile Krita from git it is there. (You can find instruction for it here: http://www.davidrevoy.com/article/193/guide-building-krita-on-linux-for-cats.html) More information on the progress of this development you can find in this Krita forum thread: http://forum.kde.org/viewtopic.php?f=139&t=98347 (I guess for you the interesting part starts from around page 7.) Kind regards: Viktoria Mozart Couto <moz...@gm...> írta: >Hello, Nikolai, After installing the actual driver for graphics tablets Huion 610, noticed that the tablet works perfectly in GIMP 2.8.10; Works in MyPaint but you must turn on the table on the menu-help-settings GTK input devices. Works in Krita 2.8 Pre-Alpha but does not recognize the pressure function! I'm sending a text file with the data that appears in the terminal when I've launch a version of Krita. I tested this on Ubuntu Studio 10.13 and Linux Mint 15 (this, running kernel 3.9.8. 3.8xo In Kernel driver does not work! Installed but did not work. Had to download and install the 3.9.8 kernel to run). I thought it would be interesting report this to you. Below is the link to see some quick tests on videos: >http://youtu.be/71Yyt7up_tYhttp://youtu.be/g7FDdn0NvFI >http://youtu.be/PSzmMBEGwjshttp://youtu.be/Orzbx3KUhgk >Best!-- Mozart Coutowww.mozartcouto.com.br >http://blogdodesenhador.blogspot.com > >------------------------------------------------------------------------------ >WatchGuard Dimension instantly turns raw network data into actionable >security intelligence. It gives you real-time visual feedback on key >security issues and trends. Skip the complicated setup - simply import >a virtual appliance and go from zero to informed in seconds. >http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk_______________________________________________ >DIGImend-users mailing list >DIG...@li... >https://lists.sourceforge.net/lists/listinfo/digimend-users > |
From: Mozart C. <moz...@gm...> - 2014-01-30 20:51:36
|
Hello, Nikolai, After installing the actual driver for graphics tablets Huion 610, noticed that the tablet works perfectly in GIMP 2.8.10; Works in MyPaint but you must turn on the table on the menu-help-settings GTK input devices. Works in Krita 2.8 Pre-Alpha but does not recognize the pressure function! I'm sending a text file with the data that appears in the terminal when I've launch a version of Krita. I tested this on Ubuntu Studio 10.13 and Linux Mint 15 ( this, running kernel 3.9.8. 3.8xo In Kernel driver does not work! Installed but did not work. Had to download and install the 3.9.8 kernel to run). I thought it would be interesting report this to you. Below is the link to see some quick tests on videos: http://youtu.be/71Yyt7up_tY http://youtu.be/g7FDdn0NvFI http://youtu.be/PSzmMBEGwjs http://youtu.be/Orzbx3KUhgk Best! -- Mozart Couto www.mozartcouto.com.br http://blogdodesenhador.blogspot.com<http://mozartcoutoimagens.blogspot.com> |
From: Andrew H. <job...@gm...> - 2014-01-26 12:07:01
|
(I didn't receive an email from the list so have nothing to reply to. If this starts a new thread, please feel free to delete the old one: all content is copied below.) Minor development: $ sudo modprobe -r usbhid $ sudo modprobe usbhid "quirks=0x5543:0x0781:0x0040" causes the pen to start working. The pen will work until a double-click, or a drag-then-click, and possibly some other combination of clicks. After that the original behaviour (no cursor driving; buttons working) resumes. Pastebin http://pastebin.com/TWyXF6Dv contains the changes to Xorg.0.log after the following operations: 1. Hot-plugging the tablet 2. Moving the pen/clicking some buttons. 3. Running the usbhid quirk hack. 4. Unplugging the tablet. Apparently, quirk 0x40 is HID_QUIRK_MULTI_INPUT. Again, grateful for any guidance on this topic! Cheers, Andrew ---------- Forwarded message ---------- From: Andrew Handley <job...@gm...> Date: 25 January 2014 15:03 Subject: Monoprice TWHA60 (5543:0781) in Mint 15: No cursor movement out-of-box To: DIG...@li... Hi all. My new tablet (observed working under Windows 7) is recognised and loads evdev. Pen buttons and tapping work (correspond to mouse-clicks). However, moving the pen doesn't cause the cursor to move. Running some of the diagnostics (below) suggests that Linux is hearing the cursor movements. `xinput --test` gives correct-looking coords and pressure values. I must be [i]one[/i] step away from getting it working, so am hesitant to try anything heavy-duty like kernel patching (shouldn't be necessary) or custom .conf files (what options could I be missing?). Recent poster http://tinyurl.com/mmgckqm may be related, but has no information. IReadTheManual on http://ubuntuforums.org/archive/index.php/t-1995385.html may also be related. I'm no Linux expert so please feel free to ask simple questions. Also new to mailing lists: hopefully this works and is in the correct format. I've uninstalled the wacom drivers (long shot) and am about to read Favux's excellent support thread http://ubuntuforums.org/archive/index.php/t-1946486.html for ideas. Grateful for any guidance! Cheers, Andrew Following are snippets of diagnostics: =================================================================== uname -a: Linux gemini 3.8.0-35-generic #50-Ubuntu SMP Tue Dec 3 01:24:59 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Mint 15 Olivia, using Mate. Installed evdev driver: 2.7.3-0ubuntu2b2. =================================================================== lsusb: Bus 003 Device 005: ID 5543:0781 UC-Logic Technology Corp. =================================================================== usbhid-dump -me -s 5543:0781 gets me 003:005:000:STREAM 1390650646.343991 09 00 83 03 AB 04 00 00 003:005:000:STREAM 1390650646.347991 09 00 82 03 B8 04 00 00 003:005:000:STREAM 1390650646.351990 09 00 81 03 C5 04 00 00 003:005:000:STREAM 1390650646.355989 09 00 7F 03 D2 04 00 00 003:005:000:STREAM 1390650646.359990 09 00 7E 03 DF 04 00 00 003:005:000:STREAM 1390650646.363995 09 00 7D 03 EC 04 00 00 etc., where the second byte corresponds to buttons, and I can convince myself that the 3rd to 6th bytes are positional. =================================================================== xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ PIXART USB OPTICAL MOUSE id=9 [slave pointer (2)] ⎜ ↳ UC-LOGIC TWHA60 id=11 [slave pointer (2)] ⎜ ↳ UC-LOGIC TWHA60 id=12 [slave pointer (2)] ⎜ ↳ UC-LOGIC TWHA60 id=13 [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)] ↳ Power Button id=8 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)] =================================================================== xinput --test $DEV_NUMBER gives motion a[2]=1249 a[3]=1130 motion a[2]=1246 a[3]=1129 motion a[2]=1243 a[3]=1127 motion a[2]=1240 a[3]=1125 motion a[2]=1237 a[3]=1123 motion a[2]=1234 a[3]=1121 motion a[2]=1231 a[3]=1119 motion a[2]=1228 a[3]=1116 where the coords look correct: origin in top left; max is (2047,2047). Pressure sensitivity seems to be a[4]. Idea: Python script to parse this and manually move the cursor :) =================================================================== Descriptors are Bus 003 Device 005: ID 5543:0781 UC-Logic Technology Corp. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x5543 UC-Logic Technology Corp. idProduct 0x0781 bcdDevice 0.00 iManufacturer 5 UC-LOGIC iProduct 6 TWHA60 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 84 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.11 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 179 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 2 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.11 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 181 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 2 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 2 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.11 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 92 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 8 Device Status: 0x0000 (Bus Powered) |
From: Andrew H. <job...@gm...> - 2014-01-25 15:04:21
|
Hi all. My new tablet (observed working under Windows 7) is recognised and loads evdev. Pen buttons and tapping work (correspond to mouse-clicks). However, moving the pen doesn't cause the cursor to move. Running some of the diagnostics (below) suggests that Linux is hearing the cursor movements. `xinput --test` gives correct-looking coords and pressure values. I must be [i]one[/i] step away from getting it working, so am hesitant to try anything heavy-duty like kernel patching (shouldn't be necessary) or custom .conf files (what options could I be missing?). Recent poster http://tinyurl.com/mmgckqm may be related, but has no information. IReadTheManual on http://ubuntuforums.org/archive/index.php/t-1995385.html may also be related. I'm no Linux expert so please feel free to ask simple questions. Also new to mailing lists: hopefully this works and is in the correct format. I've uninstalled the wacom drivers (long shot) and am about to read Favux's excellent support thread http://ubuntuforums.org/archive/index.php/t-1946486.html for ideas. Grateful for any guidance! Cheers, Andrew Following are snippets of diagnostics: =================================================================== uname -a: Linux gemini 3.8.0-35-generic #50-Ubuntu SMP Tue Dec 3 01:24:59 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Mint 15 Olivia, using Mate. Installed evdev driver: 2.7.3-0ubuntu2b2. =================================================================== lsusb: Bus 003 Device 005: ID 5543:0781 UC-Logic Technology Corp. =================================================================== usbhid-dump -me -s 5543:0781 gets me 003:005:000:STREAM 1390650646.343991 09 00 83 03 AB 04 00 00 003:005:000:STREAM 1390650646.347991 09 00 82 03 B8 04 00 00 003:005:000:STREAM 1390650646.351990 09 00 81 03 C5 04 00 00 003:005:000:STREAM 1390650646.355989 09 00 7F 03 D2 04 00 00 003:005:000:STREAM 1390650646.359990 09 00 7E 03 DF 04 00 00 003:005:000:STREAM 1390650646.363995 09 00 7D 03 EC 04 00 00 etc., where the second byte corresponds to buttons, and I can convince myself that the 3rd to 6th bytes are positional. =================================================================== xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ PIXART USB OPTICAL MOUSE id=9 [slave pointer (2)] ⎜ ↳ UC-LOGIC TWHA60 id=11 [slave pointer (2)] ⎜ ↳ UC-LOGIC TWHA60 id=12 [slave pointer (2)] ⎜ ↳ UC-LOGIC TWHA60 id=13 [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)] ↳ Power Button id=8 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)] =================================================================== xinput --test $DEV_NUMBER gives motion a[2]=1249 a[3]=1130 motion a[2]=1246 a[3]=1129 motion a[2]=1243 a[3]=1127 motion a[2]=1240 a[3]=1125 motion a[2]=1237 a[3]=1123 motion a[2]=1234 a[3]=1121 motion a[2]=1231 a[3]=1119 motion a[2]=1228 a[3]=1116 where the coords look correct: origin in top left; max is (2047,2047). Pressure sensitivity seems to be a[4]. Idea: Python script to parse this and manually move the cursor :) =================================================================== Descriptors are Bus 003 Device 005: ID 5543:0781 UC-Logic Technology Corp. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x5543 UC-Logic Technology Corp. idProduct 0x0781 bcdDevice 0.00 iManufacturer 5 UC-LOGIC iProduct 6 TWHA60 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 84 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.11 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 179 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 2 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.11 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 181 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 2 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 2 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.11 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 92 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 8 Device Status: 0x0000 (Bus Powered) |
From: Ólafur B. <ol...@te...> - 2014-01-16 17:01:06
|
Hey, Has anyone tried to configure evdev with yiynova MVP22U? I am unable to get the pointer to move, however I see the /dev/input/event0 spit's out alot of stuff when I move the stylus on the screen. Bus 003 Device 002: ID 5543:004d UC-Logic Technology Corp. Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x5543 UC-Logic Technology Corp. idProduct 0x004d bcdDevice 0.00 iManufacturer 5 iProduct 6 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 84 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.11 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 179 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 2 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.11 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 181 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 2 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 2 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.11 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 92 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 8 Best regards, Olafur Bergsson Technical Manager Tern Systems hf. Hlidasmari 15 IS-202 Kopavogur; Iceland Comp Tel +354 5-250-500 Comp Fax:+354 5-250-501 ola...@te... www.tern.is |