digimend-users Mailing List for DIGImend (Page 5)
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: Benjamin T. <ben...@re...> - 2015-03-17 02:13:49
|
On Mar 17 2015 or thereabouts, Sergey Jin' Bostandzhyan wrote: > OK, you gave me some pointers, I know what was wrong. > > On Mon, Mar 16, 2015 at 09:15:15PM -0400, Benjamin Tissoires wrote: > > If your distribution enabled src checksum, you can compare: > > the SRCVERSION field of modinfo ./hid-uclogic.ko in the > > digimend-kernel-driver tree and the output of > > cat /sys/module/hid_uclogic/srcversion > > The problem I had was: I still had the hid-huion module around and > somehow it got loaded first, instead of hid-uclogic. > > After removing the old hid-huion module and modprobing hid-uclogic > things started to look as expected, I see only one device now: > > xsetwacom --list devices > HUION PenTablet Pen stylus id: 15 type: STYLUS > > > (giving that out of my head, I don't have it enabled ATM). > > > > Also, xinput should show at least: > > That's what I have, so looks good: > > ⎡ Virtual core pointer id=2 [master pointer (3)] > ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] > ⎜ ↳ SynPS/2 Synaptics TouchPad id=12 [slave pointer (2)] > ⎜ ↳ MCE IR Keyboard/Mouse (ite-cir) id=13 [slave pointer (2)] > ⎜ ↳ HUION PenTablet Pen stylus id=15 [slave pointer (2)] > ⎜ ↳ HUION PenTablet Mouse id=16 [slave pointer (2)] > ⎜ ↳ HUION PenTablet Consumer Control id=17 [slave pointer (2)] > ⎣ Virtual core keyboard id=3 [master keyboard (2)] > ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] > ↳ Power Button id=6 [slave keyboard (3)] > ↳ Video Bus id=7 [slave keyboard (3)] > ↳ Power Button id=8 [slave keyboard (3)] > ↳ Sleep Button id=9 [slave keyboard (3)] > ↳ CNF7017 id=10 [slave keyboard (3)] > ↳ AT Translated Set 2 keyboard id=11 [slave keyboard (3)] > ↳ ITE8708 CIR transceiver id=14 [slave keyboard (3)] > ↳ HUION PenTablet Keyboard id=18 [slave keyboard (3)] > ↳ HUION PenTablet System Control id=19 [slave keyboard (3)] You are missing the "HUION PenTablet Pad pad" interface... > > > Here's also the updated dmesg log with the uclogic module: > > [49913.355176] usb 6-2: new full-speed USB device number 4 using > uhci_hcd > [49913.500176] usb 6-2: New USB device found, idVendor=256c, > idProduct=006e > [49913.500182] usb 6-2: New USB device strings: Mfr=5, Product=6, > SerialNumber=0 > [49913.500186] usb 6-2: Product: PenTablet > [49913.500189] usb 6-2: Manufacturer: HUION > [49913.509671] input: HUION PenTablet Pen as > /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/0003:256C:006E.0007/input/input41 > [49913.509928] input: HUION PenTablet Pad as > /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/0003:256C:006E.0007/input/input42 ... which is created here. [edit: keeping this part for documenting purpose, this is not required right now, we would have to update the xf86-input-wacom driver first. See below] So actually, you are just missing a udev rule to properly tag the device as a ID_INPUT_TABLET: [bentiss@plouf ~]$ cat /etc/udev/rules.d/65-digimend.rules # udev rules for digimend devices ACTION!="add|change", GOTO="digimend_end" KERNEL!="event[0-9]*", GOTO="digimend_end" ENV{ID_BUS}=="usb", ENV{ID_VENDOR_ID}=="256c", ENV{ID_MODEL_ID}=="006e", ENV{ID_INPUT}="1", ENV{ID_INPUT_JOYSTICK}="", ENV{ID_INPUT_TABLET}="1" ATTRS{name}=="* Pad", ENV{ID_BUS}=="usb", ENV{ID_VENDOR_ID}=="256c", ENV{ID_MODEL_ID}=="006e", ENV{ID_INPUT_TABLET_PAD}="1" LABEL="digimend_end" [bentiss@plouf ~]$ Then run "sudo udevadm control --reload " With this rule, "udevadm info --exportdb" should show the event node "HUION PenTablet Pad" tagged with ID_INPUT_TABLET_PAD=1. Then, xinput should show up the "HUION PenTablet Pad pad" device. If it does not, then you will have to send me the Xorg.log when you plug the tablet. [end of the useless though documenting garbage :) ] > > > Unless they sent me something else without me knowing - I bought a regular > > > H610, not the "pro" one. The stickers also say H610, so I guess it's > > > indeed not the "pro" version. > > > > That's interesting and frustrating. I thought that the name would be > > enough the discriminate, but it doesn't look like it. > > > > The two tablets are close enough the share the same user-space > > configuration, but I hope that they do not always have the name "HUION > > PenTablet" or the other tablet will get the layout of the H610* when > > configuring the pads buttons :( > > Well, if they can not be reliably autodetected, please add some fallback > parameter for the kernel module (or maybe it's already there, I'll have to > check), it's still better than nothing. No, the kernel will be fine. It's the userspace which will consider all "HUION PenTablet" as H610 Pro and will show the same UI for configuring the tablet. It's not a problem for the stylus part, but it will be one for the buttons of the tablet (what we refer to pad). > > > So, back to xsetwacom: > > xsetwacom set 15 button 3 key + > -> OK > > xsetwacom set 15 button 4 key + > Invalid offset into Wacom Button Actions property. > > So despite the new driver it still does not let me map the other buttons. > What am I missing? The pad interface :) Oh. Actually, you also need to add a patch in xf86-input-wacom :( Without it, the pad will be rejected by the driver while it could work just fine. I'll send a patch to digimend-kernel-tree to make the pad interface looks like an old legacy Wacom pad so that you will be able to continue the tests. Sorry for that. > > Btw, Gimp gives me three input devices: > > HUION PenTablet Consumer Control > HUION PenTablet Mouse > HUION PenTablet Pen stylus > > I enabled all three of them, I could see that only the last one is > used as real input; btw drawing etc. worked just fine. You can definitively ignore Mouse and Consumer Control. We keep them in the kernel because we don't know if they are used by any tablet, given that it looks like there is no reliable way to know which tablet is which. > > > If you have something to test for the remaining keys or need me to try > something out - just let me know. > OK. So it's best to wait for the update on the driver first. With this update, you won't even need the udev rule. I'll do that tomorrow. Cheers, Benjamin |
From: Sergey J. B. <ji...@me...> - 2015-03-17 01:45:10
|
OK, you gave me some pointers, I know what was wrong. On Mon, Mar 16, 2015 at 09:15:15PM -0400, Benjamin Tissoires wrote: > If your distribution enabled src checksum, you can compare: > the SRCVERSION field of modinfo ./hid-uclogic.ko in the > digimend-kernel-driver tree and the output of > cat /sys/module/hid_uclogic/srcversion The problem I had was: I still had the hid-huion module around and somehow it got loaded first, instead of hid-uclogic. After removing the old hid-huion module and modprobing hid-uclogic things started to look as expected, I see only one device now: xsetwacom --list devices HUION PenTablet Pen stylus id: 15 type: STYLUS > (giving that out of my head, I don't have it enabled ATM). > > Also, xinput should show at least: That's what I have, so looks good: ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=12 [slave pointer (2)] ⎜ ↳ MCE IR Keyboard/Mouse (ite-cir) id=13 [slave pointer (2)] ⎜ ↳ HUION PenTablet Pen stylus id=15 [slave pointer (2)] ⎜ ↳ HUION PenTablet Mouse id=16 [slave pointer (2)] ⎜ ↳ HUION PenTablet Consumer Control id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Power Button id=8 [slave keyboard (3)] ↳ Sleep Button id=9 [slave keyboard (3)] ↳ CNF7017 id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=11 [slave keyboard (3)] ↳ ITE8708 CIR transceiver id=14 [slave keyboard (3)] ↳ HUION PenTablet Keyboard id=18 [slave keyboard (3)] ↳ HUION PenTablet System Control id=19 [slave keyboard (3)] Here's also the updated dmesg log with the uclogic module: [49913.355176] usb 6-2: new full-speed USB device number 4 using uhci_hcd [49913.500176] usb 6-2: New USB device found, idVendor=256c, idProduct=006e [49913.500182] usb 6-2: New USB device strings: Mfr=5, Product=6, SerialNumber=0 [49913.500186] usb 6-2: Product: PenTablet [49913.500189] usb 6-2: Manufacturer: HUION [49913.509671] input: HUION PenTablet Pen as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/0003:256C:006E.0007/input/input41 [49913.509928] input: HUION PenTablet Pad as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/0003:256C:006E.0007/input/input42 [49913.510334] uclogic 0003:256C:006E.0007: input,hidraw0: USB HID v1.11 Keypad [HUION PenTablet] on usb-0000:00:1d.1-2/input0 [49913.512981] input: HUION PenTablet Mouse as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.1/0003:256C:006E.0008/input/input43 [49913.513853] uclogic 0003:256C:006E.0008: input,hiddev0,hidraw1: USB HID v1.11 Mouse [HUION PenTablet] on usb-0000:00:1d.1-2/input1 [49913.518336] input: HUION PenTablet Keyboard as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.2/0003:256C:006E.0009/input/input45 [49913.518525] input: HUION PenTablet Consumer Control as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.2/0003:256C:006E.0009/input/input46 [49913.518632] input: HUION PenTablet System Control as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.2/0003:256C:006E.0009/input/input47 [49913.518874] uclogic 0003:256C:006E.0009: input,hidraw2: USB HID v1.11 Keyboard [HUION PenTablet] on usb-0000:00:1d.1-2/input2 > Nick should help you here, I have no idea of the scripts used to > unbind/re-bind the tablet in the out-of-the-tree drivers. I think this part got resolved now. > > Unless they sent me something else without me knowing - I bought a regular > > H610, not the "pro" one. The stickers also say H610, so I guess it's > > indeed not the "pro" version. > > That's interesting and frustrating. I thought that the name would be > enough the discriminate, but it doesn't look like it. > > The two tablets are close enough the share the same user-space > configuration, but I hope that they do not always have the name "HUION > PenTablet" or the other tablet will get the layout of the H610* when > configuring the pads buttons :( Well, if they can not be reliably autodetected, please add some fallback parameter for the kernel module (or maybe it's already there, I'll have to check), it's still better than nothing. So, back to xsetwacom: xsetwacom set 15 button 3 key + -> OK xsetwacom set 15 button 4 key + Invalid offset into Wacom Button Actions property. So despite the new driver it still does not let me map the other buttons. What am I missing? Btw, Gimp gives me three input devices: HUION PenTablet Consumer Control HUION PenTablet Mouse HUION PenTablet Pen stylus I enabled all three of them, I could see that only the last one is used as real input; btw drawing etc. worked just fine. If you have something to test for the remaining keys or need me to try something out - just let me know. Kind regards, Jin |
From: Benjamin T. <ben...@re...> - 2015-03-17 01:15:27
|
On Mar 17 2015 or thereabouts, Sergey 'Jin' Bostandzhyan wrote: > Hi Benjamin, > > On Mon, Mar 16, 2015 at 08:43:34PM -0400, Benjamin Tissoires wrote: > > I bet Nick is already asleep in his timezone, so I answer :) > > well, I should be too - since I am also somewhat in his timezone ;) Anyway... > > > These names don't look like the ones I would have expected. > > You should have only one "HUION PenTablet Pen stylus", no "HUION PenTablet > > eraser" and one "HUION PenTablet Pad pad". > > hmm, can I somehow verify that the new driver is indeed loaded? If your distribution enabled src checksum, you can compare: the SRCVERSION field of modinfo ./hid-uclogic.ko in the digimend-kernel-driver tree and the output of cat /sys/module/hid_uclogic/srcversion (giving that out of my head, I don't have it enabled ATM). Also, xinput should show at least: ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ HUION PenTablet Pen stylus id=14 [slave pointer (2)] ⎜ ↳ HUION PenTablet Pad pad id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] And maybe the other HUION PenTablet Consumer Control, Keyboard, etc... > > > So I think the new master of hid-uclogic is not handling the device as > > it should. > > > > can you output the few new lines in the dmesg while you are plugging the > > tablet? > > Here are the lines from the tests in my previous mail: > > [43467.811182] usb 6-2: new full-speed USB device number 3 using uhci_hcd > [43467.955295] usb 6-2: New USB device found, idVendor=256c, idProduct=006e > [43467.955306] usb 6-2: New USB device strings: Mfr=5, Product=6, SerialNumber=0 > [43467.955314] usb 6-2: Product: PenTablet > [43467.955321] usb 6-2: Manufacturer: HUION > [43467.965574] input: HUION PenTablet Pen as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/0003:256C:006E.0004/input/input34 > [43467.965940] input: HUION PenTablet Pad as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/0003:256C:006E.0004/input/input35 > [43467.966680] uclogic 0003:256C:006E.0004: input,hidraw0: USB HID v1.11 Keypad [HUION PenTablet] on usb-0000:00:1d.1-2/input0 > [43467.969564] input: HUION PenTablet Mouse as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.1/0003:256C:006E.0005/input/input36 > [43467.970476] uclogic 0003:256C:006E.0005: input,hiddev0,hidraw1: USB HID v1.11 Mouse [HUION PenTablet] on usb-0000:00:1d.1-2/input1 > [43467.975384] input: HUION PenTablet Keyboard as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.2/0003:256C:006E.0006/input/input38 > [43467.975683] input: HUION PenTablet Consumer Control as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.2/0003:256C:006E.0006/input/input39 > [43467.975866] input: HUION PenTablet System Control as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.2/0003:256C:006E.0006/input/input40 > [43467.976278] uclogic 0003:256C:006E.0006: input,hidraw2: USB HID v1.11 Keyboard [HUION PenTablet] on usb-0000:00:1d.1-2/input2 > [45212.704187] usb 6-2: USB disconnect, device number 3 On these lines, you are using the proper kernel. Can you double check if hid_huion is not currently handling the tablet? > > > xsetwacom sems to work OK (3 buttons on the stylus as you said). > > 16 and 17 are interfaces declared in the device but are not used. > > The new master should remove them. > > Well, that kind of makes me think I did not get the new driver? Looks like it :( > > I did an rmmod hid_huion, did a make install as root from the digimend > tree, that should have done it, right? Nick should help you here, I have no idea of the scripts used to unbind/re-bind the tablet in the out-of-the-tree drivers. > > > Can you just confirm that you have an Huion H610 and not the "H610 Pro"? > > I have the Pro and get the same output than you, but I thought the H610 > > not Pro was declared as "HUION H610". > > Unless they sent me something else without me knowing - I bought a regular > H610, not the "pro" one. The stickers also say H610, so I guess it's > indeed not the "pro" version. That's interesting and frustrating. I thought that the name would be enough the discriminate, but it doesn't look like it. The two tablets are close enough the share the same user-space configuration, but I hope that they do not always have the name "HUION PenTablet" or the other tablet will get the layout of the H610* when configuring the pads buttons :( Cheers, Benjamin |
From: Sergey 'J. B. <ji...@me...> - 2015-03-17 00:52:43
|
Hi Benjamin, On Mon, Mar 16, 2015 at 08:43:34PM -0400, Benjamin Tissoires wrote: > I bet Nick is already asleep in his timezone, so I answer :) well, I should be too - since I am also somewhat in his timezone ;) Anyway... > These names don't look like the ones I would have expected. > You should have only one "HUION PenTablet Pen stylus", no "HUION PenTablet > eraser" and one "HUION PenTablet Pad pad". hmm, can I somehow verify that the new driver is indeed loaded? > So I think the new master of hid-uclogic is not handling the device as > it should. > > can you output the few new lines in the dmesg while you are plugging the > tablet? Here are the lines from the tests in my previous mail: [43467.811182] usb 6-2: new full-speed USB device number 3 using uhci_hcd [43467.955295] usb 6-2: New USB device found, idVendor=256c, idProduct=006e [43467.955306] usb 6-2: New USB device strings: Mfr=5, Product=6, SerialNumber=0 [43467.955314] usb 6-2: Product: PenTablet [43467.955321] usb 6-2: Manufacturer: HUION [43467.965574] input: HUION PenTablet Pen as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/0003:256C:006E.0004/input/input34 [43467.965940] input: HUION PenTablet Pad as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/0003:256C:006E.0004/input/input35 [43467.966680] uclogic 0003:256C:006E.0004: input,hidraw0: USB HID v1.11 Keypad [HUION PenTablet] on usb-0000:00:1d.1-2/input0 [43467.969564] input: HUION PenTablet Mouse as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.1/0003:256C:006E.0005/input/input36 [43467.970476] uclogic 0003:256C:006E.0005: input,hiddev0,hidraw1: USB HID v1.11 Mouse [HUION PenTablet] on usb-0000:00:1d.1-2/input1 [43467.975384] input: HUION PenTablet Keyboard as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.2/0003:256C:006E.0006/input/input38 [43467.975683] input: HUION PenTablet Consumer Control as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.2/0003:256C:006E.0006/input/input39 [43467.975866] input: HUION PenTablet System Control as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.2/0003:256C:006E.0006/input/input40 [43467.976278] uclogic 0003:256C:006E.0006: input,hidraw2: USB HID v1.11 Keyboard [HUION PenTablet] on usb-0000:00:1d.1-2/input2 [45212.704187] usb 6-2: USB disconnect, device number 3 > xsetwacom sems to work OK (3 buttons on the stylus as you said). > 16 and 17 are interfaces declared in the device but are not used. > The new master should remove them. Well, that kind of makes me think I did not get the new driver? I did an rmmod hid_huion, did a make install as root from the digimend tree, that should have done it, right? > Can you just confirm that you have an Huion H610 and not the "H610 Pro"? > I have the Pro and get the same output than you, but I thought the H610 > not Pro was declared as "HUION H610". Unless they sent me something else without me knowing - I bought a regular H610, not the "pro" one. The stickers also say H610, so I guess it's indeed not the "pro" version. Kind regards, Jin |
From: Benjamin T. <ben...@re...> - 2015-03-17 00:43:45
|
Hi Sergei, I bet Nick is already asleep in his timezone, so I answer :) On Mar 17 2015 or thereabouts, Sergey 'Jin' Bostandzhyan wrote: > Hi Nick, > > On Mon, Mar 16, 2015 at 11:47:05PM +0200, Nikolai Kondrashov wrote: > > Benjamin Tissoires and me are working on making digimend-kernel-drivers > > compatible with current and future versions of the Wacom driver > > (xf86-input-wacom), especially with regard to adding support for remapping > > frame buttons to arbitrary key combinations. > > thank you guys! It would be really cool to get this to work. > > > This concerns Huion, Yiynova, Ugee tablets, as well as UC-Logic TWHA60 v3 > > tablet. > > I have a Huion H610, you pinged me on IRC earlier and I tried xsetwacom with > the latest master head of the kernel driver. > > I get the following devices: > > xsetwacom --list devices > HUION PenTablet stylus id: 16 type: STYLUS > HUION PenTablet eraser id: 17 type: ERASER > HUION PenTablet pad id: 18 type: PAD > HUION PenTablet stylus id: 19 type: STYLUS > These names don't look like the ones I would have expected. You should have only one "HUION PenTablet Pen stylus", no "HUION PenTablet eraser" and one "HUION PenTablet Pad pad". So I think the new master of hid-uclogic is not handling the device as it should. can you output the few new lines in the dmesg while you are plugging the tablet? > > The only one that actually worked was id: 19, I did: > > xsetwacom --set 19 button 3 key + > > ...and then a click on the stylus key indeed produced a + > > I was however not able to map the keys of id's 16-18, I tried some > combinations and all I got was: > > xsetwacom --set 16 button 1 key + > Property 'Wacom Button Actions' does not exist on device. > > At the same time buttons >3 on device id 19 produced the following > error: > > xsetwacom --set 19 button 4 key + > Invalid offset into Wacom Button Actions property. > > I guess that's OK, because the stylus only has 3 buttons (the tip + 2 extra > buttons), but I'd also expect the pad (id 18) to be mappable. > > At the same time I am not sure what id's 16 + 17 are? xsetwacom sems to work OK (3 buttons on the stylus as you said). 16 and 17 are interfaces declared in the device but are not used. The new master should remove them. > > > We would like to ask everyone owning one of these tablets to please take some > > diagnostics information from their tablets and send them in reply to this > > message. > > [...] > > > Please send the output of either of these commands, plus "lsusb -v" output. > > ./uclogic-probe 6 3 > M 48 00 55 00 49 00 4F 00 4E 00 00 00 00 00 00 00 > P 50 00 65 00 6E 00 54 00 61 00 62 00 6C 00 65 00 74 00 00 00 > S 64 0E 03 40 9C A8 61 03 00 FF 07 A0 0F 08 00 > S 65 04 03 20 A0 > S 6E 04 03 00 30 > S 79 14 03 48 00 41 00 36 00 30 00 00 00 00 00 00 00 00 00 00 00 > S 7A 08 03 01 08 00 00 00 00 > S 7B 0C 03 48 00 4B 00 20 00 4F 00 6E 00 > > > > Part of the lsusb -v output: > > Bus 006 Device 003: ID 256c:006e > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 0 (Defined at Interface level) > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 64 > idVendor 0x256c > idProduct 0x006e > bcdDevice 0.00 > iManufacturer 5 HUION > iProduct 6 PenTablet > iSerial 0 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 84 > bNumInterfaces 3 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0xa0 > (Bus Powered) > Remote Wakeup > MaxPower 100mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 3 Human Interface Device > bInterfaceSubClass 1 Boot Interface Subclass > bInterfaceProtocol 2 Mouse > iInterface 0 > HID Device Descriptor: > bLength 9 > bDescriptorType 33 > bcdHID 1.11 > bCountryCode 0 Not supported > bNumDescriptors 1 > bDescriptorType 34 Report > wDescriptorLength 179 > Report Descriptors: > ** UNAVAILABLE ** > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0010 1x 16 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.11 > bCountryCode 0 Not supported > bNumDescriptors 1 > bDescriptorType 34 Report > wDescriptorLength 92 > Report Descriptors: > ** UNAVAILABLE ** > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 EP 3 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0008 1x 8 bytes > bInterval 8 > Device Status: 0x0000 > (Bus Powered) > > > I hope that helps, ping me if you need anything else. Thank you! Can you just confirm that you have an Huion H610 and not the "H610 Pro"? I have the Pro and get the same output than you, but I thought the H610 not Pro was declared as "HUION H610". Cheers, Benjamin > > Kind regards, > Jin > |
From: Sergey 'J. B. <ji...@me...> - 2015-03-16 23:53:18
|
Hi Nick, On Mon, Mar 16, 2015 at 11:47:05PM +0200, Nikolai Kondrashov wrote: > Benjamin Tissoires and me are working on making digimend-kernel-drivers > compatible with current and future versions of the Wacom driver > (xf86-input-wacom), especially with regard to adding support for remapping > frame buttons to arbitrary key combinations. thank you guys! It would be really cool to get this to work. > This concerns Huion, Yiynova, Ugee tablets, as well as UC-Logic TWHA60 v3 > tablet. I have a Huion H610, you pinged me on IRC earlier and I tried xsetwacom with the latest master head of the kernel driver. I get the following devices: xsetwacom --list devices HUION PenTablet stylus id: 16 type: STYLUS HUION PenTablet eraser id: 17 type: ERASER HUION PenTablet pad id: 18 type: PAD HUION PenTablet stylus id: 19 type: STYLUS The only one that actually worked was id: 19, I did: xsetwacom --set 19 button 3 key + ...and then a click on the stylus key indeed produced a + I was however not able to map the keys of id's 16-18, I tried some combinations and all I got was: xsetwacom --set 16 button 1 key + Property 'Wacom Button Actions' does not exist on device. At the same time buttons >3 on device id 19 produced the following error: xsetwacom --set 19 button 4 key + Invalid offset into Wacom Button Actions property. I guess that's OK, because the stylus only has 3 buttons (the tip + 2 extra buttons), but I'd also expect the pad (id 18) to be mappable. At the same time I am not sure what id's 16 + 17 are? > We would like to ask everyone owning one of these tablets to please take some > diagnostics information from their tablets and send them in reply to this > message. [...] > Please send the output of either of these commands, plus "lsusb -v" output. ./uclogic-probe 6 3 M 48 00 55 00 49 00 4F 00 4E 00 00 00 00 00 00 00 P 50 00 65 00 6E 00 54 00 61 00 62 00 6C 00 65 00 74 00 00 00 S 64 0E 03 40 9C A8 61 03 00 FF 07 A0 0F 08 00 S 65 04 03 20 A0 S 6E 04 03 00 30 S 79 14 03 48 00 41 00 36 00 30 00 00 00 00 00 00 00 00 00 00 00 S 7A 08 03 01 08 00 00 00 00 S 7B 0C 03 48 00 4B 00 20 00 4F 00 6E 00 Part of the lsusb -v output: Bus 006 Device 003: ID 256c:006e Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x256c idProduct 0x006e bcdDevice 0.00 iManufacturer 5 HUION iProduct 6 PenTablet iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 84 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.11 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 179 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 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.11 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 92 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 8 Device Status: 0x0000 (Bus Powered) I hope that helps, ping me if you need anything else. Thank you! Kind regards, Jin |
From: Nikolai K. <sp...@gm...> - 2015-03-16 21:47:12
|
Dear users of digimend-kernel-drivers, I'm writing to the DIGImend-users list and addressing a lot of people directly with a "blind" copy. Benjamin Tissoires and me are working on making digimend-kernel-drivers compatible with current and future versions of the Wacom driver (xf86-input-wacom), especially with regard to adding support for remapping frame buttons to arbitrary key combinations. This concerns Huion, Yiynova, Ugee tablets, as well as UC-Logic TWHA60 v3 tablet. We would like to ask everyone owning one of these tablets to please take some diagnostics information from their tablets and send them in reply to this message. To do that please download, build or install the latest version of uclogic-tools (previously huion-tools): https://github.com/DIGImend/uclogic-tools/releases/tag/v4 Find the bus number and device address of your tablet in "lsusb" output: $ lsusb Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 04f2:b2ea Chicony Electronics Co., Ltd Integrated Camera [ThinkPad] Bus 001 Device 003: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] Bus 001 Device 008: ID 256c:006e Here, the last line is a Huion tablet. It is on bus 1, with device address 8. If you can't spot your tablet, try unplugging it, running "lsusb", plugging it back, running "lsusb" again and finding the new line. Execute uclogic-probe, supplying it with the bus number and device address you found. For the lsusb output above, and if you installed uclogic-tools, it will look like this: $ sudo uclogic-probe 1 8 If you just built it without installing, run from the build tree, like this: $ sudo ./uclogic-probe 1 8 Please send the output of either of these commands, plus "lsusb -v" output. More information on uclogic-tools building, installation and usage is available in its README.md: https://github.com/DIGImend/uclogic-tools/blob/master/README.md Thank you. Sincerely, Nick |
From: Nikolai K. <sp...@gm...> - 2015-03-11 15:00:15
|
On 03/05/2015 11:43 PM, Ulrich Lauther wrote: > My HUION graphics tablet H610PRO comes with a couple of pen tips, > obviously because they wear out. > Just out of curiosity: does anybody know what the physical effect > and cause for any wearout is? AFAIK, the nibs (pen tips) get ground down on the tablet surface over time. You can find some articles/videos on the web if you search for "worn out wacom pen nib/tip". Nick |
From: Ulrich L. <ulr...@t-...> - 2015-03-05 21:43:24
|
My HUION graphics tablet H610PRO comes with a couple of pen tips, obviously because they wear out. Just out of curiosity: does anybody know what the physical effect and cause for any wearout is? ulrich |
From: Nikolai K. <sp...@gm...> - 2015-03-04 17:14:38
|
On 03/04/2015 06:57 PM, Ulrich Lauther wrote: > On Wed, Mar 04, 2015 at 04:37:45PM +0200, Nikolai Kondrashov wrote: >> On 03/04/2015 04:30 PM, Ulrich Lauther wrote: >>> On Wed, Mar 04, 2015 at 02:05:37PM +0200, Nikolai Kondrashov wrote: >>>>> Maybe some h-file missing? >>>> >>>> This is two of the newly-used usage macros missing from older kernels, as >>>> Christopher noticed. Should be fixed now. Please redownload and try again. >>>> >>> Thanks a lot! Now everything seems to work. >>> Do you still want me to send any test output? >> >> No, thank you. >> >>> Will I have to reinstall the driver whenever a new kernel arrives? >> >> Yes, unfortunately. I need to get around to DKMS support implementation. >> > I found that the tablet stops to work when the computer is suspended and resumed. > One way to get it to work, is to unplug / plug the tablet > or to do > rmmod hid_uclogic; modprobe hid_uclogic > > This, of course can be automated by a script in pm-utils/sleep.d. > But could the driver itself take care of this? Hmm, this is interesting. I'll need to reproduce this. Do you get anything in "dmesg" output, or /var/log/syslog? Nick |
From: Ulrich L. <ulr...@t-...> - 2015-03-04 16:57:23
|
On Wed, Mar 04, 2015 at 04:37:45PM +0200, Nikolai Kondrashov wrote: > On 03/04/2015 04:30 PM, Ulrich Lauther wrote: > >On Wed, Mar 04, 2015 at 02:05:37PM +0200, Nikolai Kondrashov wrote: > >>>Maybe some h-file missing? > >> > >>This is two of the newly-used usage macros missing from older kernels, as > >>Christopher noticed. Should be fixed now. Please redownload and try again. > >> > >Thanks a lot! Now everything seems to work. > >Do you still want me to send any test output? > > No, thank you. > > >Will I have to reinstall the driver whenever a new kernel arrives? > > Yes, unfortunately. I need to get around to DKMS support implementation. > I found that the tablet stops to work when the computer is suspended and resumed. One way to get it to work, is to unplug / plug the tablet or to do rmmod hid_uclogic; modprobe hid_uclogic This, of course can be automated by a script in pm-utils/sleep.d. But could the driver itself take care of this? ulrich -- -lauther |
From: Nikolai K. <sp...@gm...> - 2015-03-04 14:37:50
|
On 03/04/2015 04:30 PM, Ulrich Lauther wrote: > On Wed, Mar 04, 2015 at 02:05:37PM +0200, Nikolai Kondrashov wrote: >>> Maybe some h-file missing? >> >> This is two of the newly-used usage macros missing from older kernels, as >> Christopher noticed. Should be fixed now. Please redownload and try again. >> > Thanks a lot! Now everything seems to work. > Do you still want me to send any test output? No, thank you. > Will I have to reinstall the driver whenever a new kernel arrives? Yes, unfortunately. I need to get around to DKMS support implementation. Nick |
From: Nikolai K. <sp...@gm...> - 2015-03-04 12:05:41
|
Hi Ulrich, On 03/04/2015 03:20 AM, Ulrich Lauther wrote: > On Wed, Mar 04, 2015 at 01:22:38AM +0200, Nikolai Kondrashov wrote: >> >> Actually, wait with this. I suspect that your problem might be caused by the >> faulty driver-rebinding script (hid-rebind). Could you please try the latest >> master: >> >> https://github.com/DIGImend/digimend-kernel-drivers/archive/master.zip >> > > Compilation does not work: > > /usr/local/src/digimend-kernel-drivers-master/hid-uclogic.c: In function ‘uclogic_input_configured’: > /usr/local/src/digimend-kernel-drivers-master/hid-uclogic.c:764:7: error: ‘HID_CP_CONSUMER_CONTROL’ undeclared (first use in > this function) > /usr/local/src/digimend-kernel-drivers-master/hid-uclogic.c:764:7: note: each undeclared identifier is reported only once for > each function it appears in > /usr/local/src/digimend-kernel-drivers-master/hid-uclogic.c:767:7: error: ‘HID_GD_SYSTEM_CONTROL’ undeclared (first use in this > function) > make[2]: *** [/usr/local/src/digimend-kernel-drivers-master/hid-uclogic.o] Error 1 > make[1]: *** [_module_/usr/local/src/digimend-kernel-drivers-master] Error 2 > make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-46-generic' > make: *** [modules] Error 2 > > I deleted the whole digimend-kernel-drivers-master directory and then unpacked the zip-file, to have a clean start. > Then "make" in the newly created directory. > > Maybe some h-file missing? This is two of the newly-used usage macros missing from older kernels, as Christopher noticed. Should be fixed now. Please redownload and try again. 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 |
From: Christopher B. <chr...@gm...> - 2015-03-04 04:34:39
|
On Tue, 3 Mar 2015 20:40:13 -0300 Mozart Couto <moz...@gm...> wrote: >Hi, Nick, > >Today, I installed Ubuntu Mate and when I tried to install the driver >v5 appeared huion these mansagem the terminal immediately after the >command "make". How can I solve this? >*The text in bold italics was translated for me because it's in >Portuguese on my terminal* > > >make -C /lib/modules/3.13.0-46-generic/build >SUBDIRS=/home/mozart/digimend-kernel-drivers-master modules >make[1]: Entrando no diretório *(Entering directory)* >`/usr/src/linux-headers-3.13.0-46-generic' >/usr/src/linux-headers-3.13.0-46-generic/arch/x86/Makefile:98: stack >protector enabled but no compiler support >/usr/src/linux-headers-3.13.0-46-generic/arch/x86/Makefile:113: >CONFIG_X86_X32 enabled but no binutils support >make[1]: gcc: Comando não encontrado* ( Command not found)* > CC [M] /home/mozart/digimend-kernel-drivers-master/hid-kye.o >/bin/sh: 1: gcc: not found >make[2]: ** [/home/mozart/digimend-kernel-drivers-master/hid-kye.o] >Erro 127 make[1]: ** >[_module_/home/mozart/digimend-kernel-drivers-master] Erro 2 make[1]: >Saindo do diretório *( Leaving directory )* >`/usr/src/linux-headers-3.13.0-46-generic' make: ** [modules] Erro 2 > >Thank U. have you installed 'build-essential' package? -- Regards, Christopher Barry Random geeky fortune: Tomorrow's computers some time next month. -- DEC |
From: Christopher B. <chr...@gm...> - 2015-03-04 04:29:07
|
On Wed, 4 Mar 2015 02:20:02 +0100 Ulrich Lauther <ulr...@t-...> wrote: >On Wed, Mar 04, 2015 at 01:22:38AM +0200, Nikolai Kondrashov wrote: >> >> Actually, wait with this. I suspect that your problem might be >> caused by the faulty driver-rebinding script (hid-rebind). Could you >> please try the latest master: >> >> https://github.com/DIGImend/digimend-kernel-drivers/archive/master.zip >> > >Compilation does not work: > >/usr/local/src/digimend-kernel-drivers-master/hid-uclogic.c: In >function >‘uclogic_input_configured’: /usr/local/src/digimend-kernel-drivers-master/hid-uclogic.c:764:7: >error: ‘HID_CP_CONSUMER_CONTROL’ undeclared (first use in > this function) >/usr/local/src/digimend-kernel-drivers-master/hid-uclogic.c:764:7: >note: each undeclared identifier is reported only once for each >function it appears >in /usr/local/src/digimend-kernel-drivers-master/hid-uclogic.c:767:7: >error: ‘HID_GD_SYSTEM_CONTROL’ undeclared (first use in this > function) >make[2]: *** >[/usr/local/src/digimend-kernel-drivers-master/hid-uclogic.o] Error 1 >make[1]: *** [_module_/usr/local/src/digimend-kernel-drivers-master] >Error 2 make[1]: Leaving directory >`/usr/src/linux-headers-3.13.0-46-generic' make: *** [modules] Error 2 > >I deleted the whole digimend-kernel-drivers-master directory and then >unpacked the zip-file, to have a clean start. Then "make" in the newly >created directory. > >Maybe some h-file missing? > > > ulrich > I added the following, copied from 3.19 hid.h: #define HID_GD_SYSTEM_CONTROL 0x00010080 #define HID_CP_CONSUMER_CONTROL 0x000c0001 to /usr/src/<kenel-header-version>/linux/hid.h and it compiles now. have not tested yet. -- Regards, Christopher Barry Random geeky fortune: IBM Pollyanna Principle: Machines should work. People should think. |
From: Christopher B. <chr...@gm...> - 2015-03-04 04:21:08
|
On Wed, 4 Mar 2015 02:20:02 +0100 Ulrich Lauther <ulr...@t-...> wrote: >On Wed, Mar 04, 2015 at 01:22:38AM +0200, Nikolai Kondrashov wrote: >> >> Actually, wait with this. I suspect that your problem might be >> caused by the faulty driver-rebinding script (hid-rebind). Could you >> please try the latest master: >> >> https://github.com/DIGImend/digimend-kernel-drivers/archive/master.zip >> > >Compilation does not work: > >/usr/local/src/digimend-kernel-drivers-master/hid-uclogic.c: In >function >‘uclogic_input_configured’: /usr/local/src/digimend-kernel-drivers-master/hid-uclogic.c:764:7: >error: ‘HID_CP_CONSUMER_CONTROL’ undeclared (first use in > this function) >/usr/local/src/digimend-kernel-drivers-master/hid-uclogic.c:764:7: >note: each undeclared identifier is reported only once for each >function it appears >in /usr/local/src/digimend-kernel-drivers-master/hid-uclogic.c:767:7: >error: ‘HID_GD_SYSTEM_CONTROL’ undeclared (first use in this > function) >make[2]: *** >[/usr/local/src/digimend-kernel-drivers-master/hid-uclogic.o] Error 1 >make[1]: *** [_module_/usr/local/src/digimend-kernel-drivers-master] >Error 2 make[1]: Leaving directory >`/usr/src/linux-headers-3.13.0-46-generic' make: *** [modules] Error 2 > >I deleted the whole digimend-kernel-drivers-master directory and then >unpacked the zip-file, to have a clean start. Then "make" in the newly >created directory. > >Maybe some h-file missing? > > > ulrich > I too get the exact same errors on fresh pull of master. linux/hid.h has probably been updated in newer kernels. I'm on 3.12, and there is no HID_GD_SYSTEM_CONTROL nor HID_CP* section in my <linux/hid.h> (not in 3.14 either) but it does appear in 3.19 source. -- Regards, Christopher Barry Random geeky fortune: How much net could a network work, if a network could net work? |
From: Ulrich L. <ulr...@t-...> - 2015-03-04 01:20:18
|
On Wed, Mar 04, 2015 at 01:22:38AM +0200, Nikolai Kondrashov wrote: > > Actually, wait with this. I suspect that your problem might be caused by the > faulty driver-rebinding script (hid-rebind). Could you please try the latest > master: > > https://github.com/DIGImend/digimend-kernel-drivers/archive/master.zip > Compilation does not work: /usr/local/src/digimend-kernel-drivers-master/hid-uclogic.c: In function ‘uclogic_input_configured’: /usr/local/src/digimend-kernel-drivers-master/hid-uclogic.c:764:7: error: ‘HID_CP_CONSUMER_CONTROL’ undeclared (first use in this function) /usr/local/src/digimend-kernel-drivers-master/hid-uclogic.c:764:7: note: each undeclared identifier is reported only once for each function it appears in /usr/local/src/digimend-kernel-drivers-master/hid-uclogic.c:767:7: error: ‘HID_GD_SYSTEM_CONTROL’ undeclared (first use in this function) make[2]: *** [/usr/local/src/digimend-kernel-drivers-master/hid-uclogic.o] Error 1 make[1]: *** [_module_/usr/local/src/digimend-kernel-drivers-master] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-46-generic' make: *** [modules] Error 2 I deleted the whole digimend-kernel-drivers-master directory and then unpacked the zip-file, to have a clean start. Then "make" in the newly created directory. Maybe some h-file missing? ulrich |
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: Mozart C. <moz...@gm...> - 2015-03-03 23:40:19
|
Hi, Nick, Today, I installed Ubuntu Mate and when I tried to install the driver v5 appeared huion these mansagem the terminal immediately after the command "make". How can I solve this? *The text in bold italics was translated for me because it's in Portuguese on my terminal* make -C /lib/modules/3.13.0-46-generic/build SUBDIRS=/home/mozart/digimend-kernel-drivers-master modules make[1]: Entrando no diretório *(Entering directory)* `/usr/src/linux-headers-3.13.0-46-generic' /usr/src/linux-headers-3.13.0-46-generic/arch/x86/Makefile:98: stack protector enabled but no compiler support /usr/src/linux-headers-3.13.0-46-generic/arch/x86/Makefile:113: CONFIG_X86_X32 enabled but no binutils support make[1]: gcc: Comando não encontrado* ( Command not found)* CC [M] /home/mozart/digimend-kernel-drivers-master/hid-kye.o /bin/sh: 1: gcc: not found make[2]: ** [/home/mozart/digimend-kernel-drivers-master/hid-kye.o] Erro 127 make[1]: ** [_module_/home/mozart/digimend-kernel-drivers-master] Erro 2 make[1]: Saindo do diretório *( Leaving directory )* `/usr/src/linux-headers-3.13.0-46-generic' make: ** [modules] Erro 2 Thank U. -- Mozart Couto www.mozartcouto.com.br http://blogdodesenhador.blogspot.com <http://mozartcoutoimagens.blogspot.com> |
From: Nikolai K. <sp...@gm...> - 2015-03-03 23:22:44
|
On 03/03/2015 08:26 PM, Nikolai Kondrashov wrote: > On 03/02/2015 12:21 AM, Ulrich Lauther wrote: >> On Sun, Mar 01, 2015 at 08:43:55PM +0200, Nikolai Kondrashov wrote: >> Sorry for sending so many data, but I am not sure what is relevant and what not. > > Thanks Ulrich, you sent the right amount, as I needed :) > > Now, I see that the out-of-tree driver is not being used, but the stock one is > being used instead. > > We'll need to figure out why. > > Could you please send the contents of /var/log/syslog after plugging the > tablet in? After that, please try to reinstall the driver and send whatever > output you get on the terminal during that. Actually, wait with this. I suspect that your problem might be caused by the faulty driver-rebinding script (hid-rebind). Could you please try the latest master: https://github.com/DIGImend/digimend-kernel-drivers/archive/master.zip Thank you. 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: 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 18:26:07
|
On 03/02/2015 12:21 AM, Ulrich Lauther wrote: > On Sun, Mar 01, 2015 at 08:43:55PM +0200, Nikolai Kondrashov wrote: > Sorry for sending so many data, but I am not sure what is relevant and what not. Thanks Ulrich, you sent the right amount, as I needed :) Now, I see that the out-of-tree driver is not being used, but the stock one is being used instead. We'll need to figure out why. Could you please send the contents of /var/log/syslog after plugging the tablet in? After that, please try to reinstall the driver and send whatever output you get on the terminal during that. Thank you. Nick |
From: Nikolai K. <sp...@gm...> - 2015-03-02 10:39:28
|
Hi Christopher, On 03/01/2015 11:47 PM, Christopher Barry wrote: > Greets, > > I'm running Debian Jessie(SID), but with the > Linux 3.12-1-amd64 #1 SMP Debian 3.12.9-1 (2014-02-01) x86_64 kernel > (the latest kernel 3.14 has issues with randomly shutting off my DP > monitor that only a reboot fixes). > > I'm using a Huion 610, and I'd like to get all the buttons to work if > possible. I'll be using it in Blender 2.71. > > Thanks a lot for all your work on this! You're welcome! I wouldn't recommend using anything but the latest release [1] at the moment. The work on buttons is ongoing. We should have something for testing in 2-4 weeks. We have an outdated experimental branch, but the final code is going to work differently, so we're not going to help you with it. Nick [1] https://github.com/DIGImend/digimend-kernel-drivers/releases/tag/v5 |