digimend-devel Mailing List for DIGImend (Page 15)
Brought to you by:
spb_nick
Menu
▾
▴
digimend-devel — Development matters
You can subscribe to this list here.
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(8) |
Jun
(27) |
Jul
(54) |
Aug
(54) |
Sep
(13) |
Oct
(20) |
Nov
(7) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2013 |
Jan
(3) |
Feb
(3) |
Mar
(6) |
Apr
(1) |
May
(8) |
Jun
(5) |
Jul
(4) |
Aug
(10) |
Sep
(44) |
Oct
(12) |
Nov
(5) |
Dec
(14) |
| 2014 |
Jan
(16) |
Feb
(3) |
Mar
(3) |
Apr
(5) |
May
(2) |
Jun
(14) |
Jul
(38) |
Aug
(15) |
Sep
(15) |
Oct
(12) |
Nov
(38) |
Dec
(31) |
| 2015 |
Jan
(73) |
Feb
(71) |
Mar
(57) |
Apr
(36) |
May
(33) |
Jun
(20) |
Jul
(4) |
Aug
(5) |
Sep
(1) |
Oct
(11) |
Nov
(2) |
Dec
(6) |
| 2016 |
Jan
(7) |
Feb
(3) |
Mar
(6) |
Apr
(2) |
May
(7) |
Jun
(5) |
Jul
(3) |
Aug
(5) |
Sep
(5) |
Oct
(8) |
Nov
(13) |
Dec
|
|
From: Nikolai K. <sp...@gm...> - 2015-01-05 20:58:45
|
On 01/05/2015 11:13 AM, Vikko Okviandho wrote: > Here it is Hmm, they look the same. Could it be that you still used the original and not the specially-built usbhid-dump by accident? Can you recall how your commands looked when you recorded these traces? Otherwise this would mean that the initialization sequence doesn't work and we'll need to find a new one, and that won't be easy. Thank you. Nick |
|
From: Nikolai K. <sp...@gm...> - 2015-01-05 12:23:22
|
On 01/05/2015 11:13 AM, Vikko Okviandho wrote: > Here it is Thanks! I'll take a look in the evening (in about 8 hours). Nick |
|
From: Nikolai K. <sp...@gm...> - 2015-01-05 12:22:57
|
On 01/05/2015 10:49 AM, Vikko Okviandho wrote: > Nevermind. My idiocy took over. Fixed the configure phase error by running > sudo apt-get install libusb-1.0-0-dev Ah, sorry, my fault, I gave you build dependencies of another package of mine. Glad you figured it out. Nick On 01/05/2015 10:49 AM, Vikko Okviandho wrote: > Nevermind. My idiocy took over. Fixed the configure phase error by running sudo apt-get install libusb-1.0-0-dev > > On 5 January 2015 at 15:46, Vikko Okviandho <tc...@gm... <mailto:tc...@gm...>> wrote: > > Unfortunately, the process of compiling failed. The problem was in configure phase. > > "..checking for LIBUSB... no > configure: error: Package requirements (libusb-1.0 >= 1.0.0) were not met: > > No package 'libusb-1.0' found.." > > I was also unable to install the libusb package. > > Here's the output > > sudo apt-get install libusb > Reading package lists... Done > Building dependency tree > Reading state information... Done > E: Unable to locate package libusb > > I already do apt-get update with no error. What should I do? Manually download the package? Where can I download? I mean, from multiverse or universe? Or else? > > On 4 January 2015 at 22:05, Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...>> wrote: > > Hi Vikko, > > I'll be copying digimend-devel from now on, so others can benefit from our > discussion. I should've done it from the start. Please keep the maillist in > the CC by answering using "Reply to all". > > On 01/04/2015 01:11 PM, Vikko Okviandho wrote: > > Err.. sorry. But I don't get what to do with the archive kye.zip (called > usbhid-dump-kye.zip when downloaded) > Should I install this or what? And how do I start with "Collect raw > samples"? > > > You don't need to install it, but you need to build it. > > First you'll need to install build dependencies: > > sudo apt-get install autotools-dev autoconf automake libtool pkg-config libxml2-dev > > Then unpack the archive and go into the resulting directory and build the > package: > > ./bootstrap && ./configure && make > > Please send the output, if it fails. > > If it succeeds, you'll then be able to run usbhid-dump from the same directory > as such: > > src/usbhid-dump > > You'll be able to dump input from your tablet as such: > > src/usbhid-dump -m 0458:501a -es > > If it works, please proceed with "Collect raw samples" and further from the > diagnostic collection HOWTO, using the command above, redirecting the output > to files, as described. > > Thank you. > > Nick > > On 01/04/2015 01:11 PM, Vikko Okviandho wrote: > > Err.. sorry. But I don't get what to do with the archive kye.zip (called usbhid-dump-kye.zip when downloaded) > Should I install this or what? And how do I start with "Collect raw samples"? > > On 4 January 2015 at 05:55, Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> wrote: > > Hi Vikko, > > On 12/20/2014 12:28 PM, Vikko Okviandho wrote: > > I'm still waiting > > > Thanks for the diagnostics. The tablet behavior and the report descriptor look > quite different from the previous version, so we won't get away with a simple > driver modification. > > We need to see if it will respond to the usual initialization attempt and how. > > Could you please try collecting the diagnostics with this version of > usbhid-dump, which tries to initialize the tablet before dumping: > > https://github.com/DIGImend/____usbhid-dump/archive/kye.zip <https://github.com/DIGImend/__usbhid-dump/archive/kye.zip> <https://github.com/DIGImend/__usbhid-dump/archive/kye.zip <https://github.com/DIGImend/usbhid-dump/archive/kye.zip>> > > You can start with "Collect raw samples", as the previous steps will produce > the same results. > > Thank you. > > Nick > > On 12/20/2014 12:28 PM, Vikko Okviandho wrote: > > I'm still waiting > > On 15 December 2014 at 06:42, Vikko Okviandho <tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>>>> wrote: > > Well.. I have the mouse bundled. So I went until the mouse part. Here's the output. I can do this again if necessary. > > On 15 December 2014 at 02:37, Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>> wrote: > > On 12/14/2014 09:22 PM, Vikko Okviandho wrote: > > Same as before and everyone. Able to move the pointer, but no clicks. And > absolutely no pressure. Getting desperate here. Hahaha.. Btw, it's 0x501a. > > > Alright, could you please collect the diagnostics according to this page: > http://digimend.github.io/______support/howto/trbl/______diagnostics/ <http://digimend.github.io/____support/howto/trbl/____diagnostics/> <http://digimend.github.io/____support/howto/trbl/____diagnostics/ <http://digimend.github.io/__support/howto/trbl/__diagnostics/>> <http://digimend.github.io/____support/howto/trbl/____diagnostics/ <http://digimend.github.io/__support/howto/trbl/__diagnostics/> <http://digimend.github.io/__support/howto/trbl/__diagnostics/ <http://digimend.github.io/support/howto/trbl/diagnostics/>>> > > Up to and including the pen coordinates, no need to go further for now. > > BTW, does your tablet have a mouse? > > Thank you. > > Nick > > On 12/14/2014 09:22 PM, Vikko Okviandho wrote: > > Same as before and everyone. Able to move the pointer, but no clicks. And absolutely no pressure. Getting desperate here. Hahaha.. Btw, it's 0x501a. > > On 15 December 2014 at 02:19, Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>>> wrote: > > On 12/14/2014 09:08 PM, Vikko Okviandho wrote: > > Here's my uname -r output 3.13.0-40-generic > Should I still install linux-image-3.11.0-26-generic? > > > No, that will do. What's the tablet's behavior with that kernel? > > Nick > > On 15 December 2014 at 02:03, Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>>>> wrote: > > On 12/14/2014 08:22 PM, Vikko Okviandho wrote: > > I downloaded and installed the one from > http://kernel.ubuntu.com/~__________kernel-ppa/mainline/v3.4-__________precise/ <http://kernel.ubuntu.com/~________kernel-ppa/mainline/v3.4-________precise/> <http://kernel.ubuntu.com/~________kernel-ppa/mainline/v3.4-________precise/ <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/>> <http://kernel.ubuntu.com/~________kernel-ppa/mainline/v3.4-________precise/ <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/> <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/>>> <http://kernel.ubuntu.com/~________kernel-ppa/mainline/v3.4-________precise/ <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/> <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/>> <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ > <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/>>>> <http://kernel.ubuntu.com/~________kernel-ppa/mainline/v3.4-________precise/ <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/> <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/>> <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/>>> <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/> > <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/>> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/> <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/ <http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/>>>>> > > > Um, I'm not sure if that is official. > > But it got worse. I can't even move the pointer anymore and the indicator > light of the tablet lit continuously until I put it off from my laptop. > What's next? > > > Try running "sudo apt-get install linux-image-3.11.0-26-generic" and then > rebooting into that kernel. > > Nick > > On 12/14/2014 08:22 PM, Vikko Okviandho wrote: > > I downloaded and installed the one from http://kernel.ubuntu.com/~__________kernel-ppa/mainline/v3.4-__________precise/ <http://kernel.ubuntu.com/~________kernel-ppa/mainline/v3.4-________precise/> <http://kernel.ubuntu.com/~________kernel-ppa/mainline/v3.4-________precise/ <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/>> <http://kernel.ubuntu.com/~________kernel-ppa/mainline/v3.4-________precise/ <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/> <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/>>> <http://kernel.ubuntu.com/~________kernel-ppa/mainline/v3.4-________precise/ <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/> <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ > <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/>> <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/>>>> <http://kernel.ubuntu.com/~________kernel-ppa/mainline/v3.4-________precise/ <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/> <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/>> <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/>>> > <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/>> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/> <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/ <http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/>>>>> > But it got worse. I can't even move the pointer anymore and the indicator light of the tablet lit continuously until I put it off from my laptop. What's next? > > On 15 December 2014 at 00:47, Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>>> <mailto:sp...@gm... > <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>>>>__> wrote: > > Yes, the one from the official repositories. > > On Dec 14, 2014 7:44 PM, "Vikko Okviandho" <tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>>>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>>>>> <mailto:tc...@gm... > <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>>>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>>>>>>__> wrote: > > I'll try. Should I use the 'official Ubuntu' one? > > On 14 December 2014 at 23:28, Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>>> > <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>>>>__> wrote: > > Hi Vikko, > > On 12/12/2014 05:02 AM, Vikko Okviandho wrote: > > First, I want to apologize in advance for any bother I would make to you. > > > Not a problem, if you're prepared to wait for my answers :) > > So, I got this Genius (KYE) MousePen i608x drawing tablet few months ago. > And since then, I tried to make it usable on Ubuntu 12.04.5. I looked > everywhere, even I tried to compile your Digimend work > (linux_3.2.0-31.50+digimend.6.____________1) myself to no avail. I tried to download the > .deb, but SF (or my ISP) won't allow me. > > What should I do? I searched in Ubuntu Forums and found no answer since the > links are expired or no more available. I guess the posts are too old so > they removed them. > > I would appreciate any helps. I don't want to use it under windows > exclusively. Even the tablet performs not so well under windows. > > > First of all, AFAIK, your tablet should work on kernels starting with v3.4. > It seems that Ubuntu 12.04 should have kernel v3.11 available, try installing > and booting into it and check if the tablet works. > > Nick > > > > > > > > > > |
|
From: Vikko O. <tc...@gm...> - 2015-01-05 09:14:02
|
Here it is On 5 January 2015 at 15:49, Vikko Okviandho <tc...@gm...> wrote: > Nevermind. My idiocy took over. Fixed the configure phase error by > running sudo apt-get install libusb-1.0-0-dev > > On 5 January 2015 at 15:46, Vikko Okviandho <tc...@gm...> wrote: > >> Unfortunately, the process of compiling failed. The problem was in >> configure phase. >> >> "..checking for LIBUSB... no >> configure: error: Package requirements (libusb-1.0 >= 1.0.0) were not met: >> >> No package 'libusb-1.0' found.." >> >> I was also unable to install the libusb package. >> >> Here's the output >> >> sudo apt-get install libusb >> Reading package lists... Done >> Building dependency tree >> Reading state information... Done >> E: Unable to locate package libusb >> >> I already do apt-get update with no error. What should I do? Manually >> download the package? Where can I download? I mean, from multiverse or >> universe? Or else? >> >> On 4 January 2015 at 22:05, Nikolai Kondrashov <sp...@gm...> wrote: >> >>> Hi Vikko, >>> >>> I'll be copying digimend-devel from now on, so others can benefit from >>> our >>> discussion. I should've done it from the start. Please keep the maillist >>> in >>> the CC by answering using "Reply to all". >>> >>> On 01/04/2015 01:11 PM, Vikko Okviandho wrote: >>> >>>> Err.. sorry. But I don't get what to do with the archive kye.zip (called >>>> usbhid-dump-kye.zip when downloaded) >>>> Should I install this or what? And how do I start with "Collect raw >>>> samples"? >>>> >>> >>> You don't need to install it, but you need to build it. >>> >>> First you'll need to install build dependencies: >>> >>> sudo apt-get install autotools-dev autoconf automake libtool >>> pkg-config libxml2-dev >>> >>> Then unpack the archive and go into the resulting directory and build the >>> package: >>> >>> ./bootstrap && ./configure && make >>> >>> Please send the output, if it fails. >>> >>> If it succeeds, you'll then be able to run usbhid-dump from the same >>> directory >>> as such: >>> >>> src/usbhid-dump >>> >>> You'll be able to dump input from your tablet as such: >>> >>> src/usbhid-dump -m 0458:501a -es >>> >>> If it works, please proceed with "Collect raw samples" and further from >>> the >>> diagnostic collection HOWTO, using the command above, redirecting the >>> output >>> to files, as described. >>> >>> Thank you. >>> >>> Nick >>> >>> On 01/04/2015 01:11 PM, Vikko Okviandho wrote: >>> >>>> Err.. sorry. But I don't get what to do with the archive kye.zip >>>> (called usbhid-dump-kye.zip when downloaded) >>>> Should I install this or what? And how do I start with "Collect raw >>>> samples"? >>>> >>>> On 4 January 2015 at 05:55, Nikolai Kondrashov <sp...@gm... >>>> <mailto:sp...@gm...>> wrote: >>>> >>>> Hi Vikko, >>>> >>>> On 12/20/2014 12:28 PM, Vikko Okviandho wrote: >>>> >>>> I'm still waiting >>>> >>>> >>>> Thanks for the diagnostics. The tablet behavior and the report >>>> descriptor look >>>> quite different from the previous version, so we won't get away >>>> with a simple >>>> driver modification. >>>> >>>> We need to see if it will respond to the usual initialization >>>> attempt and how. >>>> >>>> Could you please try collecting the diagnostics with this version of >>>> usbhid-dump, which tries to initialize the tablet before dumping: >>>> >>>> https://github.com/DIGImend/__usbhid-dump/archive/kye.zip < >>>> https://github.com/DIGImend/usbhid-dump/archive/kye.zip> >>>> >>>> You can start with "Collect raw samples", as the previous steps >>>> will produce >>>> the same results. >>>> >>>> Thank you. >>>> >>>> Nick >>>> >>>> On 12/20/2014 12:28 PM, Vikko Okviandho wrote: >>>> >>>> I'm still waiting >>>> >>>> On 15 December 2014 at 06:42, Vikko Okviandho < >>>> tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... >>>> <mailto:tc...@gm...>>> wrote: >>>> >>>> Well.. I have the mouse bundled. So I went until the mouse >>>> part. Here's the output. I can do this again if necessary. >>>> >>>> On 15 December 2014 at 02:37, Nikolai Kondrashov < >>>> sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... >>>> <mailto:sp...@gm...>>> wrote: >>>> >>>> On 12/14/2014 09:22 PM, Vikko Okviandho wrote: >>>> >>>> Same as before and everyone. Able to move the >>>> pointer, but no clicks. And >>>> absolutely no pressure. Getting desperate here. >>>> Hahaha.. Btw, it's 0x501a. >>>> >>>> >>>> Alright, could you please collect the diagnostics >>>> according to this page: >>>> http://digimend.github.io/____support/howto/trbl/____ >>>> diagnostics/ <http://digimend.github.io/__support/howto/trbl/__ >>>> diagnostics/> <http://digimend.github.io/__support/howto/trbl/__ >>>> diagnostics/ <http://digimend.github.io/support/howto/trbl/diagnostics/ >>>> >> >>>> >>>> Up to and including the pen coordinates, no need to go >>>> further for now. >>>> >>>> BTW, does your tablet have a mouse? >>>> >>>> Thank you. >>>> >>>> Nick >>>> >>>> On 12/14/2014 09:22 PM, Vikko Okviandho wrote: >>>> >>>> Same as before and everyone. Able to move the >>>> pointer, but no clicks. And absolutely no pressure. Getting desperate here. >>>> Hahaha.. Btw, it's 0x501a. >>>> >>>> On 15 December 2014 at 02:19, Nikolai Kondrashov < >>>> sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... >>>> <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto: >>>> sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>> >>>> wrote: >>>> >>>> On 12/14/2014 09:08 PM, Vikko Okviandho wrote: >>>> >>>> Here's my uname -r output >>>> 3.13.0-40-generic >>>> Should I still install >>>> linux-image-3.11.0-26-generic? >>>> >>>> >>>> No, that will do. What's the tablet's >>>> behavior with that kernel? >>>> >>>> Nick >>>> >>>> On 15 December 2014 at 02:03, Nikolai >>>> Kondrashov <sp...@gm... <mailto:sp...@gm...> <mailto: >>>> sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... >>>> <mailto:sp...@gm...> <mailto:sp...@gm... <mailto: >>>> sp...@gm...>>> <mailto:sp...@gm... <mailto: >>>> sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> >>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto: >>>> sp...@gm... <mailto:sp...@gm...>>>>> wrote: >>>> >>>> On 12/14/2014 08:22 PM, Vikko >>>> Okviandho wrote: >>>> >>>> I downloaded and installed the >>>> one from >>>> http://kernel.ubuntu.com/~________kernel-ppa/mainline/v3.4-_ >>>> _______precise/ <http://kernel.ubuntu.com/~___ >>>> ___kernel-ppa/mainline/v3.4-______precise/> < >>>> http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ >>>> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/>> >>>> <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-__ >>>> ____precise/ <http://kernel.ubuntu.com/~___ >>>> _kernel-ppa/mainline/v3.4-____precise/> <http://kernel.ubuntu.com/~___ >>>> _kernel-ppa/mainline/v3.4-____precise/ <http://kernel.ubuntu.com/~__ >>>> kernel-ppa/mainline/v3.4-__precise/>>> <http://kernel.ubuntu.com/~___ >>>> ___kernel-ppa/mainline/v3.4-______precise/ < >>>> http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/> < >>>> http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ < >>>> http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/>> < >>>> http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ >>>> <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__ >>>> precise/> <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__ >>>> precise/ <http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/ >>>> >>>> >>>> >>>> >>>> Um, I'm not sure if that is official. >>>> >>>> But it got worse. I can't even >>>> move the pointer anymore and the indicator >>>> light of the tablet lit >>>> continuously until I put it off from my laptop. >>>> What's next? >>>> >>>> >>>> Try running "sudo apt-get install >>>> linux-image-3.11.0-26-generic" and then >>>> rebooting into that kernel. >>>> >>>> Nick >>>> >>>> On 12/14/2014 08:22 PM, Vikko >>>> Okviandho wrote: >>>> >>>> I downloaded and installed the >>>> one from http://kernel.ubuntu.com/~________kernel-ppa/mainline/v3.4-_ >>>> _______precise/ <http://kernel.ubuntu.com/~___ >>>> ___kernel-ppa/mainline/v3.4-______precise/> < >>>> http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ >>>> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/>> >>>> <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-__ >>>> ____precise/ <http://kernel.ubuntu.com/~___ >>>> _kernel-ppa/mainline/v3.4-____precise/> <http://kernel.ubuntu.com/~___ >>>> _kernel-ppa/mainline/v3.4-____precise/ <http://kernel.ubuntu.com/~__ >>>> kernel-ppa/mainline/v3.4-__precise/>>> <http://kernel.ubuntu.com/~___ >>>> ___kernel-ppa/mainline/v3.4-______precise/ < >>>> http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/> < >>>> http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ < >>>> http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/>> >>>> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____ >>>> precise/ <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__ >>>> precise/> <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__ >>>> precise/ <http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/ >>>> >>>> >>>> But it got worse. I can't even >>>> move the pointer anymore and the indicator light of the tablet lit >>>> continuously until I put it off from my laptop. What's next? >>>> >>>> On 15 December 2014 at 00:47, >>>> Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...> >>>> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto: >>>> sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... >>>> <mailto:sp...@gm...>>> <mailto:sp...@gm... <mailto: >>>> sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> >>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto: >>>> sp...@gm... <mailto:sp...@gm...>>>> <mailto: >>>> sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... >>>> <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto: >>>> sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> >>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto: >>>> sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... >>>> <mailto:sp...@gm...> <mailto:sp...@gm... <mailto: >>>> sp...@gm...>>>>>> wrote: >>>> >>>> Yes, the one from the >>>> official repositories. >>>> >>>> On Dec 14, 2014 7:44 PM, >>>> "Vikko Okviandho" <tc...@gm... <mailto:tc...@gm...> >>>> <mailto:tc...@gm... <mailto:tc...@gm...>> <mailto: >>>> tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... >>>> <mailto:tc...@gm...>>> <mailto:tc...@gm... <mailto: >>>> tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>> >>>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto: >>>> tc...@gm... <mailto:tc...@gm...>>>> <mailto: >>>> tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... >>>> <mailto:tc...@gm...>> <mailto:tc...@gm... <mailto: >>>> tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>>> >>>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto: >>>> tc...@gm... <mailto:tc...@gm...>> <mailto:tc...@gm... >>>> <mailto:tc...@gm...> <mailto:tc...@gm... <mailto: >>>> tc...@gm...>>>>>> wrote: >>>> >>>> I'll try. Should I use >>>> the 'official Ubuntu' one? >>>> >>>> On 14 December 2014 at >>>> 23:28, Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...> >>>> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto: >>>> sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... >>>> <mailto:sp...@gm...>>> <mailto:sp...@gm... <mailto: >>>> sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> >>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto: >>>> sp...@gm... <mailto:sp...@gm...>>>> <mailto: >>>> sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... >>>> <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto: >>>> sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> >>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto: >>>> sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... >>>> <mailto:sp...@gm...> <mailto:sp...@gm... <mailto: >>>> sp...@gm...>>>>>> wrote: >>>> >>>> Hi Vikko, >>>> >>>> On 12/12/2014 05:02 >>>> AM, Vikko Okviandho wrote: >>>> >>>> First, I want >>>> to apologize in advance for any bother I would make to you. >>>> >>>> >>>> Not a problem, if >>>> you're prepared to wait for my answers :) >>>> >>>> So, I got this >>>> Genius (KYE) MousePen i608x drawing tablet few months ago. >>>> And since then, >>>> I tried to make it usable on Ubuntu 12.04.5. I looked >>>> everywhere, >>>> even I tried to compile your Digimend work >>>> >>>> (linux_3.2.0-31.50+digimend.6.__________1) myself to no avail. I tried >>>> to download the >>>> .deb, but SF >>>> (or my ISP) won't allow me. >>>> >>>> What should I >>>> do? I searched in Ubuntu Forums and found no answer since the >>>> links are >>>> expired or no more available. I guess the posts are too old so >>>> they removed >>>> them. >>>> >>>> I would >>>> appreciate any helps. I don't want to use it under windows >>>> exclusively. >>>> Even the tablet performs not so well under windows. >>>> >>>> >>>> First of all, >>>> AFAIK, your tablet should work on kernels starting with v3.4. >>>> It seems that >>>> Ubuntu 12.04 should have kernel v3.11 available, try installing >>>> and booting into it >>>> and check if the tablet works. >>>> >>>> Nick >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> >> > |
|
From: Vikko O. <tc...@gm...> - 2015-01-05 08:50:13
|
Nevermind. My idiocy took over. Fixed the configure phase error by running sudo apt-get install libusb-1.0-0-dev On 5 January 2015 at 15:46, Vikko Okviandho <tc...@gm...> wrote: > Unfortunately, the process of compiling failed. The problem was in > configure phase. > > "..checking for LIBUSB... no > configure: error: Package requirements (libusb-1.0 >= 1.0.0) were not met: > > No package 'libusb-1.0' found.." > > I was also unable to install the libusb package. > > Here's the output > > sudo apt-get install libusb > Reading package lists... Done > Building dependency tree > Reading state information... Done > E: Unable to locate package libusb > > I already do apt-get update with no error. What should I do? Manually > download the package? Where can I download? I mean, from multiverse or > universe? Or else? > > On 4 January 2015 at 22:05, Nikolai Kondrashov <sp...@gm...> wrote: > >> Hi Vikko, >> >> I'll be copying digimend-devel from now on, so others can benefit from our >> discussion. I should've done it from the start. Please keep the maillist >> in >> the CC by answering using "Reply to all". >> >> On 01/04/2015 01:11 PM, Vikko Okviandho wrote: >> >>> Err.. sorry. But I don't get what to do with the archive kye.zip (called >>> usbhid-dump-kye.zip when downloaded) >>> Should I install this or what? And how do I start with "Collect raw >>> samples"? >>> >> >> You don't need to install it, but you need to build it. >> >> First you'll need to install build dependencies: >> >> sudo apt-get install autotools-dev autoconf automake libtool >> pkg-config libxml2-dev >> >> Then unpack the archive and go into the resulting directory and build the >> package: >> >> ./bootstrap && ./configure && make >> >> Please send the output, if it fails. >> >> If it succeeds, you'll then be able to run usbhid-dump from the same >> directory >> as such: >> >> src/usbhid-dump >> >> You'll be able to dump input from your tablet as such: >> >> src/usbhid-dump -m 0458:501a -es >> >> If it works, please proceed with "Collect raw samples" and further from >> the >> diagnostic collection HOWTO, using the command above, redirecting the >> output >> to files, as described. >> >> Thank you. >> >> Nick >> >> On 01/04/2015 01:11 PM, Vikko Okviandho wrote: >> >>> Err.. sorry. But I don't get what to do with the archive kye.zip (called >>> usbhid-dump-kye.zip when downloaded) >>> Should I install this or what? And how do I start with "Collect raw >>> samples"? >>> >>> On 4 January 2015 at 05:55, Nikolai Kondrashov <sp...@gm... >>> <mailto:sp...@gm...>> wrote: >>> >>> Hi Vikko, >>> >>> On 12/20/2014 12:28 PM, Vikko Okviandho wrote: >>> >>> I'm still waiting >>> >>> >>> Thanks for the diagnostics. The tablet behavior and the report >>> descriptor look >>> quite different from the previous version, so we won't get away with >>> a simple >>> driver modification. >>> >>> We need to see if it will respond to the usual initialization >>> attempt and how. >>> >>> Could you please try collecting the diagnostics with this version of >>> usbhid-dump, which tries to initialize the tablet before dumping: >>> >>> https://github.com/DIGImend/__usbhid-dump/archive/kye.zip < >>> https://github.com/DIGImend/usbhid-dump/archive/kye.zip> >>> >>> You can start with "Collect raw samples", as the previous steps will >>> produce >>> the same results. >>> >>> Thank you. >>> >>> Nick >>> >>> On 12/20/2014 12:28 PM, Vikko Okviandho wrote: >>> >>> I'm still waiting >>> >>> On 15 December 2014 at 06:42, Vikko Okviandho <tc...@gm... >>> <mailto:tc...@gm...> <mailto:tc...@gm... <mailto: >>> tc...@gm...>>> wrote: >>> >>> Well.. I have the mouse bundled. So I went until the mouse >>> part. Here's the output. I can do this again if necessary. >>> >>> On 15 December 2014 at 02:37, Nikolai Kondrashov < >>> sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... >>> <mailto:sp...@gm...>>> wrote: >>> >>> On 12/14/2014 09:22 PM, Vikko Okviandho wrote: >>> >>> Same as before and everyone. Able to move the >>> pointer, but no clicks. And >>> absolutely no pressure. Getting desperate here. >>> Hahaha.. Btw, it's 0x501a. >>> >>> >>> Alright, could you please collect the diagnostics >>> according to this page: >>> http://digimend.github.io/____support/howto/trbl/____ >>> diagnostics/ <http://digimend.github.io/__support/howto/trbl/__ >>> diagnostics/> <http://digimend.github.io/__support/howto/trbl/__ >>> diagnostics/ <http://digimend.github.io/support/howto/trbl/diagnostics/ >>> >> >>> >>> Up to and including the pen coordinates, no need to go >>> further for now. >>> >>> BTW, does your tablet have a mouse? >>> >>> Thank you. >>> >>> Nick >>> >>> On 12/14/2014 09:22 PM, Vikko Okviandho wrote: >>> >>> Same as before and everyone. Able to move the >>> pointer, but no clicks. And absolutely no pressure. Getting desperate here. >>> Hahaha.. Btw, it's 0x501a. >>> >>> On 15 December 2014 at 02:19, Nikolai Kondrashov < >>> sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... >>> <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto: >>> sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>> >>> wrote: >>> >>> On 12/14/2014 09:08 PM, Vikko Okviandho wrote: >>> >>> Here's my uname -r output 3.13.0-40-generic >>> Should I still install >>> linux-image-3.11.0-26-generic? >>> >>> >>> No, that will do. What's the tablet's behavior >>> with that kernel? >>> >>> Nick >>> >>> On 15 December 2014 at 02:03, Nikolai >>> Kondrashov <sp...@gm... <mailto:sp...@gm...> <mailto: >>> sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... >>> <mailto:sp...@gm...> <mailto:sp...@gm... <mailto: >>> sp...@gm...>>> <mailto:sp...@gm... <mailto:sp...@gm...> >>> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto: >>> sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... >>> <mailto:sp...@gm...>>>>> wrote: >>> >>> On 12/14/2014 08:22 PM, Vikko >>> Okviandho wrote: >>> >>> I downloaded and installed the >>> one from >>> http://kernel.ubuntu.com/~________kernel-ppa/mainline/v3.4-_ >>> _______precise/ <http://kernel.ubuntu.com/~___ >>> ___kernel-ppa/mainline/v3.4-______precise/> < >>> http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ >>> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/>> < >>> http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ >>> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/> < >>> http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ < >>> http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/>>> < >>> http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ >>> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/> < >>> http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ < >>> http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/>> < >>> http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ >>> <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/> >>> <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/ < >>> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/>>>> >>> >>> >>> Um, I'm not sure if that is official. >>> >>> But it got worse. I can't even >>> move the pointer anymore and the indicator >>> light of the tablet lit >>> continuously until I put it off from my laptop. >>> What's next? >>> >>> >>> Try running "sudo apt-get install >>> linux-image-3.11.0-26-generic" and then >>> rebooting into that kernel. >>> >>> Nick >>> >>> On 12/14/2014 08:22 PM, Vikko >>> Okviandho wrote: >>> >>> I downloaded and installed the >>> one from http://kernel.ubuntu.com/~________kernel-ppa/mainline/v3.4-_ >>> _______precise/ <http://kernel.ubuntu.com/~___ >>> ___kernel-ppa/mainline/v3.4-______precise/> < >>> http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ >>> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/>> < >>> http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ >>> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/> < >>> http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ < >>> http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/>>> < >>> http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ >>> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/> < >>> http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ < >>> http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/>> >>> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____ >>> precise/ <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__ >>> precise/> <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__ >>> precise/ <http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/ >>> >>>> >>> But it got worse. I can't even >>> move the pointer anymore and the indicator light of the tablet lit >>> continuously until I put it off from my laptop. What's next? >>> >>> On 15 December 2014 at 00:47, >>> Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...> >>> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto: >>> sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... >>> <mailto:sp...@gm...>>> <mailto:sp...@gm... <mailto: >>> sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> >>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto: >>> sp...@gm... <mailto:sp...@gm...>>>> <mailto: >>> sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... >>> <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto: >>> sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> >>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto: >>> sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... >>> <mailto:sp...@gm...> <mailto:sp...@gm... <mailto: >>> sp...@gm...>>>>>> wrote: >>> >>> Yes, the one from the >>> official repositories. >>> >>> On Dec 14, 2014 7:44 PM, >>> "Vikko Okviandho" <tc...@gm... <mailto:tc...@gm...> <mailto: >>> tc...@gm... <mailto:tc...@gm...>> <mailto:tc...@gm... >>> <mailto:tc...@gm...> <mailto:tc...@gm... <mailto: >>> tc...@gm...>>> <mailto:tc...@gm... <mailto:tc...@gm...> >>> <mailto:tc...@gm... <mailto:tc...@gm...>> <mailto: >>> tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... >>> <mailto:tc...@gm...>>>> <mailto:tc...@gm... <mailto: >>> tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>> >>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto: >>> tc...@gm... <mailto:tc...@gm...>>> <mailto:tc...@gm... >>> <mailto:tc...@gm...> <mailto:tc...@gm... <mailto: >>> tc...@gm...>> <mailto:tc...@gm... <mailto:tc...@gm...> >>> <mailto:tc...@gm... <mailto:tc...@gm...>>>>>> wrote: >>> >>> I'll try. Should I use >>> the 'official Ubuntu' one? >>> >>> On 14 December 2014 at >>> 23:28, Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...> >>> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto: >>> sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... >>> <mailto:sp...@gm...>>> <mailto:sp...@gm... <mailto: >>> sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> >>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto: >>> sp...@gm... <mailto:sp...@gm...>>>> <mailto: >>> sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... >>> <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto: >>> sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> >>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto: >>> sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... >>> <mailto:sp...@gm...> <mailto:sp...@gm... <mailto: >>> sp...@gm...>>>>>> wrote: >>> >>> Hi Vikko, >>> >>> On 12/12/2014 05:02 >>> AM, Vikko Okviandho wrote: >>> >>> First, I want to >>> apologize in advance for any bother I would make to you. >>> >>> >>> Not a problem, if >>> you're prepared to wait for my answers :) >>> >>> So, I got this >>> Genius (KYE) MousePen i608x drawing tablet few months ago. >>> And since then, >>> I tried to make it usable on Ubuntu 12.04.5. I looked >>> everywhere, even >>> I tried to compile your Digimend work >>> >>> (linux_3.2.0-31.50+digimend.6.__________1) myself to no avail. I tried >>> to download the >>> .deb, but SF (or >>> my ISP) won't allow me. >>> >>> What should I >>> do? I searched in Ubuntu Forums and found no answer since the >>> links are >>> expired or no more available. I guess the posts are too old so >>> they removed >>> them. >>> >>> I would >>> appreciate any helps. I don't want to use it under windows >>> exclusively. >>> Even the tablet performs not so well under windows. >>> >>> >>> First of all, AFAIK, >>> your tablet should work on kernels starting with v3.4. >>> It seems that Ubuntu >>> 12.04 should have kernel v3.11 available, try installing >>> and booting into it >>> and check if the tablet works. >>> >>> Nick >>> >>> >>> >>> >>> >>> >>> >>> >> > |
|
From: Vikko O. <tc...@gm...> - 2015-01-05 08:46:57
|
Unfortunately, the process of compiling failed. The problem was in configure phase. "..checking for LIBUSB... no configure: error: Package requirements (libusb-1.0 >= 1.0.0) were not met: No package 'libusb-1.0' found.." I was also unable to install the libusb package. Here's the output sudo apt-get install libusb Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package libusb I already do apt-get update with no error. What should I do? Manually download the package? Where can I download? I mean, from multiverse or universe? Or else? On 4 January 2015 at 22:05, Nikolai Kondrashov <sp...@gm...> wrote: > Hi Vikko, > > I'll be copying digimend-devel from now on, so others can benefit from our > discussion. I should've done it from the start. Please keep the maillist in > the CC by answering using "Reply to all". > > On 01/04/2015 01:11 PM, Vikko Okviandho wrote: > >> Err.. sorry. But I don't get what to do with the archive kye.zip (called >> usbhid-dump-kye.zip when downloaded) >> Should I install this or what? And how do I start with "Collect raw >> samples"? >> > > You don't need to install it, but you need to build it. > > First you'll need to install build dependencies: > > sudo apt-get install autotools-dev autoconf automake libtool > pkg-config libxml2-dev > > Then unpack the archive and go into the resulting directory and build the > package: > > ./bootstrap && ./configure && make > > Please send the output, if it fails. > > If it succeeds, you'll then be able to run usbhid-dump from the same > directory > as such: > > src/usbhid-dump > > You'll be able to dump input from your tablet as such: > > src/usbhid-dump -m 0458:501a -es > > If it works, please proceed with "Collect raw samples" and further from the > diagnostic collection HOWTO, using the command above, redirecting the > output > to files, as described. > > Thank you. > > Nick > > On 01/04/2015 01:11 PM, Vikko Okviandho wrote: > >> Err.. sorry. But I don't get what to do with the archive kye.zip (called >> usbhid-dump-kye.zip when downloaded) >> Should I install this or what? And how do I start with "Collect raw >> samples"? >> >> On 4 January 2015 at 05:55, Nikolai Kondrashov <sp...@gm... >> <mailto:sp...@gm...>> wrote: >> >> Hi Vikko, >> >> On 12/20/2014 12:28 PM, Vikko Okviandho wrote: >> >> I'm still waiting >> >> >> Thanks for the diagnostics. The tablet behavior and the report >> descriptor look >> quite different from the previous version, so we won't get away with >> a simple >> driver modification. >> >> We need to see if it will respond to the usual initialization attempt >> and how. >> >> Could you please try collecting the diagnostics with this version of >> usbhid-dump, which tries to initialize the tablet before dumping: >> >> https://github.com/DIGImend/__usbhid-dump/archive/kye.zip < >> https://github.com/DIGImend/usbhid-dump/archive/kye.zip> >> >> You can start with "Collect raw samples", as the previous steps will >> produce >> the same results. >> >> Thank you. >> >> Nick >> >> On 12/20/2014 12:28 PM, Vikko Okviandho wrote: >> >> I'm still waiting >> >> On 15 December 2014 at 06:42, Vikko Okviandho <tc...@gm... >> <mailto:tc...@gm...> <mailto:tc...@gm... <mailto: >> tc...@gm...>>> wrote: >> >> Well.. I have the mouse bundled. So I went until the mouse >> part. Here's the output. I can do this again if necessary. >> >> On 15 December 2014 at 02:37, Nikolai Kondrashov < >> sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... >> <mailto:sp...@gm...>>> wrote: >> >> On 12/14/2014 09:22 PM, Vikko Okviandho wrote: >> >> Same as before and everyone. Able to move the >> pointer, but no clicks. And >> absolutely no pressure. Getting desperate here. >> Hahaha.. Btw, it's 0x501a. >> >> >> Alright, could you please collect the diagnostics >> according to this page: >> http://digimend.github.io/____support/howto/trbl/____diagnostics/ >> <http://digimend.github.io/__support/howto/trbl/__diagnostics/> < >> http://digimend.github.io/__support/howto/trbl/__diagnostics/ < >> http://digimend.github.io/support/howto/trbl/diagnostics/>> >> >> Up to and including the pen coordinates, no need to go >> further for now. >> >> BTW, does your tablet have a mouse? >> >> Thank you. >> >> Nick >> >> On 12/14/2014 09:22 PM, Vikko Okviandho wrote: >> >> Same as before and everyone. Able to move the >> pointer, but no clicks. And absolutely no pressure. Getting desperate here. >> Hahaha.. Btw, it's 0x501a. >> >> On 15 December 2014 at 02:19, Nikolai Kondrashov < >> sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... >> <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto: >> sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>> >> wrote: >> >> On 12/14/2014 09:08 PM, Vikko Okviandho wrote: >> >> Here's my uname -r output 3.13.0-40-generic >> Should I still install >> linux-image-3.11.0-26-generic? >> >> >> No, that will do. What's the tablet's behavior >> with that kernel? >> >> Nick >> >> On 15 December 2014 at 02:03, Nikolai >> Kondrashov <sp...@gm... <mailto:sp...@gm...> <mailto: >> sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... >> <mailto:sp...@gm...> <mailto:sp...@gm... <mailto: >> sp...@gm...>>> <mailto:sp...@gm... <mailto:sp...@gm...> >> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto: >> sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... >> <mailto:sp...@gm...>>>>> wrote: >> >> On 12/14/2014 08:22 PM, Vikko >> Okviandho wrote: >> >> I downloaded and installed the one >> from >> http://kernel.ubuntu.com/~________kernel-ppa/mainline/v3.4-_ >> _______precise/ <http://kernel.ubuntu.com/~___ >> ___kernel-ppa/mainline/v3.4-______precise/> < >> http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ < >> http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/>> < >> http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ < >> http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/> < >> http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ < >> http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/>>> < >> http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ < >> http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/> < >> http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ < >> http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/>> < >> http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ >> <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/> >> <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/ < >> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/>>>> >> >> >> Um, I'm not sure if that is official. >> >> But it got worse. I can't even >> move the pointer anymore and the indicator >> light of the tablet lit >> continuously until I put it off from my laptop. >> What's next? >> >> >> Try running "sudo apt-get install >> linux-image-3.11.0-26-generic" and then >> rebooting into that kernel. >> >> Nick >> >> On 12/14/2014 08:22 PM, Vikko >> Okviandho wrote: >> >> I downloaded and installed the one >> from http://kernel.ubuntu.com/~________kernel-ppa/mainline/v3.4-_ >> _______precise/ <http://kernel.ubuntu.com/~___ >> ___kernel-ppa/mainline/v3.4-______precise/> < >> http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ < >> http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/>> < >> http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ < >> http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/> < >> http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ < >> http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/>>> < >> http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ < >> http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/> < >> http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ < >> http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/>> >> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____ >> precise/ <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/> >> <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/ < >> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/>>>> >> But it got worse. I can't even >> move the pointer anymore and the indicator light of the tablet lit >> continuously until I put it off from my laptop. What's next? >> >> On 15 December 2014 at 00:47, >> Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...> <mailto: >> sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... >> <mailto:sp...@gm...> <mailto:sp...@gm... <mailto: >> sp...@gm...>>> <mailto:sp...@gm... <mailto:sp...@gm...> >> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto: >> sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... >> <mailto:sp...@gm...>>>> <mailto:sp...@gm... <mailto: >> sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> >> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto: >> sp...@gm... <mailto:sp...@gm...>>> <mailto:sp...@gm... >> <mailto:sp...@gm...> <mailto:sp...@gm... <mailto: >> sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> >> <mailto:sp...@gm... <mailto:sp...@gm...>>>>>> wrote: >> >> Yes, the one from the >> official repositories. >> >> On Dec 14, 2014 7:44 PM, >> "Vikko Okviandho" <tc...@gm... <mailto:tc...@gm...> <mailto: >> tc...@gm... <mailto:tc...@gm...>> <mailto:tc...@gm... >> <mailto:tc...@gm...> <mailto:tc...@gm... <mailto: >> tc...@gm...>>> <mailto:tc...@gm... <mailto:tc...@gm...> >> <mailto:tc...@gm... <mailto:tc...@gm...>> <mailto: >> tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... >> <mailto:tc...@gm...>>>> <mailto:tc...@gm... <mailto: >> tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>> >> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto: >> tc...@gm... <mailto:tc...@gm...>>> <mailto:tc...@gm... >> <mailto:tc...@gm...> <mailto:tc...@gm... <mailto: >> tc...@gm...>> <mailto:tc...@gm... <mailto:tc...@gm...> >> <mailto:tc...@gm... <mailto:tc...@gm...>>>>>> wrote: >> >> I'll try. Should I use >> the 'official Ubuntu' one? >> >> On 14 December 2014 at >> 23:28, Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...> >> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto: >> sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... >> <mailto:sp...@gm...>>> <mailto:sp...@gm... <mailto: >> sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> >> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto: >> sp...@gm... <mailto:sp...@gm...>>>> <mailto:sp...@gm... >> <mailto:sp...@gm...> <mailto:sp...@gm... <mailto: >> sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> >> <mailto:sp...@gm... <mailto:sp...@gm...>>> <mailto: >> sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... >> <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto: >> sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm... >> >>>>>> wrote: >> >> Hi Vikko, >> >> On 12/12/2014 05:02 >> AM, Vikko Okviandho wrote: >> >> First, I want to >> apologize in advance for any bother I would make to you. >> >> >> Not a problem, if >> you're prepared to wait for my answers :) >> >> So, I got this >> Genius (KYE) MousePen i608x drawing tablet few months ago. >> And since then, I >> tried to make it usable on Ubuntu 12.04.5. I looked >> everywhere, even >> I tried to compile your Digimend work >> >> (linux_3.2.0-31.50+digimend.6.__________1) myself to no avail. I tried >> to download the >> .deb, but SF (or >> my ISP) won't allow me. >> >> What should I do? >> I searched in Ubuntu Forums and found no answer since the >> links are expired >> or no more available. I guess the posts are too old so >> they removed them. >> >> I would >> appreciate any helps. I don't want to use it under windows >> exclusively. Even >> the tablet performs not so well under windows. >> >> >> First of all, AFAIK, >> your tablet should work on kernels starting with v3.4. >> It seems that Ubuntu >> 12.04 should have kernel v3.11 available, try installing >> and booting into it >> and check if the tablet works. >> >> Nick >> >> >> >> >> >> >> >> > |
|
From: Nikolai K. <sp...@gm...> - 2015-01-04 15:05:34
|
Hi Vikko,
I'll be copying digimend-devel from now on, so others can benefit from our
discussion. I should've done it from the start. Please keep the maillist in
the CC by answering using "Reply to all".
On 01/04/2015 01:11 PM, Vikko Okviandho wrote:
> Err.. sorry. But I don't get what to do with the archive kye.zip (called
> usbhid-dump-kye.zip when downloaded)
> Should I install this or what? And how do I start with "Collect raw
> samples"?
You don't need to install it, but you need to build it.
First you'll need to install build dependencies:
sudo apt-get install autotools-dev autoconf automake libtool pkg-config libxml2-dev
Then unpack the archive and go into the resulting directory and build the
package:
./bootstrap && ./configure && make
Please send the output, if it fails.
If it succeeds, you'll then be able to run usbhid-dump from the same directory
as such:
src/usbhid-dump
You'll be able to dump input from your tablet as such:
src/usbhid-dump -m 0458:501a -es
If it works, please proceed with "Collect raw samples" and further from the
diagnostic collection HOWTO, using the command above, redirecting the output
to files, as described.
Thank you.
Nick
On 01/04/2015 01:11 PM, Vikko Okviandho wrote:
> Err.. sorry. But I don't get what to do with the archive kye.zip (called usbhid-dump-kye.zip when downloaded)
> Should I install this or what? And how do I start with "Collect raw samples"?
>
> On 4 January 2015 at 05:55, Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...>> wrote:
>
> Hi Vikko,
>
> On 12/20/2014 12:28 PM, Vikko Okviandho wrote:
>
> I'm still waiting
>
>
> Thanks for the diagnostics. The tablet behavior and the report descriptor look
> quite different from the previous version, so we won't get away with a simple
> driver modification.
>
> We need to see if it will respond to the usual initialization attempt and how.
>
> Could you please try collecting the diagnostics with this version of
> usbhid-dump, which tries to initialize the tablet before dumping:
>
> https://github.com/DIGImend/__usbhid-dump/archive/kye.zip <https://github.com/DIGImend/usbhid-dump/archive/kye.zip>
>
> You can start with "Collect raw samples", as the previous steps will produce
> the same results.
>
> Thank you.
>
> Nick
>
> On 12/20/2014 12:28 PM, Vikko Okviandho wrote:
>
> I'm still waiting
>
> On 15 December 2014 at 06:42, Vikko Okviandho <tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>>> wrote:
>
> Well.. I have the mouse bundled. So I went until the mouse part. Here's the output. I can do this again if necessary.
>
> On 15 December 2014 at 02:37, Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> wrote:
>
> On 12/14/2014 09:22 PM, Vikko Okviandho wrote:
>
> Same as before and everyone. Able to move the pointer, but no clicks. And
> absolutely no pressure. Getting desperate here. Hahaha.. Btw, it's 0x501a.
>
>
> Alright, could you please collect the diagnostics according to this page:
> http://digimend.github.io/____support/howto/trbl/____diagnostics/ <http://digimend.github.io/__support/howto/trbl/__diagnostics/> <http://digimend.github.io/__support/howto/trbl/__diagnostics/ <http://digimend.github.io/support/howto/trbl/diagnostics/>>
>
> Up to and including the pen coordinates, no need to go further for now.
>
> BTW, does your tablet have a mouse?
>
> Thank you.
>
> Nick
>
> On 12/14/2014 09:22 PM, Vikko Okviandho wrote:
>
> Same as before and everyone. Able to move the pointer, but no clicks. And absolutely no pressure. Getting desperate here. Hahaha.. Btw, it's 0x501a.
>
> On 15 December 2014 at 02:19, Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>> wrote:
>
> On 12/14/2014 09:08 PM, Vikko Okviandho wrote:
>
> Here's my uname -r output 3.13.0-40-generic
> Should I still install linux-image-3.11.0-26-generic?
>
>
> No, that will do. What's the tablet's behavior with that kernel?
>
> Nick
>
> On 15 December 2014 at 02:03, Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>>> wrote:
>
> On 12/14/2014 08:22 PM, Vikko Okviandho wrote:
>
> I downloaded and installed the one from
> http://kernel.ubuntu.com/~________kernel-ppa/mainline/v3.4-________precise/ <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/> <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/>> <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/>>> <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/>> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/
> <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/> <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/ <http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/>>>>
>
>
> Um, I'm not sure if that is official.
>
> But it got worse. I can't even move the pointer anymore and the indicator
> light of the tablet lit continuously until I put it off from my laptop.
> What's next?
>
>
> Try running "sudo apt-get install linux-image-3.11.0-26-generic" and then
> rebooting into that kernel.
>
> Nick
>
> On 12/14/2014 08:22 PM, Vikko Okviandho wrote:
>
> I downloaded and installed the one from http://kernel.ubuntu.com/~________kernel-ppa/mainline/v3.4-________precise/ <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/> <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/>> <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/>>> <http://kernel.ubuntu.com/~______kernel-ppa/mainline/v3.4-______precise/ <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/>>
> <http://kernel.ubuntu.com/~____kernel-ppa/mainline/v3.4-____precise/ <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/> <http://kernel.ubuntu.com/~__kernel-ppa/mainline/v3.4-__precise/ <http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/>>>>
> But it got worse. I can't even move the pointer anymore and the indicator light of the tablet lit continuously until I put it off from my laptop. What's next?
>
> On 15 December 2014 at 00:47, Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>>>> wrote:
>
> Yes, the one from the official repositories.
>
> On Dec 14, 2014 7:44 PM, "Vikko Okviandho" <tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>>>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>> <mailto:tc...@gm... <mailto:tc...@gm...> <mailto:tc...@gm... <mailto:tc...@gm...>>>>>> wrote:
>
> I'll try. Should I use the 'official Ubuntu' one?
>
> On 14 December 2014 at 23:28, Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>> <mailto:sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>>>>> wrote:
>
> Hi Vikko,
>
> On 12/12/2014 05:02 AM, Vikko Okviandho wrote:
>
> First, I want to apologize in advance for any bother I would make to you.
>
>
> Not a problem, if you're prepared to wait for my answers :)
>
> So, I got this Genius (KYE) MousePen i608x drawing tablet few months ago.
> And since then, I tried to make it usable on Ubuntu 12.04.5. I looked
> everywhere, even I tried to compile your Digimend work
> (linux_3.2.0-31.50+digimend.6.__________1) myself to no avail. I tried to download the
> .deb, but SF (or my ISP) won't allow me.
>
> What should I do? I searched in Ubuntu Forums and found no answer since the
> links are expired or no more available. I guess the posts are too old so
> they removed them.
>
> I would appreciate any helps. I don't want to use it under windows
> exclusively. Even the tablet performs not so well under windows.
>
>
> First of all, AFAIK, your tablet should work on kernels starting with v3.4.
> It seems that Ubuntu 12.04 should have kernel v3.11 available, try installing
> and booting into it and check if the tablet works.
>
> Nick
>
>
>
>
>
>
>
|
|
From: Nikolai K. <sp...@gm...> - 2015-01-03 21:08:14
|
On 01/03/2015 10:23 PM, Samantha Seitz wrote: > I have not tried to run my tablet on Windows. Under are the steps I took to > installing this driver. Thanks for resending these. Did you notice the other questions in my reply? Nick On 01/03/2015 10:23 PM, Samantha Seitz wrote: > I have not tried to run my tablet on Windows. Under are the steps I took to installing this driver. > > 1. Downloaded this file https://github.com/DIGImend/digimend-kernel-drivers/archive/master.zip > > 2. Open a terminal and change DIR to where the file is located (/home/samantha/Downloads/) > > 3. run the command apt-get install zip > > 4. run the command apt-get install unzip > > 5. run the command unzip digimend-kernel-drivers-master.zip -d /tmp > > 6. Switch to /tmp/digimend-kernel-drivers-master directory > > 7. run apt-get install linux-headers-$(uname -r) > > 8. Run the make command > > 9. Run the command make install > > 10. Reboot > > On Sat, Jan 3, 2015 at 8:32 AM, Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...>> wrote: > > Hi Samantha, > > Could you please keep the maillist in the CC by using "Reply to All", instead > of just "Reply"? This way others can keep track of what's happening. > Thank you. > > On 01/02/2015 10:52 PM, Samantha Seitz wrote: > > I have not tried to run my tablet on Windows. > > > It would be good to try both on Windows and another Linux PC, if you can. > We've seen both faulty tablets and USB host controllers / cabling in the past. > > Under are the steps I took to installing this driver. > > 1. Downloaded this file https://github.com/DIGImend/__digimend-kernel-drivers/__archive/master.zip <https://github.com/DIGImend/digimend-kernel-drivers/archive/master.zip> > 2. Open a terminal and change DIR to where the file is located (/home/samantha/Downloads/) > 3. run the command apt-get install zip > 4. run the command apt-get install unzip > 5. run the command unzip digimend-kernel-drivers-__master.zip -d /tmp > 6. Switch to /tmp/digimend-kernel-drivers-__master directory > 7. run apt-get install linux-headers-$(uname -r) > 8. Run the make command > 9. Run the command make install > 10. Reboot > > > These steps look fine to me. > > Could you please send the "evtest" output for your tablet while doing the "pen > coords" sample from our diagnostics page [1]? Please disregard the usbhid-dump > command mentioned there for now. > > Thank you. > > Nick > > [1] http://localhost:4000/support/__howto/trbl/diagnostics/#__coordinates <http://localhost:4000/support/howto/trbl/diagnostics/#coordinates> > > |
|
From: Samantha S. <ivy...@gm...> - 2015-01-03 20:23:52
|
I have not tried to run my tablet on Windows. Under are the steps I took to installing this driver. 1. Downloaded this file https://github.com/DIGImend/digimend-kernel-drivers/archive/master.zip 2. Open a terminal and change DIR to where the file is located (/home/samantha/Downloads/) 3. run the command apt-get install zip 4. run the command apt-get install unzip 5. run the command unzip digimend-kernel-drivers-master.zip -d /tmp 6. Switch to /tmp/digimend-kernel-drivers-master directory 7. run apt-get install linux-headers-$(uname -r) 8. Run the make command 9. Run the command make install 10. Reboot On Sat, Jan 3, 2015 at 8:32 AM, Nikolai Kondrashov <sp...@gm...> wrote: > Hi Samantha, > > Could you please keep the maillist in the CC by using "Reply to All", > instead > of just "Reply"? This way others can keep track of what's happening. > Thank you. > > On 01/02/2015 10:52 PM, Samantha Seitz wrote: > >> I have not tried to run my tablet on Windows. >> > > It would be good to try both on Windows and another Linux PC, if you can. > We've seen both faulty tablets and USB host controllers / cabling in the > past. > > Under are the steps I took to installing this driver. >> >> 1. Downloaded this file https://github.com/DIGImend/ >> digimend-kernel-drivers/archive/master.zip >> 2. Open a terminal and change DIR to where the file is located >> (/home/samantha/Downloads/) >> 3. run the command apt-get install zip >> 4. run the command apt-get install unzip >> 5. run the command unzip digimend-kernel-drivers-master.zip -d /tmp >> 6. Switch to /tmp/digimend-kernel-drivers-master directory >> 7. run apt-get install linux-headers-$(uname -r) >> 8. Run the make command >> 9. Run the command make install >> 10. Reboot >> > > These steps look fine to me. > > Could you please send the "evtest" output for your tablet while doing the > "pen > coords" sample from our diagnostics page [1]? Please disregard the > usbhid-dump > command mentioned there for now. > > Thank you. > > Nick > > [1] http://localhost:4000/support/howto/trbl/diagnostics/#coordinates > |
|
From: Vince H. <Vi...@Pl...> - 2015-01-03 15:51:26
|
How did you get it to use wacom? X config driver parameter, or more? ------------ Vince |
|
From: Nikolai K. <sp...@gm...> - 2015-01-03 13:33:01
|
Hi Samantha, Could you please keep the maillist in the CC by using "Reply to All", instead of just "Reply"? This way others can keep track of what's happening. Thank you. On 01/02/2015 10:52 PM, Samantha Seitz wrote: > I have not tried to run my tablet on Windows. It would be good to try both on Windows and another Linux PC, if you can. We've seen both faulty tablets and USB host controllers / cabling in the past. > Under are the steps I took to installing this driver. > > 1. Downloaded this file https://github.com/DIGImend/digimend-kernel-drivers/archive/master.zip > 2. Open a terminal and change DIR to where the file is located (/home/samantha/Downloads/) > 3. run the command apt-get install zip > 4. run the command apt-get install unzip > 5. run the command unzip digimend-kernel-drivers-master.zip -d /tmp > 6. Switch to /tmp/digimend-kernel-drivers-master directory > 7. run apt-get install linux-headers-$(uname -r) > 8. Run the make command > 9. Run the command make install > 10. Reboot These steps look fine to me. Could you please send the "evtest" output for your tablet while doing the "pen coords" sample from our diagnostics page [1]? Please disregard the usbhid-dump command mentioned there for now. Thank you. Nick [1] http://localhost:4000/support/howto/trbl/diagnostics/#coordinates |
|
From: Nikolai K. <sp...@gm...> - 2015-01-03 11:59:20
|
On 01/03/2015 01:01 AM, Vince Herried wrote:
> RE: hidrd-convert not working
>
> deleted ./configure. that didn't help.
> then did a make clean.
> That fixed it.
Ah, good.
> I don't understand why I can't set my buttons on Huion.
>
> evtest reports on the buttons.
>
> Testing ... (interrupt to exit)
> Event: time 1420239552.909817, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90008
> Event: time 1420239552.909817, type 1 (EV_KEY), code 263 (BTN_7), value 1
I tried using the modified hid-huion driver with xf86-input-wacom yesterday
and was able to assign key combinations to the frame buttons with xsetwacom.
Like this:
xsetwacom --set 14 button 3 key c
This would make button 3 report key "c" for Wacom pad device belonging to the
Huion H610, with ID 14.
See man xsetwacom.
Nick
|
|
From: Vince H. <Vi...@Pl...> - 2015-01-02 23:01:18
|
RE: hidrd-convert not working deleted ./configure. that didn't help. then did a make clean. That fixed it. --------------- I don't understand why I can't set my buttons on Huion. evtest reports on the buttons. Testing ... (interrupt to exit) Event: time 1420239552.909817, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90008 Event: time 1420239552.909817, type 1 (EV_KEY), code 263 (BTN_7), value 1 On Fri, Jan 2, 2015 at 7:55 AM, Nikolai Kondrashov <sp...@gm...> wrote: > Hi Vince, > > On 12/14/2014 08:52 PM, Vince Herried wrote: >> >> [vince@desk2 Huion]$ ldd `which hidrd-convert` >> linux-gate.so.1 => (0xb779f000) >> libhidrd_util.so.0 => /usr/local/lib/libhidrd_util.so.0 >> (0xb7795000) >> libhidrd_opt.so.0 => /usr/local/lib/libhidrd_opt.so.0 >> (0xb778f000) >> libhidrd_strm.so.0 => /usr/local/lib/libhidrd_strm.so.0 >> (0xb778b000) >> libhidrd_fmt.so.0 => /usr/local/lib/libhidrd_fmt.so.0 >> (0xb777b000) >> libxml2.so.2 => /lib/libxml2.so.2 (0xb75f7000) >> libz.so.1 => /lib/libz.so.1 (0x460fc000) >> libm.so.6 => /lib/libm.so.6 (0x460b3000) >> libdl.so.2 => /lib/libdl.so.2 (0x4608f000) >> libhidrd_item.so.0 => /usr/local/lib/libhidrd_item.so.0 >> (0xb75ef000) >> libhidrd_usage.so.0 => /usr/local/lib/libhidrd_usage.so.0 >> (0xb75df000) >> libc.so.6 => /lib/libc.so.6 (0x45ecf000) >> liblzma.so.5 => /lib/liblzma.so.5 (0x46134000) >> /lib/ld-linux.so.2 (0x45eac000) >> libpthread.so.0 => /lib/libpthread.so.0 (0x46096000) > > > I tried fresh hidrd package both on 64 and 32-bit Fedora 20 hosts and it > builds and runs without a problem, including the XML format support. > > I suggest making a fresh build and seeing if it works. Perhaps some bits > from > previous configure run got stuck. > > Nick > > On 12/14/2014 08:52 PM, Vince Herried wrote: >> >> [vince@desk2 Huion]$ ldd `which hidrd-convert` >> linux-gate.so.1 => (0xb779f000) >> libhidrd_util.so.0 => /usr/local/lib/libhidrd_util.so.0 >> (0xb7795000) >> libhidrd_opt.so.0 => /usr/local/lib/libhidrd_opt.so.0 >> (0xb778f000) >> libhidrd_strm.so.0 => /usr/local/lib/libhidrd_strm.so.0 >> (0xb778b000) >> libhidrd_fmt.so.0 => /usr/local/lib/libhidrd_fmt.so.0 >> (0xb777b000) >> libxml2.so.2 => /lib/libxml2.so.2 (0xb75f7000) >> libz.so.1 => /lib/libz.so.1 (0x460fc000) >> libm.so.6 => /lib/libm.so.6 (0x460b3000) >> libdl.so.2 => /lib/libdl.so.2 (0x4608f000) >> libhidrd_item.so.0 => /usr/local/lib/libhidrd_item.so.0 >> (0xb75ef000) >> libhidrd_usage.so.0 => /usr/local/lib/libhidrd_usage.so.0 >> (0xb75df000) >> libc.so.6 => /lib/libc.so.6 (0x45ecf000) >> liblzma.so.5 => /lib/liblzma.so.5 (0x46134000) >> /lib/ld-linux.so.2 (0x45eac000) >> libpthread.so.0 => /lib/libpthread.so.0 (0x46096000) >> [vince@desk2 Huion]$ >> >> On Sun, Dec 14, 2014 at 12:16 PM, Nikolai Kondrashov <sp...@gm...> >> wrote: >>> >>> On 12/14/2014 07:13 PM, Vince Herried wrote: >>>> >>>> >>>> [vince@desk2 Huion]$ cat HID-descriptor2.native | hidrd-convert -i hex >>>> -o >>>> xml >>>> Unknown output format "xml". >>> >>> >>> >>> Alright, could you please show the output of "ldd `which hidrd-convert`"? >>> >>> Nick >>> >>> On 12/14/2014 07:13 PM, Vince Herried wrote: >>>> >>>> >>>> [vince@desk2 Huion]$ cat HID-descriptor2.native | hidrd-convert -i hex >>>> -o >>>> xml >>>> Unknown output format "xml". >>>> >>>> Formats supported by hidrd-convert: >>>> >>>> natv [IO] - native format >>>> >>>> . >>>> . >>>> . >>>> where >>>> this works >>>> [vince@desk2 Huion]$ cat HID-descriptor2.native | hidrd-convert -i hex >>>> -o >>>> code >>>> >>>> >>>> --- >>>> Vince >>>> >>>> >>>> On Sun, Dec 14, 2014 at 11:07 AM, Nikolai Kondrashov <sp...@gm... >>>> <mailto:sp...@gm...>> wrote: >>>> >>>> Hi Vince, >>>> >>>> Please keep the maillist in CC so others can benefit from our >>>> discussion. >>>> Thank you. >>>> >>>> On 12/13/2014 10:55 PM, Vince Herried wrote: >>>> >>>> Hmmm that wasn't it. it was already installed. >>>> I don't see any thing missing in the config.log >>>> $ cat config.log >>>> >>>> >>>> Please just attach files to messages directly (this time it might >>>> make >>>> sense >>>> to compress it). This way they will be preserved in the archive and >>>> it >>>> will be >>>> easier to access them. Unless you want to keep them secret, of >>>> course. >>>> Thank >>>> you. >>>> >>>> Yes, config.log looks OK. >>>> >>>> What was the exact hidrd-convert invocation that failed for you and >>>> what was >>>> the output? >>>> >>>> Nick >>>> >>>> On 12/13/2014 10:55 PM, Vince Herried wrote: >>>> >>>> Hmmm that wasn't it. it was already installed. >>>> I don't see any thing missing in the config.log >>>> $ cat config.log >>>> >>>> >>>> config.log >>>> >>>> <https://docs.google.com/file/__d/0BwgN___uWIl5AdVENmX3dvZllOV00/edit?__usp=drive_web >>>> >>>> <https://docs.google.com/file/d/0BwgN_uWIl5AdVENmX3dvZllOV00/edit?usp=drive_web>> >>>> >>>> >>>> On Sat, Dec 13, 2014 at 3:02 PM, Nikolai Kondrashov >>>> <sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... >>>> <mailto:sp...@gm...>>> wrote: >>>> >>>> On 12/13/2014 08:27 PM, Vince Herried wrote: >>>> >>>> I'm on Fedora F20 >>>> >>>> >>>> Then you need libxml2-devel package installed when >>>> configuring and building >>>> hidrd. >>>> >>>> Nick >>>> >>>> >>>> On Sat, Dec 13, 2014 at 1:23 PM, Nikolai Kondrashov >>>> <sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... >>>> <mailto:sp...@gm...>>> wrote: >>>> >>>> On 12/13/2014 08:15 PM, Vince Herried wrote: >>>> >>>> >>>> the info file gives example of converting the >>>> hex >>>> input into xml >>>> I get invalid output format. >>>> the output from your dump program is: >>>> $ cat HID-descriptor2.native >>>> 05 0D 09 02 A1 01 85 07 09 20 A1 00 09 42 >>>> 09 >>>> 44 >>>> 09 45 09 3C 09 43 09 44 15 00 25 01 75 01 >>>> 95 >>>> 06 >>>> 81 02 09 32 75 01 95 01 81 02 81 03 05 01 >>>> 09 >>>> 30 >>>> 75 10 95 01 A4 55 0D 65 13 35 00 46 10 27 >>>> 27 >>>> 40 >>>> 9C 00 00 81 02 09 31 46 6A 18 26 A8 61 81 >>>> 02 >>>> B4 >>>> 05 0D 09 30 26 FF 07 46 FF 07 55 00 66 11 >>>> E1 >>>> 75 >>>> 10 81 02 C0 C0 05 01 09 02 A1 01 85 09 09 >>>> 01 >>>> A1 >>>> 00 05 09 19 01 29 03 15 00 25 01 95 03 75 >>>> 01 >>>> 81 >>>> 02 95 05 81 01 05 01 09 30 75 10 95 01 A4 >>>> 35 >>>> 00 >>>> 46 00 08 26 00 08 81 02 09 31 46 00 08 26 >>>> 00 >>>> 08 >>>> 81 02 B4 05 0D 09 30 26 FF 07 46 FF 07 75 >>>> 10 >>>> 81 >>>> B2 C0 C0 >>>> >>>> $ cat HID-descriptor2.native | hidrd-convert >>>> -i >>>> hex -o spec >>>> produces >>>> >>>> but attempt to use -o xml generates error >>>> >>>> appears the built in help says no xml output >>>> available while the >>>> info output example shows using -o xml >>>> >>>> Did I built it wrong? >>>> >>>> >>>> >>>> Yes, most likely libxml development package wasn't >>>> installed. Check >>>> "./configure" output. Also, if you use a >>>> Debian-based >>>> distro, hidrd should >>>> be >>>> in the package repositories (although without >>>> "hex" >>>> format support). >>>> >>>> Nick >>>> >>>> >>>> >>> > |
|
From: Nikolai K. <sp...@gm...> - 2015-01-02 12:55:51
|
Hi Vince, On 12/14/2014 08:52 PM, Vince Herried wrote: > [vince@desk2 Huion]$ ldd `which hidrd-convert` > linux-gate.so.1 => (0xb779f000) > libhidrd_util.so.0 => /usr/local/lib/libhidrd_util.so.0 (0xb7795000) > libhidrd_opt.so.0 => /usr/local/lib/libhidrd_opt.so.0 (0xb778f000) > libhidrd_strm.so.0 => /usr/local/lib/libhidrd_strm.so.0 (0xb778b000) > libhidrd_fmt.so.0 => /usr/local/lib/libhidrd_fmt.so.0 (0xb777b000) > libxml2.so.2 => /lib/libxml2.so.2 (0xb75f7000) > libz.so.1 => /lib/libz.so.1 (0x460fc000) > libm.so.6 => /lib/libm.so.6 (0x460b3000) > libdl.so.2 => /lib/libdl.so.2 (0x4608f000) > libhidrd_item.so.0 => /usr/local/lib/libhidrd_item.so.0 (0xb75ef000) > libhidrd_usage.so.0 => /usr/local/lib/libhidrd_usage.so.0 (0xb75df000) > libc.so.6 => /lib/libc.so.6 (0x45ecf000) > liblzma.so.5 => /lib/liblzma.so.5 (0x46134000) > /lib/ld-linux.so.2 (0x45eac000) > libpthread.so.0 => /lib/libpthread.so.0 (0x46096000) I tried fresh hidrd package both on 64 and 32-bit Fedora 20 hosts and it builds and runs without a problem, including the XML format support. I suggest making a fresh build and seeing if it works. Perhaps some bits from previous configure run got stuck. Nick On 12/14/2014 08:52 PM, Vince Herried wrote: > [vince@desk2 Huion]$ ldd `which hidrd-convert` > linux-gate.so.1 => (0xb779f000) > libhidrd_util.so.0 => /usr/local/lib/libhidrd_util.so.0 (0xb7795000) > libhidrd_opt.so.0 => /usr/local/lib/libhidrd_opt.so.0 (0xb778f000) > libhidrd_strm.so.0 => /usr/local/lib/libhidrd_strm.so.0 (0xb778b000) > libhidrd_fmt.so.0 => /usr/local/lib/libhidrd_fmt.so.0 (0xb777b000) > libxml2.so.2 => /lib/libxml2.so.2 (0xb75f7000) > libz.so.1 => /lib/libz.so.1 (0x460fc000) > libm.so.6 => /lib/libm.so.6 (0x460b3000) > libdl.so.2 => /lib/libdl.so.2 (0x4608f000) > libhidrd_item.so.0 => /usr/local/lib/libhidrd_item.so.0 (0xb75ef000) > libhidrd_usage.so.0 => /usr/local/lib/libhidrd_usage.so.0 (0xb75df000) > libc.so.6 => /lib/libc.so.6 (0x45ecf000) > liblzma.so.5 => /lib/liblzma.so.5 (0x46134000) > /lib/ld-linux.so.2 (0x45eac000) > libpthread.so.0 => /lib/libpthread.so.0 (0x46096000) > [vince@desk2 Huion]$ > > On Sun, Dec 14, 2014 at 12:16 PM, Nikolai Kondrashov <sp...@gm...> wrote: >> On 12/14/2014 07:13 PM, Vince Herried wrote: >>> >>> [vince@desk2 Huion]$ cat HID-descriptor2.native | hidrd-convert -i hex -o >>> xml >>> Unknown output format "xml". >> >> >> Alright, could you please show the output of "ldd `which hidrd-convert`"? >> >> Nick >> >> On 12/14/2014 07:13 PM, Vince Herried wrote: >>> >>> [vince@desk2 Huion]$ cat HID-descriptor2.native | hidrd-convert -i hex -o >>> xml >>> Unknown output format "xml". >>> >>> Formats supported by hidrd-convert: >>> >>> natv [IO] - native format >>> >>> . >>> . >>> . >>> where >>> this works >>> [vince@desk2 Huion]$ cat HID-descriptor2.native | hidrd-convert -i hex -o >>> code >>> >>> >>> --- >>> Vince >>> >>> >>> On Sun, Dec 14, 2014 at 11:07 AM, Nikolai Kondrashov <sp...@gm... >>> <mailto:sp...@gm...>> wrote: >>> >>> Hi Vince, >>> >>> Please keep the maillist in CC so others can benefit from our >>> discussion. >>> Thank you. >>> >>> On 12/13/2014 10:55 PM, Vince Herried wrote: >>> >>> Hmmm that wasn't it. it was already installed. >>> I don't see any thing missing in the config.log >>> $ cat config.log >>> >>> >>> Please just attach files to messages directly (this time it might make >>> sense >>> to compress it). This way they will be preserved in the archive and it >>> will be >>> easier to access them. Unless you want to keep them secret, of course. >>> Thank >>> you. >>> >>> Yes, config.log looks OK. >>> >>> What was the exact hidrd-convert invocation that failed for you and >>> what was >>> the output? >>> >>> Nick >>> >>> On 12/13/2014 10:55 PM, Vince Herried wrote: >>> >>> Hmmm that wasn't it. it was already installed. >>> I don't see any thing missing in the config.log >>> $ cat config.log >>> >>> >>> config.log >>> <https://docs.google.com/file/__d/0BwgN___uWIl5AdVENmX3dvZllOV00/edit?__usp=drive_web >>> <https://docs.google.com/file/d/0BwgN_uWIl5AdVENmX3dvZllOV00/edit?usp=drive_web>> >>> >>> >>> On Sat, Dec 13, 2014 at 3:02 PM, Nikolai Kondrashov >>> <sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... >>> <mailto:sp...@gm...>>> wrote: >>> >>> On 12/13/2014 08:27 PM, Vince Herried wrote: >>> >>> I'm on Fedora F20 >>> >>> >>> Then you need libxml2-devel package installed when >>> configuring and building >>> hidrd. >>> >>> Nick >>> >>> >>> On Sat, Dec 13, 2014 at 1:23 PM, Nikolai Kondrashov >>> <sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... >>> <mailto:sp...@gm...>>> wrote: >>> >>> On 12/13/2014 08:15 PM, Vince Herried wrote: >>> >>> >>> the info file gives example of converting the hex >>> input into xml >>> I get invalid output format. >>> the output from your dump program is: >>> $ cat HID-descriptor2.native >>> 05 0D 09 02 A1 01 85 07 09 20 A1 00 09 42 09 >>> 44 >>> 09 45 09 3C 09 43 09 44 15 00 25 01 75 01 95 >>> 06 >>> 81 02 09 32 75 01 95 01 81 02 81 03 05 01 09 >>> 30 >>> 75 10 95 01 A4 55 0D 65 13 35 00 46 10 27 27 >>> 40 >>> 9C 00 00 81 02 09 31 46 6A 18 26 A8 61 81 02 >>> B4 >>> 05 0D 09 30 26 FF 07 46 FF 07 55 00 66 11 E1 >>> 75 >>> 10 81 02 C0 C0 05 01 09 02 A1 01 85 09 09 01 >>> A1 >>> 00 05 09 19 01 29 03 15 00 25 01 95 03 75 01 >>> 81 >>> 02 95 05 81 01 05 01 09 30 75 10 95 01 A4 35 >>> 00 >>> 46 00 08 26 00 08 81 02 09 31 46 00 08 26 00 >>> 08 >>> 81 02 B4 05 0D 09 30 26 FF 07 46 FF 07 75 10 >>> 81 >>> B2 C0 C0 >>> >>> $ cat HID-descriptor2.native | hidrd-convert -i >>> hex -o spec >>> produces >>> >>> but attempt to use -o xml generates error >>> >>> appears the built in help says no xml output >>> available while the >>> info output example shows using -o xml >>> >>> Did I built it wrong? >>> >>> >>> >>> Yes, most likely libxml development package wasn't >>> installed. Check >>> "./configure" output. Also, if you use a Debian-based >>> distro, hidrd should >>> be >>> in the package repositories (although without "hex" >>> format support). >>> >>> Nick >>> >>> >>> >> |
|
From: Nikolai K. <sp...@gm...> - 2015-01-02 11:33:04
|
Hi Erich, On 11/20/2014 10:42 PM, Erich Spaker wrote: > I have purchased a UGEE M708 Tablet and cannot seem to get it working in > Ubuntu > It is an UC-Logic (5543:0081) and I have confirmed that it is fully > functioning (both throw usb logging and using it on other computers) and i > cant seem to figure out what is going wrong. > > this is the relevant output of lsusb: > > |Bus 007 Device 004: ID 5543:0081 UC-Logic Technology Corp. > | > > and this is the relevant output of "xinput list": > > |⎡ Virtual core pointer id=2 [master pointer (3)] > ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] > ⎜ ↳ Plantronics Wireless Audio Plantronics Wireless Audio id=8 [slave pointer (2)] > ⎜ ↳ Logitech USB Optical Mouse id=9 [slave pointer (2)] > ⎜ ↳ HP HP Link-5 Micro Receiver id=11 [slave pointer (2)] > ⎜ ↳ UC-LOIC TABLET 1060 id=12 [slave pointer (2)] > ⎜ ↳ UC-LOIC TABLET 1060 id=13 [slave pointer (2)] > ⎜ ↳ UC-LOIC TABLET 1060 id=14 [slave pointer (2)] > | > > I should also note that all the buttons, including the tip of the pen, seem > to work it is only moving the cursor that is a problem > > I have attached log_files and other information, any informaton on whether > this tablet is supported and how to get it working would be greatly > appreciated Could you please try this development version of digimend-kernel-drivers which attempts to support your tablet: https://github.com/DIGImend/digimend-kernel-drivers/archive/ugee.zip Thank you. |
|
From: Nikolai K. <sp...@gm...> - 2015-01-01 22:16:26
|
Hi Samantha, On 01/01/2015 11:37 PM, Samantha Seitz wrote: > I have the Huion 1060Pro+. I was really hoping that this would work, but it > did not. the tablet recognizes that the pen is writing, but the computer > does not. It detects no strokes, but at times I could get it to detect > clicks. I am running a version of debian, though I do not know which. Hope > this helps. Does your tablet work on Windows? What kind of setup did you try? Nick |
|
From: Nikolai K. <sp...@gm...> - 2015-01-01 22:16:19
|
Hi Samantha, On 01/01/2015 11:37 PM, Samantha Seitz wrote: > I have the Huion 1060Pro+. I was really hoping that this would work, but it > did not. the tablet recognizes that the pen is writing, but the computer > does not. It detects no strokes, but at times I could get it to detect > clicks. I am running a version of debian, though I do not know which. Hope > this helps. Does your tablet work on Windows? What kind of setup up did you try? Nick |
|
From: Samantha S. <ivy...@gm...> - 2015-01-01 21:37:38
|
I have the Huion 1060Pro+. I was really hoping that this would work, but it did not. the tablet recognizes that the pen is writing, but the computer does not. It detects no strokes, but at times I could get it to detect clicks. I am running a version of debian, though I do not know which. Hope this helps. |
|
From: Nikolai K. <sp...@gm...> - 2014-12-31 16:19:48
|
Hi Masaru, On 12/30/2014 12:44 PM, Masaru Hirano wrote: > Thanks for your new driver. > Ugee-1000-L works fine. Good. How did you verify it exactly? Could you please provide evtest dumps of the pen coords test? Did you have any special X.org configuration, like using the WizardPen driver? > According to change of this case. > I could found 4 changes by sources. > But I can not adopt for other model. > Please teach me how to fit for other models. > All the product uses UC-LOGIC I assumed that all your models have the UC-Logic vendor ID (0x5543) and either the 0x45 or 0x81 product ID. If that's so, the driver should attempt to handle all of them and no further code change should be necessary. Do you have tablets with other VID:PID pairs? > So I have tried same way. > Ugee-M708 model > But this model does not work correctry. > Please teach me how to add other model. > M708 Model diagnostic files are attathched. > This case strange output > $xinput list > xinputlist.txt > UC-LOIC is strange. "UC-LOIC" is a typo on behalf of the manufacturer. It's what they've put into their device and string descriptors themselves. > $ xinput list > ⎡ Virtual core pointer id=2 [master pointer (2)] > ⎜ ↳ UC-LOIC TABLET 1060 id=10 [slave pointer (2)] > ⎜ ↳ UC-LOIC TABLET 1060 id=11 [slave pointer (2)] > ⎜ ↳ UC-LOIC TABLET 1060 id=12 [slave pointer (2)] > > I have tried M708 model diagnostic. Were these diagnostic files collected with the driver installed? The tablet should work fine as the coordinate range seems to be full and correct. Do you, by any chance, still use the WizardPen driver? Could you please provide evtest dumps of the pen coords test for this tablet as well? Nick On 12/30/2014 12:44 PM, Masaru Hirano wrote: > Hello Nick > > Thanks for your new driver. > Ugee-1000-L works fine. > > According to change of this case. > I could found 4 changes by sources. > But I can not adopt for other model. > Please teach me how to fit for other models. > All the product uses UC-LOGIC > > 1.hid-huion.c > these two codes are added. > > line228: > case USB_DEVICE_ID_UGEE_TABLET_81: > line229: > case USB_DEVICE_ID_UGEE_TABLET_45: > > 2.hid-hion.c > these two codes are added. > line275: > { HID_USB_DEVICE(USB_VENDOR_ID_UCLOGIC, USB_DEVICE_ID_UGEE_TABLET_81) }, > > line276: > { HID_USB_DEVICE(USB_VENDOR_ID_UCLOGIC, USB_DEVICE_ID_UGEE_TABLET_45) }, > > 3.hid-ids.h > these two codes are added. > line:22 > #define USB_DEVICE_ID_UGEE_TABLET_81 0x0081 > line:22 > #define USB_DEVICE_ID_UGEE_TABLET_45 0x0045 > > So I have tried same way. > Ugee-M708 model > But this model does not work correctry. > Please teach me how to add other model. > M708 Model diagnostic files are attathched. > This case strange output > $xinput list > xinputlist.txt > UC-LOIC is strange. > > $ xinput list > ⎡ Virtual core pointer id=2 [master pointer (2)] > ⎜ ↳ UC-LOIC TABLET 1060 id=10 [slave pointer (2)] > ⎜ ↳ UC-LOIC TABLET 1060 id=11 [slave pointer (2)] > ⎜ ↳ UC-LOIC TABLET 1060 id=12 [slave pointer (2)] > > I have tried M708 model diagnostic. > > According to these way > http://digimend.github.io/support/howto/trbl/diagnostics/ > > > 1.Identify original model > $ lsusb > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 007 Device 002: ID 5543:0081 UC-Logic Technology Corp. > Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 006 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse > Bus 006 Device 002: ID 0518:0001 EzKEY Corp. USB to PS2 Adaptor v1.09 > 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 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 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 > > VID=5543 > PID=0081 > > $ T=5543:0081 > > 2.Retrieve USB descriptors > 1)sudo lsusb -v -d $T > descriptors.txt > Bus 007 Device 002: ID 5543:0081 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 0x0081 > bcdDevice 0.00 > iManufacturer 5 UC-LOIC > iProduct 6 TABLET 1060 > iSerial 0 > bNumConfigurations 1 > ^C > > 2) sudo usbhid-dump -ed -m $T > hid_report_descriptors.txt > Bus 007 Device 002: ID 5543:0081 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 0x0081 > bcdDevice 0.00 > iManufacturer 5 UC-LOIC > iProduct 6 TABLET 1060 > iSerial 0 > bNumConfigurations 1 > Configuration Descriptor: > ^C > > > 3.Collect raw input samples > sudo usbhid-dump -es -m $T | tee frame_wheel_srolling.txt > 007:002:000:STREAM 1418797530.559580 > 07 80 84 01 75 01 00 00 > > 007:002:000:STREAM 1418797530.565550 > 07 80 8B 01 6F 01 00 00 > > 007:002:000:STREAM 1418797530.573564 > 07 80 94 01 68 01 00 00 > > 007:002:000:STREAM 1418797530.579546 > 07 81 A0 01 5F 01 89 00 > ^C > > 4.PEN > $ sudo usbhid-dump -es -m $T | tee pen_coords.txt > > 4-1)Pen-Coordinate > 07 80 82 55 F7 5A 00 00 > > 007:002:000:STREAM 1418797673.689610 > 07 80 89 55 E0 5A 00 00 > > 007:002:000:STREAM 1418797673.695597 > 07 80 91 55 C7 5A 00 00 > > 007:002:000:STREAM 1418797673.699593 > 07 80 98 55 AD 5A 00 00 > > 007:002:000:STREAM 1418797673.705596 > 07 80 9E 55 93 5A 00 00 > ^C > > 4-2)Pen-Tiltangle > $ sudo usbhid-dump -es -m $T | tee pen_tilt.txt > Not Supported and skip > > > 4-3)Pen-Pressure > sudo usbhid-dump -es -m $T | tee pen_pressure.txt > > 007:002:000:STREAM 1418797836.355686 > 07 80 2A 56 48 2D 00 00 > > 007:002:000:STREAM 1418797836.477668 > 07 80 41 56 48 2D 00 00 > > 007:002:000:STREAM 1418797836.509667 > 07 80 58 56 48 2D 00 00 > > 007:002:000:STREAM 1418797836.535662 > 07 80 6B 56 48 2D 00 00 > ^C > > 4-4)Pen-Buttons > sudo usbhid-dump -es -m $T | tee pen_buttons.txt > > 007:002:000:STREAM 1418797957.023720 > 07 80 9D 3C 37 2B 00 00 > > 007:002:000:STREAM 1418797957.169706 > 07 80 BD 3C 37 2B 00 00 > > 007:002:000:STREAM 1418797957.547704 > 07 80 BD 3C 56 2B 00 00 > > 007:002:000:STREAM 1418797957.831697 > 07 80 DC 3C 56 2B 00 00 > > 007:002:000:STREAM 1418797957.855690 > 07 80 FC 3C 56 2B 00 00 > > 007:002:000:STREAM 1418797957.871695 > 07 80 16 3D 56 2B 00 00 > > 007:002:000:STREAM 1418797957.913699 > 07 80 2E 3D 56 2B 00 00 > > > 5 Frame Controls > 5-1)Frame Controls Dials > sudo usbhid-dump -es -m $T | tee frame_dials.txt > > Not Supported and skip > > 5-1)Frame Controls Buttons > $ sudo usbhid-dump -es -m $T | tee frame_buttons.txt > > > 007:002:002:STREAM 1418798804.272982 > 03 04 3D 00 00 00 00 00 > > 007:002:002:STREAM 1418798804.792976 > 03 00 00 00 00 00 00 00 > > 007:002:002:STREAM 1418798806.040974 > 03 01 16 00 00 00 00 00 > > 007:002:002:STREAM 1418798806.496976 > 03 00 00 00 00 00 00 00 > > 007:002:002:STREAM 1418798807.552979 > 03 02 56 00 00 00 00 00 > ^C > > > 6.Mouse > 6-1)Mouse-Coordinates > $ sudo usbhid-dump -es -m $T | tee mouse_coords.txt > Not Supported and skip > > 6-2)Mouse-Buttons > $ sudo usbhid-dump -es -m $T | tee mouse_buttons.txt > Not Supported and skip > > > 6-3)Mouse-Wheel > $ sudo usbhid-dump -es -m $T | tee mouse_wheel.txt > Not Supported and skip > > 7.huion-probe > 7-1)Identify original model > $ lsusb > identmodel.txt > Bus 007 Device 002: ID 5543:0081 UC-Logic Technology Corp. > bus=7 > device=2 > > 7-2)huion-probe > $ sudo huion-probe 7 2 > ~/huionprobe.txt > > M 55 00 43 00 2D 00 4C 00 4F 00 49 00 43 00 00 00 > P 54 00 41 00 42 00 4C 00 45 00 54 00 20 00 31 00 30 00 36 00 30 00 > S 64 0E 03 40 9C C0 5D 03 00 FF 07 A0 0F 08 00 > S 65 04 03 20 A0 > S 6E 04 03 30 00 > S 79 28 03 44 00 46 00 53 00 2D 00 55 00 49 00 20 00 46 00 34 00 30 00 31 00 2D 00 32 00 30 00 31 00 31 00 31 00 30 00 32 00 > S 7A 08 03 01 08 00 00 00 00 > > 7-2)huion-decode > $ sudo huion-probe 6 3 | huion-decode > ~/huiondecode.txt > Manufacturer: UC-LOIC? > Product: TABLET 1060 > Max X: 40000 > Max Y: 24000 > Max pressure: 2047 > Resolution: 4000 > Internal model: DFS-UI F401-2011102 > > > 7-2)Calculation > Active Area 10"x6" > MaxX / Width = MaxY / Height = Resolution > > *40000/Width =4000 > hence Width=10 > > *24000/Height=4000 > hence Height=6 > > Best regards, > Masaru Hirano > Neoblast Inc. > > > > > > > > > > > > > > > > > On 2014年12月15日 02:00, Nikolai Kondrashov wrote: >> Hi Masaru, >> >> On 11/06/2014 07:30 AM, Masaru Hirano wrote: >>> Hello Nick >>> >>> Thanks for your support. >>> We are Ugee distributer in japan. >>> Please let us know how to make driver. >>> >>> We would like to build ugee tablet driver. >>> VID=5543 >>> PID=0081 >>> These are all fine. >>> VID=5543 >>> PID=0045 >>> These are not work fine. >>> Calibration does not been succeed. >> >> I've made a very simple change to the digimend-kernel-drivers package, >> which >> has a slight possibility of making them work. I've simply added both of the >> product IDs you sent to the list of devices supported by the hid-huion >> driver, >> so it would treat them exactly as Huion tablets. >> >> The change is available in the "ugee" branch on GitHub, which you can >> download >> here: https://github.com/DIGImend/digimend-kernel-drivers/archive/ugee.zip >> >> Please try building, installing and using the driver with your tablets. We >> might just be lucky and they might work. >> >> Nick >> >> On 11/06/2014 07:30 AM, Masaru Hirano wrote: >>> Hello Nick >>> >>> Thanks for your support. >>> We are Ugee distributer in japan. >>> Please let us know how to make driver. >>> >>> We would like to build ugee tablet driver. >>> VID=5543 >>> PID=0081 >>> These are all fine. >>> VID=5543 >>> PID=0045 >>> These are not work fine. >>> Calibration does not been succeed. >>> >>> If you give me some procedure and tools for making tablet and tablet >>> monitor driver. >>> I would like to make. >>> Under ubuntu studio 14.04 >>> >>> File 1: >>> VID=5543 >>> PID=0081 >>> are work fine. >>> >>> File 2: >>> We would like to build for them. >>> >>> We are small company of system integrator for creative buginners. >>> So we need to provide no wacom tablet and ubuntu-studio 14.04 for >>> cost effective in Japan. >>> >>> Ofcource when we made new driver, we will share for everyone. >>> >>> Best regards, >>> Masaru Hirano >>> Neoblast Inc. >>> >>> On 2014年11月05日 18:24, Nikolai Kondrashov wrote: >>>> On 11/05/2014 11:22 AM, Nikolai Kondrashov wrote: >>>>> We would appreciate it, if you could provide us with a list of Ugee >>>>> tablets >>>>> which you found working with our tablets >>>> >>>> I meant "our drivers", of course. >>>> >>>> Nick >>>> >>>> On 11/05/2014 11:22 AM, Nikolai Kondrashov wrote: >>>>> Hello Masaru, >>>>> >>>>> I'm very glad to hear that another tablet distributor is choosing to >>>>> contribute their effort to making Linux drivers for their tablets. >>>>> >>>>> This year Yiynova helped with drivers for their tablets as well, and >>>>> now have >>>>> a bunch of models supported. >>>>> >>>>> We would appreciate it, if you could provide us with a list of Ugee >>>>> tablets >>>>> which you found working with our tablets, along with their USB VID:PID >>>>> pairs, >>>>> so we can add them to the list and advertise their support. >>>>> >>>>> Regarding the so far unsupported tablets, I would also like to know >>>>> their >>>>> names and VID:PID pairs, along with their parameters (if those are >>>>> unavailable >>>>> on the web). I would also like to know which hardware they're based >>>>> on, if >>>>> possible. Is it UC-Logic, Waltop, anything else? >>>>> >>>>> This would get us started. >>>>> >>>>> Thank you. >>>>> >>>>> Sincerely, >>>>> Nick >>>>> >>>>> On 11/05/2014 03:42 AM, Masaru Hirano wrote: >>>>>> Hello developper >>>>>> >>>>>> We are neoblast inc japan. >>>>>> We are one of Ugee Distributer. >>>>>> >>>>>> There are few driver for ugee. >>>>>> Most of product work by digemend kernel driver. >>>>>> But some product (tablet monitor, sketch=pad) do not work. >>>>>> http://ugee.net/index.asp >>>>>> >>>>>> We use ubuntu-studio 14.04. >>>>>> >>>>>> Digemend kernel driver are not enough for us. >>>>>> There are no friver for tablet monitor for ubuntu 14.04. >>>>>> >>>>>> We would like to build by ourseleves. >>>>>> Please let us know how to make kernel driver. >>>>>> >>>>>> best regards, >>>>>> Masaru Hirano >>>>>> neoblast inc. >>>> >>>> >>>> >> >> >> > |
|
From: Nikolai K. <sp...@gm...> - 2014-12-30 16:02:54
|
Hi Milan, On 12/30/2014 05:09 PM, Milan Plžík wrote: > if possible, could you have a look on attached patch/comment on any merge > blockers? Thanks for sending the patch! Sorry for the delay with reviewing this. I had some difficulty managing things in the project and might still do. It looks mostly fine, I have two comments only. > + 0x05, 0x0D, /* Usage Page (Digitizer), */ > + 0x09, 0x21, /* Usage (Puck), */ > + 0xA1, 0x01, /* Collection (Application), */ > + 0x85, 0x11, /* Report ID (17), */ > + 0x09, 0x21, /* Usage (Puck), */ > + 0xA0, /* Collection (Physical), */ > + 0x05, 0x09, /* Usage Page (Button), */ > + 0x75, 0x01, /* Report Size (1), */ > + 0x19, 0x01, /* Usage Minimum (01h), */ > + 0x29, 0x03, /* Usage Maximum (03h), */ > + 0x14, /* Logical Minimum (0), */ > + 0x25, 0x01, /* Logical Maximum (1), */ > + 0x95, 0x03, /* Report Count (3), */ > + 0x81, 0x02, /* Input (Variable), */ > + 0x95, 0x04, /* Report Count (4), */ > + 0x81, 0x01, /* Input (Constant), */ > + 0x95, 0x01, /* Report Count (1), */ > + 0x0B, 0x32, 0x00, 0x0D, 0x00, /* Usage (Digitizer In Range), */ > + 0x14, /* Logical Minimum (0), */ > + 0x25, 0x01, /* Logical Maximum (1), */ > + 0x81, 0x02, /* Input (Variable), */ > + 0xA4, /* Push, */ There doesn't seem to be a Pop for this Push. It will probably work this way, but that's not neat and confusing. > + 0x05, 0x01, /* Usage Page (Desktop), */ > + 0x75, 0x10, /* Report Size (16), */ > + 0x95, 0x01, /* Report Count (1), */ > + 0x55, 0xFD, /* Unit Exponent (-3), */ > + 0x65, 0x13, /* Unit (Inch), */ > + 0x14, /* Logical Minimum (0), */ > + 0x34, /* Physical Minimum (0), */ > + 0x09, 0x30, /* Usage (X), */ > + 0x27, 0x00, 0xF0, 0x00, 0x00, /* Logical Maximum (61440), */ > + 0x46, 0xE0, 0x2E, /* Physical Maximum (12000), */ > + 0x81, 0x02, /* Input (Variable), */ > + 0x09, 0x31, /* Usage (Y), */ > + 0x27, 0x00, 0xB4, 0x00, 0x00, /* Logical Maximum (46080), */ > + 0x46, 0x28, 0x23, /* Physical Maximum (9000), */ > + 0x81, 0x02, /* Input (Variable), */ > + 0x09, 0x38, /* Usage (Wheel), */ > + 0x75, 0x08, /* Report Size (8), */ > + 0x95, 0x01, /* Report Count (1), */ > + 0x15, 0xFF, /* Logical Minimum (-1), */ > + 0x25, 0x01, /* Logical Maximum (1), */ > + 0x34, /* Physical Minimum (0), */ > + 0x44, /* Physical Maximum (0), */ > + 0x81, 0x06, /* Input (Variable, Relative), */ > + 0xC0, /* End Collection, */ > + 0xC0, /* End Collection, */ > + 0x05, 0x0C, /* Usage Page (Consumer), */ > + 0x09, 0x01, /* Usage (Consumer Control), */ > + 0xA1, 0x01, /* Collection (Application), */ > + 0x85, 0x12, /* Report ID (18), */ > + 0x14, /* Logical Minimum (0), */ > + 0x25, 0x01, /* Logical Maximum (1), */ > + 0x75, 0x01, /* Report Size (1), */ > + 0x95, 0x08, /* Report Count (8), */ > + 0x05, 0x0C, /* Usage Page (Consumer), */ > + 0x0B, 0x45, 0x00, 0x0D, 0x00, /* Usage (Digitizer Eraser), */ Does this really work? What happens if I press this button? > + 0x0A, 0x1A, 0x02, /* Usage (AC Undo), */ > + 0x0A, 0x01, 0x02, /* Usage (AC New), */ > + 0x0A, 0x2F, 0x02, /* Usage (AC Zoom), */ > + 0x0A, 0x25, 0x02, /* Usage (AC Forward), */ > + 0x0A, 0x24, 0x02, /* Usage (AC Back), */ > + 0x0A, 0x2D, 0x02, /* Usage (AC Zoom In), */ > + 0x0A, 0x2E, 0x02, /* Usage (AC Zoom Out), */ > + 0x81, 0x02, /* Input (Variable), */ > + 0x95, 0x30, /* Report Count (48), */ > + 0x81, 0x03, /* Input (Constant, Variable), */ > + 0xC0 /* End Collection */ > +}; > + Otherwise it looks good to me. Nick |
|
From: Masaru H. <mh...@ne...> - 2014-12-30 11:11:45
|
Hello Nick
Thanks for your new driver.
Ugee-1000-L works fine.
According to change of this case.
I could found 4 changes by sources.
But I can not adopt for other model.
Please teach me how to fit for other models.
All the product uses UC-LOGIC
1.hid-huion.c
these two codes are added.
line228:
case USB_DEVICE_ID_UGEE_TABLET_81:
line229:
case USB_DEVICE_ID_UGEE_TABLET_45:
2.hid-hion.c
these two codes are added.
line275:
{ HID_USB_DEVICE(USB_VENDOR_ID_UCLOGIC, USB_DEVICE_ID_UGEE_TABLET_81) },
line276:
{ HID_USB_DEVICE(USB_VENDOR_ID_UCLOGIC, USB_DEVICE_ID_UGEE_TABLET_45) },
3.hid-ids.h
these two codes are added.
line:22
#define USB_DEVICE_ID_UGEE_TABLET_81 0x0081
line:22
#define USB_DEVICE_ID_UGEE_TABLET_45 0x0045
So I have tried same way.
Ugee-M708 model
But this model does not work correctry.
Please teach me how to add other model.
M708 Model diagnostic files are attathched.
This case strange output
$xinput list > xinputlist.txt
UC-LOIC is strange.
$ xinput list
⎡ Virtual core pointer id=2 [master pointer (2)]
⎜ ↳ UC-LOIC TABLET 1060 id=10 [slave pointer (2)]
⎜ ↳ UC-LOIC TABLET 1060 id=11 [slave pointer (2)]
⎜ ↳ UC-LOIC TABLET 1060 id=12 [slave pointer (2)]
I have tried M708 model diagnostic.
According to these way
http://digimend.github.io/support/howto/trbl/diagnostics/
1.Identify original model
$ lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 5543:0081 UC-Logic Technology Corp.
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Bus 006 Device 002: ID 0518:0001 EzKEY Corp. USB to PS2 Adaptor v1.09
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 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 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
VID=5543
PID=0081
$ T=5543:0081
2.Retrieve USB descriptors
1)sudo lsusb -v -d $T > descriptors.txt
Bus 007 Device 002: ID 5543:0081 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 0x0081
bcdDevice 0.00
iManufacturer 5 UC-LOIC
iProduct 6 TABLET 1060
iSerial 0
bNumConfigurations 1
^C
2) sudo usbhid-dump -ed -m $T > hid_report_descriptors.txt
Bus 007 Device 002: ID 5543:0081 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 0x0081
bcdDevice 0.00
iManufacturer 5 UC-LOIC
iProduct 6 TABLET 1060
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
^C
3.Collect raw input samples
sudo usbhid-dump -es -m $T | tee frame_wheel_srolling.txt
007:002:000:STREAM 1418797530.559580
07 80 84 01 75 01 00 00
007:002:000:STREAM 1418797530.565550
07 80 8B 01 6F 01 00 00
007:002:000:STREAM 1418797530.573564
07 80 94 01 68 01 00 00
007:002:000:STREAM 1418797530.579546
07 81 A0 01 5F 01 89 00
^C
4.PEN
$ sudo usbhid-dump -es -m $T | tee pen_coords.txt
4-1)Pen-Coordinate
07 80 82 55 F7 5A 00 00
007:002:000:STREAM 1418797673.689610
07 80 89 55 E0 5A 00 00
007:002:000:STREAM 1418797673.695597
07 80 91 55 C7 5A 00 00
007:002:000:STREAM 1418797673.699593
07 80 98 55 AD 5A 00 00
007:002:000:STREAM 1418797673.705596
07 80 9E 55 93 5A 00 00
^C
4-2)Pen-Tiltangle
$ sudo usbhid-dump -es -m $T | tee pen_tilt.txt
Not Supported and skip
4-3)Pen-Pressure
sudo usbhid-dump -es -m $T | tee pen_pressure.txt
007:002:000:STREAM 1418797836.355686
07 80 2A 56 48 2D 00 00
007:002:000:STREAM 1418797836.477668
07 80 41 56 48 2D 00 00
007:002:000:STREAM 1418797836.509667
07 80 58 56 48 2D 00 00
007:002:000:STREAM 1418797836.535662
07 80 6B 56 48 2D 00 00
^C
4-4)Pen-Buttons
sudo usbhid-dump -es -m $T | tee pen_buttons.txt
007:002:000:STREAM 1418797957.023720
07 80 9D 3C 37 2B 00 00
007:002:000:STREAM 1418797957.169706
07 80 BD 3C 37 2B 00 00
007:002:000:STREAM 1418797957.547704
07 80 BD 3C 56 2B 00 00
007:002:000:STREAM 1418797957.831697
07 80 DC 3C 56 2B 00 00
007:002:000:STREAM 1418797957.855690
07 80 FC 3C 56 2B 00 00
007:002:000:STREAM 1418797957.871695
07 80 16 3D 56 2B 00 00
007:002:000:STREAM 1418797957.913699
07 80 2E 3D 56 2B 00 00
5 Frame Controls
5-1)Frame Controls Dials
sudo usbhid-dump -es -m $T | tee frame_dials.txt
Not Supported and skip
5-1)Frame Controls Buttons
$ sudo usbhid-dump -es -m $T | tee frame_buttons.txt
007:002:002:STREAM 1418798804.272982
03 04 3D 00 00 00 00 00
007:002:002:STREAM 1418798804.792976
03 00 00 00 00 00 00 00
007:002:002:STREAM 1418798806.040974
03 01 16 00 00 00 00 00
007:002:002:STREAM 1418798806.496976
03 00 00 00 00 00 00 00
007:002:002:STREAM 1418798807.552979
03 02 56 00 00 00 00 00
^C
6.Mouse
6-1)Mouse-Coordinates
$ sudo usbhid-dump -es -m $T | tee mouse_coords.txt
Not Supported and skip
6-2)Mouse-Buttons
$ sudo usbhid-dump -es -m $T | tee mouse_buttons.txt
Not Supported and skip
6-3)Mouse-Wheel
$ sudo usbhid-dump -es -m $T | tee mouse_wheel.txt
Not Supported and skip
7.huion-probe
7-1)Identify original model
$ lsusb > identmodel.txt
Bus 007 Device 002: ID 5543:0081 UC-Logic Technology Corp.
bus=7
device=2
7-2)huion-probe
$ sudo huion-probe 7 2 > ~/huionprobe.txt
M 55 00 43 00 2D 00 4C 00 4F 00 49 00 43 00 00 00
P 54 00 41 00 42 00 4C 00 45 00 54 00 20 00 31 00 30 00 36 00 30 00
S 64 0E 03 40 9C C0 5D 03 00 FF 07 A0 0F 08 00
S 65 04 03 20 A0
S 6E 04 03 30 00
S 79 28 03 44 00 46 00 53 00 2D 00 55 00 49 00 20 00 46 00 34 00 30 00
31 00 2D 00 32 00 30 00 31 00 31 00 31 00 30 00 32 00
S 7A 08 03 01 08 00 00 00 00
7-2)huion-decode
$ sudo huion-probe 6 3 | huion-decode > ~/huiondecode.txt
Manufacturer: UC-LOIC?
Product: TABLET 1060
Max X: 40000
Max Y: 24000
Max pressure: 2047
Resolution: 4000
Internal model: DFS-UI F401-2011102
7-2)Calculation
Active Area 10"x6"
MaxX / Width = MaxY / Height = Resolution
*40000/Width =4000
hence Width=10
*24000/Height=4000
hence Height=6
Best regards,
Masaru Hirano
Neoblast Inc.
On 2014年12月15日 02:00, Nikolai Kondrashov wrote:
> Hi Masaru,
>
> On 11/06/2014 07:30 AM, Masaru Hirano wrote:
>> Hello Nick
>>
>> Thanks for your support.
>> We are Ugee distributer in japan.
>> Please let us know how to make driver.
>>
>> We would like to build ugee tablet driver.
>> VID=5543
>> PID=0081
>> These are all fine.
>> VID=5543
>> PID=0045
>> These are not work fine.
>> Calibration does not been succeed.
>
> I've made a very simple change to the digimend-kernel-drivers package,
> which
> has a slight possibility of making them work. I've simply added both of the
> product IDs you sent to the list of devices supported by the hid-huion
> driver,
> so it would treat them exactly as Huion tablets.
>
> The change is available in the "ugee" branch on GitHub, which you can
> download
> here: https://github.com/DIGImend/digimend-kernel-drivers/archive/ugee.zip
>
> Please try building, installing and using the driver with your tablets. We
> might just be lucky and they might work.
>
> Nick
>
> On 11/06/2014 07:30 AM, Masaru Hirano wrote:
>> Hello Nick
>>
>> Thanks for your support.
>> We are Ugee distributer in japan.
>> Please let us know how to make driver.
>>
>> We would like to build ugee tablet driver.
>> VID=5543
>> PID=0081
>> These are all fine.
>> VID=5543
>> PID=0045
>> These are not work fine.
>> Calibration does not been succeed.
>>
>> If you give me some procedure and tools for making tablet and tablet
>> monitor driver.
>> I would like to make.
>> Under ubuntu studio 14.04
>>
>> File 1:
>> VID=5543
>> PID=0081
>> are work fine.
>>
>> File 2:
>> We would like to build for them.
>>
>> We are small company of system integrator for creative buginners.
>> So we need to provide no wacom tablet and ubuntu-studio 14.04 for
>> cost effective in Japan.
>>
>> Ofcource when we made new driver, we will share for everyone.
>>
>> Best regards,
>> Masaru Hirano
>> Neoblast Inc.
>>
>> On 2014年11月05日 18:24, Nikolai Kondrashov wrote:
>>> On 11/05/2014 11:22 AM, Nikolai Kondrashov wrote:
>>>> We would appreciate it, if you could provide us with a list of Ugee
>>>> tablets
>>>> which you found working with our tablets
>>>
>>> I meant "our drivers", of course.
>>>
>>> Nick
>>>
>>> On 11/05/2014 11:22 AM, Nikolai Kondrashov wrote:
>>>> Hello Masaru,
>>>>
>>>> I'm very glad to hear that another tablet distributor is choosing to
>>>> contribute their effort to making Linux drivers for their tablets.
>>>>
>>>> This year Yiynova helped with drivers for their tablets as well, and
>>>> now have
>>>> a bunch of models supported.
>>>>
>>>> We would appreciate it, if you could provide us with a list of Ugee
>>>> tablets
>>>> which you found working with our tablets, along with their USB VID:PID
>>>> pairs,
>>>> so we can add them to the list and advertise their support.
>>>>
>>>> Regarding the so far unsupported tablets, I would also like to know
>>>> their
>>>> names and VID:PID pairs, along with their parameters (if those are
>>>> unavailable
>>>> on the web). I would also like to know which hardware they're based
>>>> on, if
>>>> possible. Is it UC-Logic, Waltop, anything else?
>>>>
>>>> This would get us started.
>>>>
>>>> Thank you.
>>>>
>>>> Sincerely,
>>>> Nick
>>>>
>>>> On 11/05/2014 03:42 AM, Masaru Hirano wrote:
>>>>> Hello developper
>>>>>
>>>>> We are neoblast inc japan.
>>>>> We are one of Ugee Distributer.
>>>>>
>>>>> There are few driver for ugee.
>>>>> Most of product work by digemend kernel driver.
>>>>> But some product (tablet monitor, sketch=pad) do not work.
>>>>> http://ugee.net/index.asp
>>>>>
>>>>> We use ubuntu-studio 14.04.
>>>>>
>>>>> Digemend kernel driver are not enough for us.
>>>>> There are no friver for tablet monitor for ubuntu 14.04.
>>>>>
>>>>> We would like to build by ourseleves.
>>>>> Please let us know how to make kernel driver.
>>>>>
>>>>> best regards,
>>>>> Masaru Hirano
>>>>> neoblast inc.
>>>
>>>
>>>
>
>
>
--
=========================================
Masaru Hirano
Neoblast Inc.
Tokiwadai1-67-5-704, Itabashi-ku, Tokyo, Japan
ZIP:174-0071
E-Mail:mh...@ne...
Tel:+81-3-4570-7345
Mob:+81-70-6575-1732
Fax:+81-20-4623-9249
=========================================
|
|
From: Nikolai K. <sp...@gm...> - 2014-12-29 06:38:23
|
Hi everyone, I just finished moving the project website to http://digimend.github.io/. The old wiki is no more, replaced by redirects to the new website. Thanks to Dan Roberts for the help moving the Vocabulary! Please try the new website and report any problems you can find, either using the page "report button" (beside the page title), or by replying to this message. Any feedback is appreciated, thank you. Nick |
|
From: Milan P. <mil...@gm...> - 2014-12-16 21:05:37
|
Good day, my last year's efforts to submit patch implementing support for $subj were stopped by real life and its implications :). Attached is modified patch for current kernel master and fixed report descriptor XML. Patch was tested and works correctly with M912. Some tablet keys do not work in xorg (evtest correctly reports them), but that is caused by X server limitation (see https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/313514 ). If necessary, I can change mappings to usable keys, but I tried to keep key semantics and to be consistent with other report descriptors in hid-kye.c . Best regards, Milan Plzik |
|
From: Nikolai K. <sp...@gm...> - 2014-12-15 10:47:20
|
On 12/15/2014 02:41 AM, Dan Roberts wrote: > It took me way longer to get around to this than I had hoped, but I > submitted a pull request on github here: > https://github.com/DIGImend/digimend.github.io/pull/2 which builds a > vocabulary page. Thanks a lot, Dan! I'll review it in the evening. Nick On 12/15/2014 02:41 AM, Dan Roberts wrote: > Hi Nick, > It took me way longer to get around to this than I had hoped, but I submitted a pull request on github here: https://github.com/DIGImend/digimend.github.io/pull/2 which builds a vocabulary page. > > Cheers, > Dan > > On Wed, Nov 12, 2014 at 3:19 AM, Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...>> wrote: > > On 11/12/2014 01:17 PM, Nikolai Kondrashov wrote: > > I'm CC'ing DIGImend-devel to keep everyone posted. > > > Argh, I didn't really. Now I do. > > > On 11/12/2014 01:17 PM, Nikolai Kondrashov wrote: > > Hi Dan, > > I'm CC'ing DIGImend-devel to keep everyone posted. > > On 11/12/2014 01:12 AM, Dan Roberts wrote: > > Is there any way I can help with the transition to digimend.github.io <http://digimend.github.io> > <http://digimend.github.io> ? In regards to updating digimend-kernel-drivers > to reflect the Monoprice tablet, once I've tested that driver I'll > definitely do that. > > > Thank you, Dan. > > Among other things we need to move pages explaining some terms and describing > tablet manufacturers. I think a vocabulary page collecting these might be > enough for now. > > Let's put it into "support/misc/vocabulary/index__.md <http://index.md>". > > These are the pages that should go there: > > http://digimend.sourceforge.__net/wiki/KYE <http://digimend.sourceforge.net/wiki/KYE> > http://digimend.sourceforge.__net/wiki/LPI <http://digimend.sourceforge.net/wiki/LPI> > http://digimend.sourceforge.__net/wiki/PL <http://digimend.sourceforge.net/wiki/PL> > http://digimend.sourceforge.__net/wiki/RPS <http://digimend.sourceforge.net/wiki/RPS> > http://digimend.sourceforge.__net/wiki/Rebranded_tablets <http://digimend.sourceforge.net/wiki/Rebranded_tablets> > http://digimend.sourceforge.__net/wiki/Huion <http://digimend.sourceforge.net/wiki/Huion> > http://digimend.sourceforge.__net/wiki/UC-Logic <http://digimend.sourceforge.net/wiki/UC-Logic> > http://digimend.sourceforge.__net/wiki/Waltop <http://digimend.sourceforge.net/wiki/Waltop> > > I'm also attaching their mediawiki source files, along with > pandoc-converted markdown files. > > We'll need to link that page from /support/, say under "Miscellaneous" > heading. And more importantly, from the abbreviations used on tablet > description pages (such as PL, RPS, etc.) - that would mean editing > "_includes/tablet.html". > > Thank you. > > Nick > > On 11/12/2014 01:12 AM, Dan Roberts wrote: > > Hi Nick, > Is there any way I can help with the transition to digimend.github.io <http://digimend.github.io> <http://digimend.github.io> ? In regards to updating digimend-kernel-drivers to reflect the Monoprice tablet, once I've tested that driver I'll definitely do that. > > Thanks, > Dan > > On Sun, Nov 9, 2014 at 2:50 AM, Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...> <mailto:sp...@gm... <mailto:sp...@gm...>>> wrote: > > On 11/09/2014 12:30 PM, Nikolai Kondrashov wrote: > > You can use the edit link on the tablet page [1], or checkout and make a > change to the tablets repo [2] directly. > > > Ah, and another thing: it would be good to update the digimend-kernel-drivers > README [1] as well. So far I haven't thought up a way to not duplicate the > information there. > > Nick > > [1] https://github.com/DIGImend/____digimend-kernel-drivers/ <https://github.com/DIGImend/__digimend-kernel-drivers/> <https://github.com/DIGImend/__digimend-kernel-drivers/ <https://github.com/DIGImend/digimend-kernel-drivers/>> > > > On 11/09/2014 12:30 PM, Nikolai Kondrashov wrote: > > Hi Dan, > > On 11/09/2014 08:34 AM, Dan Roberts wrote: > > I didn't see this in the wiki so I thought I would mention I believe my > tablet to be a rebranded h610. I ordered it from monoprice here: > http://www.monoprice.com/____Product?c_id=108&cp_id=10841&____cs_id=1084101&p_id=10594 <http://www.monoprice.com/__Product?c_id=108&cp_id=10841&__cs_id=1084101&p_id=10594> <http://www.monoprice.com/__Product?c_id=108&cp_id=10841&__cs_id=1084101&p_id=10594 <http://www.monoprice.com/Product?c_id=108&cp_id=10841&cs_id=1084101&p_id=10594>> > It reports the same VID/PID as the h610, and it looks identical to the 610 > but with a slightly different pen: http://imgur.com/UfV45LZ is a picture of > my unit. On the backside of the tablet it says "10 x 6.25-inch Graphic > Drawing Tablet (4000 LPI, 200 RPS, 2048 Levels)" identical to the Monoprice > product name. The 200 RPS doesn't quite match the h610 (which is supposed to > be 233 RPS right?) but I've been successfully using (a heavily modified > version of) the hid-huion driver from a few months back. If you agree > they're the same tablet I can add that info to the wiki(s) as needed. > > > Yes, indeed, it looks very much the same. The tablet information needs to be > updated. However, as the sourceforge.net <http://sourceforge.net> <http://sourceforge.net> wiki is being phased out now, the > changes should be done to the new site. > > You can use the edit link on the tablet page [1], or checkout and make a > change to the tablets repo [2] directly. > > The data in question is kept in the "sold_as" field of the yaml front matter > of the markdown files. > > You can check the schema before modifying it [3], but it should be pretty > obvious. > > Nick > > [1] http://digimend.github.io/____tablets/Huion_H610/ <http://digimend.github.io/__tablets/Huion_H610/> <http://digimend.github.io/__tablets/Huion_H610/ <http://digimend.github.io/tablets/Huion_H610/>> > [2] https://github.com/DIGImend/____tablets <https://github.com/DIGImend/__tablets> <https://github.com/DIGImend/__tablets <https://github.com/DIGImend/tablets>> > [3] https://github.com/DIGImend/____tablets/blob/master/schema.yml <https://github.com/DIGImend/__tablets/blob/master/schema.yml> <https://github.com/DIGImend/__tablets/blob/master/schema.yml <https://github.com/DIGImend/tablets/blob/master/schema.yml>__> > > On 11/09/2014 08:34 AM, Dan Roberts wrote: > > Hi Nick, > I didn't see this in the wiki so I thought I would mention I believe my tablet to be a rebranded h610. I ordered it from monoprice here: http://www.monoprice.com/____Product?c_id=108&cp_id=10841&____cs_id=1084101&p_id=10594 <http://www.monoprice.com/__Product?c_id=108&cp_id=10841&__cs_id=1084101&p_id=10594> <http://www.monoprice.com/__Product?c_id=108&cp_id=10841&__cs_id=1084101&p_id=10594 <http://www.monoprice.com/Product?c_id=108&cp_id=10841&cs_id=1084101&p_id=10594>> It reports the same VID/PID as the h610, and it looks identical to the 610 but with a slightly different pen: http://imgur.com/UfV45LZ is a picture of my unit. On the backside of the tablet it says "10 x 6.25-inch Graphic Drawing Tablet (4000 LPI, 200 RPS, 2048 Levels)" identical to the Monoprice product name. The 200 RPS doesn't quite match the h610 (which is supposed to be 233 RPS right?) but I've been successfully using (a heavily modified version of) the hid-huion driver from > a few months back. If you agree they're the same tablet I can add that info to the wiki(s) as needed. > > Cheers, > Dan > > > > > > |
|
From: Dan R. <ade...@gm...> - 2014-12-15 00:41:39
|
Hi Nick,
It took me way longer to get around to this than I had hoped, but I
submitted a pull request on github here:
https://github.com/DIGImend/digimend.github.io/pull/2 which builds a
vocabulary page.
Cheers,
Dan
On Wed, Nov 12, 2014 at 3:19 AM, Nikolai Kondrashov <sp...@gm...>
wrote:
>
> On 11/12/2014 01:17 PM, Nikolai Kondrashov wrote:
>
>> I'm CC'ing DIGImend-devel to keep everyone posted.
>>
>
> Argh, I didn't really. Now I do.
>
>
> On 11/12/2014 01:17 PM, Nikolai Kondrashov wrote:
>
>> Hi Dan,
>>
>> I'm CC'ing DIGImend-devel to keep everyone posted.
>>
>> On 11/12/2014 01:12 AM, Dan Roberts wrote:
>>
>>> Is there any way I can help with the transition to digimend.github.io
>>> <http://digimend.github.io> ? In regards to updating
>>> digimend-kernel-drivers
>>> to reflect the Monoprice tablet, once I've tested that driver I'll
>>> definitely do that.
>>>
>>
>> Thank you, Dan.
>>
>> Among other things we need to move pages explaining some terms and
>> describing
>> tablet manufacturers. I think a vocabulary page collecting these might be
>> enough for now.
>>
>> Let's put it into "support/misc/vocabulary/index.md".
>>
>> These are the pages that should go there:
>>
>> http://digimend.sourceforge.net/wiki/KYE
>> http://digimend.sourceforge.net/wiki/LPI
>> http://digimend.sourceforge.net/wiki/PL
>> http://digimend.sourceforge.net/wiki/RPS
>> http://digimend.sourceforge.net/wiki/Rebranded_tablets
>> http://digimend.sourceforge.net/wiki/Huion
>> http://digimend.sourceforge.net/wiki/UC-Logic
>> http://digimend.sourceforge.net/wiki/Waltop
>>
>> I'm also attaching their mediawiki source files, along with
>> pandoc-converted markdown files.
>>
>> We'll need to link that page from /support/, say under "Miscellaneous"
>> heading. And more importantly, from the abbreviations used on tablet
>> description pages (such as PL, RPS, etc.) - that would mean editing
>> "_includes/tablet.html".
>>
>> Thank you.
>>
>> Nick
>>
>> On 11/12/2014 01:12 AM, Dan Roberts wrote:
>>
>>> Hi Nick,
>>> Is there any way I can help with the transition to
>>> digimend.github.io <http://digimend.github.io> ? In regards to updating
>>> digimend-kernel-drivers to reflect the Monoprice tablet, once I've tested
>>> that driver I'll definitely do that.
>>>
>>> Thanks,
>>> Dan
>>>
>>> On Sun, Nov 9, 2014 at 2:50 AM, Nikolai Kondrashov <sp...@gm...
>>> <mailto:sp...@gm...>> wrote:
>>>
>>> On 11/09/2014 12:30 PM, Nikolai Kondrashov wrote:
>>>
>>> You can use the edit link on the tablet page [1], or checkout
>>> and make a
>>> change to the tablets repo [2] directly.
>>>
>>>
>>> Ah, and another thing: it would be good to update the
>>> digimend-kernel-drivers
>>> README [1] as well. So far I haven't thought up a way to not
>>> duplicate the
>>> information there.
>>>
>>> Nick
>>>
>>> [1] https://github.com/DIGImend/__digimend-kernel-drivers/ <
>>> https://github.com/DIGImend/digimend-kernel-drivers/>
>>>
>>>
>>> On 11/09/2014 12:30 PM, Nikolai Kondrashov wrote:
>>>
>>> Hi Dan,
>>>
>>> On 11/09/2014 08:34 AM, Dan Roberts wrote:
>>>
>>> I didn't see this in the wiki so I thought I would mention I
>>> believe my
>>> tablet to be a rebranded h610. I ordered it from monoprice
>>> here:
>>> http://www.monoprice.com/__Product?c_id=108&cp_id=10841&_
>>> _cs_id=1084101&p_id=10594 <http://www.monoprice.com/
>>> Product?c_id=108&cp_id=10841&cs_id=1084101&p_id=10594>
>>> It reports the same VID/PID as the h610, and it looks
>>> identical to the 610
>>> but with a slightly different pen: http://imgur.com/UfV45LZ
>>> is a picture of
>>> my unit. On the backside of the tablet it says "10 x
>>> 6.25-inch Graphic
>>> Drawing Tablet (4000 LPI, 200 RPS, 2048 Levels)" identical
>>> to the Monoprice
>>> product name. The 200 RPS doesn't quite match the h610
>>> (which is supposed to
>>> be 233 RPS right?) but I've been successfully using (a
>>> heavily modified
>>> version of) the hid-huion driver from a few months back. If
>>> you agree
>>> they're the same tablet I can add that info to the wiki(s)
>>> as needed.
>>>
>>>
>>> Yes, indeed, it looks very much the same. The tablet information
>>> needs to be
>>> updated. However, as the sourceforge.net <http://sourceforge.net>
>>> wiki is being phased out now, the
>>> changes should be done to the new site.
>>>
>>> You can use the edit link on the tablet page [1], or checkout
>>> and make a
>>> change to the tablets repo [2] directly.
>>>
>>> The data in question is kept in the "sold_as" field of the yaml
>>> front matter
>>> of the markdown files.
>>>
>>> You can check the schema before modifying it [3], but it should
>>> be pretty
>>> obvious.
>>>
>>> Nick
>>>
>>> [1] http://digimend.github.io/__tablets/Huion_H610/ <
>>> http://digimend.github.io/tablets/Huion_H610/>
>>> [2] https://github.com/DIGImend/__tablets <
>>> https://github.com/DIGImend/tablets>
>>> [3] https://github.com/DIGImend/__tablets/blob/master/schema.yml
>>> <https://github.com/DIGImend/tablets/blob/master/schema.yml>
>>>
>>> On 11/09/2014 08:34 AM, Dan Roberts wrote:
>>>
>>> Hi Nick,
>>> I didn't see this in the wiki so I thought I would
>>> mention I believe my tablet to be a rebranded h610. I ordered it from
>>> monoprice here: http://www.monoprice.com/__
>>> Product?c_id=108&cp_id=10841&__cs_id=1084101&p_id=10594 <
>>> http://www.monoprice.com/Product?c_id=108&cp_id=10841&
>>> cs_id=1084101&p_id=10594> It reports the same VID/PID as the h610, and
>>> it looks identical to the 610 but with a slightly different pen:
>>> http://imgur.com/UfV45LZ is a picture of my unit. On the backside of
>>> the tablet it says "10 x 6.25-inch Graphic Drawing Tablet (4000 LPI, 200
>>> RPS, 2048 Levels)" identical to the Monoprice product name. The 200 RPS
>>> doesn't quite match the h610 (which is supposed to be 233 RPS right?) but
>>> I've been successfully using (a heavily modified version of) the hid-huion
>>> driver from a few months back. If you agree they're the same tablet I can
>>> add that info to the wiki(s) as needed.
>>>
>>> Cheers,
>>> Dan
>>>
>>>
>>>
>>>
>>>
>>
>
|
38 messages has been excluded from this view by a project administrator.
