You are not logged in.

#1 2016-10-28 20:52:16

CrocoDuck
Member
Registered: 2015-10-25
Posts: 9
Website

Wacom CTL-471 Bamboo One stopped working but still detected

Hi there!

I have been struggling with this problem for a couple of days and I wanna share the solution I found just in case it might be helpful to someone else. Also, I still have few questions unaswered.

My Wacom CTL-471 worked out of the box just after installing xf86-input-wacom. However, at some point in the last couple of weeks, it stopped working. I am not sure when, since I didn't use the tablet in the last 20 days. but when I plugged it back 2 days ago it was pretty much dead. The interesting thing is that lsusb and dmesg would display the expected things:

[crocoduck@arch ~]$ lsusb
Bus 002 Device 005: ID 056a:0300 Wacom Co., Ltd CTL-471 [Bamboo Splash, One by Wacom (S)]
[crocoduck@arch ~]$ dmesg
[ 1065.320749] usb 2-1: new full-speed USB device number 9 using xhci_hcd
[ 1065.459016] input: Wacom Bamboo One S Pen as /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/0003:056A:0300.0008/input/input31
[ 1065.459161] wacom 0003:056A:0300.0008: hidraw0: USB HID v1.10 Mouse [Wacom Co.,Ltd. CTL-471] on usb-0000:00:14.0-1/input0
[ 1065.461958] wacom 0003:056A:0300.0009: hidraw2: USB HID v1.10 Device [Wacom Co.,Ltd. CTL-471] on usb-0000:00:14.0-1/input1

But no mater what, xsetwacom --list devices would display nothing. I tried quite a lot of things. I tried xf86-input-wacom-git. No changes. input-wacom-dkms froze my desktop (GNOME3) right after login (weird). I tried to force remove libwacom (which is needed by gnome-settings-daemon) as the wiki states it might give troubles. Well, apparently it is -really- needed, as my system couldn't make it to gdm without it (yes, I had to reinstall it from cache through chroot). wacom-udev didn't change anything. I also tried to downgrade the kernel to the first version I remembered my tablet was working at. No changes. In all these cases moving the pen would show a cross pointer on the screen moving around as a sort of minimal mouse ghost (perhaps some minimal X functionality).

Then I found this post. Without much hope, I created /etc/X11/xorg.conf.d/50-wacom.conf with this content:

Section "InputClass"
        Identifier "Wacom class"
        MatchProduct "Wacom|WACOM|Hanwang|PTK-540WL"
        MatchDevicePath "/dev/input/event*"
        Driver "wacom"
EndSection

Section "InputClass"
        Identifier "Wacom serial class"
        MatchProduct "Serial Wacom Tablet"
        Driver "wacom"
EndSection

Section "InputClass"
        Identifier "Wacom serial class identifiers"
        MatchProduct "WACf|FUJ02e5|FUJ02e7|FUJ02e9"
        Driver "wacom"
EndSection

And that worked alright! Now I get this:

[crocoduck@arch ~]$ xsetwacom --list devices
Wacom Bamboo One S Pen stylus   	id: 10	type: STYLUS    
Wacom Bamboo One S Pen eraser   	id: 14	type: ERASER 

Which is the expected output, according also to another user report. Apparently my wacom is back to life and working as always.

If I am not wrong, that conf file should be generated by xf86-input-wacom somehow.

MilanKnizek wrote:

...installing the package xf86-input-wacom (which creates also xorg configuration file: /etc/X11/xorg.conf.d/50-wacom.conf)...

(see here).

I imagine that creation to be the automatic setup the wiki talks about. Everything points to some kind of automatic setup failure. Any of you having some suggestion on how to investigate this further and, perhaps, file a bug report?

Last edited by CrocoDuck (2016-10-28 21:00:25)


Check my Linux audio experiments on my SoundCloud.
Fancying a swim in the pond?

Offline

Board footer

Powered by FluxBB