digimend-users Mailing List for DIGImend (Page 4)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

I found that I have to black list hid_huin
To get the drivers to work .

~~~~~
Vince

-------- Forwarded Message --------
Subject: 	Re: [DIGImend-users] Fwd: About unsupported UC-Logic Tablet 
TWHA60 v3
Date: 	Wed, 08 Apr 2015 23:08:19 -0400
From: 	Chris Hanna <shi...@gm...>
To: 	Nikolai Kondrashov <sp...@gm...>

I dont know what happened, but the drivers dont work any more.  The
cursor doesnt move, I cant click with the pen or buttons, and nothing
relating to the tablet shows up in xinput list, which is a setback from
straight out of the box. Im using Ubuntu 14.04.2 Trusty Tahr, kernel
version 3.16.0-33.  Do you have any ideas on whats going on there?

On 04/08/2015 04:14 PM, Nikolai Kondrashov wrote:
> Hi Christopher,
>
> On 04/08/2015 02:00 AM, Christopher Hanna wrote:
>> I need the TWHA60 drivers for another computer now, but the link you
>> originally sent me doesn't seem to work anymore.
>
> Please use the latest development version, it has support for your tablet
> integrated now:
>
> https://github.com/DIGImend/digimend-kernel-drivers/archive/master.zip
>
>> Also when I attempted to get pressure information through xiniput
>> test, I
>> didn't understand what I should put in the device name section, but I
>> suspect that there is no pressure information being transmitted.  If
>> you can
>> help me determine the device name, I can confirm this.
>
> Look at the output of "xinput list". Find your tablet devices and use
> their
> IDs as parameter to the "xinput test". If you use the latest development
> version your stylus device name will have "Pen" on the end, making it
> easier
> to identify.
>
> Nick
>
> On 04/08/2015 02:00 AM, Christopher Hanna wrote:
>>
>> ---------- Forwarded message ----------
>> From: *Christopher Hanna* <shi...@gm...
>> <mailto:shi...@gm...>>
>> Date: 7 April 2015 at 19:00
>> Subject: Re: [DIGImend-users] About unsupported UC-Logic Tablet
>> TWHA60 v3
>> To: Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...>>
>>
>>
>> Hello Nick,
>>
>> I need the TWHA60 drivers for another computer now, but the link you
>> originally sent me doesn't seem to work anymore.  Also when I
>> attempted to get pressure information through xiniput test, I didn't
>> understand what I should put in the device name section, but I
>> suspect that there is no pressure information being transmitted.  If
>> you can help me determine the device name, I can confirm this.
>>
>> Thanks, Chris
>>
>> On 3 January 2015 at 15:03, Nikolai Kondrashov <sp...@gm...
>> <mailto:sp...@gm...>> wrote:
>>
>>     Hi Christopher,
>>
>>     Please keep the maillist in the CC, so others can benefit from
>> our discussion
>>     as well.
>>
>>     On 01/03/2015 09:56 PM, Christopher Hanna wrote:
>>
>>         On 01/03/2015 07:01 AM, Nikolai Kondrashov wrote:
>>
>>             Hi Christopher,
>>
>>             On 01/03/2015 08:35 AM, Christopher Hanna wrote:
>>
>>                 Hello there, I recently got the tablet listed in the
>> subject line, and
>>                 out of the box the pen was able to click things and
>> the buttons worked
>>                 (both on the pen and the tablet), but it can't move
>> the cursor. It was
>>                 also able to make a dot in any drawing program. I
>> tried to fix it using
>>                 the wizardpen solution, but it didn't change
>> anything, however the
>>                 wizardpen calibration program recognized the tablet
>> area and gave a
>>                 reasonable output.  Can you help me get it to work in
>> some way? Will it
>>                 ever be supported in the near future?
>>
>>
>>             There is a development version of digimend-kernel-drivers
>> which adds support
>>             for your tablet:
>>
>> https://github.com/DIGImend/__digimend-kernel-drivers/__archive/twha60.zip
>> <https://github.com/DIGImend/digimend-kernel-drivers/archive/twha60.zip>
>>
>>             Could you please try it?
>>
>>             The support for your tablet is to be in the next version,
>> released within the
>>             next two months, perhaps.
>>
>>
>>         The driver you sent me makes the cursor move as it should,
>> and all the
>>         functions it had before are retained!  Thanks Nick! Doesn't
>> seem to be any
>>         pressure sensitivity though.  It's not terribly important,
>> but any tips on
>>         getting that to work?
>>
>>
>>     You can verify if the X server gets any pressure information by
>> using "xinput
>>     test" with your tablet and seeing if you get anything in the
>> third valuator.
>>
>>     Otherwise, try following some of our (a bit dated) HOWTOs:
>>
>>     http://localhost:4000/support/
>>
>>     I would welcome any fixes or updates to them, BTW.
>>
>>     Nick
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>>
>> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
>> Develop your own process in accordance with the BPMN 2 standard
>> Learn Process modeling best practices with Bonita BPM through live
>> exercises
>> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
>> event?utm_
>> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
>>
>>
>>
>> _______________________________________________
>> DIGImend-users mailing list
>> DIG...@li...
>> https://lists.sourceforge.net/lists/listinfo/digimend-users
>>
>

Hi Christopher,

On 04/08/2015 02:00 AM, Christopher Hanna wrote:
> I need the TWHA60 drivers for another computer now, but the link you
> originally sent me doesn't seem to work anymore.

Please use the latest development version, it has support for your tablet
integrated now:

     https://github.com/DIGImend/digimend-kernel-drivers/archive/master.zip

> Also when I attempted to get pressure information through xiniput test, I
> didn't understand what I should put in the device name section, but I
> suspect that there is no pressure information being transmitted.  If you can
> help me determine the device name, I can confirm this.

Look at the output of "xinput list". Find your tablet devices and use their
IDs as parameter to the "xinput test". If you use the latest development
version your stylus device name will have "Pen" on the end, making it easier
to identify.

Nick

On 04/08/2015 02:00 AM, Christopher Hanna wrote:
>
> ---------- Forwarded message ----------
> From: *Christopher Hanna* <shi...@gm... <mailto:shi...@gm...>>
> Date: 7 April 2015 at 19:00
> Subject: Re: [DIGImend-users] About unsupported UC-Logic Tablet TWHA60 v3
> To: Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...>>
>
>
> Hello Nick,
>
> I need the TWHA60 drivers for another computer now, but the link you originally sent me doesn't seem to work anymore.  Also when I attempted to get pressure information through xiniput test, I didn't understand what I should put in the device name section, but I suspect that there is no pressure information being transmitted.  If you can help me determine the device name, I can confirm this.
>
> Thanks, Chris
>
> On 3 January 2015 at 15:03, Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...>> wrote:
>
>     Hi Christopher,
>
>     Please keep the maillist in the CC, so others can benefit from our discussion
>     as well.
>
>     On 01/03/2015 09:56 PM, Christopher Hanna wrote:
>
>         On 01/03/2015 07:01 AM, Nikolai Kondrashov wrote:
>
>             Hi Christopher,
>
>             On 01/03/2015 08:35 AM, Christopher Hanna wrote:
>
>                 Hello there, I recently got the tablet listed in the subject line, and
>                 out of the box the pen was able to click things and the buttons worked
>                 (both on the pen and the tablet), but it can't move the cursor. It was
>                 also able to make a dot in any drawing program. I tried to fix it using
>                 the wizardpen solution, but it didn't change anything, however the
>                 wizardpen calibration program recognized the tablet area and gave a
>                 reasonable output.  Can you help me get it to work in some way? Will it
>                 ever be supported in the near future?
>
>
>             There is a development version of digimend-kernel-drivers which adds support
>             for your tablet:
>
>             https://github.com/DIGImend/__digimend-kernel-drivers/__archive/twha60.zip <https://github.com/DIGImend/digimend-kernel-drivers/archive/twha60.zip>
>
>             Could you please try it?
>
>             The support for your tablet is to be in the next version, released within the
>             next two months, perhaps.
>
>
>         The driver you sent me makes the cursor move as it should, and all the
>         functions it had before are retained!  Thanks Nick!  Doesn't seem to be any
>         pressure sensitivity though.  It's not terribly important, but any tips on
>         getting that to work?
>
>
>     You can verify if the X server gets any pressure information by using "xinput
>     test" with your tablet and seeing if you get anything in the third valuator.
>
>     Otherwise, try following some of our (a bit dated) HOWTOs:
>
>     http://localhost:4000/support/
>
>     I would welcome any fixes or updates to them, BTW.
>
>     Nick
>
>
>
>
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
>
>
>
> _______________________________________________
> DIGImend-users mailing list
> DIG...@li...
> https://lists.sourceforge.net/lists/listinfo/digimend-users
>

---------- Forwarded message ----------
From: Christopher Hanna <shi...@gm...>
Date: 7 April 2015 at 19:00
Subject: Re: [DIGImend-users] About unsupported UC-Logic Tablet TWHA60 v3
To: Nikolai Kondrashov <sp...@gm...>

Hello Nick,

I need the TWHA60 drivers for another computer now, but the link you
originally sent me doesn't seem to work anymore.  Also when I attempted to
get pressure information through xiniput test, I didn't understand what I
should put in the device name section, but I suspect that there is no
pressure information being transmitted.  If you can help me determine the
device name, I can confirm this.

Thanks, Chris

On 3 January 2015 at 15:03, Nikolai Kondrashov <sp...@gm...> wrote:

> Hi Christopher,
>
> Please keep the maillist in the CC, so others can benefit from our
> discussion
> as well.
>
> On 01/03/2015 09:56 PM, Christopher Hanna wrote:
>
>> On 01/03/2015 07:01 AM, Nikolai Kondrashov wrote:
>>
>>> Hi Christopher,
>>>
>>> On 01/03/2015 08:35 AM, Christopher Hanna wrote:
>>>
>>>> Hello there, I recently got the tablet listed in the subject line, and
>>>> out of the box the pen was able to click things and the buttons worked
>>>> (both on the pen and the tablet), but it can't move the cursor. It was
>>>> also able to make a dot in any drawing program. I tried to fix it using
>>>> the wizardpen solution, but it didn't change anything, however the
>>>> wizardpen calibration program recognized the tablet area and gave a
>>>> reasonable output.  Can you help me get it to work in some way? Will it
>>>> ever be supported in the near future?
>>>>
>>>
>>> There is a development version of digimend-kernel-drivers which adds
>>> support
>>> for your tablet:
>>>
>>> https://github.com/DIGImend/digimend-kernel-drivers/archive/twha60.zip
>>>
>>> Could you please try it?
>>>
>>> The support for your tablet is to be in the next version, released
>>> within the
>>> next two months, perhaps.
>>>
>>>
>> The driver you sent me makes the cursor move as it should, and all the
>> functions it had before are retained!  Thanks Nick!  Doesn't seem to be
>> any
>> pressure sensitivity though.  It's not terribly important, but any tips on
>> getting that to work?
>>
>
> You can verify if the X server gets any pressure information by using
> "xinput
> test" with your tablet and seeing if you get anything in the third
> valuator.
>
> Otherwise, try following some of our (a bit dated) HOWTOs:
>
> http://localhost:4000/support/
>
> I would welcome any fixes or updates to them, BTW.
>
> Nick
>

Hi Nathan,

On 03/29/2015 11:47 PM, Townsend Forbes wrote:
> I own a Trust TB-1200 and use mypaint and I've just gotten the pressure
> sensitivity to work. I'd love to contribute to the project by writing it up
> for you if you want.
>
> It's pretty simple. In short you got to Degub>GTK Input Dialog, change the
> device to "Aiptek" as it's recognised, then put the pressure sensitivity to
> button 4. Simple as.
>
> Anywho, thanks for the site it's really helpful. If there's a repository of
> information I simply haven't had you'd prefer I contribute to. Please do
> say.

I'm glad to hear our site helped you.

I would appreciate it if you could send us a link to some page describing your
tablet and also the output of "sudo lsusb -v" with your tablet plugged in so
we can know more about it.

If you have anything to add to or fix in our HOWTOs at
http://digimend.github.io/support/ please feel free to use the "pencil" icon
beside the title on each page to propose the changes. You'll need to be
registered on and logged in to github.com to do that though.

If that's hard or otherwise unsuitable for you, you can send the modified text
in whatever format you prefer and we'll try to figure out how to best
integrate it.

Thank you.

Nick

Hiya

I own a Trust TB-1200 and use mypaint and I've just gotten the pressure 
sensitivity to work. I'd love to contribute to the project by writing it
 up for you if you want.

It's pretty simple. In short you got to Degub>GTK Input Dialog, 
change the device to "Aiptek" as it's recognised, then put the pressure 
sensitivity to button 4. Simple as.

Anywho, thanks for the site it's really helpful. If there's a repository
 of information I simply haven't had you'd prefer I contribute to. 
Please do say.

Yours Sincerely.
Nathan Thark

On 03/04/2015 06:57 PM, Ulrich Lauther wrote:
> On Wed, Mar 04, 2015 at 04:37:45PM +0200, Nikolai Kondrashov wrote:
>> On 03/04/2015 04:30 PM, Ulrich Lauther wrote:
>>> On Wed, Mar 04, 2015 at 02:05:37PM +0200, Nikolai Kondrashov wrote:
>>>>> Maybe some h-file missing?
>>>>
>>>> This is two of the newly-used usage macros missing from older kernels, as
>>>> Christopher noticed. Should be fixed now. Please redownload and try again.
>>>>
>>> Thanks a lot! Now everything seems to work.
>>> Do you still want me to send any test output?
>>
>> No, thank you.
>>
>>> Will I have to reinstall the driver whenever a new kernel arrives?
>>
>> Yes, unfortunately. I need to get around to DKMS support implementation.
>>
> I found that the tablet stops to work when the computer is suspended and resumed.
> One way to get it to work, is to unplug / plug the tablet
> or to do
>          rmmod hid_uclogic; modprobe hid_uclogic
>
> This, of course can be automated by a script in pm-utils/sleep.d.
> But could the driver itself take care of this?

Alright, I reproduced it. The tablet needs to be re-enabled on resume. I'll
see if we can do that.

Nick

Hi Alec,

On 03/25/2015 03:39 PM, Alec Teal wrote:
> I hate to do this but it's been 5 days and now all I'm finding from
> search results are my own questions.
>
> This is not an area I've ever had to deal with (anything with the letter
> x infront of it that is) but I really need at least an undo button.
>
> I did try with xbindkeys, but I don't want to remap "normal" keyboard
> shortcuts and Gimp doesn't recognise that the tablet has hardware buttons.
>
> Also the undo button (top one, causes active window to [attempt] to
> close) causes a segfault with xbindkeys -k which is really weird.
>
> Anyway how can I help fix this? I really need that undo button.

You can try to use the latest development version with the Wacom tablet driver
(xf86-input-wacom). The latest development version is available here:

     https://github.com/DIGImend/digimend-kernel-drivers/archive/master.zip

Build and install the above as described in README.md. Then install the Wacom
tablet driver (xf86-input-wacom) from your distro package repositories.

Put this into a file under /etc/X11/xorg.conf.d, e.g.
/etc/X11/xorg.conf.d/10-huion.conf:

     Section "InputClass"
             Identifier "Huion tablet"
             MatchUSBID "256c:006e"
             MatchDevicePath "/dev/input/event*"
             Driver "wacom"
     EndSection

Then restart X, or just the whole machine.

Connect the tablet and check if the Wacom driver has gotten hold of the tablet.
The output of "xsetwacom --list" should list your tablet devices. There should
be a pad and a stylus device.

If that's so, you should be able to use the "xsetwacom" command to change the
button bindings. E.g. to make the first button send "Ctrl-Z" (i.e. "Undo"),
you'll need to execute this command:

     xsetwacom --set "DEVICE_NAME" Button 1 key +ctrl +z -z -ctrl

where DEVICE_NAME is the pad device name from the "xsetwacom --list" output.
In my case the "xsetwacom --list" output was this:

     10594 Pad pad                           id: 13  type: PAD
     10594 Pen stylus                        id: 14  type: STYLUS

and the command, this:

     xsetwacom --set "10594 Pad pad" Button 1 key +ctrl +z -z -ctrl

Please read "xsetwacom" man page for more details on its usage.

Nick

On 03/28/2015 11:35 PM, Nikolai Kondrashov wrote:
> I have noticed some strange button behavior with my H610 which I'm yet to
> investigate, but it is supposed to work.

I don't see this now. I guess that was an issue with an rc of 4.0 kernel.

Nick

Hi Dan,

On 03/28/2015 11:39 PM, Dan Roberts wrote:
> Hi Everyone,
>      I've had my Huion H610 for almost a year now, and it has exhibited the same behavior the entire time I've owned it, across multiple drivers versions, and across changing the pen "tip".
>
> Occasionally when the pen is not touching the tablet, but in proximity, I receive events for full pressure (2047), sometimes in rapid succession. Pressure will spike from 0 to 2047 and back. When drawing in Gimp it sort of looked like the tool was "dripping", as max pressure events made large marks on the image. I instrumented hid-huion with a large amount of logging and observed that these events existed at the kernel level, and I was able to mitigate (or eliminate?) them by detecting instantaneous transitions between minimum and maximum pressure and throwing out these events. This was admittedly a pretty dirty hack, and I haven't ported it over to driver v5 yet.
>
> *Has anyone else with a H610 noticed this problem?*
> *
> *
> It seems there's some possibility it could be a hardware OR software issue, so I'm curious if anyone else has noticed this.

I think I've heard about this before, but can't find any evidence ATM. I
suspect it's rather a hardware issue. You can check with "usbhid-dump -es".
If you see the pressure jumps there (the last two bytes in pen report), then
it is 99% a hardware failure.

Nick

Hi Everyone,
    I've had my Huion H610 for almost a year now, and it has exhibited the
same behavior the entire time I've owned it, across multiple drivers
versions, and across changing the pen "tip".

Occasionally when the pen is not touching the tablet, but in proximity, I
receive events for full pressure (2047), sometimes in rapid succession.
Pressure will spike from 0 to 2047 and back. When drawing in Gimp it sort
of looked like the tool was "dripping", as max pressure events made large
marks on the image. I instrumented hid-huion with a large amount of logging
and observed that these events existed at the kernel level, and I was able
to mitigate (or eliminate?) them by detecting instantaneous transitions
between minimum and maximum pressure and throwing out these events. This
was admittedly a pretty dirty hack, and I haven't ported it over to driver
v5 yet.

*Has anyone else with a H610 noticed this problem?*

It seems there's some possibility it could be a hardware OR software issue,
so I'm curious if anyone else has noticed this.

Thanks,
Dan

Hi Dan,

On 03/28/2015 11:28 PM, Dan Roberts wrote:
> I've upgraded my driver version to 3c84976911c16963bad1386c4d76316379d12681
> and I see that I now have 6 (uniquely named, yay!) xinput devices. The *Pad
> device produces button events as expected, though Button 2 (eraser on the
> pad frame) seems to generate some keyboard input, and button 3 (pen picture
> on the pad frame) seems to be treated as a right click. All of this is with
> xf86-input-evdev though. *Are we intended now to use xf86-input-wacom to map
> abstract buttons to keyboard events?* I know compatibility with
> xf86-input-wacom was one of the goals of this patch set.

Yes, the latest master is supposed to be used with xf86-input-wacom, if you
want to use the frame buttons.

I have noticed some strange button behavior with my H610 which I'm yet to
investigate, but it is supposed to work.

Nick

Hi,
    I've upgraded my driver version
to 3c84976911c16963bad1386c4d76316379d12681 and I see that I now have 6
(uniquely named, yay!) xinput devices. The *Pad device produces button
events as expected, though Button 2 (eraser on the pad frame) seems to
generate some keyboard input, and button 3 (pen picture on the pad frame)
seems to be treated as a right click. All of this is with xf86-input-evdev
though. *Are we intended now to use xf86-input-wacom to map abstract
buttons to keyboard events?* I know compatibility with xf86-input-wacom was
one of the goals of this patch set.

Thanks,
Dan

On 03/28/2015 12:51 AM, dm...@li... wrote:
>>> ./scripts/gcc-version.sh: line 25: gcc: command not found
>>> .
> /scripts/gcc-version.sh: line 26: gcc: command not found
>>>
>>> I
> guessing I need to update something to do with a C compiler?
>>>
>>
>> Yes,
> you need to install the compiler. You might be able to do that and also
>
>> install other possible requisites by installing "build-essential"
> package.
>>
>> Nick
>>
>
> Success!
> Gcc was not installed so I used Lubuntu
> Software Centre to install Gcc GNU C compiler ver 4:4.9.1-4ubuntu2(gcc)
> rather than build-essentials and the make / sudo make install routine
> worked fine.
> Thanks Nick for your time and knowledge, the tablet is for
> my girlfriend and you've put me on the good list!

Glad to hear that :)

You're welcome.

Nick

>> ./scripts/gcc-version.sh: line 25: gcc: command not found
>> .
/scripts/gcc-version.sh: line 26: gcc: command not found
>>
>> I 
guessing I need to update something to do with a C compiler?
>>
>
>Yes, 
you need to install the compiler. You might be able to do that and also

>install other possible requisites by installing "build-essential" 
package.
>
>Nick
>

Success!
Gcc was not installed so I used Lubuntu 
Software Centre to install Gcc GNU C compiler ver 4:4.9.1-4ubuntu2(gcc) 
rather than build-essentials and the make / sudo make install routine 
worked fine.
Thanks Nick for your time and knowledge, the tablet is for 
my girlfriend and you've put me on the good list!
Martin.

Hi Martin,

Please keep the maillist in the CC. Thank you. See my reply below.

On 03/27/2015 10:04 PM, mk wrote:
> On Fri, 27 Mar 2015 12:06:06 +0200
> Nikolai Kondrashov <sp...@gm...> wrote:
> On 03/27/2015 09:13 AM, dm...@li... wrote:
>> Hi,
>> I'm strugling with the digimend v5 driver for a Huion 610 tablet on
>> lubuntu. Out of the box the tablet controls the cursor but generates
>> multiple button presses which will for instance open ten or more
>> windows on a tray icon click. I have tried the tablet in windows with
>> it's own driver and it works correctly.
>> When I try to "make" the
>> modules I get this message:
>>
>> make -C /lib/modules/3.13.0-37-
>> generic/build SUBDIRS=/home/steph/Downloads/digimend-kernel-drivers-5
>> modules
>> make[1]: *** /lib/modules/3.13.0-37-generic/build: No such file
>> or directory. Stop.
>> Makefile:10: recipe for target 'modules' failed
>>
>> make: *** [modules] Error 2
>
> That means you don't have kernel headers installed and the driver is not being
> built nor installed.
>
> If you're using Ubuntu you can try installing them with this command:
>
>       sudo apt-get install linux-headers-$(uname -r)
>
> And then try to build and install the driver again.
>
> Nick
>
> Thanks for the reply Nick.
>
> Tried to sudo apt-get install linux-headers-$(uname -r)
>
> Got this message:
>
> Reading package lists... Done
> Building dependency tree       Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Package linux-headers-3.13.0-37-generic is not available, but is referred to by another package.
> This may mean that the package is missing, has been obsoleted, or
> is only available from another source
>
> E: Package 'linux-headers-3.13.0-37-generic' has no installation candidate
>
> Tried Lubuntu Software Centre to install:
> linux-headers-3.13.0-37-generic
> but it freezes.
>
> Synaptic lists that package as obsolete which may explain the above so I used synaptic to install the next available kernel:
>
> linux-headers-3.16.0-23 (i386)
> linux-headers-3.16.0-23-generic (i386)
> linux-image-3.16.0-23-generic (i386)
> linux-image-extra-3.16.0-23-generic(i386)
>
> rebooted to this kernel and tried to make but got this message:
>
> make[1]: Entering directory '/usr/src/linux-headers-3.16.0-23-generic'
> ./scripts/gcc-version.sh: line 25: gcc: command not found
> ./scripts/gcc-version.sh: line 26: gcc: command not found
>
> I guessing I need to update something to do with a C compiler?
>

Yes, you need to install the compiler. You might be able to do that and also
install other possible requisites by installing "build-essential" package.

Nick

Hi Martin,

On 03/27/2015 09:13 AM, dm...@li... wrote:
> Hi,
> I'm strugling with the digimend v5 driver for a Huion 610 tablet on
> lubuntu. Out of the box the tablet controls the cursor but generates
> multiple button presses which will for instance open ten or more
> windows on a tray icon click. I have tried the tablet in windows with
> it's own driver and it works correctly.
> When I try to "make" the
> modules I get this message:
>
> make -C /lib/modules/3.13.0-37-
> generic/build SUBDIRS=/home/steph/Downloads/digimend-kernel-drivers-5
> modules
> make[1]: *** /lib/modules/3.13.0-37-generic/build: No such file
> or directory. Stop.
> Makefile:10: recipe for target 'modules' failed
>
> make: *** [modules] Error 2

That means you don't have kernel headers installed and the driver is not being
built nor installed.

If you're using Ubuntu you can try installing them with this command:

     sudo apt-get install linux-headers-$(uname -r)

And then try to build and install the driver again.

Nick

Hi,
I'm strugling with the digimend v5 driver for a Huion 610 tablet on 
lubuntu. Out of the box the tablet controls the cursor but generates 
multiple button presses which will for instance open ten or more 
windows on a tray icon click. I have tried the tablet in windows with 
it's own driver and it works correctly.
When I try to "make" the 
modules I get this message:

make -C /lib/modules/3.13.0-37-
generic/build SUBDIRS=/home/steph/Downloads/digimend-kernel-drivers-5 
modules
make[1]: *** /lib/modules/3.13.0-37-generic/build: No such file 
or directory. Stop.
Makefile:10: recipe for target 'modules' failed

make: *** [modules] Error 2

I don't have a dir /lib/modules/3.13.0-37-
generic/build on my system. I have tried adding the directory manually 
but then I get this error message instead:

make -C /lib/modules/3.13.0-
37-generic/build SUBDIRS=/home/steph/Downloads/digimend-kernel-drivers-
5 modules
make[1]: Entering directory '/lib/modules/3.13.0-37-
generic/build'
make[1]: *** No rule to make target 'modules'. Stop.
make
[1]: Leaving directory '/lib/modules/3.13.0-37-generic/build'
Makefile:
10: recipe for target 'modules' failed
make: *** [modules] Error 2

Again that file is not on my system. I'm guessing it's the hid-rebind.
rules that comes in the digimen-kernel-drivers-5 package. I have also 
tried the version 4 driver with the same results.
Please could you 
advise as I'm right at the limit of my understanding of linux.
Thanks

Martin.

On Wed, 25 Mar 2015 15:13:08 +0100
co...@pi... wrote:

>Dear Alec,
>
>Some times ago, I had a discussion with someone on how to map the
>button of the tablet, here is the solution we came up with :
>
>(a little disclaimer: I am not exactly a computer scientist and I have 
>managed to make the key "work" but it is not really clean and I won't
>be able to explain every step in depth ^^.
>A documentation that has helped me a lot is available on the arch
>wiki : https://wiki.archlinux.org/index.php/Map_scancodes_to_keycodes)
>
>Anyway, here is the full process I have followed :
>1. First, you need to identify the vendor_id and product_id of your 
>tablet by looking for it in the usb device list (with the 'lsusb' 
>command), my vendor ID is 256C and my product ID is 006E. I guess they 
>are the same for you but you may want to check.
>2. Then, you can create the .hwdb file containing your rules in 
>/etc/udev/hwdb.d
>I have called mine huion.hwdb
>Before writing the rules for the tablet, you need to specify that
>those rules will apply to this device by specifying its ID as :
>keyboard:usb:v256Cp006E*
>  KEYBOARD_KEY_700e0=unknown # This is a rule, see below
>
>After the first line, each rule line begins with a space. A rule is 
>defined on the left of the equality by the input key and on the right
>by the new key you want to have.
>3. To identify scancodes, I have used the command 'evtest' in root. It 
>asks you to choose the right device, for some reasons I had several 
>huion tablet listed, so I tried them all and used the one that
>actually responded to the input buttons.
>You can find in the attached file the output I get when I press the 
>eraser button.
>The first 5 lines seem to be triggered by the push down of the button 
>and the last 5 ones by the release.
>
>The first line say that the first key to be pressed has the code 700e1 
>and the following line tells us that it is LEFT_SHIFT.
>Then the two following lines say that the key KPMINUS is pressed and
>its code is 70056
>Hence, by default, pressing the eraser button leads to "shift"+ "-" 
>which is not exactly what I want. And by testing the other buttons you 
>will see that each one uses some key modifier like Alt or Ctrl.
>
>4. Now that you have identified the inputs associated to this button, 
>you can remap it in your .hwdb file
>--> From this point I have made very personal choices that you may
>want to change ^^
>I have decided to get rid of the modifier keys "shift", "alt" and
>"ctrl" so I have first mapped them to the key "rightctrl" (I did not
>find a way to completely discard these inputs), and then I have
>assigned the other inputs to key that are not on my keyboard : f13->f21
>
>Here is my .hwdb file :
>
>keyboard:usb:v256Cp006E*
>  KEYBOARD_KEY_700e0=rightctrl # map ctrl to something useless like 
>rightctrl
>  KEYBOARD_KEY_700e1=rightctrl # shift -> rightctrl
>  KEYBOARD_KEY_700e2=rightctrl # alt -> rightctrl
>  KEYBOARD_KEY_7003d=f13 # back button -> f13
>  KEYBOARD_KEY_70016=f14 # eraser --> f14
>  KEYBOARD_KEY_70056=f15 # pencil --> f15
>  KEYBOARD_KEY_70057=f16 # + --> f16
>  KEYBOARD_KEY_7000a=f17 # - -->f17
>  KEYBOARD_KEY_70019=f18 # pencil + --> f18
>  KEYBOARD_KEY_7001b=f21 # pencil - --> f21
>  KEYBOARD_KEY_70006=f20 # hand --> f20
>
>I have assigned the inputs to keys that are not on my keyboard to be 
>able to use the same button for different shortcut depending on the
>used application by using "autokey" which enables to remap (again...)
>keys to others depending on the current application.
>
>(For autokey, see for instance 
>http://www.howtogeek.com/howto/26913/how-to-customize-shortcut-keys-for-any-linux-application/ 
>)
>
>5. to load the rules you must do (as root) :
>
>udevadm hwdb --update
>udevadm trigger
>
>6. You can check your rules by launching evtest again.
>
>I think that there is a cleaner way to proceed, especially concerning 
>the modifier keys, but it seems to work...
>I hope this helps!
>
>

Nice and concise writeup - thanks a lot! You should write manuals
for a living :)

--
Regards,
Christopher Barry

Random geeky fortune:
The human race has one really effective weapon, and that is laughter.
		-- Mark Twain

Dear Alec,

Some times ago, I had a discussion with someone on how to map the button 
of the tablet, here is the solution we came up with :

(a little disclaimer: I am not exactly a computer scientist and I have 
managed to make the key "work" but it is not really clean and I won't be 
able to explain every step in depth ^^.
A documentation that has helped me a lot is available on the arch wiki : 
https://wiki.archlinux.org/index.php/Map_scancodes_to_keycodes)

Anyway, here is the full process I have followed :
1. First, you need to identify the vendor_id and product_id of your 
tablet by looking for it in the usb device list (with the 'lsusb' 
command), my vendor ID is 256C and my product ID is 006E. I guess they 
are the same for you but you may want to check.
2. Then, you can create the .hwdb file containing your rules in 
/etc/udev/hwdb.d
I have called mine huion.hwdb
Before writing the rules for the tablet, you need to specify that those 
rules will apply to this device by specifying its ID as :
keyboard:usb:v256Cp006E*
  KEYBOARD_KEY_700e0=unknown # This is a rule, see below

After the first line, each rule line begins with a space. A rule is 
defined on the left of the equality by the input key and on the right by 
the new key you want to have.
3. To identify scancodes, I have used the command 'evtest' in root. It 
asks you to choose the right device, for some reasons I had several 
huion tablet listed, so I tried them all and used the one that actually 
responded to the input buttons.
You can find in the attached file the output I get when I press the 
eraser button.
The first 5 lines seem to be triggered by the push down of the button 
and the last 5 ones by the release.

The first line say that the first key to be pressed has the code 700e1 
and the following line tells us that it is LEFT_SHIFT.
Then the two following lines say that the key KPMINUS is pressed and its 
code is 70056
Hence, by default, pressing the eraser button leads to "shift"+ "-" 
which is not exactly what I want. And by testing the other buttons you 
will see that each one uses some key modifier like Alt or Ctrl.

4. Now that you have identified the inputs associated to this button, 
you can remap it in your .hwdb file
--> From this point I have made very personal choices that you may want 
to change ^^
I have decided to get rid of the modifier keys "shift", "alt" and "ctrl" 
so I have first mapped them to the key "rightctrl" (I did not find a way 
to completely discard these inputs), and then I have assigned the other 
inputs to key that are not on my keyboard : f13->f21

Here is my .hwdb file :

keyboard:usb:v256Cp006E*
  KEYBOARD_KEY_700e0=rightctrl # map ctrl to something useless like 
rightctrl
  KEYBOARD_KEY_700e1=rightctrl # shift -> rightctrl
  KEYBOARD_KEY_700e2=rightctrl # alt -> rightctrl
  KEYBOARD_KEY_7003d=f13 # back button -> f13
  KEYBOARD_KEY_70016=f14 # eraser --> f14
  KEYBOARD_KEY_70056=f15 # pencil --> f15
  KEYBOARD_KEY_70057=f16 # + --> f16
  KEYBOARD_KEY_7000a=f17 # - -->f17
  KEYBOARD_KEY_70019=f18 # pencil + --> f18
  KEYBOARD_KEY_7001b=f21 # pencil - --> f21
  KEYBOARD_KEY_70006=f20 # hand --> f20

I have assigned the inputs to keys that are not on my keyboard to be 
able to use the same button for different shortcut depending on the used 
application by using "autokey" which enables to remap (again...) keys to 
others depending on the current application.

(For autokey, see for instance 
http://www.howtogeek.com/howto/26913/how-to-customize-shortcut-keys-for-any-linux-application/ 
)

5. to load the rules you must do (as root) :

udevadm hwdb --update
udevadm trigger

6. You can check your rules by launching evtest again.

I think that there is a cleaner way to proceed, especially concerning 
the modifier keys, but it seems to work...
I hope this helps!

Le 25.03.2015 14:39, Alec Teal a écrit :
> I hate to do this but it's been 5 days and now all I'm finding from
> search results are my own questions.
> 
> This is not an area I've ever had to deal with (anything with the 
> letter
> x infront of it that is) but I really need at least an undo button.
> 
> I did try with xbindkeys, but I don't want to remap "normal" keyboard
> shortcuts and Gimp doesn't recognise that the tablet has hardware 
> buttons.
> 
> Also the undo button (top one, causes active window to [attempt] to
> close) causes a segfault with xbindkeys -k which is really weird.
> 
> Anyway how can I help fix this? I really need that undo button.
> 
> Thanks,
> 
> Alec
> 
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, 
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub 
> for all
> things parallel software development, from weekly thought leadership 
> blogs to
> news, videos, case studies, tutorials and more. Take a look and join 
> the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> DIGImend-users mailing list
> DIG...@li...
> https://lists.sourceforge.net/lists/listinfo/digimend-users

not knowing anything about tablets I ordered a set.  I forgot the location
( google will help ).
Rather expensive abt US$15 for eight shipped from Kentucky I think.

On Wed, Mar 11, 2015 at 11:00 AM, Nikolai Kondrashov <sp...@gm...>
wrote:

> On 03/05/2015 11:43 PM, Ulrich Lauther wrote:
> > My HUION graphics tablet H610PRO comes with a couple of pen tips,
> > obviously because they wear out.
> > Just out of curiosity: does anybody know what the physical effect
> > and cause for any wearout is?
>
> AFAIK, the nibs (pen tips) get ground down on the tablet surface over time.
> You can find some articles/videos on the web if you search for "worn out
> wacom
> pen nib/tip".
>
> Nick
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> DIGImend-users mailing list
> DIG...@li...
> https://lists.sourceforge.net/lists/listinfo/digimend-users
>

Included is a copy of my version of the Huion drivers and a
shell script I wrote to configure the buttons. Just tested it again after
install of
new kernel ( 3.19.1-201.fc21.i686+PAE ).

-----Installing------

cd into the folder this guy creates
(if a new kernel  $ touch *c)
$ make
$sudo make install
restart X
remove / reinstall the usb to tablet
run the huion.sh shell script.

-------------
I haven't been able to get the huion.sh shell script to trigger
automagically when
plugging in the tablet.
I am left handed and setup the X11 config (
/etc/X11/xorg.conf.d/50-huion.conf ) appropriately
( included in my tarfile).

Hopefully the huion.sh script makes sense to allow you to config to your
desires.

There has been a good bit of traffic on the developers news group
with efforts to re-organize the modules but they didn't work for me,
probably because
I didn't understand them.

------------
Vince

I hate to do this but it's been 5 days and now all I'm finding from 
search results are my own questions.

This is not an area I've ever had to deal with (anything with the letter 
x infront of it that is) but I really need at least an undo button.

I did try with xbindkeys, but I don't want to remap "normal" keyboard 
shortcuts and Gimp doesn't recognise that the tablet has hardware buttons.

Also the undo button (top one, causes active window to [attempt] to 
close) causes a segfault with xbindkeys -k which is really weird.

Anyway how can I help fix this? I really need that undo button.

Thanks,

Alec

On 03/17/2015 05:15 AM, Vince Herried wrote:
> running a stock kernel   3.18.9-200.fc21.i686+PAE  ( no modified kernel updates )
> I get
> [vince@desk2 uclogic-tools-4]$  sudo ./uclogic-probe 4 3
> M 48 00 55 00 49 00 4F 00 4E 00 00 00 00 00 00 00
> P 50 00 65 00 6E 00 54 00 61 00 62 00 6C 00 65 00 74 00 00 00
> S 64 0E 03 40 9C A8 61 03 00 FF 07 A0 0F 08 00
> S 65 04 03 20 A0
> S 6E 04 03 00 30
> S 79 14 03 48 00 41 00 36 00 30 00 00 00 00 00 00 00 00 00 00 00
> S 7A 08 03 01 08 00 00 00 00
> S 7B 0C 03 48 00 4B 00 20 00 4F 00 6E 00

Thanks a lot, Vince!

Nick

running a stock kernel   3.18.9-200.fc21.i686+PAE  ( no modified kernel
updates )
I get
[vince@desk2 uclogic-tools-4]$  sudo ./uclogic-probe 4 3
M 48 00 55 00 49 00 4F 00 4E 00 00 00 00 00 00 00
P 50 00 65 00 6E 00 54 00 61 00 62 00 6C 00 65 00 74 00 00 00
S 64 0E 03 40 9C A8 61 03 00 FF 07 A0 0F 08 00
S 65 04 03 20 A0
S 6E 04 03 00 30
S 79 14 03 48 00 41 00 36 00 30 00 00 00 00 00 00 00 00 00 00 00
S 7A 08 03 01 08 00 00 00 00
S 7B 0C 03 48 00 4B 00 20 00 4F 00 6E 00

On Mon, Mar 16, 2015 at 5:47 PM, Nikolai Kondrashov <sp...@gm...>
wrote:

> Dear users of digimend-kernel-drivers,
>
> I'm writing to the DIGImend-users list and addressing a lot of people
> directly
> with a "blind" copy.
>
> Benjamin Tissoires and me are working on making digimend-kernel-drivers
> compatible with current and future versions of the Wacom driver
> (xf86-input-wacom), especially with regard to adding support for remapping
> frame buttons to arbitrary key combinations.
>
> This concerns Huion, Yiynova, Ugee tablets, as well as UC-Logic TWHA60 v3
> tablet.
>
> We would like to ask everyone owning one of these tablets to please take
> some
> diagnostics information from their tablets and send them in reply to this
> message.
>
> To do that please download, build or install the latest version of
> uclogic-tools (previously huion-tools):
>
>     https://github.com/DIGImend/uclogic-tools/releases/tag/v4
>
> Find the bus number and device address of your tablet in "lsusb" output:
>
>     $ lsusb
>     Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching
> Hub
>     Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>     Bus 001 Device 004: ID 04f2:b2ea Chicony Electronics Co., Ltd
> Integrated Camera [ThinkPad]
>     Bus 001 Device 003: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0
> [ThinkPad]
>     Bus 001 Device 008: ID 256c:006e
>
> Here, the last line is a Huion tablet. It is on bus 1, with device address
> 8.
> If you can't spot your tablet, try unplugging it, running "lsusb",
> plugging it
> back, running "lsusb" again and finding the new line.
>
> Execute uclogic-probe, supplying it with the bus number and device address
> you
> found. For the lsusb output above, and if you installed uclogic-tools, it
> will
> look like this:
>
>     $ sudo uclogic-probe 1 8
>
> If you just built it without installing, run from the build tree, like
> this:
>
>     $ sudo ./uclogic-probe 1 8
>
> Please send the output of either of these commands, plus "lsusb -v" output.
>
> More information on uclogic-tools building, installation and usage is
> available in its README.md:
>
>     https://github.com/DIGImend/uclogic-tools/blob/master/README.md
>
> Thank you.
>
> Sincerely,
> Nick
>

2012	Jan	Feb	Mar	Apr (58)	May (72)	Jun (24)	Jul	Aug (12)	Sep (9)	Oct (10)	Nov (2)	Dec (4)
2013	Jan (5)	Feb (23)	Mar	Apr	May (4)	Jun (7)	Jul (2)	Aug (2)	Sep (5)	Oct (7)	Nov (31)	Dec (11)
2014	Jan (13)	Feb (4)	Mar (1)	Apr (1)	May (1)	Jun (2)	Jul (12)	Aug (10)	Sep (13)	Oct (15)	Nov (49)	Dec (4)
2015	Jan (49)	Feb (62)	Mar (81)	Apr (10)	May (4)	Jun (6)	Jul (17)	Aug (3)	Sep (1)	Oct (4)	Nov	Dec (8)
2016	Jan (8)	Feb (5)	Mar (7)	Apr (7)	May (3)	Jun (4)	Jul (12)	Aug (8)	Sep (6)	Oct (4)	Nov (1)	Dec

digimend-users Mailing List for DIGImend (Page 4)

digimend-users — General discussion and user support