Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
11-18-2013, 12:55 PM
|
#1
|
Member
Registered: Feb 2010
Location: Georgia
Distribution: Slackware64 14.2
Posts: 779
Rep: 
|
Wacom tablets in 14.1
I recently bought a Wacom tablet (intuos, model CTH680), and I'm having a tough time getting it to work. Everything I've found online has been distro-specific stuff for Debian or Arch, so I thought I'd see if anyone has any ideas for how to make it work.
Using KDE, when I go to Graphics Tablet under input devices, it says no tablets found, ensure kded is started, etc (can't remember exact wording). dmesg and lsusb both show the tablet as being connected (at least, there's a Wacom line for it).
Beyond this I'm not really sure what to do. I've never used a Wacom tablet with Linux but I've always heard that support is great, so I'm sort of at a loss now.
|
|
|
11-18-2013, 05:32 PM
|
#2
|
Member
Registered: Oct 2011
Distribution: Slackware64
Posts: 364
Rep:
|
I'm looking into it right now. I remember getting my wacom bamboo working was interesting. I'm looking at the kernel driver details right now, and then will look at the X11 driver after.
|
|
1 members found this post helpful.
|
11-18-2013, 05:46 PM
|
#3
|
Member
Registered: Oct 2011
Distribution: Slackware64
Posts: 364
Rep:
|
OK. To be of help, I need to see output of 'lsusb -v'. From there I can check the driver code for support.
EDIT:
Really, all I need is the idProduct line.
Last edited by j_v; 11-18-2013 at 05:49 PM.
|
|
|
11-18-2013, 06:10 PM
|
#4
|
Member
Registered: Feb 2010
Location: Georgia
Distribution: Slackware64 14.2
Posts: 779
Original Poster
Rep: 
|
Quote:
Originally Posted by j_v
OK. To be of help, I need to see output of 'lsusb -v'. From there I can check the driver code for support.
EDIT:
Really, all I need is the idProduct line.
|
Thanks, this bit is beyond me.
The lsusb -v output concerning the tablet:
http://pastebin.com/jbL2LQcG
|
|
|
11-18-2013, 06:43 PM
|
#5
|
Member
Registered: Oct 2011
Distribution: Slackware64
Posts: 364
Rep:
|
OK, I found what I was looking for. Support is very new. There is some discussion on backporting a few patches for kernel and x11 drivers. I'll sort out the details and be back later with help.
EDIT:
Also, I will provide links for you to follow up in case you have further questions.
Last edited by j_v; 11-18-2013 at 06:45 PM.
|
|
1 members found this post helpful.
|
11-18-2013, 07:05 PM
|
#6
|
Member
Registered: Oct 2011
Distribution: Slackware64
Posts: 364
Rep:
|
One other thing I forgot: are you using the stock kernel (3.10.17) from installation? This is so that I can make sure driver patches apply cleanly.
|
|
|
11-18-2013, 07:06 PM
|
#7
|
Member
Registered: Feb 2010
Location: Georgia
Distribution: Slackware64 14.2
Posts: 779
Original Poster
Rep: 
|
Thanks. I might just end up returning this one since I can't easily use it right now.
edit: yeah, I'm all stock aside from using Nvidia instead of nouveau. You don't have to go to any extra trouble like that though, it isn't a really big deal.
Last edited by Cultist; 11-18-2013 at 07:07 PM.
|
|
|
11-18-2013, 07:10 PM
|
#8
|
Member
Registered: Oct 2011
Distribution: Slackware64
Posts: 364
Rep:
|
It's up to you. Should be able to have you up and going tonight, but it's your tablet. I don't mind either way.
|
|
|
11-18-2013, 07:19 PM
|
#9
|
Member
Registered: Feb 2010
Location: Georgia
Distribution: Slackware64 14.2
Posts: 779
Original Poster
Rep: 
|
Quote:
Originally Posted by j_v
It's up to you. Should be able to have you up and going tonight, but it's your tablet. I don't mind either way.
|
No worries. Probably going to hold off for now, but definitely thanks anyway.
|
|
|
11-18-2013, 07:26 PM
|
#10
|
Member
Registered: Oct 2011
Distribution: Slackware64
Posts: 364
Rep:
|
OK. Well, I'm going to finish porting the patches to 3.10.17 kernel. Also, there is the linuxwacom site: http://sourceforge.net/apps/mediawik...itle=Main_Page
Good luck.
|
|
1 members found this post helpful.
|
12-25-2013, 10:21 AM
|
#11
|
LQ Newbie
Registered: Dec 2013
Posts: 3
Rep: 
|
@j_v, can we pick this back up? I just bought a CTH-680 for my wife and am having trouble getting it to work as well. I'm comfortable compiling drivers etc. and applying patches. Can you guide me in the right direction?
|
|
|
12-25-2013, 05:32 PM
|
#12
|
Moderator
Registered: Oct 2008
Distribution: Slackware [64]-X.{0|1|2|37|-current} ::12<=X<=15, FreeBSD_12{.0|.1}
Posts: 6,315
|
Quote:
Originally Posted by jsdevel
@j_v, can we pick this back up? I just bought a CTH-680 for my wife and am having trouble getting it to work as well. I'm comfortable compiling drivers etc. and applying patches. Can you guide me in the right direction?
|
I bought a Wacom Intuos for my daughter a year ago and after a little confusion setting it up she has been VERY happy with it! It is a different model than the CTH-680 discussed in this thread, but I would be surprised if the configuration were significantly different. So, assuming you have the driver working, and patched if necessary, here is what we did...
First, for reference, hers is an Intuos-4 4x6 device. We originally installed it to Slackware 13.37, then she used it since about February 2013 under Slackware 14.0, and under Slackware 14.1 since mid-November.
She uses it intensively, almost every day, usually with the Gimp, but sometimes for other things and often as her desktop pointer input device. Hers is USB, not wireless. If you have the USB device, plug it in and look at the output of dmesg to see that it was detected. I can't help with wireless devices.
The key for me/us was to explore the options available via the xsetwacom utility, so first thing I would recommend is:
We then experimented with the various options to figure out what they actually do. Apparently the button numbers are not consistent across the devices, so we had to figure out the mappings for those, not too bad.
Then, in the Gimp we had to specify a number of options (I don't know them well enough but will ask her for pointers if that would be helpful).
We then wrote our own scripts to configure the device for our own environments. Mine looks like this (with my reminder comments included...):
Code:
#!/bin/bash
# See man xsetwacom for all details
# xsetwacom [options] [command [arguments]]
# options: -d, -h, -v, -V
# commands: list, get, set
# Example useful commands (space is signifigant in commands):
# xsetwacom get 'Wacom Intuos4 4x6 pad' all
# xsetwacom get 'Wacom Intuos4 4x6 pad' Button 11
# (ex. return) key +Control_L +z -z
# xsetwacom set "Wacom Intuos4 4x6 pad" Device "Action"
# Device must one from following list, Action must include 'key' if key
# Example: xsetwacom set "Wacom Intuos4 4x6 pad" Button 11 "key ctrl z"
# Complex actions may be scripted using + or - prefix before key actions
#Button order (Device) top to bottom:
# Button 2
# Button 3
# Button 8
# AbsWheelDown (Ring CW)
# Button 1 (in ring)
# AbsWheelUP (Ring CCW)
# Button 9
# Button 10
# Button 11
# Gimp key codes may be mapped to buttons (not case sensitive)
# a = airbrush
# n = pencil
# p = paintbrush
# ctrl +z = Undo
# ctrl +y = Redo
# ctrl +j = Shrink wrap
# shift b = bucket fill
# shift plus = '+' key
# minus = '-' key
# shift = shift key
# ctrl = ctrl key
# alt = alt key
# backspace = backspace key
# ctrl alt shift o = brush down
# ctrl alt shift p = brush up
#
# Top buttons
xsetwacom set "Wacom Intuos4 4x6 pad" Button 2 "key n"
xsetwacom set "Wacom Intuos4 4x6 pad" Button 3 "key p"
xsetwacom set "Wacom Intuos4 4x6 pad" Button 8 "key shift"
#Ring
xsetwacom set "Wacom Intuos4 4x6 pad" AbsWheelDown "key shift +plus"
xsetwacom set "Wacom Intuos4 4x6 pad" Button 1 "key ctrl +shift +a -a -shift -ctrl +1" # button inside touchring, zoom 100%
xsetwacom set "Wacom Intuos4 4x6 pad" AbsWheelUp "key minus"
#Bottom buttons
xsetwacom set "Wacom Intuos4 4x6 pad" Button 9 "key ctrl +j"
xsetwacom set "Wacom Intuos4 4x6 pad" Button 10 "key ctrl +y"
xsetwacom set "Wacom Intuos4 4x6 pad" Button 11 "key ctrl +z"
Last edited by astrogeek; 12-25-2013 at 06:25 PM.
|
|
1 members found this post helpful.
|
12-26-2013, 05:54 PM
|
#13
|
Member
Registered: Oct 2011
Distribution: Slackware64
Posts: 364
Rep:
|
I'm working on some slackbuilds that will have the support for the intuos cth680 and some other recent models. If they test out ok, I will post them to my github account and leave a post here with a link. Be aware that I can't test the cth680 itself, only that the module and driver work generally (I have a ctl470).
Update:
I've tested builds of most recent module and xorg driver, and these work fine here. I have to finish writing the actual slackbuilds, but these should be ready within the hour.
Last edited by j_v; 12-26-2013 at 08:03 PM.
Reason: update
|
|
|
12-26-2013, 09:16 PM
|
#15
|
Member
Registered: Oct 2011
Distribution: Slackware64
Posts: 364
Rep:
|
Also, I think that you should look at astrogeek's setup script. While I suspect your model is slightly newer, his script should be straight forward to edit for your hardware, if needed.
|
|
|
All times are GMT -5. The time now is 10:44 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|