Same issue as @prab except I’ve got the XP-Pen star03.
I installed and built the xp-pen-tablet package first, rebooted, result:
[ ~]$ xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ PIXART USB OPTICAL MOUSE id=9 [slave pointer (2)]
⎜ ↳ UC-Logic TABLET 1060N Pen id=10 [slave pointer (2)]
⎜ ↳ UC-Logic TABLET 1060N Pad id=11 [slave pointer (2)]
⎜ ↳ UC-Logic TABLET 1060N Mouse id=12 [slave pointer (2)]
⎜ ↳ UC-Logic TABLET 1060N Keyboard id=13 [slave pointer (2)]
⎜ ↳ UC-Logic TABLET 1060N Consumer Control id=14 [slave pointer (2)]
⎜ ↳ UC-Logic TABLET 1060N System Control id=15 [slave pointer (2)]
⎜ ↳ XP-PEN MOUSE id=19 [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)]
↳ AT Translated Set 2 keyboard id=16 [slave keyboard (3)]
↳ XP-PEN ERASER id=17 [slave keyboard (3)]
↳ XP-PEN STYLUS id=18 [slave keyboard (3)]
[ ~]$ lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 5543:0081 UC-Logic Technology Corp. TABLET 1060N
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 003: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]
Bus 006 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[ ~]$ xsetwacom --list devices
Then I downloaded specific driver from site, installed, rebooted, used above commands - no change, i.e. nothing but one button acknowledged, which apparently has an ‘Esc’ effect.
Any more suggestions (I couldn’t quite follow @prab 's last note)?
Thanks
By last note, I believe you are referring to Digimend driver and/or uclogic-prob.
uclogic-prob:
When you execute the command “lsusb” the xp-pen will be listed with a specific Bus number and Device number. From your output it seems to be
Bus 004 Device 002. With that information, you can run the command “sudo uclogic-probe 4 2”. It might do the trick in your case.If not, you can try using the Digimend drivers.
Digimend drivers are available in the AUR: digimend-kernel-drivers-dkms-git
after installing, try the uclogic-probe procedure.
Usually a 2 weeks information becomes old in Linux world, so a year old discussion or 5 months one becomes irelevant. Moved your topic here and will try to cover a few things for you regarding tablet drivers.
AUR packages are maintained by community members/users and are not curated by official team members of Arch, but that doesn’t mean they are a bad thing to use. Just needs caution.
digimend-kernel-drivers-dkms-git AUR package is safe.
To install it you will need to install first the linux headers.
Open up terminal and run:
It will automatically install dkms too and set things up. Once is done you can check /usr/share/X11/xorg.conf.d/50-digimend.conf
that already has the entry for your tablet ID 5543:0081 and the driver used is wacom.
Once you reboot, the xsetwacom --list should also display your tablet.
Thanks. Following the above referenced Arch-advice I was told pacman couldn’t find the digimend header files, which made sense in the light of your post, which did exactly that:
returns “no operation specified” (and pacman -S … still doesn’t install the AUR package).
With the linux header files now installed, inside the folder with PKGBUILD, I ran
successfully, in /usr/share/X11/xorg.conf.d/50-digimend.conf, tablet ID and driver are shown. However, even after reboots, xsetwacom is not recognised as command.
-How is digimend-kernel-drivers-dkms-git built, as your post?
Pacman will never install AUR packages. You need an AUR helper for that.
Pamac does that.
Ok, that is a way to do it, but makes sense only if you want to change things in the PKGBUILD and then always you will take care of it, but since is using DKMS, the module for the kernel was also build?
You never mentioned that before. Is not recognized or is not listing any device? Those are not the same thing.
If is not recognized as command then you have to install xf86-input-wacom package. Is the only one that provides it. Also have to reboot after installing it.
If you respected the steps, then this is what you should see in terminal output (depending what kernel you are using):