You are not logged in.
Hi, recently attempted to set up a new wacom Intuos S CTL4100 usb wacom tablet on my devuan system, lsusb sees the device as does dmesg yet gnome control center wacom tablet setup doesn't, I noticed via internet research upon the problem that the device concerned requires kernel image version 4.10 and input-wacom version 2.6.30 (yes recognize that this particular kernel image is not yet available for devuan, so understood there and no problem) question arises though, since there appears where the input-wacom Xorg package on my system (may need to uninstall and return to the stable version as I upgraded it to the ceres version (yep also aware of that)) seems to be a systemd service rather than a module driver for an init sysv kernel module etc ... read a few other forums discussing this particular device which appears to have system recog problems for example xsetwacom doesn't see the device even though lsusb sees it) so my question is (as it is obvious to me that the xorg input-wacom driver requires a init sysv framework (as in devuan there is no systemd emulator (not that a systemd emulator that fools systemd based software into running under the sysinit framework wouldn't be helpful)) Has anyone any idea how to fool the xorg into recognizing this device and running it without systemd in the devuan tradition ? perhaps udev script code etc ?
All the best
Happy winter festival and Happy new year afterwards
Nick
Offline
4.19 kernel is in ascii-backports
What wacom package are you talking about? The only one I see is xserver-xorg-input-wacom which is still at version 0.34.
Offline
Thanks had seen the 4.19 kernel ( the xserver file in question is xserver-xorg-input-wacom 0.34.99.1-1+b1 whose files include
/.
/lib
/lib/systemd
/lib/systemd/system
/lib/systemd/system/wacom-inputattach@.service
/lib/udev
/lib/udev/rules.d
/lib/udev/rules.d/69-wacom.rules
/usr
/usr/bin
/usr/bin/isdv4-serial-debugger
/usr/bin/isdv4-serial-inputattach
/usr/bin/xsetwacom
/usr/include
/usr/include/xorg
/usr/include/xorg/Xwacom.h
/usr/include/xorg/isdv4.h
/usr/include/xorg/wacom-properties.h
/usr/include/xorg/wacom-util.h
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/pkgconfig
/usr/lib/x86_64-linux-gnu/pkgconfig/xorg-wacom.pc
/usr/lib/xorg
/usr/lib/xorg/modules
/usr/lib/xorg/modules/input
/usr/lib/xorg/modules/input/wacom_drv.so
/usr/share
/usr/share/X11
/usr/share/X11/xorg.conf.d
/usr/share/X11/xorg.conf.d/70-wacom.conf
/usr/share/doc
/usr/share/doc/xserver-xorg-input-wacom
/usr/share/doc/xserver-xorg-input-wacom/changelog.Debian.amd64.gz
/usr/share/doc/xserver-xorg-input-wacom/changelog.Debian.gz
/usr/share/doc/xserver-xorg-input-wacom/copyright
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/xsetwacom.1.gz
/usr/share/man/man4
/usr/share/man/man4/wacom.4.gz
if am not mistaken (and I know I may be wrong) this unstable version has support for serial wacom tablets and runs as a systemd service
Offline
which is why it is possible for xsetwacom to see no tablet at all whilst lsusb sees the tablet
Offline
if am not mistaken (and I know I may be wrong) this unstable version has support for serial wacom tablets and runs as a systemd service
Looks that way, yes.
Fortunately the unit file is pretty simple:
empty@E485:~ $ systemctl cat wacom-inputattach@ --no-p
# /usr/lib/systemd/system/wacom-inputattach@.service
[Unit]
Description=inputattach for Wacom ISDv4-compatible serial devices
[Service]
Type=simple
ExecStart=/usr/bin/isdv4-serial-inputattach /dev/%I
Restart=on-success
empty@E485:~ $
You could try the conversion script supplied by the sysvinit maintainers, which results in this init script:
### BEGIN INIT INFO
# Provides: wacom-inputattach@${device}
# Required-Start: $remote_fs
# Required-Stop: $remote_fs
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Description: inputattach for Wacom ISDv4-compatible serial devices
### END INIT INFO
DESC="wacom-inputattach@${device}"
DAEMON=/usr/bin/isdv4-serial-inputattach
DAEMON_ARGS="/dev/${device}"
PIDFILE=/run/wacom-inputattach@${device}-sysd2v.pid
START_ARGS="--background --make-pidfile"
Replace ${device} with the actual name assigned to the tablet under /dev
Save that file to /etc/init.d/wacom-inputattach@${device} (with ${device} replaced) and then use
# update-rc.d wacom-inputattach@${device} defaults
And again, ${device} needs to be substituted with the correct name.
Last edited by Head_on_a_Stick (2019-12-26 16:25:15)
Brianna Ghey — Rest In Power
Offline
if test -x ./autogen.sh; then ./autogen.sh; else ./configure; fi && make && sudo make install || echo "Build Failed"
https://github.com/linuxwacom/input-wacom
Thanks but have just fixed the problem by downloading the source code from github and autogen using above commands
Will try the other workaround though Thanks
Offline
I think the first thing to try would be the backports kernel. That's easy to do or undo, and it won't hurt anything. I'd try it with the ascii version of the xserver package.
The only difference I can find between the jessie version and ceres version of xserver-xorg-input-wacom is in the wacom.conf file. There's no difference between the ascii and ceres versions of 70-wacom.conf.
The udev rules file is the same (jessie/ceres), and the pkgconfig file was moved and is only different in the version listed within.
(jessie) -xserver-xorg-input-wacom: /usr/share/X11/xorg.conf.d/50-wacom.conf
(ceres) +xserver-xorg-input-wacom: /usr/share/X11/xorg.conf.d/70-wacom.conf
Sorry I don't know what to do with this information, but here are the diffs.
$ diff -u 50-wacom.conf 70-wacom.conf
--- 50-wacom.conf 2019-12-26 11:19:49.159183000 -0500
+++ 70-wacom.conf 2019-12-26 11:21:26.183183000 -0500
@@ -1,24 +1,69 @@
+# Some of the below input classes appear 3x times, once for each of
+# "tablet", "touchscreen", and "touchpad" to ensure that the Wacom
+# driver is not accidentally bound to other types of hardware that
+# Wacom has made which are not handled by the wacom driver (e.g the
+# Wacom Bluetooth Keyboard)
+#
+# https://sourceforge.net/p/linuxwacom/bugs/294/
+
Section "InputClass"
- Identifier "Wacom USB device class"
+ Identifier "Wacom USB tablet class"
MatchUSBID "056a:*"
MatchDevicePath "/dev/input/event*"
+ MatchIsTablet "true"
Driver "wacom"
EndSection
Section "InputClass"
- Identifier "Wacom PnP device class"
- MatchPnPID "WACf*|WCOM*|WACM*|FUJ02e5|FUJ02e7|FUJ02e9"
+ Identifier "Wacom USB touchscreen class"
+ MatchUSBID "056a:*"
MatchDevicePath "/dev/input/event*"
+ MatchIsTouchscreen "true"
Driver "wacom"
EndSection
Section "InputClass"
- Identifier "Wacom class"
+ Identifier "Wacom USB touchpad class"
+ MatchUSBID "056a:*"
+ MatchDevicePath "/dev/input/event*"
+ MatchIsTouchpad "true"
+ Driver "wacom"
+EndSection
+
+Section "InputClass"
+ Identifier "Wacom tablet class"
+ MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
+ MatchDevicePath "/dev/input/event*"
+ MatchIsTablet "true"
+ Driver "wacom"
+EndSection
+
+Section "InputClass"
+ Identifier "Wacom touchscreen class"
+ MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
+ MatchDevicePath "/dev/input/event*"
+ MatchIsTouchscreen "true"
+ Driver "wacom"
+EndSection
+
+Section "InputClass"
+ Identifier "Wacom touchpad class"
MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
MatchDevicePath "/dev/input/event*"
+ MatchIsTouchpad "true"
Driver "wacom"
EndSection
+# Serial Wacom devices should always be one of tablet, touchscreen, or
+# touchpad so we can safely get away with just one match section in
+# these cases
+Section "InputClass"
+ Identifier "Wacom PnP device class"
+ MatchPnPID "WACf*|WCOM*|WACM*|FUJ02e5|FUJ02e7|FUJ02e9"
+ MatchDevicePath "/dev/input/event*"
+ Driver "wacom"
+EndSection
+
Section "InputClass"
Identifier "Wacom serial class"
MatchProduct "Serial Wacom Tablet"
@@ -56,4 +101,3 @@
Driver "wacom"
Option "Button2" "3"
EndSection
-
Offline