Another „OpenTabletDriver is not recocnizing my tablet” thread (Huion Kamvas 13 in this case)
Hi all ^ _ ^
I'm enjoying Bazzite a lot so far (switched from Fedora) but I can't get my Kamvas 13 tablet to work. Installed OTD via
ujust but the tablet not being detected (console searches but says nothing detected) even though it is there when I do lsusb.
Had a search around here and also did sudo rmmod wacom hid_uclogic as suggested on my question on Discourse (1) and elsewhere but I just get a message saying:
rmmod: ERROR: Module wacom is not currently loaded
rmmod: ERROR: Module hid_uclogic is not currently loaded
Which seems to me like hid is already disabled (but wacom is as well?). Not sure what to make of that …
On Fedora I remember installing the official Huion drivers (2) by extracting the archive they provide and running ./install.sh, is there a way to do that on Bazzite somehow?
Any other ideas what I could try? Thanks in advance! 💖
(1) https://universal-blue.discourse.group/t/huion-kamvas-not-showing-up-in-opentabletdriver-system-setting-on-bazzite/3208
(2) https://driverdl.huion.com/driver/Linux/HuionTablet_LinuxDriver_v15.0.0.162.x86_64.tar.xzUniversal Blue
Huion Kamvas not showing up in OpenTabletDriver / system setting on...
Hi! Just switched to Bazzite from Fedora when I got a new PC last week. So far it has been very, very good but I can’t get my Huion Kamvas pen tablet display to work. It shows up as Bus 001 Device 017: ID 256c:006d HUION Huion Tablet_GS1331 when I lsusb but the display just turns off again after showing the logo briefly and neither the Plasma...
148 Replies
Looking at that install script (and i could be wrong) there are things to edit to make it install on atomic, but i will have no idea if it will be functional, also it seems like this tablet driver forces X11 which we do not support, it is only available on the nvidia image up until most likely fedora 41 which will be soon.
i would try running it inside distrobox and hope that works, not sure about much else really.
Sadly im one of those who just have a wacom (i rarely use) and it just works so i am pretty useless here 😅
Hi, thanks for the answer! That's interesting, I'm pretty sure I've used the tablet with Wayland on Fedora, so there must have been another way (or it does run via XWaylandSessuib or whatever it's called?). I think I did a session randomly installing libwacom / digimend / input remapper and other stuff and it worked without me having to run the Huion-app after that, it just showed up in Plasma system settings (which it never did on X).
Any ideas about the OpenTabletDriver, what these messages mean?
the installer script from my understanding disables wayland and sets x11 as default
its towards the bottom
Yeah, that's way above my head but it looks like it wants X11. Welp, any ideas what to do about OpenTabletDriver not seing my tablet?
no idea sadly, as i said i got a wacom and it just works so i am useless with anything OTD specific
o yeah, you said, lucky you ^ _ ^ well i made a ubuntu box with boxbuddy and installed the .deb version of the huion-gui, exported it to bazzite, it opens up fine but doesn't see the tablet …
😦
hmm I have an huion kanvas but it worked out of the box for me on wayland, kde. (arch, not bazzite, I can give it a shot tomorrow on bazzite) You sure you need open tablet driver?
could you provide an
lsmod that i can check from arch if it also does not work for you in bazzite? see if i find anything related to it in the modules and see if we are missing anything or if there is something we could try include if it does not break other stuff 🤔sure, tomorrow Ill do some tinkering
cheers
Ok I just hooked up the tablet, it works out of the box, no huion drivers, no open tablet drivers (kamvas pro 16)
This is lsmod dump:
on kde I just had to change this
this is on arch (endevour os really)
let me know if you need any more info or whatever, I'll be around a bit
in fact, let me drop to bazzite and check there
hmm on bazzite I get the screen but nothing under the tablet settings
lsmod dump on bazzite
that's interesting, it's the same for me on bazzite, tablet is not in the system settings. @Potajito am i understanding this right, it works for you out of the box on arch but not on bazzite? i feel like it might have been like that for me on fedora wayland as well, that it the tablet just turned up in the system settings and i didn't even used the huion drivers/app (that might have been fedora with x).
looks to a be a bazzite config thing imo, I'm 100% running wayland on both platforms, 100% no extra drivers installed
this was with the tablet connected? i forgot to mention that last night sorry
yeah, both dumps with the tablet connected
might be done by uclogic which the post mentioned to unload
usbhid 86016 1 hid_uclogic
that 1 before hid shows it is being used
checking bazzite one now
yep uclogic has 0 devices using it
just out of curiosity can you try
sudo modprobe hid_uclogic see what happenson bazzite or arch? both? (can't do it right now)
bazzite when you are free obviously
its the only lead i got atm that uclogic doesnt load maybe
its the only thing i spotted with my limited knowledge of what modules these use 🙂
I just wanted to say that I'm super grateful that you both are looking into this, thank you so much!
Well i am trying what i can without the hardware or knowledge of it
i havent found anything else that sticks out in the list sadly
as of now, nothing, the commands runs but no output
lsmod still shows hid_uclogic as 0 after modprobe
hmm then i am unsure
as in it matches what happens on arch (no drivers needed)
so something to do with libinput?
I'm going to post some outputs here on bazzite so I can check them on arch:
libinput list-devices on bazzite
and arch libinput list-devices
this shows both the pen and the tablet
while bazzite shows neither
does it ring any bell @HikariKnight ?
dont know the exact package that handles that 🤔
@ellen_bogen @Potajito try
rpm-ostree install kcm_wacomtablet
might be that onetrying
no luck!
😦
it was the closest thing related i could find when searching for huion and kcm in the packages
I can see it from bazzite using
sudo dmesg | grep -i pad
[ 6.997852] input: HID 256c:006d Pad as /devices/pci0000:00/0000:00:08.1/0000:0f:00.4/usb7/7-2/7-2.4/7-2.4:1.0/0003:256C:006D.0009/input/input24
[ 6.998027] uclogic 0003:256C:006D.0009: input,hidraw8: USB HID v1.11 Keypad [HID 256c:006d] on usb-0000:0f:00.4-2.4/input0
hmm
im curious if gnome would notice it then and if the problem is isolated to plasma and a missing package
it also uses uclogic as i suspected but the module stays unused which makes even less sense
but if it were a plasma issue, shouldn't it show up on libinput list-devices anyway?
oh right true
could something be up with libinput then?
i have to head out so i wont be able to help investigating this much more today
yeah I have to do some work, I'll try to research a bit the issue, I think libinput is the culprit. I was thinking maybe doing some udev rules and see if that helps, but I don't have to do any of that on arch, so I don't think is the right way
if it can be solved with an udev rule it is an easy inclusion
just pasting somethings to try later don't mind me too much:
SUBSYSTEM=="hid", ACTION=="add", ENV{HID_ID}=="0003:0000099A:00002620", \
RUN+="hid-rebind"
SUBSYSTEM=="hid", ACTION=="add", ENV{HID_ID}=="0003:0000256C:", \
RUN+="hid-rebind"
SUBSYSTEM=="hid", ACTION=="add", ENV{HID_ID}=="0003:00005543:", \
RUN+="hid-rebind"
SUBSYSTEM=="hid", ACTION=="add", ENV{HID_ID}=="0003:00000458:", \
RUN+="hid-rebind"
SUBSYSTEM=="hid", ACTION=="add", ENV{HID_ID}=="0003:00002179:", \
RUN+="hid-rebind"
SUBSYSTEM=="hid", ACTION=="add", ENV{HID_ID}=="0003:000028BD:*", \
RUN+="hid-rebind"
SUBSYSTEM=="hid", ACTION=="add", ENV{HID_ID}=="0003:00000543:0000E621", \
RUN+="hid-rebind"
SUBSYSTEM=="hid", ACTION=="add", ENV{HID_ID}=="0003:00002133:00000018", \
RUN+="hid-rebind"
libwacom
libinput list-devices seems to not see my tablet and rpm-ostree install kcm_wacomtablet sadly doesn't seem to change anything (it's also not turning up in otd or system settings.we got libwacom 2.11.0
The tablet is supported on libwacom and that talks with libinput, so something is getting lost somewhere
Well means we got something to track at least
What version does arch have?
2.12.2
maybe it was added recently in the newer version?
I can check, I'll give it a shot at home
from github
im curous if support was added in 2.12.0
GitHub
Added more device names for kamvas 13 variants by LostNulide · Pull...
I am using the Kamvas 13 with the same model number, but it couldn't be detected by libwacom.
After some searching, I found out that the device name used in the descriptor doesn't m...
Hmmm could it be? Mine is kamvas 16 and Ellen's is 13 both are mentioned
@ellen_bogen can you give me the
lsusb output with the tablet connected?I think we are onto something. Can I layer latest libwacom with an rpm, copr or something and try?
as long as the dependencies and their version are there yes
since its not a kernel driver
cant seem to layer rpm Could not depsolve transaction; 1 problem detected:
Problem: cannot install both libwacom-data-2.12.2-2.fc41.noarch from @commandline and libwacom-data-2.11.0-1.fc40.noarch from @System
- conflicting requests
probably missing something
probably need to
rpm-ostree override remove then rpm-ostree installcant seem to be able to
pablo@bazzite /v/h/p/Downloads [1]> rpm-ostree override remove libwacom-data
Checking out tree 5ff3834... done
Resolving dependencies... done
error: Could not depsolve transaction; 1 problem detected:
Problem: package libwacom-2.11.0-1.fc40.i686 from @System requires libwacom-data = 2.11.0-1.fc40, but none of the providers can be installed
and if I just try "libwacom" instead of "libwacom-data"
rpm-ostree override remove libwacom
error: Multiple packages match "libwacom"
gotta go, will keep on later
sure, my kamvas 13 shows up as „Bus 001 Device 098: ID 256c:006d HUION Huion Tablet_GS1331“ in
lsusbhmm thats the one that was there from before
I can't seem to upgrade libwacom on bazzite but I'm thinking of downgrading the one in arch and see the behaviour
try that probably way easier
sry Ive not checked in a while I had issues wiith opentablet as well and was guided in removing hid_uclogic
Huion Kamvas 24 Pro what worked for me and has remain the best always functional after trying many diff installs of openTabletDriver
ujust install-opentabletdriver
That for some reason installs it in an Arch distro and has been just fine even on system reboot pen works
Only thing i cant get to work is miniKD100
@Serge#007 mh, that's a bit weird that it works for you out of the box with otd (on arch via ujust, did the same) but for me. but well, they're different models … are you on bazzite as well?
doing this today, I haven't forgotten!
DAMN
I was conviced that outdated libwacom was going to be the issue, but downgrading to 2.11 doesn't make a difference, tablet still works on arch
😦
I don't know what else to try. I think ellen said that they thing fedora worked, i'm tempted to try it there, at least on a vm
open to ideas
i would do the same
should I try plain fedora, kinoite, aurora?
since we are supposed to be 1:1 with fedora upstream (excluding newer packages that we have)
aurora would be a good try too incase they happen to have it fixed for a bizzare reason
ill try fedora then aurora
fedora gnome works
trying aurora
hi, thanks for all the work you put in! just to be clear, i don't know if otd ever recocniced my tablet with fedora wayland, i just know that it somehow worked, i'm pretty sure it showed up in kde tablet settings and i remapped the keys with input renamer. i do remember being in the otd discord and not getting it to work but that might have been on x …
np! hopefully we fix this
ok aurora DOESN'T work.
I'm going to try plain fedora KDE
wonder if it only affects kde
OK IT WORKS on Fedora KDE
something is missing on atomic distro (going to try bazzite gnome)
but this is interesting
when it's "going to work" you get this screen
but when it doesn't you get this one
haha, yeah, what an amazing treasure hunt that you're on ^ _ ^
haha yeah, I should be doing something more productive haha
no, please don't ^ _ ^
@HikariKnight does this ring a bell? like, it seems some package is missing, because the "not connected" interface is quite different
bazzite gnome now
yeah this is what i get
what do you mean by „going to work“? is that screen before you install otd or what are the steps you do before it's working (i get the completely empty screen as well, unfortunately)?
I don't install anything extra, we shouldn't. That's the screen that I get before connecting the tablet
but it's the "good" interface, it means its going to work when you connect it, meanwhile, the screen that hikari posted is the bad one, you connect the tablet and it doesn't find it
if it works on fedora kinoite, can you also check ublue kinoite
i haven't tried kinote yet, I tried aurora (didn't work) I'm going to try bazzite gnome and then I'll give a shot a kinoite
ah, ok. thanks for the clarification.
feels like we are almost there cmon
HHM!
Bazzite gnome semiworks? I can see the tablet, but the pen doesn't work (it did on fedora workstation gnome)
atomic distros are doing something. Let me try plain kinoite
yeah, Kinoite works!
it's something ublue images are doing
I think I've done all the tests I can think of, any idea? Has to be some config issue/missing package on ublue images
unlue kinoite did not right? since thats supposed to be 1:1 with kinoite
let me try
i tried plain kinoite, didn't know there was a uble kinoite, I thought ublue kinoite was aurora
nope
ublue kinoite is part of the main images, we dont advertise them but they are supposed to be used as a base for aurora, bazzite and so on
so if it doesnt work there then there is indeed something in ublue that is missing
can you point me to an iso plz?
cant seem to find it
no iso
have to rebase from fedora kinoite or build iso yourself
ahh nise, rebase it is
could I get a rebase command? 👉 👈
already getting it
rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/kinoite-main:latest
not meant for end users to really use as they are not our end products, but we dont stop people from using them since they are a by-product of what we makegreat, rebasing 🤞
if it is happening in ublue main it should be easy to fix in theory, idk how involved it would be myself though
but ideally it should work there since it works in fedora kinoite, meaning its something aurora/bazzite does that breaks it
yeah NOT working on ublue kinoite
ok at least we have tracked down where it happens.
i can try take a look at it later this month but i am busy a great deal this month sadly. worst case i cant take a proper look at this until next month...
no worries, at least we have pinned it down. Should I bug an issue on ublue github?
yes please do and add all the findings you found in it and tag me in the message so i can keep it in my github notifications
might also be worth that this was an issue we discovered in bazzite and tracked down to the main images
Sure, I'll get to it when I have a moment!
awesome thanks so much
for completness sake @HikariKnight is your wacom tablet working fine on ublue images?
i will actually double check that in a few, i need to just dig it out
great, let me know so I can report it!
works
nice, ty!
this thing needs charging 🤣
GitHub
Huion tablets not working in ublue images, while Fedora's images wo...
Hi! Huion tablets are not working on ublue images: Bazzite KDE: Not working Bazzite Gnome: tablet shows up but pen doesn't work, so I'd consider it now working Aurora: Not working Kinoite U...
Yes I am on bazzite gaming-pc/kde version. I ran ujust install via the default terminal
by which i assumed would have just installed the driver no different than discover center. But yeah that generated an arch box and installed
thats what its supposed to do because it installs opentabletdriver which is a userland driver from what i understand
this issue is with whats meant to work out of box in ublue because it does in fedora kinoite
Oh and btw I forgot to mention the only way the tablet actually appears in the display config --> drawing tablets was when I installed the actual Huion linux debian driver in an ubuntu toolbox and launch it. By which the settings are wonky and cannot be set.
Even while functional with opentabletdriver in Arch it remains not found
That's really interesting, I tried that as well (installing the Huion .deb in Ubuntu via Box Buddy) but it had no effect for me … But wait that was regular Ubuntu not ubuntu-toolbox (whatever that is), I'll try it now.
@Potajito & @HikariKnight thanks so much for spending so much time on this! 🥰 I'll have an eye on the Github issue to see how it develops.
Welp, doesn't work with ubuntu-toolbox for me either … Does anybody now how I can get rid of the links to distrobox-apps on the host-system? Uninstalled the Huion app in the (non-toolbox) Ubuntu box but the (now non-functional) desktop-entry is still there and I don't know how delete it … Even when I remove it from the Application Launcher (via right-click on the icon > Edit Applications) it's still there.
sometimes the applications take a while to get remove, maybe reboot. Also there is boxbuddy to manage installed distroboxes, probalby there are some options there too
Yeah, I thought a reboot might be needed as well, I'll see if that works, thanks ^__^
If you do a search in general for uclogic you should find my conversation where @Johnny Appleseed helped me out. Maybe its the way you handled removing uclogic? he had me blacklist it which then yielded success. I had no care on breaking something so i followed his instruction. Therefore I would recommend caution or get guidance on at least how to undo a blacklist.
Mh, interesting, I'll check that out and think about how daring I want to be with this system ^__^
It's not super dangerous ™️ but you are changing kernel boot options so it's not impossible to have to revert that and if you typo'd something it could cause that not to boot
the short version is a lot of tablets conflict with the uclogic driver with open tablet driver so if it's in the OTD supported list that might be the issue
can also try doing
sudo rmmod hid_uclogic before running OTD and that's less permanent
to revert the kernel arguments you'd have to do a rpm-ostree kargs --remove=modprobe.blacklist=hid_uclogic or what have youYou can always just rebase to kinoite in the meantime , depends on how many bazzite features you need
yeah, i was thinking about that as well (super new to all this ^__^). and i could also just go back to bazzite if the rebase doesn't work? i'm gonna check out some tutorials on rebasing.
pretty straightforward, rebase either works and system boots or doesnt and it stays the same
just to double chekc: from what i read just update the system, reboot, pin the bazzite version i'm on and then do
rpm-ostree rebase fedora:fedora/40/x86_64/kinoite? or should i use the rollback-helper-tool?rollback-helper is bazzite only
Shouldn't they rebase to stable or something like that instesd of 40?
I once rebssed to 39 and didn't get the update to 40 when that came up
i never rebased to fedora normal edition
anyway taht should work, worst case they will need to rebase to 41 when that happens
doing it now, wish me luck ^__^
well rebasing worked and the system settings (and lsusb) sees the tablet but it still turns itself off after a second. distrobox is gone and i installed otd via flatpak (how did you do it on kinoite @Potajito ?) but that still doesn't see the tablet +___+
yo dont need otd
tablet shoyuld work out of the box
oh
dang
also, are you sure tablet is not working? as in, it shows up there
on the screen you sent, is recognized at least
i was wondering if the turning-off is something about not getting enough power from usb or something but i tried both that i have and it turns of with both of them.
yeah, it looks like it should work from the system settings but it just shows the logo and the turns the screen off
sorry but what is your issue exactly? because the tablet seems to be recognized from that screen
oh ok, then it looks like a different issue
but the tablet is being recognized it seems
yeah. it looks like it
check connections, check also in windows if possible and see how that behaves
but I think that's a different issue not related to drivers
super weird. i'll have a look if i can find the other cables with the external power socket.
do you know how to install nvidia drivers on kinoite by any change? my card seems not to be recocnized +___+
I haven't done it, but it should be easy https://rpmfusion.org/Howto/NVIDIA#OSTree_.28Silverblue.2FKinoite.2Fetc.29
this basically
sudo rpm-ostree install akmod-nvidia xorg-x11-drv-nvidia
sudo rpm-ostree install akmod-nvidia xorg-x11-drv-nvidia-cuda #optional if using nvidia-smi or cuda
sudo rpm-ostree kargs --append=rd.driver.blacklist=nouveau --append=modprobe.blacklist=nouveau --append=nvidia-drm.modeset=1 # this might not be needed at some point when ostree systems will support the standard way to specify this.
interesting, this looks like it's installing x-drivers but it would also work in wayland? i'll try it.
can't get the tablet to work, though +___+ i had a laptop before and it just worked with one usb-c cable, which is what i tried until today. i now connected anothe usb-c cable to the tablet and connected it via a usb-charger to a power-plug but it still turns itself off after a second. there's also this weird 3-in-1-cable that needs a hdmi-port of which i have only one so it'll not be a solution but i'll try it next
how are you connecting your tablet (do you have a kamvas 13 as well)?
it works with the 3in1-cable 🤦♀️
yay, i found a displayport cable which i can use to connect my monitor to the pc. this might actually work!
yeah, in that command there are both
is a 16, it has an hdmi plug for the pc, and then a split cabe to plug the power->to the tablet
ah, ok.
for future reference: you need to do https://rpmfusion.org/Howto/OSTree before the above otherwise you'll only get errors.
but it seems to work now (system settings still can't see the gpu but i'm used to that, blender can, so i'm all good!). gonna check out the tablet with krita, tomorrow, thanks for all the help!
no worries, share your findings!
my findings until now (aside from the tablet working perfectly with krita) are unfortunately that kinoite is pretty unstable and crashes a lot (mostly while playing video) to the point that i need to hard restart the computer sometimes. also lots of random crashes of plasmashell when opening programs or waking up from sleep. can't tell if this is a hardware issue since this is a new (bought used) computer for me, so i can't compare it to previous distros (did not have fedora 40 on my previous laptop crashing on my at all, though afaik) i'm testing that old pinned bazzite install now to see if it is more stable, i'm afraid that kinoite didn't really like layering all those nvidia/cuda/vulkan drivers on top, there's always a weird „unkown“ package in discover to update that is a lot of gstreamer and mesa drivers but i can't tell if it ever gets installed.
hello, dear people ^__^ i rebased to bazzite just now in the hope that with plasma 6.2 my tablet maybe might magically work (and it was also a complete nightmare trying to get docker-compose to work on kinoite, did not succeed and it seems like it also isn't working ootb on bazzite) but unfortunately plasma 6.2 can't see my tablet either. any of you have some time to investigate this, has any idea what i can try? i have not installed any drivers or done any rpm-ostree kargs --append=modprobe.blacklist=hid_uclogic
can try doing
sudo rmmod hid_uclogic and then running OTD to see if that works
if so the last command would blacklist the module at boot
if it's on the OTD supported tablet list it should work https://opentabletdriver.net/Tablets
but sometimes a pre-existing kernel module conflicts with OTDooohhhh, odt sees my kamvas 13! interesting! problem now is that even though I think i've mapped it to the tabled the cursor is still only on my main monitor +___+
that was in artist mode, in absolute mode the curser is on the tablet display but it's jumping around all over /is nowhere near the pen tip and sometimes there's a crosshair-cursor in addition to the mouse courser. also not sure what's with the resolution, the tablet is 1920 x 1080p but if i put that in it's not doing it any good. not sure what to do about this …