Thread: [DIGImend-users] Experiencing lag (with Huion 1060)
Brought to you by:
spb_nick
Menu
▾
▴
digimend-users
|
From: Sarah O. <owe...@gm...> - 2015-02-28 22:57:11
|
I am trying to set up my Huion 1060pro ( http://huion-tablet.com/product/product.php?sku=1020), in Ubuntu 14.04. I installed the DIGImend drivers by following the instructions on github, and I'm having a few problems. When drawing on Krita or the Gimp, my brush-stroke lags seconds behind where my pen is. The stroke seems to buffer up, and will finish out the stroke, but takes forever to do so. To solve this problem, I was thinking I might need an xorg.config to lower sampling rate? My computer has 8g of RAM (5 reported as "free"). My other problem is none of the butttons work, except for left-click on the pen. Does this device have a known status with the drivers? (It looked like it fell in the "other" category for supported Huion devices). Thanks! Sarah |
|
From: Dan R. <ade...@gm...> - 2015-03-01 00:26:14
|
Hi Sarah,
I have a Huion h610 which has a similar report rate and experienced
similar issues, but they have stopped recently. I *believe* they were
resolved when I switched to a slightly modified version of the current
driver. There is a new version of the driver in development, that *might*
resolve it for you if i'm not mistaken. By the way, what is the USB VID and
PID of your Huion 1060? I don't see it in the tablet list on
http://digimend.github.io/tablets/ . My h610 is 256c:006e (according to
lsusb) for example.
Thanks,
Dan
On Sat, Feb 28, 2015 at 2:56 PM, Sarah Owens <owe...@gm...> wrote:
> I am trying to set up my Huion 1060pro (
> http://huion-tablet.com/product/product.php?sku=1020), in Ubuntu 14.04.
> I installed the DIGImend drivers by following the instructions on github,
> and I'm having a few problems.
>
> When drawing on Krita or the Gimp, my brush-stroke lags seconds behind
> where my pen is. The stroke seems to buffer up, and will finish out the
> stroke, but takes forever to do so.
>
> To solve this problem, I was thinking I might need an xorg.config to lower
> sampling rate? My computer has 8g of RAM (5 reported as "free").
>
> My other problem is none of the butttons work, except for left-click on
> the pen. Does this device have a known status with the drivers? (It
> looked like it fell in the "other" category for supported Huion devices).
>
> Thanks!
> Sarah
>
>
> ------------------------------------------------------------------------------
> 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
>
>
|
|
From: Sarah O. <owe...@gm...> - 2015-03-01 00:51:05
|
Thanks for the info, Dan. Is the new version of the driver in a feature branch? (I built from master earlier today). >From lsusb, I think my USB is 256c:006e, like yours. The device was unnamed, but it was one of two that showed up on lsusb after I had connected the tablet. (The second one was "058f:6254 Alcor Micro Corp. USB Hub") Sarah On Sat, Feb 28, 2015 at 4:26 PM, Dan Roberts <ade...@gm...> wrote: > Hi Sarah, > I have a Huion h610 which has a similar report rate and experienced > similar issues, but they have stopped recently. I *believe* they were > resolved when I switched to a slightly modified version of the current > driver. There is a new version of the driver in development, that *might* > resolve it for you if i'm not mistaken. By the way, what is the USB VID and > PID of your Huion 1060? I don't see it in the tablet list on > http://digimend.github.io/tablets/ . My h610 is 256c:006e (according to > lsusb) for example. > > Thanks, > Dan > > On Sat, Feb 28, 2015 at 2:56 PM, Sarah Owens <owe...@gm...> > wrote: > >> I am trying to set up my Huion 1060pro ( >> http://huion-tablet.com/product/product.php?sku=1020), in Ubuntu 14.04. >> I installed the DIGImend drivers by following the instructions on github, >> and I'm having a few problems. >> >> When drawing on Krita or the Gimp, my brush-stroke lags seconds behind >> where my pen is. The stroke seems to buffer up, and will finish out the >> stroke, but takes forever to do so. >> >> To solve this problem, I was thinking I might need an xorg.config to >> lower sampling rate? My computer has 8g of RAM (5 reported as "free"). >> >> My other problem is none of the butttons work, except for left-click on >> the pen. Does this device have a known status with the drivers? (It >> looked like it fell in the "other" category for supported Huion devices). >> >> Thanks! >> Sarah >> >> >> ------------------------------------------------------------------------------ >> 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 >> >> > |
|
From: Dan R. <ade...@gm...> - 2015-03-01 02:51:52
|
Hi Sarah,
That USB hub is interesting, doubly so that it has the same USB IDs as
the h610 but different specs on Huion's website... (tons of Huion tablets
share the same USB IDs though).
As far as I know the new driver isn't in any particular branch in the
official digimend git repository at the moment, a series of patches are
being merged into the kernel tree, and I guess those patches will then be
rebased against the digimend driver tree. I'm considering attempting that
this weekend for my own benefit. You can see the patches and the
surrounding discussion in the digimend-devel mailing list:
http://sourceforge.net/p/digimend/mailman/message/33498174/ this patch in
particular .
If you're feeling brave, since you have the same USB IDs as me, you might
be interested in trying out my modification to see if it makes any
difference. What it does is renames the Pen interface to "... Pen", which
allows Gimp to properly identify it (resolved an issue with me where I'd
have to restart Gimp multiple times and keep plugging/unplugging the tablet
until Gimp properly recognized the device, my theory is the issue you're
describing, which I also had, is related to this recognition issue)
You can find my change here:
https://github.com/Ademan/digimend-kernel-drivers/tree/rename_pen and you
can see here:
https://github.com/Ademan/digimend-kernel-drivers/commit/5a4f198af725b3137d19634ee8a0af7032f689d5
that it is a very simple change with little potential for issues.
However, if you do choose to test it, know it is a hack that only I have
tested, and* the main digimend driver should do something very similar (but
better) in the near future.*
To test it simply build it like you would the regular digimend driver, make
install it, and then you'll need to (as root) rmmod hid-uclogic ; modprobe
hid-uclogic to ensure your kernel loads/reloads the newly installed module.
In Gimp you'll want to disable the old device, and enable the new one
(named with "Pen" at the end).
Just to reiterate though, I think the new official changes should arrive
fairly soon, you're probably better off just waiting for that.
Cheers,
Dan
On Sat, Feb 28, 2015 at 4:50 PM, Sarah Owens <owe...@gm...> wrote:
> Thanks for the info, Dan. Is the new version of the driver in a feature
> branch? (I built from master earlier today).
>
> From lsusb, I think my USB is 256c:006e, like yours. The device was
> unnamed, but it was one of two that showed up on lsusb after I had
> connected the tablet. (The second one was "058f:6254 Alcor Micro Corp. USB
> Hub")
>
> Sarah
>
> On Sat, Feb 28, 2015 at 4:26 PM, Dan Roberts <ade...@gm...> wrote:
>
>> Hi Sarah,
>> I have a Huion h610 which has a similar report rate and experienced
>> similar issues, but they have stopped recently. I *believe* they were
>> resolved when I switched to a slightly modified version of the current
>> driver. There is a new version of the driver in development, that *might*
>> resolve it for you if i'm not mistaken. By the way, what is the USB VID and
>> PID of your Huion 1060? I don't see it in the tablet list on
>> http://digimend.github.io/tablets/ . My h610 is 256c:006e (according to
>> lsusb) for example.
>>
>> Thanks,
>> Dan
>>
>> On Sat, Feb 28, 2015 at 2:56 PM, Sarah Owens <owe...@gm...>
>> wrote:
>>
>>> I am trying to set up my Huion 1060pro (
>>> http://huion-tablet.com/product/product.php?sku=1020), in Ubuntu
>>> 14.04. I installed the DIGImend drivers by following the instructions on
>>> github, and I'm having a few problems.
>>>
>>> When drawing on Krita or the Gimp, my brush-stroke lags seconds behind
>>> where my pen is. The stroke seems to buffer up, and will finish out the
>>> stroke, but takes forever to do so.
>>>
>>> To solve this problem, I was thinking I might need an xorg.config to
>>> lower sampling rate? My computer has 8g of RAM (5 reported as "free").
>>>
>>> My other problem is none of the butttons work, except for left-click on
>>> the pen. Does this device have a known status with the drivers? (It
>>> looked like it fell in the "other" category for supported Huion devices).
>>>
>>> Thanks!
>>> Sarah
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> 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
>>>
>>>
>>
>
|
|
From: Sarah O. <owe...@gm...> - 2015-03-01 04:08:27
|
I'm trying out your patch, and from my git-log, I've gotten the patch successfully. From xinput --list, my only tablet option is called HUION PenTablet, (also the name Gimp gives it), which I think is what it was called before. What should the new name be, and where should I see the change? Thanks, Sarah On Sat, Feb 28, 2015 at 6:51 PM, Dan Roberts <ade...@gm...> wrote: > Hi Sarah, > That USB hub is interesting, doubly so that it has the same USB IDs as > the h610 but different specs on Huion's website... (tons of Huion tablets > share the same USB IDs though). > > As far as I know the new driver isn't in any particular branch in the > official digimend git repository at the moment, a series of patches are > being merged into the kernel tree, and I guess those patches will then be > rebased against the digimend driver tree. I'm considering attempting that > this weekend for my own benefit. You can see the patches and the > surrounding discussion in the digimend-devel mailing list: > http://sourceforge.net/p/digimend/mailman/message/33498174/ this patch in > particular . > > If you're feeling brave, since you have the same USB IDs as me, you might > be interested in trying out my modification to see if it makes any > difference. What it does is renames the Pen interface to "... Pen", which > allows Gimp to properly identify it (resolved an issue with me where I'd > have to restart Gimp multiple times and keep plugging/unplugging the tablet > until Gimp properly recognized the device, my theory is the issue you're > describing, which I also had, is related to this recognition issue) > > You can find my change here: > https://github.com/Ademan/digimend-kernel-drivers/tree/rename_pen and you > can see here: > https://github.com/Ademan/digimend-kernel-drivers/commit/5a4f198af725b3137d19634ee8a0af7032f689d5 > that it is a very simple change with little potential for issues. > > However, if you do choose to test it, know it is a hack that only I have > tested, and* the main digimend driver should do something very similar > (but better) in the near future.* > > To test it simply build it like you would the regular digimend driver, > make install it, and then you'll need to (as root) rmmod hid-uclogic ; > modprobe hid-uclogic to ensure your kernel loads/reloads the newly > installed module. > > In Gimp you'll want to disable the old device, and enable the new one > (named with "Pen" at the end). > > Just to reiterate though, I think the new official changes should arrive > fairly soon, you're probably better off just waiting for that. > > Cheers, > Dan > > On Sat, Feb 28, 2015 at 4:50 PM, Sarah Owens <owe...@gm...> > wrote: > >> Thanks for the info, Dan. Is the new version of the driver in a feature >> branch? (I built from master earlier today). >> >> From lsusb, I think my USB is 256c:006e, like yours. The device was >> unnamed, but it was one of two that showed up on lsusb after I had >> connected the tablet. (The second one was "058f:6254 Alcor Micro Corp. USB >> Hub") >> >> Sarah >> >> On Sat, Feb 28, 2015 at 4:26 PM, Dan Roberts <ade...@gm...> wrote: >> >>> Hi Sarah, >>> I have a Huion h610 which has a similar report rate and experienced >>> similar issues, but they have stopped recently. I *believe* they were >>> resolved when I switched to a slightly modified version of the current >>> driver. There is a new version of the driver in development, that *might* >>> resolve it for you if i'm not mistaken. By the way, what is the USB VID and >>> PID of your Huion 1060? I don't see it in the tablet list on >>> http://digimend.github.io/tablets/ . My h610 is 256c:006e (according to >>> lsusb) for example. >>> >>> Thanks, >>> Dan >>> >>> On Sat, Feb 28, 2015 at 2:56 PM, Sarah Owens <owe...@gm...> >>> wrote: >>> >>>> I am trying to set up my Huion 1060pro ( >>>> http://huion-tablet.com/product/product.php?sku=1020), in Ubuntu >>>> 14.04. I installed the DIGImend drivers by following the instructions on >>>> github, and I'm having a few problems. >>>> >>>> When drawing on Krita or the Gimp, my brush-stroke lags seconds behind >>>> where my pen is. The stroke seems to buffer up, and will finish out the >>>> stroke, but takes forever to do so. >>>> >>>> To solve this problem, I was thinking I might need an xorg.config to >>>> lower sampling rate? My computer has 8g of RAM (5 reported as "free"). >>>> >>>> My other problem is none of the butttons work, except for left-click on >>>> the pen. Does this device have a known status with the drivers? (It >>>> looked like it fell in the "other" category for supported Huion devices). >>>> >>>> Thanks! >>>> Sarah >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> 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 >>>> >>>> >>> >> > |
|
From: Dan R. <ade...@gm...> - 2015-03-01 04:52:38
|
Forgot to reply-all. On Sat, Feb 28, 2015 at 8:51 PM, Dan Roberts <ade...@gm...> wrote: > Hi Sarah, > It should be named "HUION PenTablet Pen" in that case. It should be > named that in Gimp as well as `xinput --list`. The fact that it's not > showing up makes me wonder if either the wrong driver is being loaded for > your tablet, do you mind checking out the output from dmesg when you plug > in your tablet? (I've had hid-huion, the old driver, grab the tablet > instead of the new hid-uclogic, and I'd see messages with 'huion' instead > of 'uclogic'). Did you make sure to rmmod and modprobe the hid-uclogic to > reload it? You should probably also re-connect the tablet for good measure. > The only other possibility that comes to mind is that the 1060 has > significantly different interfaces from the h610, which shouldn't happen > based on my understanding of the code, but it's not impossible since I'm > not 100% familiar with the new code. > > Thanks, > Dan > > On Sat, Feb 28, 2015 at 8:07 PM, Sarah Owens <owe...@gm...> > wrote: > >> I'm trying out your patch, and from my git-log, I've gotten the patch >> successfully. From xinput --list, my only tablet option is called HUION >> PenTablet, (also the name Gimp gives it), which I think is what it was >> called before. What should the new name be, and where should I see the >> change? >> >> Thanks, >> Sarah >> >> On Sat, Feb 28, 2015 at 6:51 PM, Dan Roberts <ade...@gm...> wrote: >> >>> Hi Sarah, >>> That USB hub is interesting, doubly so that it has the same USB IDs >>> as the h610 but different specs on Huion's website... (tons of Huion >>> tablets share the same USB IDs though). >>> >>> As far as I know the new driver isn't in any particular branch in the >>> official digimend git repository at the moment, a series of patches are >>> being merged into the kernel tree, and I guess those patches will then be >>> rebased against the digimend driver tree. I'm considering attempting that >>> this weekend for my own benefit. You can see the patches and the >>> surrounding discussion in the digimend-devel mailing list: >>> http://sourceforge.net/p/digimend/mailman/message/33498174/ this patch >>> in particular . >>> >>> If you're feeling brave, since you have the same USB IDs as me, you >>> might be interested in trying out my modification to see if it makes any >>> difference. What it does is renames the Pen interface to "... Pen", which >>> allows Gimp to properly identify it (resolved an issue with me where I'd >>> have to restart Gimp multiple times and keep plugging/unplugging the tablet >>> until Gimp properly recognized the device, my theory is the issue you're >>> describing, which I also had, is related to this recognition issue) >>> >>> You can find my change here: >>> https://github.com/Ademan/digimend-kernel-drivers/tree/rename_pen and >>> you can see here: >>> https://github.com/Ademan/digimend-kernel-drivers/commit/5a4f198af725b3137d19634ee8a0af7032f689d5 >>> that it is a very simple change with little potential for issues. >>> >>> However, if you do choose to test it, know it is a hack that only I have >>> tested, and* the main digimend driver should do something very similar >>> (but better) in the near future.* >>> >>> To test it simply build it like you would the regular digimend driver, >>> make install it, and then you'll need to (as root) rmmod hid-uclogic ; >>> modprobe hid-uclogic to ensure your kernel loads/reloads the newly >>> installed module. >>> >>> In Gimp you'll want to disable the old device, and enable the new one >>> (named with "Pen" at the end). >>> >>> Just to reiterate though, I think the new official changes should arrive >>> fairly soon, you're probably better off just waiting for that. >>> >>> Cheers, >>> Dan >>> >>> On Sat, Feb 28, 2015 at 4:50 PM, Sarah Owens <owe...@gm...> >>> wrote: >>> >>>> Thanks for the info, Dan. Is the new version of the driver in a >>>> feature branch? (I built from master earlier today). >>>> >>>> From lsusb, I think my USB is 256c:006e, like yours. The device was >>>> unnamed, but it was one of two that showed up on lsusb after I had >>>> connected the tablet. (The second one was "058f:6254 Alcor Micro Corp. USB >>>> Hub") >>>> >>>> Sarah >>>> >>>> On Sat, Feb 28, 2015 at 4:26 PM, Dan Roberts <ade...@gm...> >>>> wrote: >>>> >>>>> Hi Sarah, >>>>> I have a Huion h610 which has a similar report rate and >>>>> experienced similar issues, but they have stopped recently. I *believe* >>>>> they were resolved when I switched to a slightly modified version of the >>>>> current driver. There is a new version of the driver in development, that >>>>> *might* resolve it for you if i'm not mistaken. By the way, what is the USB >>>>> VID and PID of your Huion 1060? I don't see it in the tablet list on >>>>> http://digimend.github.io/tablets/ . My h610 is 256c:006e (according >>>>> to lsusb) for example. >>>>> >>>>> Thanks, >>>>> Dan >>>>> >>>>> On Sat, Feb 28, 2015 at 2:56 PM, Sarah Owens <owe...@gm...> >>>>> wrote: >>>>> >>>>>> I am trying to set up my Huion 1060pro ( >>>>>> http://huion-tablet.com/product/product.php?sku=1020), in Ubuntu >>>>>> 14.04. I installed the DIGImend drivers by following the instructions on >>>>>> github, and I'm having a few problems. >>>>>> >>>>>> When drawing on Krita or the Gimp, my brush-stroke lags seconds >>>>>> behind where my pen is. The stroke seems to buffer up, and will finish out >>>>>> the stroke, but takes forever to do so. >>>>>> >>>>>> To solve this problem, I was thinking I might need an xorg.config to >>>>>> lower sampling rate? My computer has 8g of RAM (5 reported as "free"). >>>>>> >>>>>> My other problem is none of the butttons work, except for left-click >>>>>> on the pen. Does this device have a known status with the drivers? (It >>>>>> looked like it fell in the "other" category for supported Huion devices). >>>>>> >>>>>> Thanks! >>>>>> Sarah >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> 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 >>>>>> >>>>>> >>>>> >>>> >>> >> > |
|
From: Sarah O. <owe...@gm...> - 2015-03-01 05:06:26
|
I did rmmod and then modprobe, I also tried unplugging and re-plugging the tablet. My dmseg had both huion and uclogic messages in it: [15749.195783] usb 2-4.1: New USB device found, idVendor=256c, idProduct=006e [15749.195793] usb 2-4.1: New USB device strings: Mfr=5, Product=6, SerialNumber=0 [15749.195798] usb 2-4.1: Product: PenTablet [15749.195802] usb 2-4.1: Manufacturer: HUION [15749.198068] input: HUION PenTablet as /devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4.1/2-4.1:1.0/input/input42 [15749.198477] huion 0003:256C:006E.0019: input,hidraw0: USB HID v1.11 Mouse [HUION PenTablet] on usb-0000:00:14.0-4.1/input0 [15749.200575] input: HUION PenTablet as /devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4.1/2-4.1:1.1/input/input43 [15749.201177] uclogic 0003:256C:006E.001A: input,hiddev0,hidraw1: USB HID v1.11 Mouse [HUION PenTablet] on usb-0000:00:14.0-4.1/input1 [15749.202780] input: HUION PenTablet as /devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4.1/2-4.1:1.2/input/input44 [15749.202944] uclogic 0003:256C:006E.001B: input,hidraw2: USB HID v1.11 Keyboard [HUION PenTablet] on usb-0000:00:14.0-4.1/input2 If it turns out to be different than your case, I don't mind waiting on the official change. Thanks, Sarah |
|
From: Dan R. <ade...@gm...> - 2015-03-01 06:14:16
|
Hi Sarah,
I do not have any huion in my dmesg output, it appears to have grabbed
your tablet before the uclogic driver could. This may be an issue not just
with my modifications but any future digimend driver. You should be able to
temporarily prevent it from loading by just rmmod hid-huion . You can check
for an external hid-huion modules with
find /lib/modules/$(uname -r)/extra -name 'hid-huion.ko'
You'll probably want to blacklist hid-huion to prevent that from happening
for future digimend drivers. If you'd rather not pursue my modifications
any further, please do keep the blacklist in mind when the next digimend
driver comes around.
Thanks,
Dan
On Sat, Feb 28, 2015 at 9:05 PM, Sarah Owens <owe...@gm...> wrote:
> I did rmmod and then modprobe, I also tried unplugging and re-plugging the
> tablet. My dmseg had both huion and uclogic messages in it:
>
> [15749.195783] usb 2-4.1: New USB device found, idVendor=256c,
> idProduct=006e
> [15749.195793] usb 2-4.1: New USB device strings: Mfr=5, Product=6,
> SerialNumber=0
> [15749.195798] usb 2-4.1: Product: PenTablet
> [15749.195802] usb 2-4.1: Manufacturer: HUION
> [15749.198068] input: HUION PenTablet as
> /devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4.1/2-4.1:1.0/input/input42
> [15749.198477] huion 0003:256C:006E.0019: input,hidraw0: USB HID v1.11
> Mouse [HUION PenTablet] on usb-0000:00:14.0-4.1/input0
> [15749.200575] input: HUION PenTablet as
> /devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4.1/2-4.1:1.1/input/input43
> [15749.201177] uclogic 0003:256C:006E.001A: input,hiddev0,hidraw1: USB HID
> v1.11 Mouse [HUION PenTablet] on usb-0000:00:14.0-4.1/input1
> [15749.202780] input: HUION PenTablet as
> /devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4.1/2-4.1:1.2/input/input44
> [15749.202944] uclogic 0003:256C:006E.001B: input,hidraw2: USB HID v1.11
> Keyboard [HUION PenTablet] on usb-0000:00:14.0-4.1/input2
>
>
> If it turns out to be different than your case, I don't mind waiting on
> the official change.
>
> Thanks,
> Sarah
>
>
|
|
From: Sarah O. <owe...@gm...> - 2015-03-01 06:46:25
|
Blacklisting worked-- the tablet's name changed, and I no longer have huion output. Unfortunately my drawing is still laggy, haha, but I feel like I understand things better, and I'm more confident about it working later, now that the default huion drivers won't interfere. I appreciate all your help, Dan! Sarah On Sat, Feb 28, 2015 at 10:14 PM, Dan Roberts <ade...@gm...> wrote: > Hi Sarah, > I do not have any huion in my dmesg output, it appears to have grabbed > your tablet before the uclogic driver could. This may be an issue not just > with my modifications but any future digimend driver. You should be able to > temporarily prevent it from loading by just rmmod hid-huion . You can > check for an external hid-huion modules with > > find /lib/modules/$(uname -r)/extra -name 'hid-huion.ko' > > You'll probably want to blacklist hid-huion to prevent that from > happening for future digimend drivers. If you'd rather not pursue my > modifications any further, please do keep the blacklist in mind when the > next digimend driver comes around. > > Thanks, > Dan > > On Sat, Feb 28, 2015 at 9:05 PM, Sarah Owens <owe...@gm...> > wrote: > >> I did rmmod and then modprobe, I also tried unplugging and re-plugging >> the tablet. My dmseg had both huion and uclogic messages in it: >> >> [15749.195783] usb 2-4.1: New USB device found, idVendor=256c, >> idProduct=006e >> [15749.195793] usb 2-4.1: New USB device strings: Mfr=5, Product=6, >> SerialNumber=0 >> [15749.195798] usb 2-4.1: Product: PenTablet >> [15749.195802] usb 2-4.1: Manufacturer: HUION >> [15749.198068] input: HUION PenTablet as >> /devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4.1/2-4.1:1.0/input/input42 >> [15749.198477] huion 0003:256C:006E.0019: input,hidraw0: USB HID v1.11 >> Mouse [HUION PenTablet] on usb-0000:00:14.0-4.1/input0 >> [15749.200575] input: HUION PenTablet as >> /devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4.1/2-4.1:1.1/input/input43 >> [15749.201177] uclogic 0003:256C:006E.001A: input,hiddev0,hidraw1: USB >> HID v1.11 Mouse [HUION PenTablet] on usb-0000:00:14.0-4.1/input1 >> [15749.202780] input: HUION PenTablet as >> /devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4.1/2-4.1:1.2/input/input44 >> [15749.202944] uclogic 0003:256C:006E.001B: input,hidraw2: USB HID v1.11 >> Keyboard [HUION PenTablet] on usb-0000:00:14.0-4.1/input2 >> >> >> If it turns out to be different than your case, I don't mind waiting on >> the official change. >> >> Thanks, >> Sarah >> >> > |
|
From: Nikolai K. <sp...@gm...> - 2015-03-01 19:01:09
|
Hi Sarah, On 03/01/2015 12:56 AM, Sarah Owens wrote: > I am trying to set up my Huion 1060pro > (http://huion-tablet.com/product/product.php?sku=1020), in Ubuntu 14.04. I > installed the DIGImend drivers by following the instructions on github, and > I'm having a few problems. > > When drawing on Krita or the Gimp, my brush-stroke lags seconds behind where > my pen is. The stroke seems to buffer up, and will finish out the stroke, > but takes forever to do so. > > To solve this problem, I was thinking I might need an xorg.config to lower > sampling rate? My computer has 8g of RAM (5 reported as "free"). > > My other problem is none of the butttons work, except for left-click on the > pen. Does this device have a known status with the drivers? (It looked > like it fell in the "other" category for supported Huion devices). This is unlikely to be due to the tablet or driver behavior, but we can test that. Could you please send the output of this command: sudo usbhid-dump -es -m 256c:006e while you scribble with the pen? This way we'll see the rate of incoming reports. Just in case this is caused by the driver, please also send the output of "evtest" for the pen interface, while doing the same. The pen interface will be the one which produces output while you move the pen. Thank you. Nick |
|
From: Sarah O. <owe...@gm...> - 2015-03-02 00:05:12
|
Sure, here are some lines from usbhid-dump: 002:011:000:STREAM 1425254057.106243 07 81 BC 46 1B 2A FF 07 002:011:000:STREAM 1425254057.136175 07 81 BC 46 1D 2A FF 07 002:011:000:STREAM 1425254057.140231 07 81 BC 46 1F 2A FF 07 002:011:000:STREAM 1425254057.144242 07 81 BC 46 21 2A FF 07 002:011:000:STREAM 1425254057.148184 07 81 BC 46 23 2A FF 07 002:011:000:STREAM 1425254057.152161 07 81 BA 46 28 2A FF 07 And here are some lines from evtest: Event: time 1425254448.564150, -------------- SYN_REPORT ------------ Event: time 1425254448.568167, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042 Event: time 1425254448.568167, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 Event: time 1425254448.568167, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0043 Event: time 1425254448.568167, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 Event: time 1425254448.568167, type 3 (EV_ABS), code 0 (ABS_X), value 13767 Event: time 1425254448.568167, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 1730 Event: time 1425254448.568167, -------------- SYN_REPORT ------------ Event: time 1425254448.572168, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042 Event: time 1425254448.572168, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 Event: time 1425254448.572168, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0043 Event: time 1425254448.572168, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 Event: time 1425254448.572168, type 3 (EV_ABS), code 1 (ABS_Y), value 17067 Event: time 1425254448.572168, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 2047 Event: time 1425254448.572168, -------------- SYN_REPORT ------------ Event: time 1425254448.576169, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042 Event: time 1425254448.576169, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 Event: time 1425254448.576169, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0043 Event: time 1425254448.576169, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 Event: time 1425254448.576169, type 3 (EV_ABS), code 0 (ABS_X), value 13770 Event: time 1425254448.576169, -------------- SYN_REPORT ------------ Event: time 1425254448.580162, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042 Event: time 1425254448.580162, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 Event: time 1425254448.580162, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0043 Event: time 1425254448.580162, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 Event: time 1425254448.580162, type 3 (EV_ABS), code 0 (ABS_X), value 13773 Event: time 1425254448.580162, type 3 (EV_ABS), code 1 (ABS_Y), value 17065 The evtest looked like events were registering immediately--when I clicked with the pen, it would immediately register an ABS_PRESSURE, and when I took the pen away from the tablet, all events would immediately stop. Thanks, Sarah On Sun, Mar 1, 2015 at 11:00 AM, Nikolai Kondrashov <sp...@gm...> wrote: > Hi Sarah, > > > On 03/01/2015 12:56 AM, Sarah Owens wrote: > >> I am trying to set up my Huion 1060pro >> (http://huion-tablet.com/product/product.php?sku=1020), in Ubuntu >> 14.04. I >> installed the DIGImend drivers by following the instructions on github, >> and >> I'm having a few problems. >> >> When drawing on Krita or the Gimp, my brush-stroke lags seconds behind >> where >> my pen is. The stroke seems to buffer up, and will finish out the stroke, >> but takes forever to do so. >> >> To solve this problem, I was thinking I might need an xorg.config to lower >> sampling rate? My computer has 8g of RAM (5 reported as "free"). >> >> My other problem is none of the butttons work, except for left-click on >> the >> pen. Does this device have a known status with the drivers? (It looked >> like it fell in the "other" category for supported Huion devices). >> > > This is unlikely to be due to the tablet or driver behavior, but we can > test > that. > > Could you please send the output of this command: > > sudo usbhid-dump -es -m 256c:006e > > while you scribble with the pen? > > This way we'll see the rate of incoming reports. > > Just in case this is caused by the driver, please also send the output of > "evtest" for the pen interface, while doing the same. The pen interface > will > be the one which produces output while you move the pen. > > Thank you. > > Nick > |
|
From: Nikolai K. <sp...@gm...> - 2015-03-02 10:33:41
|
On 03/02/2015 02:04 AM, Sarah Owens wrote: > Sure, here are some lines from usbhid-dump: > > 002:011:000:STREAM 1425254057.106243 > 07 81 BC 46 1B 2A FF 07 > > 002:011:000:STREAM 1425254057.136175 > 07 81 BC 46 1D 2A FF 07 > > 002:011:000:STREAM 1425254057.140231 > 07 81 BC 46 1F 2A FF 07 > > 002:011:000:STREAM 1425254057.144242 > 07 81 BC 46 21 2A FF 07 > > 002:011:000:STREAM 1425254057.148184 > 07 81 BC 46 23 2A FF 07 > > 002:011:000:STREAM 1425254057.152161 > 07 81 BA 46 28 2A FF 07 > > > And here are some lines from evtest: > > Event: time 1425254448.564150, -------------- SYN_REPORT ------------ > Event: time 1425254448.568167, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042 > Event: time 1425254448.568167, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 > Event: time 1425254448.568167, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0043 > Event: time 1425254448.568167, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 > Event: time 1425254448.568167, type 3 (EV_ABS), code 0 (ABS_X), value 13767 > Event: time 1425254448.568167, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 1730 > Event: time 1425254448.568167, -------------- SYN_REPORT ------------ > Event: time 1425254448.572168, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042 > Event: time 1425254448.572168, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 > Event: time 1425254448.572168, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0043 > Event: time 1425254448.572168, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 > Event: time 1425254448.572168, type 3 (EV_ABS), code 1 (ABS_Y), value 17067 > Event: time 1425254448.572168, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 2047 > Event: time 1425254448.572168, -------------- SYN_REPORT ------------ > Event: time 1425254448.576169, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042 > Event: time 1425254448.576169, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 > Event: time 1425254448.576169, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0043 > Event: time 1425254448.576169, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 > Event: time 1425254448.576169, type 3 (EV_ABS), code 0 (ABS_X), value 13770 > Event: time 1425254448.576169, -------------- SYN_REPORT ------------ > Event: time 1425254448.580162, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042 > Event: time 1425254448.580162, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 > Event: time 1425254448.580162, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0043 > Event: time 1425254448.580162, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 > Event: time 1425254448.580162, type 3 (EV_ABS), code 0 (ABS_X), value 13773 > Event: time 1425254448.580162, type 3 (EV_ABS), code 1 (ABS_Y), value 17065 Thanks, Sarah! However, I'll need to have more output to calculate and compare the report rate. A thousand events, at least. You can just do a few scribbles and send gzipped output. Or, you can calculate the report rate yourself. You have the timestamps both in usbhid-dump and evtest output. In usbhid-dump you need to sample every report, and in evtest only the SYN_REPORT lines. > The evtest looked like events were registering immediately--when I clicked > with the pen, it would immediately register an ABS_PRESSURE, and when I took > the pen away from the tablet, all events would immediately stop. Yes, I would expect that. I was suspecting simply too many reports, but now when I look at your evtest samples I see that BTN_TOUCH is toggled on and off in every report, which might be the reason for the slowdown. I'll check the code and will try it with my H610. Meanwhile can you check that you get BTN_TOUCH toggled in every evtest report? Or perhaps just send me both full usbhid-dump and full evtest outputs. BTW, which version of the driver are you using? Nick |
|
From: Nikolai K. <sp...@gm...> - 2015-03-03 20:46:47
|
On 03/03/2015 07:23 AM, Sarah Owens wrote:
> I sent this, and didn't notice it bounce because of my large attachment, so
> here it is without the tests (but let me know if you'd like to see them)
I've got them, you got the bounce from the maillist. Which is actually a good
thing, because you seem to have added some other files into the archive
accidentally.
> Ok, I think I understand what you were looking for now. The SYN_REPORTs
> from evntest happened about 245 times in a second (every 4ms?), and the
> reports from usbhid were about the same (235 times / second).
> I attached the two files, just in case I misunderstood again, haha. I
> didn't see a version number for the driver, but I got the most recent
> version just a few days ago-- plus the one-line change from Dan Roberts.
>
> In the evtest, I clicked the side-button of the pen 3 times ("BTN_0"
> registering 1 and 0 on push and release, respectively) and during the time
> that button was held down, the events looked normal-- just registering x and
> y position.
>
> I started scribbling at 1425314198.986, and every event while the pen was
> pressed down registered 2 different BTN_TOUCHes, value 1 and then 0 (on then
> off, I think).
>
> BTN_TOUCH being toggled every time would explain the sort of lines I was
> seeing. I attached a png of 3 lines I drew-- the first line on the left is
> drawn with my laptop trackpad, the middle one is drawn with the tablet by
> clicking the button on the body of the pen, and the rightmost one was drawn
> with the pen tip pressing on the tablet. Something I also found interesting
> was the trackpad line can be undone as a single action (as expected), but
> the other two will only undo a single star at a time even though my stroke
> was continuous.
I think I managed to reproduce this locally and it seems to be a problem with
driver rebinding script (hid-rebind). I'll work on a fix.
Meanwhile you can rebind the drivers manually via sysfs, if you can figure out
how. Basically, all the interfaces should be handled by hid-uclogic now.
Thanks, Sarah!
Nick
|
|
From: Nikolai K. <sp...@gm...> - 2015-03-03 22:10:48
|
On 03/03/2015 10:46 PM, Nikolai Kondrashov wrote:
> On 03/03/2015 07:23 AM, Sarah Owens wrote:
>> I sent this, and didn't notice it bounce because of my large attachment, so
>> here it is without the tests (but let me know if you'd like to see them)
>
> I've got them, you got the bounce from the maillist. Which is actually a good
> thing, because you seem to have added some other files into the archive
> accidentally.
>
>> Ok, I think I understand what you were looking for now. The SYN_REPORTs
>> from evntest happened about 245 times in a second (every 4ms?), and the
>> reports from usbhid were about the same (235 times / second).
>> I attached the two files, just in case I misunderstood again, haha. I
>> didn't see a version number for the driver, but I got the most recent
>> version just a few days ago-- plus the one-line change from Dan Roberts.
>>
>> In the evtest, I clicked the side-button of the pen 3 times ("BTN_0"
>> registering 1 and 0 on push and release, respectively) and during the time
>> that button was held down, the events looked normal-- just registering x and
>> y position.
>>
>> I started scribbling at 1425314198.986, and every event while the pen was
>> pressed down registered 2 different BTN_TOUCHes, value 1 and then 0 (on then
>> off, I think).
>>
>> BTN_TOUCH being toggled every time would explain the sort of lines I was
>> seeing. I attached a png of 3 lines I drew-- the first line on the left is
>> drawn with my laptop trackpad, the middle one is drawn with the tablet by
>> clicking the button on the body of the pen, and the rightmost one was drawn
>> with the pen tip pressing on the tablet. Something I also found interesting
>> was the trackpad line can be undone as a single action (as expected), but
>> the other two will only undo a single star at a time even though my stroke
>> was continuous.
>
> I think I managed to reproduce this locally and it seems to be a problem with
> driver rebinding script (hid-rebind). I'll work on a fix.
Alright, I pushed a fix onto the git repo. Please try the latest master:
https://github.com/DIGImend/digimend-kernel-drivers/archive/master.zip
Nick
|
|
From: Sarah O. <owe...@gm...> - 2015-03-04 00:42:58
|
That fixed it! In evtest, it's not triggering the button on and off every
time, and my strokes don't lag at all anymore. Even my other tablet
buttons started working!
Thanks!!
Sarah
On Tue, Mar 3, 2015 at 2:10 PM, Nikolai Kondrashov <sp...@gm...>
wrote:
> On 03/03/2015 10:46 PM, Nikolai Kondrashov wrote:
>
>> On 03/03/2015 07:23 AM, Sarah Owens wrote:
>>
>>> I sent this, and didn't notice it bounce because of my large attachment,
>>> so
>>> here it is without the tests (but let me know if you'd like to see them)
>>>
>>
>> I've got them, you got the bounce from the maillist. Which is actually a
>> good
>> thing, because you seem to have added some other files into the archive
>> accidentally.
>>
>> Ok, I think I understand what you were looking for now. The SYN_REPORTs
>>> from evntest happened about 245 times in a second (every 4ms?), and the
>>> reports from usbhid were about the same (235 times / second).
>>> I attached the two files, just in case I misunderstood again, haha. I
>>> didn't see a version number for the driver, but I got the most recent
>>> version just a few days ago-- plus the one-line change from Dan Roberts.
>>>
>>> In the evtest, I clicked the side-button of the pen 3 times ("BTN_0"
>>> registering 1 and 0 on push and release, respectively) and during the
>>> time
>>> that button was held down, the events looked normal-- just registering x
>>> and
>>> y position.
>>>
>>> I started scribbling at 1425314198.986, and every event while the pen was
>>> pressed down registered 2 different BTN_TOUCHes, value 1 and then 0 (on
>>> then
>>> off, I think).
>>>
>>> BTN_TOUCH being toggled every time would explain the sort of lines I was
>>> seeing. I attached a png of 3 lines I drew-- the first line on the left
>>> is
>>> drawn with my laptop trackpad, the middle one is drawn with the tablet by
>>> clicking the button on the body of the pen, and the rightmost one was
>>> drawn
>>> with the pen tip pressing on the tablet. Something I also found
>>> interesting
>>> was the trackpad line can be undone as a single action (as expected), but
>>> the other two will only undo a single star at a time even though my
>>> stroke
>>> was continuous.
>>>
>>
>> I think I managed to reproduce this locally and it seems to be a problem
>> with
>> driver rebinding script (hid-rebind). I'll work on a fix.
>>
>
> Alright, I pushed a fix onto the git repo. Please try the latest master:
>
> https://github.com/DIGImend/digimend-kernel-drivers/archive/master.zip
>
> Nick
>
|
|
From: Nikolai K. <sp...@gm...> - 2015-03-04 10:33:17
|
On 03/04/2015 02:42 AM, Sarah Owens wrote: > That fixed it! In evtest, it's not triggering the button on and off every > time, and my strokes don't lag at all anymore. Even my other tablet buttons > started working! Wonderful! > Thanks!! You're welcome :) Nick |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X