Re: [DIGImend-users] DIGImend: Need frame button diagnostics

[Sergey J. B. <ji...@me...>]

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