digimend-users Mailing List for DIGImend
Brought to you by:
spb_nick
You can subscribe to this list here.
2012 |
Jan
|
Feb
|
Mar
|
Apr
(58) |
May
(72) |
Jun
(24) |
Jul
|
Aug
(12) |
Sep
(9) |
Oct
(10) |
Nov
(2) |
Dec
(4) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2013 |
Jan
(5) |
Feb
(23) |
Mar
|
Apr
|
May
(4) |
Jun
(7) |
Jul
(2) |
Aug
(2) |
Sep
(5) |
Oct
(7) |
Nov
(31) |
Dec
(11) |
2014 |
Jan
(13) |
Feb
(4) |
Mar
(1) |
Apr
(1) |
May
(1) |
Jun
(2) |
Jul
(12) |
Aug
(10) |
Sep
(13) |
Oct
(15) |
Nov
(49) |
Dec
(4) |
2015 |
Jan
(49) |
Feb
(62) |
Mar
(81) |
Apr
(10) |
May
(4) |
Jun
(6) |
Jul
(17) |
Aug
(3) |
Sep
(1) |
Oct
(4) |
Nov
|
Dec
(8) |
2016 |
Jan
(8) |
Feb
(5) |
Mar
(7) |
Apr
(7) |
May
(3) |
Jun
(4) |
Jul
(12) |
Aug
(8) |
Sep
(6) |
Oct
(4) |
Nov
(1) |
Dec
|
From: Nikolai K. <sp...@gm...> - 2016-11-19 19:38:18
|
Hi everyone, I'll be closing both DIGImend-devel and DIGImend-users mailing lists for posting tomorrow. Later I'll download the archives and post them somewhere and then delete the maillists from sourceforge.net. A separate message about that will be sent. Details: http://spbnick.github.io/2016/07/31/Wrapping-up-DIGImend-work.html Nick |
From: Rüdiger S. <rem...@we...> - 2016-10-27 08:57:15
|
Hi, for some curious reasons the attached device report descritors are embedded in the message text. So again, I've written a patch for Waltop Mars A tablet (Medion P82018), which fixes the "both stylus buttons generate same action" problem. See attached patch for kernel 4.7 |
From: <co+...@io...> - 2016-10-12 22:00:37
|
Hello. I recently obtained a Huion H420. I'm using Arch Linux and am currently at kernel version 4.7.6-1-ARCH. I got the tablet, plugged it in, and it magically worked. Because there was no configuration, I'm working under the assumption that I *am* actually using the drivers that DIGImend have created (nice work, if so!). When I plug the tablet in, the following lines are logged in dmesg: [14630.036416] usb 2-1.2: new full-speed USB device number 6 using ehci-pci [14630.123752] input: HUION H420 Pen as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/0003:256C:006E.000D/input/input36 [14630.124340] uclogic 0003:256C:006E.000D: input,hidraw3: USB HID v1.11 Device [HUION H420] on usb-0000:00:1d.0-1.2/input0 [14630.126440] input: HUION H420 Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.1/0003:256C:006E.000E/input/input37 [14630.127087] uclogic 0003:256C:006E.000E: input,hiddev0,hidraw4: USB HID v1.11 Mouse [HUION H420] on usb-0000:00:1d.0-1.2/input1 [14630.129470] input: HUION H420 Keyboard as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.2/0003:256C:006E.000F/input/input39 [14630.180392] input: HUION H420 Consumer Control as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.2/0003:256C:006E.000F/input/input40 [14630.180752] input: HUION H420 System Control as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.2/0003:256C:006E.000F/input/input41 [14630.181134] uclogic 0003:256C:006E.000F: input,hidraw5: USB HID v1.11 Keyboard [HUION H420] on usb-0000:00:1d.0-1.2/input2 My problem: There don't appear to be any tools available for configuring the pressure sensitivity curve. The programs I use (GIMP, Krita, Blender) have varying degrees of support for configuring custom curves. In the case of Blender, there just isn't any ability to configure anything, and the pressure sensitivity curve is far too severe. It goes from maximum pressure when painting to very little pressure in just a few very noticeable steps. Is there a tool I can use to configure things system-wide, or are applications expected to provide everything on Linux? M |
From: Nikolai K. <sp...@gm...> - 2016-09-02 11:20:27
|
Hi Matt, On 09/02/2016 02:11 PM, Matt Heffernan wrote: > I have recently purchased a Huion 610Pro and want to get it to work in > relative mode. it currently works in absolute mode but i am trying to > use it as a mouse primarily and cannot for the life of my figure out how > to do this. I have searched the web and tried many things but i had no > joy. Does any one have any tips on how to do this? Take a look at "man evdev" ("Mode" option), "man xinput", and "xinput list-props <your_device_id>". Otherwise please see http://spbnick.github.io/2016/07/31/Wrapping-up-DIGImend-work.html Nick |
From: Matt H. <alc...@ho...> - 2016-09-02 11:11:52
|
Hi All I have recently purchased a Huion 610Pro and want to get it to work in relative mode. it currently works in absolute mode but i am trying to use it as a mouse primarily and cannot for the life of my figure out how to do this. I have searched the web and tried many things but i had no joy. Does any one have any tips on how to do this? Thanks Matt |
From: Nikolai K. <sp...@gm...> - 2016-09-01 12:58:58
|
On 08/31/2016 05:51 PM, Christopher Barry wrote: > On Wed, 31 Aug 2016 15:32:32 +0300 > Nikolai Kondrashov <sp...@gm...> wrote: > >> On 08/31/2016 02:58 PM, Nikolai Kondrashov wrote: >>> Hi everyone, >>> >>> I would like to regretfully inform you that I'm wrapping up my work >>> on the DIGImend project. Within two months I'm going to stop all >>> work on the project, with the exception of accepting patches, as >>> time allows, if a replacement is not found. Meanwhile I will be >>> focusing on syncing with upstream kernel and writing HOWTOs on >>> diagnosing problems and adding tablet support. >>> >>> See more at >>> http://localhost:4000/2016/07/31/Wrapping-up-DIGImend-work.html >> >> And of course I had to screw up the URL: >> >> http://spbnick.github.io/2016/07/31/Wrapping-up-DIGImend-work.html >> >> Nick >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> DIGImend-users mailing list >> DIG...@li... >> https://lists.sourceforge.net/lists/listinfo/digimend-users > > Thank you Nick for all of the effort and energy you've put into it. It > really helped me use my tablet with blender at a time when a tablet was > the only way to get done what I needed to get done. > > My hat is off to you fine sir :) > > Cheers, and best of luck to you in the new focus of your talent and > energy. Thanks, Christopher! All the best luck to you too, along with inspiration :) Nick |
From: Christopher B. <chr...@gm...> - 2016-08-31 14:51:38
|
On Wed, 31 Aug 2016 15:32:32 +0300 Nikolai Kondrashov <sp...@gm...> wrote: >On 08/31/2016 02:58 PM, Nikolai Kondrashov wrote: >> Hi everyone, >> >> I would like to regretfully inform you that I'm wrapping up my work >> on the DIGImend project. Within two months I'm going to stop all >> work on the project, with the exception of accepting patches, as >> time allows, if a replacement is not found. Meanwhile I will be >> focusing on syncing with upstream kernel and writing HOWTOs on >> diagnosing problems and adding tablet support. >> >> See more at >> http://localhost:4000/2016/07/31/Wrapping-up-DIGImend-work.html > >And of course I had to screw up the URL: > > http://spbnick.github.io/2016/07/31/Wrapping-up-DIGImend-work.html > >Nick > >------------------------------------------------------------------------------ >_______________________________________________ >DIGImend-users mailing list >DIG...@li... >https://lists.sourceforge.net/lists/listinfo/digimend-users Thank you Nick for all of the effort and energy you've put into it. It really helped me use my tablet with blender at a time when a tablet was the only way to get done what I needed to get done. My hat is off to you fine sir :) Cheers, and best of luck to you in the new focus of your talent and energy. -- Regards, Christopher |
From: Nikolai K. <sp...@gm...> - 2016-08-31 12:32:42
|
On 08/31/2016 02:58 PM, Nikolai Kondrashov wrote: > Hi everyone, > > I would like to regretfully inform you that I'm wrapping up my work on the > DIGImend project. Within two months I'm going to stop all work on the project, > with the exception of accepting patches, as time allows, if a replacement is > not found. Meanwhile I will be focusing on syncing with upstream kernel and > writing HOWTOs on diagnosing problems and adding tablet support. > > See more at http://localhost:4000/2016/07/31/Wrapping-up-DIGImend-work.html And of course I had to screw up the URL: http://spbnick.github.io/2016/07/31/Wrapping-up-DIGImend-work.html Nick |
From: Nikolai K. <sp...@gm...> - 2016-08-31 11:58:50
|
Hi everyone, I would like to regretfully inform you that I'm wrapping up my work on the DIGImend project. Within two months I'm going to stop all work on the project, with the exception of accepting patches, as time allows, if a replacement is not found. Meanwhile I will be focusing on syncing with upstream kernel and writing HOWTOs on diagnosing problems and adding tablet support. See more at http://localhost:4000/2016/07/31/Wrapping-up-DIGImend-work.html Thanks everyone for your help over the years! Nick |
From: Craig A. <cr...@co...> - 2016-08-13 15:55:12
|
My office system and laptop are both running Debian. I am researching purchasing a Huion support 1060 plus for the office and a Huion 680s for the laptop. I found one mailing list thread on the Huion 1060 plus: https://sourceforge.net/p/digimend/mailman/digimend-users/thread/CAKwYL5HKA_Xb6mWUZUx3Q5gP%3DMG_7rFuapDVQu1coho7-q%3DaNA%40mail.gmail.com/#msg33510111 I'm currently using these application: inkscape, gimp, freecad, openscad. Before I do the buys, I'd like to hear about support for these 2 tablets. If there are issues, what alternatives would be currently recommended? Later, Craig Anderson |
From: pim c. <pim...@ho...> - 2016-07-26 08:30:40
|
Greetings, I used to run Linux Mint 17.3 and my Huion H610 pro worked fine with that with your drivers.So I upgraded to Linux Mint 18 and suddenly it doesn't work anymore.I checked lsusb and while it does recognize the device it clearly does not know what it is or how it is supposed to work(It simple lists the device ID but not the vendor or any other additional information). I tried reinstalling the drivers with the .deb package. Did not work. Tried reloading the drivers with modprobe, did not work either. Finally I removed all the drivers and tried installing it from source. That did not work either.I checked the module files and the one for my tablet(hid-uclogic.ko) was not in the module files for my current kernel(4.4.0-31). The debian package does say that it is installed so I am out of options. As an additional note lsmod does list hid-uclogic. So I have no idea what is up with that.Could you please help me? Thanks in advance,Pim Coremans |
From: Caleb L. <ca...@te...> - 2016-07-20 00:08:02
|
Hopefully I'm not spamming the mailing list, but another thing I've just found: On the original desktop that it was working just fine on, is now no longer working. I'm certain it's plugged in (I can see it in lsusb), but not see it in xinput. I wonder if it's an issue of: it works when installed, but when any updates are done (such as installing a newer kernel), that it stops working. Or if there's just some underlying unpredictable bug in general. Nonetheless, I downloaded the source on the other computer (the clean Ubuntu 16.04 install, not upgraded from 15.10), and manually compiled, and it's working fine now on there, again. On Tue, Jul 19, 2016 at 6:10 PM, Caleb Langeslag <ca...@te...> wrote: > As an additional status report: > I manually built the modules from source and it worked just fine on the > computer that it wasn't working on (Ubuntu 16.04, upgraded from 15.10, > 4.4.0-31 kernel) > > On Tue, Jul 19, 2016 at 5:49 PM, Caleb Langeslag <ca...@te...> > wrote: > >> Output of lsusb is: >> >> Bus 003 Device 004: ID 256c:006e >> Device Descriptor: >> bLength 18 >> bDescriptorType 1 >> bcdUSB 1.10 >> bDeviceClass 0 (Defined at Interface level) >> bDeviceSubClass 0 >> bDeviceProtocol 0 >> bMaxPacketSize0 8 >> idVendor 0x256c >> idProduct 0x006e >> bcdDevice 0.00 >> iManufacturer 5 (error) >> iProduct 6 Tablet Monitor >> iSerial 0 >> bNumConfigurations 1 >> Configuration Descriptor: >> bLength 9 >> bDescriptorType 2 >> wTotalLength 84 >> bNumInterfaces 3 >> bConfigurationValue 1 >> iConfiguration 0 >> bmAttributes 0xa0 >> (Bus Powered) >> Remote Wakeup >> MaxPower 100mA >> Interface Descriptor: >> bLength 9 >> bDescriptorType 4 >> bInterfaceNumber 0 >> bAlternateSetting 0 >> bNumEndpoints 1 >> bInterfaceClass 3 Human Interface Device >> bInterfaceSubClass 1 Boot Interface Subclass >> bInterfaceProtocol 2 Mouse >> iInterface 0 >> HID Device Descriptor: >> bLength 9 >> bDescriptorType 33 >> bcdHID 1.11 >> bCountryCode 0 Not supported >> bNumDescriptors 1 >> bDescriptorType 34 Report >> wDescriptorLength 177 >> Report Descriptors: >> ** UNAVAILABLE ** >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x81 EP 1 IN >> bmAttributes 3 >> Transfer Type Interrupt >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0040 1x 64 bytes >> bInterval 2 >> Interface Descriptor: >> bLength 9 >> bDescriptorType 4 >> bInterfaceNumber 1 >> bAlternateSetting 0 >> bNumEndpoints 1 >> bInterfaceClass 3 Human Interface Device >> bInterfaceSubClass 1 Boot Interface Subclass >> bInterfaceProtocol 2 Mouse >> iInterface 0 >> HID Device Descriptor: >> bLength 9 >> bDescriptorType 33 >> bcdHID 1.11 >> bCountryCode 0 Not supported >> bNumDescriptors 1 >> bDescriptorType 34 Report >> wDescriptorLength 244 >> Report Descriptors: >> ** UNAVAILABLE ** >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x82 EP 2 IN >> bmAttributes 3 >> Transfer Type Interrupt >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0010 1x 16 bytes >> bInterval 2 >> Interface Descriptor: >> bLength 9 >> bDescriptorType 4 >> bInterfaceNumber 2 >> bAlternateSetting 0 >> bNumEndpoints 1 >> bInterfaceClass 3 Human Interface Device >> bInterfaceSubClass 0 No Subclass >> bInterfaceProtocol 0 None >> iInterface 0 >> HID Device Descriptor: >> bLength 9 >> bDescriptorType 33 >> bcdHID 1.0b >> bCountryCode 0 Not supported >> bNumDescriptors 1 >> bDescriptorType 34 Report >> wDescriptorLength 92 >> Report Descriptors: >> ** UNAVAILABLE ** >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x83 EP 3 IN >> bmAttributes 3 >> Transfer Type Interrupt >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0008 1x 8 bytes >> bInterval 8 >> Device Status: 0x0000 >> (Bus Powered) >> >> ====================== >> >> modinfo on WORKING desktop (fresh 16.04 install): >> >> filename: /lib/modules/4.4.0-24-generic/updates/dkms/hid-uclogic.ko >> version: 6 >> license: GPL >> author: Nikolai Kondrashov >> author: Martin Rusko >> srcversion: 34A15E7DFFC53AA6F4BEACF >> alias: hid:b0003g*v00002179p00000053 >> alias: hid:b0003g*v00005543p00003031 >> alias: hid:b0003g*v00005543p00000045 >> alias: hid:b0003g*v00005543p00000081 >> alias: hid:b0003g*v00005543p0000004D >> alias: hid:b0003g*v00005543p0000006E >> alias: hid:b0003g*v0000256Cp0000006E >> alias: hid:b0003g*v00005543p00000781 >> alias: hid:b0003g*v00005543p00000522 >> alias: hid:b0003g*v00005543p00000064 >> alias: hid:b0003g*v00005543p00000005 >> alias: hid:b0003g*v00005543p00000004 >> alias: hid:b0003g*v00005543p00000003 >> alias: hid:b0003g*v00005543p00000042 >> depends: hid >> vermagic: 4.4.0-24-generic SMP mod_unload modversions >> >> >> ====================== >> >> modinfo on non-working desktop (16.04, upgraded from 15.10): >> >> filename: /lib/modules/4.4.0-31-generic/updates/dkms/hid-uclogic.ko >> version: 6 >> license: GPL >> author: Nikolai Kondrashov >> author: Martin Rusko >> srcversion: 34A15E7DFFC53AA6F4BEACF >> alias: hid:b0003g*v00002179p00000053 >> alias: hid:b0003g*v00005543p00003031 >> alias: hid:b0003g*v00005543p00000045 >> alias: hid:b0003g*v00005543p00000081 >> alias: hid:b0003g*v00005543p0000004D >> alias: hid:b0003g*v00005543p0000006E >> alias: hid:b0003g*v0000256Cp0000006E >> alias: hid:b0003g*v00005543p00000781 >> alias: hid:b0003g*v00005543p00000522 >> alias: hid:b0003g*v00005543p00000064 >> alias: hid:b0003g*v00005543p00000005 >> alias: hid:b0003g*v00005543p00000004 >> alias: hid:b0003g*v00005543p00000003 >> alias: hid:b0003g*v00005543p00000042 >> depends: hid >> vermagic: 4.4.0-31-generic SMP mod_unload modversions >> >> >> >> On Sun, Jul 17, 2016 at 10:39 AM, Nikolai Kondrashov <sp...@gm...> >> wrote: >> >>> Hi Caleb, >>> >>> On 07/15/2016 07:16 AM, Caleb Langeslag wrote: >>> >>>> So a friend recently acquired a Huion GT-190. >>>> >>> >>> We don't have information on that tablet. Could you send "lsusb -v" >>> output for >>> the start? Thank you. >>> >>> Plugged it in, installed the latest DIGImend DKMS deb package on Ubuntu >>>> 15.10, and it worked perfectly. Later on, just recently upgraded to >>>> Ubuntu >>>> 16.04, and now the tablet does not function whatsoever. It's plugged in >>>> and >>>> shows up under lsusb, but is not listed under 'xinput --list'. >>>> >>> >>> This is interesting. >>> >>> Next, I grabbed the graphics tablet and plugged it into another desktop, >>>> with a fresh clean Ubuntu 16.04 installation (no upgrade), and >>>> installed the >>>> DIGImend drivers, and it works perfectly fine on there. >>>> >>>> I'm wondering if there's a packaging issue with the deb package, when >>>> dealing with OS version upgrades, or if it's some bug in Canonical's >>>> work. >>>> >>>> On the other desktop (that was upgraded from 15.10), I tried >>>> uninstalling >>>> the package, restarting, reinstalling the package, restarting, and no >>>> resulting difference. Also tried "Mark for complete removal" under >>>> Synaptic >>>> for the 'digimend-dkms' package, and reinstalling after. I've also tried >>>> rmmod to unload the kernel module (hid_uclogic), and insmod to manually >>>> load >>>> the the module for the current kernel version, with no change. >>>> >>>> On both computers, I can run lsmod and see hid_uclogic loaded. >>>> >>>> When I run 'watch -n 0.5 xinput --list' on both computers, and plug in >>>> the tablet, I get the results of: >>>> >>>> - On the upgraded 16.04 computer: "NUVOTON WPM USB" appears for a >>>> second, then disappears. Nothing else comes up thereafter. >>>> - On the cleanly installed 16.04 computer: "NUVOTON WPM USB" >>>> appears for a second, disappears, then the Tablet Monitor >>>> Pen/Mouse/Consumer-Control items appear and stay. >>>> >>>> If there's any further information required, then feel free to ask. >>>> >>> >>> Alright, can you send the output of "/sbin/modinfo hid-uclogic" from both >>> machines? I suspect that the driver won't even build on 16.04, as it has >>> the >>> 4.4 kernel with HID driver interface changed slightly, introducing >>> incompatibility. >>> >>> You can try building and installing the latest development version >>> manually >>> from >>> https://github.com/DIGImend/digimend-kernel-drivers/archive/master.zip >>> >>> Nick >>> >> >> > |
From: Caleb L. <ca...@te...> - 2016-07-19 23:10:31
|
As an additional status report: I manually built the modules from source and it worked just fine on the computer that it wasn't working on (Ubuntu 16.04, upgraded from 15.10, 4.4.0-31 kernel) On Tue, Jul 19, 2016 at 5:49 PM, Caleb Langeslag <ca...@te...> wrote: > Output of lsusb is: > > Bus 003 Device 004: ID 256c:006e > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 0 (Defined at Interface level) > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 > idVendor 0x256c > idProduct 0x006e > bcdDevice 0.00 > iManufacturer 5 (error) > iProduct 6 Tablet Monitor > iSerial 0 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 84 > bNumInterfaces 3 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0xa0 > (Bus Powered) > Remote Wakeup > MaxPower 100mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 3 Human Interface Device > bInterfaceSubClass 1 Boot Interface Subclass > bInterfaceProtocol 2 Mouse > iInterface 0 > HID Device Descriptor: > bLength 9 > bDescriptorType 33 > bcdHID 1.11 > bCountryCode 0 Not supported > bNumDescriptors 1 > bDescriptorType 34 Report > wDescriptorLength 177 > Report Descriptors: > ** UNAVAILABLE ** > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 2 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 3 Human Interface Device > bInterfaceSubClass 1 Boot Interface Subclass > bInterfaceProtocol 2 Mouse > iInterface 0 > HID Device Descriptor: > bLength 9 > bDescriptorType 33 > bcdHID 1.11 > bCountryCode 0 Not supported > bNumDescriptors 1 > bDescriptorType 34 Report > wDescriptorLength 244 > Report Descriptors: > ** UNAVAILABLE ** > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x82 EP 2 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0010 1x 16 bytes > bInterval 2 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 2 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 3 Human Interface Device > bInterfaceSubClass 0 No Subclass > bInterfaceProtocol 0 None > iInterface 0 > HID Device Descriptor: > bLength 9 > bDescriptorType 33 > bcdHID 1.0b > bCountryCode 0 Not supported > bNumDescriptors 1 > bDescriptorType 34 Report > wDescriptorLength 92 > Report Descriptors: > ** UNAVAILABLE ** > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 EP 3 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0008 1x 8 bytes > bInterval 8 > Device Status: 0x0000 > (Bus Powered) > > ====================== > > modinfo on WORKING desktop (fresh 16.04 install): > > filename: /lib/modules/4.4.0-24-generic/updates/dkms/hid-uclogic.ko > version: 6 > license: GPL > author: Nikolai Kondrashov > author: Martin Rusko > srcversion: 34A15E7DFFC53AA6F4BEACF > alias: hid:b0003g*v00002179p00000053 > alias: hid:b0003g*v00005543p00003031 > alias: hid:b0003g*v00005543p00000045 > alias: hid:b0003g*v00005543p00000081 > alias: hid:b0003g*v00005543p0000004D > alias: hid:b0003g*v00005543p0000006E > alias: hid:b0003g*v0000256Cp0000006E > alias: hid:b0003g*v00005543p00000781 > alias: hid:b0003g*v00005543p00000522 > alias: hid:b0003g*v00005543p00000064 > alias: hid:b0003g*v00005543p00000005 > alias: hid:b0003g*v00005543p00000004 > alias: hid:b0003g*v00005543p00000003 > alias: hid:b0003g*v00005543p00000042 > depends: hid > vermagic: 4.4.0-24-generic SMP mod_unload modversions > > > ====================== > > modinfo on non-working desktop (16.04, upgraded from 15.10): > > filename: /lib/modules/4.4.0-31-generic/updates/dkms/hid-uclogic.ko > version: 6 > license: GPL > author: Nikolai Kondrashov > author: Martin Rusko > srcversion: 34A15E7DFFC53AA6F4BEACF > alias: hid:b0003g*v00002179p00000053 > alias: hid:b0003g*v00005543p00003031 > alias: hid:b0003g*v00005543p00000045 > alias: hid:b0003g*v00005543p00000081 > alias: hid:b0003g*v00005543p0000004D > alias: hid:b0003g*v00005543p0000006E > alias: hid:b0003g*v0000256Cp0000006E > alias: hid:b0003g*v00005543p00000781 > alias: hid:b0003g*v00005543p00000522 > alias: hid:b0003g*v00005543p00000064 > alias: hid:b0003g*v00005543p00000005 > alias: hid:b0003g*v00005543p00000004 > alias: hid:b0003g*v00005543p00000003 > alias: hid:b0003g*v00005543p00000042 > depends: hid > vermagic: 4.4.0-31-generic SMP mod_unload modversions > > > > On Sun, Jul 17, 2016 at 10:39 AM, Nikolai Kondrashov <sp...@gm...> > wrote: > >> Hi Caleb, >> >> On 07/15/2016 07:16 AM, Caleb Langeslag wrote: >> >>> So a friend recently acquired a Huion GT-190. >>> >> >> We don't have information on that tablet. Could you send "lsusb -v" >> output for >> the start? Thank you. >> >> Plugged it in, installed the latest DIGImend DKMS deb package on Ubuntu >>> 15.10, and it worked perfectly. Later on, just recently upgraded to >>> Ubuntu >>> 16.04, and now the tablet does not function whatsoever. It's plugged in >>> and >>> shows up under lsusb, but is not listed under 'xinput --list'. >>> >> >> This is interesting. >> >> Next, I grabbed the graphics tablet and plugged it into another desktop, >>> with a fresh clean Ubuntu 16.04 installation (no upgrade), and installed >>> the >>> DIGImend drivers, and it works perfectly fine on there. >>> >>> I'm wondering if there's a packaging issue with the deb package, when >>> dealing with OS version upgrades, or if it's some bug in Canonical's >>> work. >>> >>> On the other desktop (that was upgraded from 15.10), I tried uninstalling >>> the package, restarting, reinstalling the package, restarting, and no >>> resulting difference. Also tried "Mark for complete removal" under >>> Synaptic >>> for the 'digimend-dkms' package, and reinstalling after. I've also tried >>> rmmod to unload the kernel module (hid_uclogic), and insmod to manually >>> load >>> the the module for the current kernel version, with no change. >>> >>> On both computers, I can run lsmod and see hid_uclogic loaded. >>> >>> When I run 'watch -n 0.5 xinput --list' on both computers, and plug in >>> the tablet, I get the results of: >>> >>> - On the upgraded 16.04 computer: "NUVOTON WPM USB" appears for a >>> second, then disappears. Nothing else comes up thereafter. >>> - On the cleanly installed 16.04 computer: "NUVOTON WPM USB" appears >>> for a second, disappears, then the Tablet Monitor >>> Pen/Mouse/Consumer-Control items appear and stay. >>> >>> If there's any further information required, then feel free to ask. >>> >> >> Alright, can you send the output of "/sbin/modinfo hid-uclogic" from both >> machines? I suspect that the driver won't even build on 16.04, as it has >> the >> 4.4 kernel with HID driver interface changed slightly, introducing >> incompatibility. >> >> You can try building and installing the latest development version >> manually >> from >> https://github.com/DIGImend/digimend-kernel-drivers/archive/master.zip >> >> Nick >> > > |
From: Caleb L. <ca...@te...> - 2016-07-19 22:49:21
|
Output of lsusb is: Bus 003 Device 004: ID 256c:006e Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x256c idProduct 0x006e bcdDevice 0.00 iManufacturer 5 (error) iProduct 6 Tablet Monitor iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 84 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.11 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 177 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 2 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.11 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 244 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 2 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 2 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.0b bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 92 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 8 Device Status: 0x0000 (Bus Powered) ====================== modinfo on WORKING desktop (fresh 16.04 install): filename: /lib/modules/4.4.0-24-generic/updates/dkms/hid-uclogic.ko version: 6 license: GPL author: Nikolai Kondrashov author: Martin Rusko srcversion: 34A15E7DFFC53AA6F4BEACF alias: hid:b0003g*v00002179p00000053 alias: hid:b0003g*v00005543p00003031 alias: hid:b0003g*v00005543p00000045 alias: hid:b0003g*v00005543p00000081 alias: hid:b0003g*v00005543p0000004D alias: hid:b0003g*v00005543p0000006E alias: hid:b0003g*v0000256Cp0000006E alias: hid:b0003g*v00005543p00000781 alias: hid:b0003g*v00005543p00000522 alias: hid:b0003g*v00005543p00000064 alias: hid:b0003g*v00005543p00000005 alias: hid:b0003g*v00005543p00000004 alias: hid:b0003g*v00005543p00000003 alias: hid:b0003g*v00005543p00000042 depends: hid vermagic: 4.4.0-24-generic SMP mod_unload modversions ====================== modinfo on non-working desktop (16.04, upgraded from 15.10): filename: /lib/modules/4.4.0-31-generic/updates/dkms/hid-uclogic.ko version: 6 license: GPL author: Nikolai Kondrashov author: Martin Rusko srcversion: 34A15E7DFFC53AA6F4BEACF alias: hid:b0003g*v00002179p00000053 alias: hid:b0003g*v00005543p00003031 alias: hid:b0003g*v00005543p00000045 alias: hid:b0003g*v00005543p00000081 alias: hid:b0003g*v00005543p0000004D alias: hid:b0003g*v00005543p0000006E alias: hid:b0003g*v0000256Cp0000006E alias: hid:b0003g*v00005543p00000781 alias: hid:b0003g*v00005543p00000522 alias: hid:b0003g*v00005543p00000064 alias: hid:b0003g*v00005543p00000005 alias: hid:b0003g*v00005543p00000004 alias: hid:b0003g*v00005543p00000003 alias: hid:b0003g*v00005543p00000042 depends: hid vermagic: 4.4.0-31-generic SMP mod_unload modversions On Sun, Jul 17, 2016 at 10:39 AM, Nikolai Kondrashov <sp...@gm...> wrote: > Hi Caleb, > > On 07/15/2016 07:16 AM, Caleb Langeslag wrote: > >> So a friend recently acquired a Huion GT-190. >> > > We don't have information on that tablet. Could you send "lsusb -v" output > for > the start? Thank you. > > Plugged it in, installed the latest DIGImend DKMS deb package on Ubuntu >> 15.10, and it worked perfectly. Later on, just recently upgraded to >> Ubuntu >> 16.04, and now the tablet does not function whatsoever. It's plugged in >> and >> shows up under lsusb, but is not listed under 'xinput --list'. >> > > This is interesting. > > Next, I grabbed the graphics tablet and plugged it into another desktop, >> with a fresh clean Ubuntu 16.04 installation (no upgrade), and installed >> the >> DIGImend drivers, and it works perfectly fine on there. >> >> I'm wondering if there's a packaging issue with the deb package, when >> dealing with OS version upgrades, or if it's some bug in Canonical's work. >> >> On the other desktop (that was upgraded from 15.10), I tried uninstalling >> the package, restarting, reinstalling the package, restarting, and no >> resulting difference. Also tried "Mark for complete removal" under >> Synaptic >> for the 'digimend-dkms' package, and reinstalling after. I've also tried >> rmmod to unload the kernel module (hid_uclogic), and insmod to manually >> load >> the the module for the current kernel version, with no change. >> >> On both computers, I can run lsmod and see hid_uclogic loaded. >> >> When I run 'watch -n 0.5 xinput --list' on both computers, and plug in >> the tablet, I get the results of: >> >> - On the upgraded 16.04 computer: "NUVOTON WPM USB" appears for a >> second, then disappears. Nothing else comes up thereafter. >> - On the cleanly installed 16.04 computer: "NUVOTON WPM USB" appears >> for a second, disappears, then the Tablet Monitor >> Pen/Mouse/Consumer-Control items appear and stay. >> >> If there's any further information required, then feel free to ask. >> > > Alright, can you send the output of "/sbin/modinfo hid-uclogic" from both > machines? I suspect that the driver won't even build on 16.04, as it has > the > 4.4 kernel with HID driver interface changed slightly, introducing > incompatibility. > > You can try building and installing the latest development version manually > from > https://github.com/DIGImend/digimend-kernel-drivers/archive/master.zip > > Nick > |
From: Nikolai K. <sp...@gm...> - 2016-07-17 15:39:27
|
Hi Caleb, On 07/15/2016 07:16 AM, Caleb Langeslag wrote: > So a friend recently acquired a Huion GT-190. We don't have information on that tablet. Could you send "lsusb -v" output for the start? Thank you. > Plugged it in, installed the latest DIGImend DKMS deb package on Ubuntu > 15.10, and it worked perfectly. Later on, just recently upgraded to Ubuntu > 16.04, and now the tablet does not function whatsoever. It's plugged in and > shows up under lsusb, but is not listed under 'xinput --list'. This is interesting. > Next, I grabbed the graphics tablet and plugged it into another desktop, > with a fresh clean Ubuntu 16.04 installation (no upgrade), and installed the > DIGImend drivers, and it works perfectly fine on there. > > I'm wondering if there's a packaging issue with the deb package, when > dealing with OS version upgrades, or if it's some bug in Canonical's work. > > On the other desktop (that was upgraded from 15.10), I tried uninstalling > the package, restarting, reinstalling the package, restarting, and no > resulting difference. Also tried "Mark for complete removal" under Synaptic > for the 'digimend-dkms' package, and reinstalling after. I've also tried > rmmod to unload the kernel module (hid_uclogic), and insmod to manually load > the the module for the current kernel version, with no change. > > On both computers, I can run lsmod and see hid_uclogic loaded. > > When I run 'watch -n 0.5 xinput --list' on both computers, and plug in the tablet, I get the results of: > > - On the upgraded 16.04 computer: "NUVOTON WPM USB" appears for a second, then disappears. Nothing else comes up thereafter. > - On the cleanly installed 16.04 computer: "NUVOTON WPM USB" appears for a second, disappears, then the Tablet Monitor Pen/Mouse/Consumer-Control items appear and stay. > > If there's any further information required, then feel free to ask. Alright, can you send the output of "/sbin/modinfo hid-uclogic" from both machines? I suspect that the driver won't even build on 16.04, as it has the 4.4 kernel with HID driver interface changed slightly, introducing incompatibility. You can try building and installing the latest development version manually from https://github.com/DIGImend/digimend-kernel-drivers/archive/master.zip Nick |
From: Nikolai K. <sp...@gm...> - 2016-07-17 15:11:32
|
Hi Jens, On 07/06/2016 01:13 PM, Jens Verwiebe wrote: > Thanks for your nice work on this project. > This deseverves some feedback for sure. Thanks a lot for your detailed feedback! Glad to hear the tablet worked for you, even if you had problems with the pressure. Theoretically the Wacom driver can be modified to work with your tablet without too much problem, and then you'll be able to set pressure curves for the general use to fix problems with clicking. Unfortunately, nowadays I don't have time to do that work, and there are no people interested enough to help yet, but you can try it yourself, or perhaps ask the xf86-input-wacom developers to do it. They added support for Huion tablets, at least. And of course, if you have any spare cycles and are interested in furthering Linux support for graphics tablets, your contributions will always be welcome :) Nick |
From: Caleb L. <ca...@te...> - 2016-07-15 04:44:38
|
So a friend recently acquired a Huion GT-190. Plugged it in, installed the latest DIGImend DKMS deb package on Ubuntu 15.10, and it worked perfectly. Later on, just recently upgraded to Ubuntu 16.04, and now the tablet does not function whatsoever. It's plugged in and shows up under lsusb, but is not listed under 'xinput --list'. Next, I grabbed the graphics tablet and plugged it into another desktop, with a fresh clean Ubuntu 16.04 installation (no upgrade), and installed the DIGImend drivers, and it works perfectly fine on there. I'm wondering if there's a packaging issue with the deb package, when dealing with OS version upgrades, or if it's some bug in Canonical's work. On the other desktop (that was upgraded from 15.10), I tried uninstalling the package, restarting, reinstalling the package, restarting, and no resulting difference. Also tried "Mark for complete removal" under Synaptic for the 'digimend-dkms' package, and reinstalling after. I've also tried rmmod to unload the kernel module (hid_uclogic), and insmod to manually load the the module for the current kernel version, with no change. On both computers, I can run lsmod and see hid_uclogic loaded. When I run 'watch -n 0.5 xinput --list' on both computers, and plug in the tablet, I get the results of: - On the upgraded 16.04 computer: "NUVOTON WPM USB" appears for a second, then disappears. Nothing else comes up thereafter. - On the cleanly installed 16.04 computer: "NUVOTON WPM USB" appears for a second, disappears, then the Tablet Monitor Pen/Mouse/Consumer-Control items appear and stay. If there's any further information required, then feel free to ask. |
From: Nikolai K. <sp...@gm...> - 2016-07-06 15:05:02
|
On 07/06/2016 05:30 AM, Christopher Barry wrote: > > DKMS make.log for digimend-6 for kernel 4.6.0-1-amd64 (x86_64) > Tue Jul 5 22:26:59 EDT 2016 > make -C /lib/modules/4.6.0-1-amd64/build > SUBDIRS=/var/lib/dkms/digimend/6/build modules make[1]: Entering > directory '/usr/src/linux-headers-4.6.0-1-amd64' CC > [M] /var/lib/dkms/digimend/6/build/hid-kye.o CC > [M] /var/lib/dkms/digimend/6/build/hid-uclogic.o CC > [M] /var/lib/dkms/digimend/6/build/hid-polostar.o /var/lib/dkms/digimend/6/build/hid-uclogic.c:1101:22: > error: initialization from incompatible pointer type > [-Werror=incompatible-pointer-types] .input_configured = > uclogic_input_configured, > ^ /var/lib/dkms/digimend/6/build/hid-uclogic.c:1101:22: note: (near > initialization for ‘uclogic_driver.input_configured’) cc1: some > warnings being treated as > errors /usr/src/linux-headers-4.6.0-1-common/scripts/Makefile.build:302: > recipe for target '/var/lib/dkms/digimend/6/build/hid-uclogic.o' failed > make[4]: *** [/var/lib/dkms/digimend/6/build/hid-uclogic.o] Error > 1 /usr/src/linux-headers-4.6.0-1-common/Makefile:1446: recipe for > target '_module_/var/lib/dkms/digimend/6/build' failed make[3]: *** > [_module_/var/lib/dkms/digimend/6/build] Error 2 Makefile:146: recipe > for target 'sub-make' failed make[2]: *** [sub-make] Error 2 > Makefile:8: recipe for target 'all' failed make[1]: *** [all] Error 2 > make[1]: Leaving directory '/usr/src/linux-headers-4.6.0-1-amd64' > Makefile:9: recipe for target 'modules' failed make: *** [modules] > Error 2 > > > is it me? No, newer kernels changed the input_configured function prototype. You'll need to use the latest master version, where a workaround is implemented, and build and install it manually, or using DKMS. This will be included in the next release, but when that comes I can't say yet. Nick |
From: Jens V. <in...@je...> - 2016-07-06 10:26:53
|
Hi folks Thanks for your nice work on this project. This deseverves some feedback for sure. I recently needed a new tablet and decided to be brave :) I bought now a XP-Pen Star 03 10*6" tablett for general use + a bit texture drawing for my Linux Mint 17.3. Wanted to test something pretty cheap but big with no battery needed in the pen ( around 50 bucks ). Got the DigiMend drivers. The tablet is recognized as expected. lsusb: ID 5543:0081 UC-Logic Technology Corp. xinput --list: ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=8 [slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=9 [slave pointer (2)] ⎜ ↳ USB Keyboard id=11 [slave pointer (2)] ⎜ ↳ UC-Logic TABLET 1060N Pen id=12 [slave pointer (2)] ⎜ ↳ UC-Logic TABLET 1060N Mouse id=13 [slave pointer (2)] ⎜ ↳ UC-Logic TABLET 1060N Pad id=14 [slave pointer (2)] ⎜ ↳ UC-Logic TABLET 1060N Consumer Control id=16 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Power Button id=7 [slave keyboard (3)] ↳ USB Keyboard id=10 [slave keyboard (3)] ↳ UC-Logic TABLET 1060N Keyboard id=15 [slave keyboard (3)] ↳ UC-Logic TABLET 1060N System Control id=17 [slave keyboard (3)] I made a few tweaks to adapt handling and enforce releability: - created a 52-uc-logic.conf where i set the Option "ButtonMapping" "1 3 2" aka static, no script needed at startup + this survives a sleep/resume, no need for extra actions though: Section "InputClass" Identifier "Graphics tablet mouse" MatchIsPointer "on" MatchProduct "UC-Logic" MatchDevicePath "/dev/input/event*" Driver "evdev" # Apply custom Options below. EndSection Section "InputClass" Identifier "Graphics tablet pen" MatchIsTablet "on" MatchProduct "UC-Logic" MatchDevicePath "/dev/input/event*" Driver "evdev" Option "ButtonMapping" "1 3 2" EndSection The tablet wasn't longer recognized when waking the machine from sleep/suspend: - set SUSPEND_MODULES="$SUSPEND_MODULES hid_uclogic" in a pm/config.d module This all works nicely for painting in Blender, Gimp, Krita. I observed the pressure is a bit more sensitive in the lower ranges than my former wacom graffire4 ( threshhold ? ). This is not a problem in painting use, as the apps allow for manipulating the pressurecurves anyway. I also work most of the time with the pen for general purpose aka editing, coding, mouse-like use. Here a little problem shows up from the very sensitive pen: in rare cases click/doubleclick fails. I tried to use the xsetwacom way described for WALTOP tablets and this seems to work in a way, but did not solve my little problem it seems. Mapping pen buttons was possible. /xinput list-props "UC-Logic TABLET 1060N Pen stylus"/ showed up as expected but /xsetwacom set "UC-Logic TABLET 1060N Pen stylus" Threshold 27/ seemed to have no effect. But perhaps i had interference with evdev, not sure. Anyway, from this i've learned that for general purpose use it would be nice the evdev driver would have an pressure threshold for more reliable action tuning in for example filemangers, editors etc. No complaints about usage in drawing applications. Again thx for your effords. I am a developer too ( Blender, LuxRender ) so if you perhaps need more details just lemme know. Cheers ... Jens Jens -- Jens Verwiebe Allerskehre 44 - 22309 Hamburg Tel.: +49 40 68 78 50 mobile: +49 172 400 49 07 mailto: in...@je... web: http://www.jensverwiebe.de |
From: Christopher B. <chr...@gm...> - 2016-07-06 02:31:15
|
DKMS make.log for digimend-6 for kernel 4.6.0-1-amd64 (x86_64) Tue Jul 5 22:26:59 EDT 2016 make -C /lib/modules/4.6.0-1-amd64/build SUBDIRS=/var/lib/dkms/digimend/6/build modules make[1]: Entering directory '/usr/src/linux-headers-4.6.0-1-amd64' CC [M] /var/lib/dkms/digimend/6/build/hid-kye.o CC [M] /var/lib/dkms/digimend/6/build/hid-uclogic.o CC [M] /var/lib/dkms/digimend/6/build/hid-polostar.o /var/lib/dkms/digimend/6/build/hid-uclogic.c:1101:22: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .input_configured = uclogic_input_configured, ^ /var/lib/dkms/digimend/6/build/hid-uclogic.c:1101:22: note: (near initialization for ‘uclogic_driver.input_configured’) cc1: some warnings being treated as errors /usr/src/linux-headers-4.6.0-1-common/scripts/Makefile.build:302: recipe for target '/var/lib/dkms/digimend/6/build/hid-uclogic.o' failed make[4]: *** [/var/lib/dkms/digimend/6/build/hid-uclogic.o] Error 1 /usr/src/linux-headers-4.6.0-1-common/Makefile:1446: recipe for target '_module_/var/lib/dkms/digimend/6/build' failed make[3]: *** [_module_/var/lib/dkms/digimend/6/build] Error 2 Makefile:146: recipe for target 'sub-make' failed make[2]: *** [sub-make] Error 2 Makefile:8: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-4.6.0-1-amd64' Makefile:9: recipe for target 'modules' failed make: *** [modules] Error 2 is it me? -- Regards, Christopher |
From: Nikolai K. <sp...@gm...> - 2016-07-03 16:13:38
|
Hi Mozart, On 07/03/2016 06:38 PM, Mozart Couto wrote: > It's happening a problem with the stylus of uc-logic 6x8 graphic tables.I > believe that this also occurs with all other using the same technology. I > watched it from the Debian-based distributions like Ubuntu and its other > flavors, 14.04 and 16.04 versions than the click of the "right"button (the > top of the stylus pen button) does not respond naturally. You must click > several times to make it work. You must click and click and randomly it can > work. It would be possible to solve this problem and make that hardware back > to work as before, in the distributions below 14.04? There was a problem in a recent xf86-input-evdev driver version. Try updating it or using an older one. If that doesn't help, send output of "usbhid-dump", "evtest", and "xinput test" while you click that button. Nick |
From: Mozart C. <moz...@gm...> - 2016-07-03 15:38:19
|
Hello everyone! It's happening a problem with the stylus of uc-logic 6x8 graphic tables.I believe that this also occurs with all other using the same technology. I watched it from the Debian-based distributions like Ubuntu and its other flavors, 14.04 and 16.04 versions than the click of the "right"button (the top of the stylus pen button) does not respond naturally. You must click several times to make it work. You must click and click and randomly it can work. It would be possible to solve this problem and make that hardware back to work as before, in the distributions below 14.04? Thank you. -- Mozart Couto www.mozartcouto.com.br http://blogdodesenhador.blogspot.com <http://mozartcoutoimagens.blogspot.com> |
From: Nikolai K. <sp...@gm...> - 2016-06-26 16:52:24
|
Hi Masaru, On 06/26/2016 07:30 PM, Masaru Hirano wrote: > I have Upgraded to Ubuntu 16.04 LTS > But I have met compile error. > Ubuntu 14.04 have no errors. > > I thinks this is ssl error. > Is there anybody who knows solution. > Please help me. > > Below are make install error. > > sudo make install > [sudo] muteki password: > make -C /lib/modules/4.4.0-24-generic/build > SUBDIRS=/home/muteki/digimend/digimend-kernel-drivers-6 modules_install > make[1]: directorie '/usr/src/linux-headers-4.4.0-24-generic' in > INSTALL /home/muteki/digimend/digimend-kernel-drivers-6/hid-kye.ko > At main.c:222: > - SSL error:02001002:system library:fopen:No such file or directory: > bss_file.c:175 > - SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:178 > sign-file: certs/signing_key.pem: No such file or directory > INSTALL /home/muteki/digimend/digimend-kernel-drivers-6/hid-polostar.ko > At main.c:222: > - SSL error:02001002:system library:fopen:No such file or directory: > bss_file.c:175 > - SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:178 > sign-file: certs/signing_key.pem: No such file or directory > INSTALL /home/muteki/digimend/digimend-kernel-drivers-6/hid-uclogic.ko > At main.c:222: > - SSL error:02001002:system library:fopen:No such file or directory: > bss_file.c:175 > - SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:178 > sign-file: certs/signing_key.pem: No such file or directory This looks like a problem with your SSL setup, not related to the drivers. It also looks, like the installation completes. Have you tried if the driver works? Otherwise, if it doesn't, please try using the .deb package if you can. Nick |
From: Masaru H. <mhi...@gm...> - 2016-06-26 16:30:57
|
I have Upgraded to Ubuntu 16.04 LTS But I have met compile error. Ubuntu 14.04 have no errors. I thinks this is ssl error. Is there anybody who knows solution. Please help me. Below are make install error. sudo make install [sudo] muteki password: make -C /lib/modules/4.4.0-24-generic/build SUBDIRS=/home/muteki/digimend/digimend-kernel-drivers-6 modules_install make[1]: directorie '/usr/src/linux-headers-4.4.0-24-generic' in INSTALL /home/muteki/digimend/digimend-kernel-drivers-6/hid-kye.ko At main.c:222: - SSL error:02001002:system library:fopen:No such file or directory: bss_file.c:175 - SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:178 sign-file: certs/signing_key.pem: No such file or directory INSTALL /home/muteki/digimend/digimend-kernel-drivers-6/hid-polostar.ko At main.c:222: - SSL error:02001002:system library:fopen:No such file or directory: bss_file.c:175 - SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:178 sign-file: certs/signing_key.pem: No such file or directory INSTALL /home/muteki/digimend/digimend-kernel-drivers-6/hid-uclogic.ko At main.c:222: - SSL error:02001002:system library:fopen:No such file or directory: bss_file.c:175 - SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:178 sign-file: certs/signing_key.pem: No such file or directory DEPMOD 4.4.0-24-generic make[1]: directorie '/usr/src/linux-headers-4.4.0-24-generic' out install -D -m 0644 digimend.conf /etc/depmod.d/digimend.conf depmod -a install hid-rebind /sbin/hid-rebind install -m 0644 90-hid-rebind.rules /lib/udev/rules.d/90-hid-rebind.rules udevadm control --reload |
From: PRAJITH <pra...@gm...> - 2016-05-08 19:15:31
|
Is there any DIGIMend driver available for Iball Take Note? http://www.iball.co.in/Product/Take-Note-A414/181 Thanks, |