New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Huion Q11K not detected #76

Open
mifth opened this Issue Sep 28, 2017 · 98 comments

Comments

Projects
None yet
@mifth

mifth commented Sep 28, 2017

Hi.
I have Linux 64bit, Ubuntu 17.04.
I have compiled and installed Digimend but nothing works. (((
My Huion Q11K Inspiroy is not recognized and not seen in xinput --list. My Pen does not work at all. I even cannot move a pointer. ((
It seems this is the same issue as here #59

MJA0vEsa.txt
33S7rT7w.txt
Dy9G4pMW.txt
1SdDM2VL.txt

  • dmesg

I also tried to set my conf but it did not help:
https://pastebin.com/05E9hQQW

Please, help me if you can!
I just need to get my pen get working with 2 its buttons.

Thank you.

@spbnick

This comment has been minimized.

Member

spbnick commented Sep 29, 2017

This might be something new from Huion, even though they reuse the product ID, again. Could you please run uclogic-probe on your tablet and post its output here?

@spbnick

This comment has been minimized.

Member

spbnick commented Sep 29, 2017

Also, lsusb -v and usbhid-dump output would be useful.

@mifth

This comment has been minimized.

mifth commented Sep 29, 2017

Hi!
Thanks for the reply. Yep, it seems they bypass manufacturer name.
FR4w1nRu.txt - usbhid-dump
w34dqZe6.txt - lsusb
text2.txt - lsusb2
text.txt - uclogic

I would be happy if I could just draw and press rightclick and middleclick.

Thanks a lot!

@mifth

This comment has been minimized.

mifth commented Sep 29, 2017

https://pastebin.com/sWh9Bzhh - I also tried with decode

I have these libs installed
https://packages.ubuntu.com/search?keywords=libusb-0.1-4
selection_268

@spbnick

This comment has been minimized.

Member

spbnick commented Sep 29, 2017

Thank you.
Could you please edit your comments to have the text from pastebin embedded, and not linked, so we don't lose it?

Also, could you please build and try to use the latest uclogic-tools master? That might give us a bit more data. Thank you.

@mifth

This comment has been minimized.

mifth commented Sep 29, 2017

Ok, I did it.

text.txt - uclogic tools master

w34dqZe6.txt - lsusb

FR4w1nRu.txt - usbhid-dump

uclogic tools still does not work. May be I have a problem with libusb?
selection_270

@spbnick

This comment has been minimized.

Member

spbnick commented Sep 29, 2017

What do you mean by "does not work"?

@mifth

This comment has been minimized.

mifth commented Sep 29, 2017

It writes
"Failed to get manufacturer string descriptor: Pipe error
Failed to get product string descriptor: Pipe error"

Is it ok?

@spbnick

This comment has been minimized.

Member

spbnick commented Sep 29, 2017

Right, this shows us that the tablet is very different from what was using that VID:PID before and that more needs to be done to make it work. Now, please do full diagnostics as described at http://digimend.github.io/support/howto/trbl/diagnostics/ and post the results here, either as is or in an archive.

@mifth

This comment has been minimized.

mifth commented Sep 29, 2017

Good. Here is my test. Buttons at the tablet did not write anything into the file.
test.zip

@spbnick

This comment has been minimized.

Member

spbnick commented Sep 29, 2017

Thank you. So, this case is indeed similar to #59. Without discovering the initialization sequence which the Windows driver sends, we can make the movement, pressure, and pen buttons work. However, spatial resolution will be lower than advertised, and frame buttons will not work.

The frame wheel dump seems to contain a lot of reports from the pen. Does this tablet actually have a wheel? It seems it doesn't.

If you're willing to drive this further, then please capture and post some USB traffic on Windows while the tablet is being plugged in.

@mifth

This comment has been minimized.

mifth commented Sep 29, 2017

Thank you too!
That's good that its possible to make the pen get working.
There is no wheel at the tablet. Only buttons.
Also, there is no tilt. As far as i know.

I'm ready to go further. I have windows7 vm. Also, i have some friends with windows os.
What should i do to get the usb traffic?

@spbnick

This comment has been minimized.

Member

spbnick commented Sep 29, 2017

The VM should be enough and might even be preferred. Install Wireshark on the host, start Windows VM, install tablet drivers on it, start recording USB traffic on all interfaces in Wireshark, connect your tablet, and connect it to the VM. Wait a little, then disconnect the tablet, then stop recording. That should catch it. Save the file, compress, and post it here.

For safety, though, I would filter out the traffic from other devices before posting the capture on the web. Or at least make sure you do not have any devices connected that receive or transmit any sensitive data during the capture. Such as a network card, webcam, a microphone, or a keyboard where you type your passwords.

@mifth

This comment has been minimized.

mifth commented Sep 29, 2017

Ok, I did it. I hope I did it correctly.
test_shark.zip

@spbnick

This comment has been minimized.

Member

spbnick commented Sep 29, 2017

Thank you, this seems to be what we need. I'll try to update uclogic-tools to support your tablet, if it makes sense, or make another small tool, on the weekend. Once we have your tablet outputting full-featured reports under Linux we'll be able to make the driver work.

@mifth

This comment has been minimized.

mifth commented Sep 29, 2017

Oooooooooooo!!!!!!!! Thank you bratan!
Be the force with you!

@spbnick

This comment has been minimized.

Member

spbnick commented Oct 1, 2017

Alright, I pushed probing and decoding your tablet parameters to the latest uclogic-tools master. Please download, build, and run it on your tablet. Then (if it doesn't fail), without unplugging your tablet, collect diagnostics samples for pen coordinates, pressure, and buttons, plus frame buttons. Please post results here.

@mifth

This comment has been minimized.

mifth commented Oct 1, 2017

Hi!
Thanks for the code! I did it:

Text File.txt

@spbnick

This comment has been minimized.

Member

spbnick commented Oct 1, 2017

Yes, that's working fine. Please proceed to collecting diagnostics, after running the new uclogic-probe and without reconnecting your tablet.

@mifth

This comment has been minimized.

mifth commented Oct 1, 2017

Oh, sorry i forgot to get diagnostics. I'll do it asap when i get to the computer.

@mifth

This comment has been minimized.

mifth commented Oct 1, 2017

Hi again!
I did the new test.
test2.zip

@spbnick

This comment has been minimized.

Member

spbnick commented Oct 1, 2017

That doesn't seem to have worked, but let's check. Did you run the new uclogic-probe right before collecting these new files?

@mifth

This comment has been minimized.

mifth commented Oct 2, 2017

I used uclogic-tools from your post #76 (comment)

@mifth

This comment has been minimized.

mifth commented Oct 2, 2017

Ok, I did another test with latest master code.
test3.zip

@mifth

This comment has been minimized.

mifth commented Oct 2, 2017

I rebooted my machine and did the test again.
test4.zip

@spbnick

This comment has been minimized.

Member

spbnick commented Oct 2, 2017

Thank you. These also show the old reports. What we should be seeing in usbhid-dump output, when pen is moved, is reports starting with "08", instead of "0A". We also should be getting something when frame buttons are pressed. I'll take a closer look at the windows driver trace and try to figure out the initialization sequence. I will update uclogic-tools with it and update you. However, this is not likely to happen today, perhaps tomorrow.

@mifth

This comment has been minimized.

mifth commented Oct 2, 2017

Thank you. I'll wait for sure.

@spbnick

This comment has been minimized.

Member

spbnick commented Oct 4, 2017

Alright. I couldn't see anything more special in the Windows trace than what we already do in uclogic-probe. However, I'm not sure what exactly happens with the tablet between running uclogic-probe, and usbhid-dump. I suspect that the driver reinitializes the tablet when uclogic-probe finishes.

To check that, and to see if there is something else that could be interfering, please capture tablet USB traffic on Linux:

  1. Start the capture
  2. Plug in the tablet
  3. Run uclogic-probe
  4. Start usbhid-dump -es
  5. Do a stroke with the pen
  6. Stop usbhid-dump
  7. Stop the capture
  8. Make sure nothing sensitive got into the capture
  9. Post the capture here
@mifth

This comment has been minimized.

mifth commented Oct 4, 2017

Ok, i'll do it this evening when get back home.

@spbnick

This comment has been minimized.

Member

spbnick commented Nov 19, 2017

@Miridyan I believe you can do that through xinput settings, namely coordinate transformation matrix.

@kolrabi

This comment has been minimized.

kolrabi commented Dec 13, 2017

Can you people check out #85 and see if that makes the tablet work better "out of the box"?

@C4duceus

This comment has been minimized.

C4duceus commented Dec 28, 2017

Hey guys, I recently purchased an Inspiroy Q11K. Though I am not a programmer by any means, I'd like to contribute to this project in any way I can.

@jmarct

This comment has been minimized.

jmarct commented Mar 6, 2018

Hello.
I want to buy an Huion Q11 to use with Blender on Linux Mint 18.3 KDE. Can you confirm (or not) that it will be working.
Thank you.
Jean Marc

@konachan700

This comment has been minimized.

konachan700 commented Mar 6, 2018

@jmarct

This comment has been minimized.

jmarct commented Mar 6, 2018

Thank for the fast answer.

@jeanollion

This comment has been minimized.

jeanollion commented Apr 14, 2018

First of all thanks a lot to @konachan700 and all the digimend team for the drivers.
I have a Q11K, using the driver pointed by @konachan700 I can use the tablet & the 2 stylus button work perfectly (the stylus needs to be close to the tablet for it's buttons to work)
However I don't know how to use the tablet's button. Under Krita, if I set a shortcut for a command (e.g "undo") using of of the button, the displayed shortcut is always "ctrl+ unknow caracter", and when I press the button the command is not run. How can I use the tablet's button under Krita? Thanks in advance

@konachan700

This comment has been minimized.

konachan700 commented Apr 27, 2018

@Rabcor

This comment has been minimized.

Rabcor commented Sep 13, 2018

Hello! Driver has a conflict with hid-generic and with uclogic. You should be add tablet's vid&pid to "hid_have_special_driver" in "drivers/hid/hid-core.c" and rebiuld a kernel, or manually unbind a tablet from hid-generic every connect. 2018-04-27 8:02 GMT+03:00 Henry notifications@github.com:

I can't get @konachan700 https://github.com/konachan700 's method to work on my Solus OS distro. It had worked on Ubuntu when I tried it, but after switching, I'm not having any luck. Although the make and make install build, there's no response from my Q11k tablet. Any suggestions? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#76 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AH3hs-jnxMpWLQgYNFvqFLzEseFh11unks5tsqZlgaJpZM4PnpxL .

Can you specify how to unbind the tablet from hid-generic? It sounds like it'd be fairly simple to automate it with udev rules maybe. A lot simpler of a deal than patching the kernel at least.

As for patching the kernel, I tried to make a patch for it https://pastebin.com/kzyQBQBs (not sure if it's correctly done, can you verify?)

@spbnick

This comment has been minimized.

Member

spbnick commented Sep 13, 2018

@Rabcor

This comment has been minimized.

Rabcor commented Sep 25, 2018

@spbnick thanks that looks like something that would do the trick, 1 question though.

Will (should) that script work as is for the huion tablet in question? (E.g. if I just make that UDEV rule for that device) and the driver in question; or will I need to edit the file?

Edit: well, I never tried the hid-rebind script, but I seem to have managed to get it working right without using the script nor modifying the kernel. On kernel 4.14 (manjaro) seemingly works perfectly so far in conjunction with the xf86-wacom driver.

@LuciusTalane

This comment has been minimized.

LuciusTalane commented Nov 13, 2018

Greetings great people, I am really new at Ubuntu (this month new) I tried to follow most of the steps in the post but I'm not able to replicate the results or I get different ones when trying to identify the tablet, if you don't mind I'd love you to check my .txt about "lsusb" and "uclogic-probe" I tried @konachan700 drivers but I'm not able to install them as I get some permission errors and I'm kinda stuck, I'll proceed to post my txt file and I hope I can make it work with your help, I'm really exited about Ubuntu, but I really need my tablet for work. thanks in advance.
UclogicHuionLucius.txt

@LuciusTalane

This comment has been minimized.

LuciusTalane commented Nov 13, 2018

update: I managed to install @konachan700 drivers posted above, but the tablet is not recognized yet:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0c45:5204 Microdia
Bus 001 Device 003: ID 256c:006e
Bus 001 Device 002: ID 04d9:fa56 Holtek Semiconductor, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
It continues in blank with "lsusb"

@Rabcor

This comment has been minimized.

Rabcor commented Nov 13, 2018

It continues in blank with "lsusb"

Sure... but did you try actually using it? (It's also quite important that you create that xorg config file suggested above, and install the xf86-input-wacom driver too)

@LuciusTalane

This comment has been minimized.

LuciusTalane commented Nov 13, 2018

It continues in blank with "lsusb"

Sure... but did you try actually using it? (It's also quite important that you create that xorg config file suggested above, and install the xf86-input-wacom driver too)

Sure I tried, no response at all, I installed the xf86 wacom driver, and I tried to follow the steps shown above, but it seems I'm doing something wrong.

@Rabcor

This comment has been minimized.

Rabcor commented Nov 13, 2018

It continues in blank with "lsusb"

Sure... but did you try actually using it? (It's also quite important that you create that xorg config file suggested above, and install the xf86-input-wacom driver too)

Sure I tried, no response at all, I installed the xf86 wacom driver, and I tried to follow the steps shown above, but it seems I'm doing something wrong.

Hmm, allright, try doing what I did.

0: install xf86-input-wacom and set the xorg conf thing
1: install digimend (may need to be installed from git, you may need a more recent version of it than you currently have)
2: install konachan's driver (make sure you use make & make install)
3: reboot & test
4: if it doesn't work you may need to patch the kernel (read the readme on konachan's drivers for details) or use the script @spbnick linked to earlier (the one which I sadly couldn't figure out how to use)
5: if it still doesn't work after that (unlikely) you might need to use another distro (try manjaro, it's a much better distro for installing packages that aren't officially supported thanks to the access to AUR and stuff, also better optimized kernel and whatnot)

You're doing pretty good for someone who just started using linux, it's only a pain in the ass when you first set it up, after you finally configure it and get everything working it'll run like a charm ;)

@LuciusTalane

This comment has been minimized.

LuciusTalane commented Nov 13, 2018

It continues in blank with "lsusb"

Sure... but did you try actually using it? (It's also quite important that you create that xorg config file suggested above, and install the xf86-input-wacom driver too)

Sure I tried, no response at all, I installed the xf86 wacom driver, and I tried to follow the steps shown above, but it seems I'm doing something wrong.

Hmm, allright, try doing what I did.

0: install xf86-input-wacom and set the xorg conf thing
1: install digimend (may need to be installed from git, you may need a more recent version of it than you currently have)
2: install konachan's driver (make sure you use make & make install)
3: reboot & test
4: if it doesn't work you may need to patch the kernel (read the readme on konachan's drivers for details) or use the script @spbnick linked to earlier (the one which I sadly couldn't figure out how to use)
5: if it still doesn't work after that (unlikely) you might need to use another distro (try manjaro, it's a much better distro for installing packages that aren't officially supported thanks to the access to AUR and stuff, also better optimized kernel and whatnot)

You're doing pretty good for someone who just started using linux, it's only a pain in the ass when you first set it up, after you finally configure it and get everything working it'll run like a charm ;)

Long read ahead:
Thank you for the words I appreciate it, quick update about my current state, I will make a summary in form of a list for any interested:
The tablet works now - but only in wired mode (I might missed something).

I haven't touched anything yet but I was using the front usb ports, I tried the back ones and worked in my current state.

Tried on Krita and Gimp, the pressure is working good so far.

One issue so far that catches my attention is when I take away the pen from the tablet (proximity detection) it makes right click every time. Example at krita: I select some brush and start drawing, the second I take away the pen from the tablet to a minimum distance it makes the right click function which in Krita is to select another brush. At gimp right clicking opens properties. (still its a huge step because I can start working and test how designing works at linux).

OS related: I was using manjaro weeks ago but my GPU (AMD Rx550 4g) had driver issues, from what I understood is that manjaro failed to recognize the proper driver, using one that is incompatible forcing the monitor to be in rest mode or sometimes using wrong drivers (not the ones recommended for me which I manually installed) and making the experience clumsy. Making a research and watching videos (including The linux gamer at youtube) several people including him had or have issues with AMD GPUs at Manjaro, because the official AMDPRO linux drivers are available and more stable at Ubuntu based distros , for what I understood actually, I don't know better(so far it works flawlessly and even at the same level in games using steamplay).

What I have so far:

*konachan700 Drivers.
*digimend, 6, 4.15.0-38-generic, x86_64: installed(I think it’s updated).
*David Revoy (https://www.davidrevoy.com/article331/setup-huion-giano-wh1409-tablet-on-linux-mint-18-1-ubuntu-16-04#c0331-1513) first steps because I failed at “Call your text-editor in admin mode”(sudo xed /usr/share/X11/xorg.conf.d/50-huion.conf) it returns (sudo: xed: command not found) for me.
*Libwacom: I thik I installed properly, the command returns ($ xsetwacom --list devices
Huion Q11K Tablet stylus id: 12 type: STYLUS ) which is my tablet but I have no idea how to edit preferences.
*Xorg thingy: I tried to follow the steps mentioned from “davidrevoy.com/article331” but at the part of -Add a custom X11 rules: I got (xed: command not found) as mentioned early, what I did? I created manually what he proposed but manually, I created a xorg.conf.d file using his tablet code at the same location(/usr/share/X11/xorg.conf.d/50-huion.conf). I literally have no idea if that’s okay to do but that’s what I have so far.
*Ximput - -list: I don’t know if it is okay but I have two entries about the tablet and one is recognized as keyboard (

↳ Huion Q11K Tablet stylus id=12 [slave pointer (2)]
⎜ ↳ SONiX USB DEVICE id=14 [slave pointer (2)]
⎜ ↳ Huion Q11K Keyboard ).

I’ll try to fix what I did wrong or re-follow the steps to see If I’m missing something, for now is workable and I’m happy because I have no results yesterday and now I have pressure levels.
The wireless mode does not work so far and it would be great if it did.
Buttons I did not test so far because I mostly use keyboard shortcuts even at windows.
Thank you for reading (English is not my main Language).

@LuciusTalane

This comment has been minimized.

LuciusTalane commented Nov 14, 2018

Good news update:
Wireless: after a restart, unplug and plug of the tablet, the wireless started to work.
Pressure: I had some vibration on the tablet detection in wired mode, wireless works great.
Buttons: 2 or 3 buttons are working (more testing needed). more than I need anyways so I'm happy so far.
conf: I changed my config to the one posted by @Hideaki974.
Thanks to all of you for help the artist community because of your hard work on the drivers.
I'll be checking for updates for the Q11K from now on.
personal question: I dont know about other tablets on linux, but will be possible in the future to have some UI for the tablet configuration? would be great.
In any case, I'll proceed to further testing on my tablet and I hope you all have a great week.
Thanks again.

@Rabcor

This comment has been minimized.

Rabcor commented Nov 15, 2018

@LuciusTalane there already is a UI configuration for the Wacom drivers, which you are using, but they only exist in some desktop environments (only ones I know are Gnome and KDE)

I recommend you use it to set the 'force proportions' option at least.

Although ironically now I'm the one having issues making it work with the 4.18 kernel lol (worked fine on 4.14) the konachan drivers do not want to compile on the 4.18 (and 4.19) kernel.

@LuciusTalane

This comment has been minimized.

LuciusTalane commented Nov 15, 2018

Same here, worked just fine and now is not detected anymore, I shall do more testing.

@Rabcor

This comment has been minimized.

Rabcor commented Nov 15, 2018

Same here, worked just fine and now is not detected anymore, I shall do more testing.

Well if you switch kernels you (probably) have to recompile the driver against that kernel's headers. I never had any issues with this driver on 4.14 kernel, it just worked.

Edit: I even just now tested it, went to 4.14, compiled and installed the driver, rebooted and it just worked (the device never shows up under lsusb but does show under xsetwacom --list devices)

I have no idea why it won't compile on 4.18.

@LuciusTalane

This comment has been minimized.

LuciusTalane commented Nov 15, 2018

Sometimes my tablet appears at "xinput --list" with name and model, but if so, it does not appear at all at "xsetwacom --list", and sometimes neither of the commands show it (and the tablet does not work obviously). Restarted the session, unpluged and pluged the usb again, and the tablet shows up in either of the two commands (xinput and xsetwacom) and works, I find it pretty strange and annoying, but at least I can design(when it works). there should be better options coming from the companies who sell graphic tablets by now, it's 2018 and we keep struggling.
Anyways I'm truly grateful that I found this git, I'll keep checking it to configure it the best way possible 👍

@LuciusTalane

This comment has been minimized.

LuciusTalane commented Nov 15, 2018

@LuciusTalane there already is a UI configuration for the Wacom drivers, which you are using, but they only exist in some desktop environments (only ones I know are Gnome and KDE)

I recommend you use it to set the 'force proportions' option at least.

Although ironically now I'm the one having issues making it work with the 4.18 kernel lol (worked fine on 4.14) the konachan drivers do not want to compile on the 4.18 (and 4.19) kernel.

There is one installed and updated in my Ubuntu, I'm using gnome, but it says there is no tablet detected, And I tried another from the software shop thingy, also did not work.

@Rabcor

This comment has been minimized.

Rabcor commented Nov 15, 2018

I am on manjaro so something might be a bit different there, anyhow I found out why it won't compile on 4.18, it's this patch: https://lore.kernel.org/patchwork/patch/935088/

Meaning this line:
hdev->quirks |= HID_QUIRK_NO_EMPTY_INPUT;

In q11k_device.c is the cause of the failure to comiple. I am not a real programmer though (I mean I know some python and C# basically) so I don't know if it's safe to remove or if there's something I should replace it with.

Update: I replaced it with this line:
hdev->quirks |= BIT(8);

And it would compile properly. (And also it works perfectly again for me 😄 )

Edit: @LuciusTalane do you have the huion Q11k or Q11k V2? And also as I said, mine just works wirelessly, even when it is turned off I can see it in the xinput --list or xsetwacom --list devices.

@LuciusTalane

This comment has been minimized.

LuciusTalane commented Nov 15, 2018

I am on manjaro so something might be a bit different there, anyhow I found out why it won't compile on 4.18, it's this patch: https://lore.kernel.org/patchwork/patch/935088/

Meaning this line:
hdev->quirks |= HID_QUIRK_NO_EMPTY_INPUT;

In q11k_device.c is the cause of the failure to comiple. I am not a real programmer though (I mean I know some python and C# basically) so I don't know if it's safe to remove or if there's something I should replace it with.

Update: I replaced it with this line:
hdev->quirks |= BIT(8);

And it would compile properly. (And also it works perfectly again for me smile )

Edit: @LuciusTalane do you have the huion Q11k or Q11k V2? And also as I said, mine just works wirelessly, even when it is turned off I can see it in the xinput --list or xsetwacom --list devices.

hello again, thanks for the update, I have the Q11K (first version) it works wireless for me also, and it's detected most of the time but sometimes it's not detected at all as I mentioned.
Where do I edit those lines? I installed so much things I'm kinda lost right now

Edit: Needless to say, even like this I can work properly with a good pressure detection and 2 buttons, so I'm more than grateful so far :)

@Rabcor

This comment has been minimized.

Rabcor commented Nov 15, 2018

I am on manjaro so something might be a bit different there, anyhow I found out why it won't compile on 4.18, it's this patch: https://lore.kernel.org/patchwork/patch/935088/
Meaning this line:
hdev->quirks |= HID_QUIRK_NO_EMPTY_INPUT;
In q11k_device.c is the cause of the failure to comiple. I am not a real programmer though (I mean I know some python and C# basically) so I don't know if it's safe to remove or if there's something I should replace it with.
Update: I replaced it with this line:
hdev->quirks |= BIT(8);
And it would compile properly. (And also it works perfectly again for me smile )
Edit: @LuciusTalane do you have the huion Q11k or Q11k V2? And also as I said, mine just works wirelessly, even when it is turned off I can see it in the xinput --list or xsetwacom --list devices.

hello again, thanks for the update, I have the Q11K (first version) it works wireless for me also, and it's detected most of the time but sometimes it's not detected at all as I mentioned.
Where do I edit those lines? I installed so much things I'm kinda lost right now

Edit: Needless to say, even like this I can work properly with a good pressure detection and 2 buttons, so I'm more than grateful so far :)

You're not hearing me, this was a compilation issue, if you managed to install the driver your problem is something else, I already told you this... And I already told you what file to edit, in the source code, for konachan's q11k driver, you would edit that source file before you run the make && make install commands.

I have not encountered the issue with the tablet not being detected sometimes. This will not solve the detection issue you are having.

@spbnick

This comment has been minimized.

Member

spbnick commented Nov 15, 2018

@Rabcor, please have some patience. It's easy to get lost in these details and get confused, especially for newbies, like @LuciusTalane says he is. I know it's frustrating when people don't get what you're saying (trust me), but let's not start snapping at each other.

@LuciusTalane

This comment has been minimized.

LuciusTalane commented Nov 15, 2018

@Rabcor, please have some patience. It's easy to get lost in these details and get confused, especially for newbies, like @LuciusTalane says he is. I know it's frustrating when people don't get what you're saying (trust me), but let's not start snapping at each other.

I get lost sometimes when people mentions some standard linux commands (Like when I did not know he was talking about the kachan drive's source to edit that specific line, but now I get it). but I also get @Rabcor I should pay more attention.

Good news so far: The tablet is working better and it gets detected every time. I'll keep paying attention to this git post nonetheless.
Thank you all again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment