[SOLVED] Wacom tablets in 14.1

jsdevel · 12-29-2013, 12:40 AM

Thanks for the help guys! Sorry for the late reply. I was at the in-laws

Here's what I'm seeing on

Code:

lsusb

:

Code:

Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 056a:0303 Wacom Co., Ltd 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 045e:0780 Microsoft Corp. 
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

When I run

Code:

xsetwacom --list devices

I'm not seeing my device displayed.

@astrogeek, should I fix this before using your script?
@j_v, will your build fix xsetwacom not detecting the tablet?

Thank you for your replies!

j_v · 12-29-2013, 04:57 PM

Quote:

Originally Posted by jsdevel

Thanks for the help guys! Sorry for the late reply. I was at the in-laws

Here's what I'm seeing on

Code:

lsusb

:

Code:

Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 056a:0303 Wacom Co., Ltd 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 045e:0780 Microsoft Corp. 
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

When I run

Code:

xsetwacom --list devices

I'm not seeing my device displayed.

@astrogeek, should I fix this before using your script?
@j_v, will your build fix xsetwacom not detecting the tablet?

Thank you for your replies!

It should fix things. I've compared the kernel driver source for 3.10.25, 3.12.6, 3.13pre5, and linux-next wacom driver. Besides the 'input-wacom' out-of-tree module, only the linux-next (linus' git) kernel supports your tablet. So for basic, kernel level support for the cth680, you can build your own kernel from linux-next or install the out of tree module (the later is what the 'input-wacom' SlackBuild does); also note that I didn't include the older serial driver, but you shouldn't need that as your device uses usb connection. Also the newer 'xf86-input-wacom' xorg driver will be needed, because support for the cth680 is also very recent (not included in the xf86-input-wacom-0.19.0 that is installed by default. While I cannot guarantee that the current wacom drivers are perfect, if you upgrade the wacom kernel driver and xorg driver, you should be able to start using the tablet; once you see support in lsusb and /var/log/Xorg.0.log (or what ever you Xorg log name is), you should follow astrogeek's help for getting the buttons, etc, setup.

jsdevel · 01-02-2014, 03:37 AM

@j_v, I'm attempting to run your slackbuild. I'm on fedora 20 and have a few issues:

1. After installing pacman, makepkg is located under /bin instead of /sbin (I changed the path in my copy so no biggie)
2. -l wasn't a valid option. -L was. I'm assuming this was intended to turn logging on?
3. When running the script as root, I got an error about running it as root so I had to add --asroot.
4. After doing #3, it's informing me that PKGBUILD doesn't exist.

It appears that the module has been compiled and installed in the proper location. I'm going to reboot to test it out (still need to install the xwacom driver.

j_v · 01-02-2014, 05:43 PM

Quote:

Originally Posted by jsdevel

@j_v, I'm attempting to run your slackbuild. I'm on fedora 20 and have a few issues:

You lost me there... Fedora? I thought I was helping you with a Slackware issue? I don't mind helping you anyway, but
the Slackware forum is not the place. I'm probably on thin enough ice as it is, using this 'Solved' thread for this.
I'll gladly help you in a more generalized venue (the "Linux - Hardware" forum seems appropriate).

Quote:

1. After installing pacman, makepkg is located under /bin instead of /sbin (I changed the path in my copy so no biggie)

pacman? That is the Arch linux package manager.

Quote:

2. -l wasn't a valid option. -L was. I'm assuming this was intended to turn logging on?

I haven't run Arch in a long time, and even then it was mostly in VM's, so I don't know what pacman's options are.

Quote:

3. When running the script as root, I got an error about running it as root so I had to add --asroot.
4. After doing #3, it's informing me that PKGBUILD doesn't exist.

Again, this is because you are trying to use Arch Linux's pacman for a Slackware style package build script,
on Fedora Linux. Hopefully nothing on your Fedora system has been hosed by all this mixing packagers.

I have started a new thread in Linux - Hardware: http://www.linuxquestions.org/questi...et-4175489929/. Please post further questions, etc., to that thread.

John