grease pencil and krita input not working

[antonvdh]

Hello Adion,

Hope you can help me out I have no pressure input for blender grease pencil also thicker line is not working.

[antonvdh]

Sorry I see what the problem is I have in no pencil pressure sensitivity under Linux. Also Gimp is not working with pressure sensitivity. openSUSE 13.2 KDE 3.5

[aidyw]

Hmmm, I only use Ubuntu and I have no such issues. There is not much I can say apart from are you mapping the outputs from the driver onto the correct controls within the software. I believe Gimp allows you to define these mappings. Aidan

On 8 March 2016 at 08:40, Anton notifications@github.com wrote:

Sorry I see what the problem is I have in no pencil pressure sensitivity under Linux. Also Gimp is not working with pressure sensitivity. openSUSE 13.2 KDE 3.5

— Reply to this email directly or view it on GitHub https://github.com/aidyw/bosto-2g-linux-kernel-module/issues/5#issuecomment-193651158 .

[aidyw]

Check in Gimp Edit>Input Devices.

Just a thought, but for me Ubuntu 15.10 kernel 4.2.0-30. All works just fine. Aidan

On 8 March 2016 at 08:40, Anton notifications@github.com wrote:

Sorry I see what the problem is I have in no pencil pressure sensitivity under Linux. Also Gimp is not working with pressure sensitivity. openSUSE 13.2 KDE 3.5

— Reply to this email directly or view it on GitHub https://github.com/aidyw/bosto-2g-linux-kernel-module/issues/5#issuecomment-193651158 .

[antonvdh]

Now I have no input at all.

[antonvdh]

Sorry I cannot switch that easy to Ubuntu. Should it work out of the box with Ubuntu 15.10 kernel 4.2.0-30

[antonvdh]

Hello for GIMP I got the pencil drawing back to work but I can only draw when I disable all options except Core Pointer which I cannot disable. Pressure sensitivity is not working.

[aidyw]

Anton, You do have debug capabilities available in the driver. If you read the Git page it explains how you can get detailed debugging from the driver. In the case of pressure sensitivity you will see this operating by looking through the code and turning on debug output for the variables you wish to monitor. If pressure sensitivity is not reported by your hardware or perhaps the driver this will be evident at the driver level. On the other hand if you discover that the driver is correctly reporting the pressure to the kernel, then as the kernel to driver interface is a well defined interface and has not changed AFAIK, then you can concentrate on your X11 configuration or the applications themselves.

From the code below (master branch) you can see pressure is reported from the data[7[ and data[6] bytes.

// Set 2048 Level pressure sensitivity.         

p = (data[7] >> 6) | (data[6] << 2); p = le16_to_cpup((__le16 *)&p);

These can be seen by debugging the following line from the start of the hanwang_parse_packet procedure.

dev_dbg(&dev->dev, "Bosto packet: [B0:-:B8] %02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x\n”,

Regards Aidan

On 9 Mar 2016, at 18:15, Anton notifications@github.com wrote:

Hello for GIMP I got the pencil drawing back to work but I can only draw when I disable all options except Core Pointer which I cannot disable. Pressure sensitivity is not working.

— Reply to this email directly or view it on GitHub https://github.com/aidyw/bosto-2g-linux-kernel-module/issues/5#issuecomment-194405833.

[antonvdh]

Sorry I do not understand how to see I got pencil pressure. Woukld be strange because in Gimp I changed screen to disable for the UNIPEN Tablet GIMP Input devices. I have tested it also in Ubuntu 15.10 which gave me again flickering lines so I am back to openSUSE because I don want to break my Bosto Kingtee 22U. I was hoping I could use the tablet with greasepencil blender which would save me a lot drawing animatics.

I have read Diagnostics I can see this in the control file: home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:297 [bosto_2g]hanwang_parsepacket = "Error packet. Packet data[0]: %02x " /home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:291 [bosto_2g]hanwang_parsepacket = "Tablet Event. Packet data[0]: %02x\012" /home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:248 [bosto_2g]hanwang_parsepacket = "PEN TOUCH: ID:Tool %x:%x\012" /home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:206 [bosto_2g]hanwang_parsepacket = "Bosto packet:Float [B0:-:B8] %02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x\012" /home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:204 [bosto_2g]hanwang_parsepacket = "PEN FLOAT: ID:Tool %x:%x\012" /home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:197 [bosto_2g]hanwang_parsepacket = "Unknown tablet tool %02x " /home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:192 [bosto_2g]hanwang_parsepacket = "TOOL IN ERASER:Exit ID:Tool %x:%x\012" /home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:183 [bosto_2g]hanwang_parsepacket = "TOOL IN:Exit ID:Tool %x:%x\012" /home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:173 [bosto_2g]hanwang_parsepacket = "Bosto packet:TOOL IN [B0:-:B8] %02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x\012" /home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:171 [bosto_2g]hanwang_parsepacket = "TOOL IN: ID:Tool %x:%x\012" /home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:166 [bosto_2g]hanwang_parsepacket = "Bosto packet:TOOL OUT [B0:-:B8] %02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x\012" /home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:164 [bosto_2g]hanwang_parsepacket = "TOOL OUT. PEN ID:Tool %x:%x\012" /home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:148 [bosto_2g]hanwang_parsepacket = "Bosto packet: [B0:-:B8] %02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x\012"

[aidyw]

You have printed the control file. The control file flag 'p' tells the kernel debugger what it should send to syslog. So tail -f /var/log/syslog to see a realtime output.

However your control file has no flags set against any of the debug options. I have updated the readme on github to reflect a couple of unclear statements. (Instead of ....=_"Bosto packet... you need to see ...=p"Bosto packet....). With correct debug flags set move to syslog.

You see below a snip from my syslog output. The 2 bytes B6 & B7 starting in this case d2:60 and increasing as I put pressure on the pen. ie. running down the output. These 2 bytes are manipulated to extract 2048 levels from the 32bits and reported to the input subsystem as an ABS_PRESSURE event.

Mar 10 19:07:52 laplace kernel: [ 135.836576] usb 2-3: Bosto packet: [B0:-:B8] 02:e0:19:db:1a:d6:d2:60:40:00 Mar 10 19:07:52 laplace kernel: [ 135.840578] usb 2-3: Bosto packet: [B0:-:B8] 02:e1:19:db:1a:d7:d2:60:40:00 Mar 10 19:07:52 laplace kernel: [ 135.844582] usb 2-3: Bosto packet: [B0:-:B8] 02:e1:19:db:1a:d7:d2:a0:40:00 Mar 10 19:07:52 laplace kernel: [ 135.846580] usb 2-3: Bosto packet: [B0:-:B8] 02:e0:19:db:1a:d7:d2:e0:40:00 Mar 10 19:07:52 laplace kernel: [ 135.850579] usb 2-3: Bosto packet: [B0:-:B8] 02:e0:19:db:1a:d7:d3:20:40:00 Mar 10 19:07:52 laplace kernel: [ 135.852582] usb 2-3: Bosto packet: [B0:-:B8] 02:e0:19:db:1a:d7:d3:60:40:00 Mar 10 19:07:52 laplace kernel: [ 135.856581] usb 2-3: Bosto packet: [B0:-:B8] 02:e0:19:db:1a:d7:d3:a0:40:00 Mar 10 19:07:52 laplace kernel: [ 135.860582] usb 2-3: Bosto packet: [B0:-:B8] 02:e0:19:db:1a:d7:d3:e0:40:00 Mar 10 19:07:52 laplace kernel: [ 135.864259] usb 2-3: Bosto packet: [B0:-:B8] 02:e0:19:db:1a:d7:d4:20:40:00 Mar 10 19:07:52 laplace kernel: [ 135.866582] usb 2-3: Bosto packet: [B0:-:B8] 02:e0:19:db:1a:d7:d4:60:40:00 Mar 10 19:07:52 laplace kernel: [ 135.868582] usb 2-3: Bosto packet: [B0:-:B8] 02:e0:19:db:1a:d7:d4:a0:40:00 Mar 10 19:07:52 laplace kernel: [ 135.872582] usb 2-3: Bosto packet: [B0:-:B8] 02:e1:19:db:1a:d7:d4:e0:40:00 Mar 10 19:07:52 laplace kernel: [ 135.876583] usb 2-3: Bosto packet: [B0:-:B8] 02:e1:19:db:1a:d7:d5:20:40:00 Mar 10 19:07:52 laplace kernel: [ 135.878583] usb 2-3: Bosto packet: [B0:-:B8] 02:e1:19:db:1a:d7:d5:60:40:00 Mar 10 19:07:52 laplace kernel: [ 135.882583] usb 2-3: Bosto packet: [B0:-:B8] 02:e0:19:db:1a:d7:d5:e0:40:00 Mar 10 19:07:52 laplace kernel: [ 135.884583] usb 2-3: Bosto packet: [B0:-:B8] 02:e0:19:db:1a:d7:d6:20:40:00 Mar 10 19:07:52 laplace kernel: [ 135.888583] usb 2-3: Bosto packet: [B0:-:B8] 02:e1:19:db:1a:d7:d6:60:40:00 Mar 10 19:07:52 laplace kernel: [ 135.892583] usb 2-3: Bosto packet: [B0:-:B8] 02:e1:19:db:1a:d7:d6:a0:40:00 Mar 10 19:07:52 laplace kernel: [ 135.894579] usb 2-3: Bosto packet: [B0:-:B8] 02:e1:19:db:1a:d7:d6:e0:40:00 Mar 10 19:07:52 laplace kernel: [ 135.898579] usb 2-3: Bosto packet: [B0:-:B8] 02:e1:19:dc:1a:d7:d7:20:40:00 Mar 10 19:07:52 laplace kernel: [ 135.900581] usb 2-3: Bosto packet: [B0:-:B8] 02:e1:19:dc:1a:d7:d7:60:40:00 Mar 10 19:07:52 laplace kernel: [ 135.904582] usb 2-3: Bosto packet: [B0:-:B8] 02:e1:19:dc:1a:d7:d7:a0:40:00 Mar 10 19:07:52 laplace kernel: [ 135.908585] usb 2-3: Bosto packet: [B0:-:B8] 02:e0:19:dc:1a:d7:d8:20:40:00

So perhaps try again. See what you have. Regards Aidan

On 10 March 2016 at 16:42, Anton notifications@github.com wrote:

Sorry I do not understand how to see I got pencil pressure. Woukld be strange becaus eI had to change screen to disable for the UNIPEN Tablet GIMP Input devices. Also I find it strange KRITA is not working. I have tested it also in Ubuntu 15.10 which gave me again flickering lines so I am back to openSUSE because I don want to break my Bosto Kingtee 22U. I was hoping I could use the tablet with greasepencil blender which would save me a lot drawing animatics.

I have read Diagnostics I can see this in the control file: home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:297 [bosto_2g]hanwang_parsepacket = "Error packet. Packet data[0]: %02x " /home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:291

/home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:248 [bosto_2g]hanwang_parsepacket = "PEN TOUCH: ID:Tool %x:%x\012" /home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:206 [bosto_2g]hanwang_parsepacket = "Bosto packet:Float [B0:-:B8] %02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x\012" /home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:204 [bosto_2g]hanwang_parsepacket = "PEN FLOAT: ID:Tool %x:%x\012" /home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:197 [bosto_2g]hanwang_parsepacket = "Unknown tablet tool %02x " /home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:192 [bosto_2g]hanwang_parsepacket = "TOOL IN ERASER:Exit ID:Tool %x:%x\012" /home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:183 [bosto_2g]hanwang_parsepacket = "TOOL IN:Exit ID:Tool %x:%x\012" /home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:173 [bosto_2g]hanwang_parsepacket = "Bosto packet:TOOL IN [B0:-:B8] %02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x\012" /home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:171 [bosto_2g]hanwang_parsepacket = "TOOL IN: ID:Tool %x:%x\012" /home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:166 [bosto_2g]hanwang_parsepacket = "Bosto packet:TOOL OUT [B0:-:B8] %02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x\012" /home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:164 [bosto_2g]hanwang_parsepacket = "TOOL OUT. PEN ID:Tool %x:%x\012" /home/anton/bosto-2g-linux-kernel-module/bosto_2g.c:148 [bosto_2g]hanwang_parsepacket = "Bosto packet: [B0:-:B8] %02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x:%02x\012"

— Reply to this email directly or view it on GitHub https://github.com/aidyw/bosto-2g-linux-kernel-module/issues/5#issuecomment-194912193 .

[antonvdh]

OK I have installed Ubuntu 15.10 on my ASUS N53S laptop Bosto Kingtee 22 U Pencil did not work out of the box. Installed the bosto-2g-linux-kernel-module. anton@N53SN:~/bosto-2g-linux-kernel-module$ sudo make [sudo] password for anton: gcc detach_usbhid.c -I/usr/include/libusb-1.0 -L/lib/-linux-gnu/libusb-1.0.so.0 -lusb-1.0 -o detach_usbhid make -C /lib/modules/4.2.0-16-generic/build M= modules make[1]: Entering directory '/usr/src/linux-headers-4.2.0-16-generic' HOSTCC scripts/basic/fixdep HOSTCC scripts/basic/bin2c HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/conf scripts/kconfig/conf --silentoldconfig Kconfig make[2]: *** No rule to make target 'arch/x86/entry/syscalls/syscall_32.tbl', needed by 'arch/x86/entry/syscalls/../../include/generated/asm/syscalls_32.h'. Stop. arch/x86/Makefile:184: recipe for target 'archheaders' failed make[1]: *** [archheaders] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-4.2.0-16-generic' Makefile:10: recipe for target 'all' failed make: *** [all] Error 2 anton@N53SN:~/bosto-2g-linux-kernel-module$ insmod ./bosto_2g.ko insmod: ERROR: could not insert module ./bosto_2g.ko: Operation not permitted

Also tried to set the right input tablet. anton@N53SN:~/bosto_14wa-master/scripts$ ./inputtransform ./inputtransform:40:ininitialize': Cannot parse 'VGA-1-2 connected 1024x768+3286+0 0mm x 0mm' as Display header (RuntimeError) from ./inputtransform:89:in new' from ./inputtransform:89:inblock in parse' from ./inputtransform:89:in each' from ./inputtransform:89:inmap' from ./inputtransform:89:in parse' from ./inputtransform:67:ininitialize' from ./inputtransform:119:in new' from ./inputtransform:119:ininitialize' from ./inputtransform:197:in new' from ./inputtransform:197:in

' ` I guess I have no luck.

[lesliev]

The pen will not work out of the box, you do need the driver.

These are the instructions in the readme:

sudo apt-get install libusb-1.0.0-dev build-essential linux-headers-generic git
cd ~
git clone https://github.com/aidyw/bosto-2g-linux-kernel-module.git
cd bosto-2g-linux-kernel-module
make clean && make
sudo make install

You should not run sudo make, you only need sudo for the last step. Though now that you have done that, you will have written some files as root user which a normal user cannot overwrite. So I recommend removing the whole bosto-2g-linux-kernel-module directory using the root user and starting again, following the above instructions precisely.

If you see anything that says "warning" during the make clean && make step, that's fine, but if you see something saying "error", that will stop the compilation and you need to resolve it before you can try running that step again.

The error mentioned above seems to be related to a missing file called "arch/x86/entry/syscalls/syscall_32.tbl". This may have to do with kernel version mismatch or perhaps you didn't install the linux headers.

Did you get any errors when you ran sudo apt-get install libusb-1.0.0-dev build-essential linux-headers-generic git ? If you run it again, does it say that everything is installed?

Also, what is the output of uname -a ?

[antonvdh]

anton@N53SN:~/bosto-2g-linux-kernel-module$ uname -a Linux N53SN 4.2.0-30-generic #36-Ubuntu SMP Fri Feb 26 00:58:07 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux I have followed the install as described without problems until target clean failed and gave me Error 1 anton@N53SN:~$ sudo apt-get install libusb-1.0.0-dev build-essential linux-headers-generic git [sudo] password for anton: Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'libusb-1.0-0-dev' for regex 'libusb-1.0.0-dev' build-essential is already the newest version. libusb-1.0-0-dev is already the newest version. git is already the newest version. linux-headers-generic is already the newest version. The following packages were automatically installed and are no longer required: libandroid-properties1 liboxideqtcore0 liboxideqtquick0 libqt5positioning5 qml-module-qt-labs-folderlistmodel qml-module-qt-labs-settings qml-module-qtwebkit qml-module-ubuntu-onlineaccounts qtdeclarative5-accounts-plugin Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

anton@N53SN:~$ git clone https://github.com/aidyw/bosto-2g-linux-kernel-module.git Cloning into 'bosto-2g-linux-kernel-module'... remote: Counting objects: 180, done. remote: Total 180 (delta 0), reused 0 (delta 0), pack-reused 180 Receiving objects: 100% (180/180), 70.82 KiB | 0 bytes/s, done. Resolving deltas: 100% (105/105), done. Checking connectivity... done. anton@N53SN:~$ cd bosto-2g-linux-kernel-module

anton@N53SN:~/bosto-2g-linux-kernel-module$ make clean && make make -C /lib/modules/4.2.0-30-generic/build M=/home/anton/bosto-2g-linux-kernel-module clean make[1]: Entering directory '/usr/src/linux-headers-4.2.0-30-generic' make[1]: Leaving directory '/usr/src/linux-headers-4.2.0-30-generic' rm detach_usbhid rm: cannot remove ‘detach_usbhid’: No such file or directory Makefile:14: recipe for target 'clean' failed make: *** [clean] Error 1 anton@N53SN:~/bosto-2g-linux-kernel-module$ make gcc detach_usbhid.c -I/usr/include/libusb-1.0 -L/lib/-linux-gnu/libusb-1.0.so.0 -lusb-1.0 -o detach_usbhid make -C /lib/modules/4.2.0-30-generic/build M=/home/anton/bosto-2g-linux-kernel-module modules make[1]: Entering directory '/usr/src/linux-headers-4.2.0-30-generic' CC [M] /home/anton/bosto-2g-linux-kernel-module/bosto_2g.o Building modules, stage 2. MODPOST 1 modules CC /home/anton/bosto-2g-linux-kernel-module/bosto_2g.mod.o LD [M] /home/anton/bosto-2g-linux-kernel-module/bosto_2g.ko make[1]: Leaving directory '/usr/src/linux-headers-4.2.0-30-generic' anton@N53SN:~/bosto-2g-linux-kernel-module$ sudo make install [sudo] password for anton: cp ./bosto_2g.ko /lib/modules/4.2.0-30-generic echo bosto_2g >> /etc/modules depmod cp ./load_bosto_2g.sh /usr/local/bin cp ./detach_usbhid /usr/local/bin cp ./load_bosto_2g.rules /etc/udev/rules.d /sbin/udevadm control --reload modprobe bosto_2g anton@N53SN:~/bosto-2g-linux-kernel-module$ insmod ./bosto_2g.ko insmod: ERROR: could not insert module ./bosto_2g.ko: Operation not permitted anton@N53SN:~/bosto-2g-linux-kernel-module$ lsmod | grep bosto_2g bosto_2g 16384 0

[lesliev]

The make clean is failing. Instead of make clean && make try just doing make and post the output.

[antonvdh]

Sorry I just added make and sudo make install .

[antonvdh]

I have connected the Bosto Kingtee Tablet and disabled the laptop screen so I have now only one screen to avoid conflicts. I can see the pencil cursor but it is only moving up and down at the right -side from the Bosto Kingtee 22U. Cannot use it.

[antonvdh]

Should I use Ubuntu 14.04 ? I cannot use the pencil anymore. Tested with Gimp, Krita, Mypaint and Blender.

[antonvdh]

From the Bosto forum : kernel versions starting with 4.1 broke the compatibility. Is there any change the bosto-2g-linux-kernel-module will be upgraded ?

[aidyw]

Sorry Anton, bit short of time. Actually I never saw any follow up from you on the debug outputs, so it was not useful for me to further comment. Aidan

On 16 Mar 2016, at 19:39, Anton notifications@github.com wrote:

From the Bosto forum : kernel versions starting with 4.1 broke the compatibility. The advise was use KXStudio.

— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/aidyw/bosto-2g-linux-kernel-module/issues/5#issuecomment-197479394

[lesliev]

On 17 March 2016 at 07:39, Anton notifications@github.com wrote:

From the Bosto forum : kernel versions starting with 4.1 broke the compatibility. The advise was use KXStudio.

Oh dear, I'll have to do some testing on Linux 4.

[antonvdh]

Sorry I thought I have given all the output you asked as far as I know.

Greetings Anton Op 16 mrt. 2016 21:32 schreef "Aidan Walton" notifications@github.com:

Sorry Anton, bit short of time. Actually I never saw any follow up from you on the debug outputs, so it was not useful for me to further comment. Aidan

On 16 Mar 2016, at 19:39, Anton notifications@github.com wrote:

From the Bosto forum : kernel versions starting with 4.1 broke the compatibility. The advise was use KXStudio.

— You are receiving this because you commented. Reply to this email directly or view it on GitHub < https://github.com/aidyw/bosto-2g-linux-kernel-module/issues/5#issuecomment-197479394

— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/aidyw/bosto-2g-linux-kernel-module/issues/5#issuecomment-197535760

[antonvdh]

Hello Aidon

Hope you can find some time. I have some info about the bosto kingtee 22U mini digitizer The 14WA, 22HD and 22HDX seem to use digitizers based on Hanvon technology . None of these drivers work for the 22U mini. The 22U mini seems to use a digitizer based on Waltop technology.

Greetings Anton Op 16 mrt. 2016 21:35 schreef "anton vandehaterd" antonvdh@gmail.com:

Sorry I thought I have given all the output you asked as far as I know.

Greetings Anton Op 16 mrt. 2016 21:32 schreef "Aidan Walton" notifications@github.com:

Sorry Anton, bit short of time. Actually I never saw any follow up from you on the debug outputs, so it was not useful for me to further comment. Aidan

On 16 Mar 2016, at 19:39, Anton notifications@github.com wrote:

From the Bosto forum : kernel versions starting with 4.1 broke the compatibility. The advise was use KXStudio.

— You are receiving this because you commented. Reply to this email directly or view it on GitHub < https://github.com/aidyw/bosto-2g-linux-kernel-module/issues/5#issuecomment-197479394

— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/aidyw/bosto-2g-linux-kernel-module/issues/5#issuecomment-197535760

[aidyw]

Its very difficult to help in any way. Different hardware could be very different in how it presents to the system. I have no way of knowing. Aidan

On 17 Mar 2016, at 07:55, Anton notifications@github.com wrote:

Hello Aidon

Hope you can find some time. I have some info about the bosto kingtee 22U mini digitizer The 14WA, 22HD and 22HDX seem to use digitizers based on Hanvon technology . None of these drivers work for the 22U mini. The 22U mini seems to use a digitizer based on Waltop technology.

Greetings Anton Op 16 mrt. 2016 21:35 schreef "anton vandehaterd" antonvdh@gmail.com:

Sorry I thought I have given all the output you asked as far as I know.

Greetings Anton Op 16 mrt. 2016 21:32 schreef "Aidan Walton" notifications@github.com:

Sorry Anton, bit short of time. Actually I never saw any follow up from you on the debug outputs, so it was not useful for me to further comment. Aidan

On 16 Mar 2016, at 19:39, Anton notifications@github.com wrote:

From the Bosto forum : kernel versions starting with 4.1 broke the compatibility. The advise was use KXStudio.

— You are receiving this because you commented. Reply to this email directly or view it on GitHub < https://github.com/aidyw/bosto-2g-linux-kernel-module/issues/5#issuecomment-197479394

— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/aidyw/bosto-2g-linux-kernel-module/issues/5#issuecomment-197535760

— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/aidyw/bosto-2g-linux-kernel-module/issues/5#issuecomment-197732581