How to set up a Wacom Tablet
Relax, only for reference >> http://linuxwacom.sourceforge.net/wiki/ ... /Main_Page
With your device plugged, does Lupu "see" it?
With your device plugged, does Lupu "see" it?
Code: Select all
dmesg | grep -i wacom
>>> Living with the immediacy of death helps you sort out your priorities. It helps you live a life less trivial <<<
Code: Select all
# dmesg | grep -i wacom
usbcore: registered new interface driver wacom
wacom: v1.52:USB Wacom tablet driver
Show us this:
And if this returns anything. I'll need to look over the opening post..
Is this your "Small" item?
Code: Select all
lsusb -vv | grep Intuos
Code: Select all
xsetwacom --list devices
Code: Select all
lsusb -vv | grep Intuos
I've find a file at /etc/X11 "wacom_xorgdotconf_bits" explaining how to modify the xorg.conf file, it seems it was installed by the wacom driver, but when I did that, X crashed, I had to go back to the backup xorg.conf
That opening char can only be *one of two* keyboard choices.
Try again, though this time. And please, only the device in question:
Then, one @ a time now:
Attach the above /root/wacom_xorgdotconf_bits.gz file with your reply.
==
And what you should probably do in the meantime is look over the opening post.
It appears someone there's done most of the investigative work for'ya!
Try again, though this time. And please, only the device in question:
Code: Select all
lsusb -vv
Code: Select all
cp /etc/X11/wacom_xorgdotconf_bits /root
gzip /root/wacom_xorgdotconf_bits
==
And what you should probably do in the meantime is look over the opening post.
It appears someone there's done most of the investigative work for'ya!
>>> Living with the immediacy of death helps you sort out your priorities. It helps you live a life less trivial <<<
let's see. I have to admit I don't understand 100% what I'm doing or what I should do..
Output, just the wacom plugged to teh computer, no other usb device
attached, the wacom_xorgdotconf txt file
Output, just the wacom plugged to teh computer, no other usb device
Code: Select all
# lsusb -vv
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0001
Bus 003 Device 001: ID 1d6b:0001
Bus 004 Device 001: ID 1d6b:0001
Bus 005 Device 001: ID 1d6b:0001
Bus 006 Device 001: ID 1d6b:0001
Bus 005 Device 002: ID 056a:0026
#
- Attachments
-
- wacom_xorgdotconf_bits.txt.gz
- (900 Bytes) Downloaded 279 times
If this is your device, you may need a pup with a newer kernel than Lucid.
Is that an old box that would struggle to run a current pup?
==
Run and post the output here:
Code: Select all
056a:0026
PTH-450
Intuos5 touch (S)
Kernel 3.5 or better
Input-wacom v2.6.30† << Touch features of tablet unavailable prior to 2.6.38
==
Run and post the output here:
Code: Select all
xsetwacom --list devices
Well, if you had an older device you'd probably be OK.
Tahr offers a few compatible kernel options.
Run the code line in my last post and let's see the return..
Tahr offers a few compatible kernel options.
Run the code line in my last post and let's see the return..
Go with this one:
Use wget and reduce the possibility of browser corruption.
Then run the checksum from the same directory:
b183cdb5cd0a1a6c3314d2d7f2ddd6ff
PS -- High speed Internet?
Code: Select all
wget http://ftp.nluug.nl/ftp/pub/os/Linux/distr/puppylinux/puppy-tahr/iso/tahrpup%20-6.0-CE/tahr-6.0.5_noPAE.iso
Then run the checksum from the same directory:
Code: Select all
md5sum tahr-6.0.5_noPAE.iso
PS -- High speed Internet?
fernan, I've used Wacom tablets on older Puppies. It can be a hassle to set up, but you can probably get yours working with your favored OS. Even if a newer Puppy can detect it, it can still be annoyingly complicated to get it to recognise pressure for painting.
I have my Intuos Pen and Touch Small working on Puppy 6.3.2 Slacko. I installed xf86-input-wacom-0.19.0-i486-4.txz (You'd need a different driver for your Puppy.) It automatically picked up the tablet, but acted only as a mouse. And xsetwacom didn't recognise the tablet.
I edited /lib/udev/rules.d/60-wacom.rules to be:
I'm sure much of it was unnecessary.
Then I pointed the stylus and eraser entries in /etc/X11/xorg.conf to /dev/input/wacom. If you want touch capability then you'd do so with it too. (I don't like the touch function. I drives me nuts that bumping it with my hand moves the cursor.)
I can't remember if I created the /dev/input/wacom link to /dev/input/event5 or whether the above wacom rules file made them. There are /dev/input/tablet-intuos-pts-4x6 and /dev/input/wacom-touch links to /dev/input/event5 and /dev/input/event6 respectively that I'm pretty sure the rules file created. I don't understand the rules file well enough to know whether the line I added:
did that or whether it would have found the name by itself.
Note that "056a" (the Vendor) represents Wacom, and "0302" represents my Intuos PTS device. You can find the code for your device by using the lsusb command in a terminal or by using the information entry in the main Puppy menu, usually under the System sub-menu. The item is usually called HardInfo or Sys-Info or something like that. Look for the section on USB devices. You'll find the code there.
Here is my /etc/X11/xorg.conf:
Hmmm... I just now noticed that I have two entries in the Section "ServerLayout" part for InputDevice "stylus" and "eraser", first with option "SendCoreEvents" and then without. I can't remember why, and I'm sure both aren't needed. But it works, so I am reluctant to spend time changing it.
Note that you should only copy the Wacom related parts to your xorg.config file (the bits in the Section "ServerLayout" and the large part at the end I've marked as Wacom). The other parts will probably mess up your display. Once you've got it working satisfactorily make a copy of the xorg.config (I called my copy "xorg.config.wacom-working") because if you change the display Puppy will make a new xorg.config file without your wacom-related edits. It will back up the file, but you'll have to go through the files to work out which one. Saving it with an informative name makes life easier for you.
I hope this helps and that you have an easier time getting your Wacom tablet working than I did.
I've set up a few different tablets on several of my computers over the years. The old Amiga computer was probably the easiest (that computer was decades ahead of its time). Microsoft Windows was easy, but that's natural as Microsoft has control of the commercial market (hate that OS). Linux has, sadly, been a royal pain in the ass every time trying to get it to even recognise the tablet, let alone use all its capabilities... though it is starting to get easier, thank goodness.
Good luck.
I have my Intuos Pen and Touch Small working on Puppy 6.3.2 Slacko. I installed xf86-input-wacom-0.19.0-i486-4.txz (You'd need a different driver for your Puppy.) It automatically picked up the tablet, but acted only as a mouse. And xsetwacom didn't recognise the tablet.
I edited /lib/udev/rules.d/60-wacom.rules to be:
Code: Select all
# From https://wiki.archlinux.org/index.php/Wacom_Tablet
ACTION!="add|change", GOTO="wacom_end"
# Match all wacom tablets with a serial ID starting with WACf or FUJ*
ATTRS{id}=="WACf*" ENV{NAME}="Serial Wacom Tablet", ENV{ID_INPUT}="1", ENV{ID_INPUT_TABLET}="1"
ATTRS{id}=="FUJ*" ENV{NAME}="Serial Wacom Tablet", ENV{ID_INPUT}="1", ENV{ID_INPUT_TABLET}="1"
# LABEL="wacom_end"
KERNEL!="event[0-9]*", GOTO="wacom_end"
# Port specific link for users of multiple tablets of the same type.
# The ID_PATH variable is set by the "path_id" script in an earlier rule file.
ATTRS{idVendor}=="056a", ENV{ID_PATH}=="?*", SYMLINK="input/by-path/$env{ID_PATH}-wacom"
# Multiple interface support for stylus and touch devices.
DRIVERS=="wacom", ATTRS{bInterfaceNumber}=="00", ENV{WACOM_TYPE}="stylus"
DRIVERS=="wacom", ATTRS{bInterfaceNumber}=="01", ENV{WACOM_TYPE}="touch"
# Type-named links for multiple tablets. If you want to use multiple
# tablets of the _same_ type, you will probably need to use the links
# from /dev/input/by-path to identify which is plugged into what usb
# port. For different tablet types though, just pick your links from
# the list below.
#
# We override SYMLINK for tabletpc devices because the by-path link
# is not required with such devices, there will only ever be one.
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0000", SYMLINK+="input/tablet-penpartner"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0003", SYMLINK+="input/tablet-cintiq_partner"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0010", SYMLINK+="input/tablet-graphire"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0011", SYMLINK+="input/tablet-graphire2-4x5"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0012", SYMLINK+="input/tablet-graphire2-5x7"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0013", SYMLINK+="input/tablet-graphire3"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0014", SYMLINK+="input/tablet-graphire3-6x8"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0015", SYMLINK+="input/tablet-graphire4-4x5"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0016", SYMLINK+="input/tablet-graphire4-6x8"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0017", SYMLINK+="input/tablet-bamboofun-4x5"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0018", SYMLINK+="input/tablet-bamboofun-6x8"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0019", SYMLINK+="input/tablet-bamboo1-medium"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0020", SYMLINK+="input/tablet-intuos-4x5"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0021", SYMLINK+="input/tablet-intuos-6x8"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0022", SYMLINK+="input/tablet-intuos-9x12"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0023", SYMLINK+="input/tablet-intuos-12x12"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0024", SYMLINK+="input/tablet-intuos-12x18"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0030", SYMLINK+="input/tablet-pl400"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0031", SYMLINK+="input/tablet-pl500"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0032", SYMLINK+="input/tablet-pl600"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0033", SYMLINK+="input/tablet-pl600sx"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0034", SYMLINK+="input/tablet-pl550"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0035", SYMLINK+="input/tablet-pl800"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0037", SYMLINK+="input/tablet-pl700"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0038", SYMLINK+="input/tablet-pl510"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0039", SYMLINK+="input/tablet-dtu710"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="003f", SYMLINK+="input/tablet-cintiq21ux"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0041", SYMLINK+="input/tablet-intuos2-4x5"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0042", SYMLINK+="input/tablet-intuos2-6x8"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0043", SYMLINK+="input/tablet-intuos2-9x12"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0044", SYMLINK+="input/tablet-intuos2-12x12"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0045", SYMLINK+="input/tablet-intuos2-12x18"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0047", SYMLINK+="input/tablet-intuos2-6x8a"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0060", SYMLINK+="input/tablet-volito"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0061", SYMLINK+="input/tablet-penstation2"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0062", SYMLINK+="input/tablet-volito2-4x5"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0063", SYMLINK+="input/tablet-volito2-2x3"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0064", SYMLINK+="input/tablet-penpartner2"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0065", SYMLINK+="input/tablet-bamboo"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0069", SYMLINK+="input/tablet-bamboo1"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0081", SYMLINK+="input/tablet-graphire_bt-6x8"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0090", SYMLINK="input/tablet-tpc90"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0093", SYMLINK="input/tablet-tpc93-$env{WACOM_TYPE}"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="009a", SYMLINK="input/tablet-tpc9a-$env{WACOM_TYPE}"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00b0", SYMLINK+="input/tablet-intuos3-4x5"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00b1", SYMLINK+="input/tablet-intuos3-6x8"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00b2", SYMLINK+="input/tablet-intuos3-9x12"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00b3", SYMLINK+="input/tablet-intuos3-12x12"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00b4", SYMLINK+="input/tablet-intuos3-12x19"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00b5", SYMLINK+="input/tablet-intuos3-6x11"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00b7", SYMLINK+="input/tablet-intuos3-4x6"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00b8", SYMLINK+="input/tablet-intuos4-4x6"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00b9", SYMLINK+="input/tablet-intuos4-6x9"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00ba", SYMLINK+="input/tablet-intuos4-8x13"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00bb", SYMLINK+="input/tablet-intuos4-12x19"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00c0", SYMLINK+="input/tablet-dtf521"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00c4", SYMLINK+="input/tablet-dtf720"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00c5", SYMLINK+="input/tablet-cintiq20wsx"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00c6", SYMLINK+="input/tablet-cintiq12wx"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00c7", ENV{WACOM_TYPE}!="touch", SYMLINK+="input/tablet-dtu1931"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0302", SYMLINK+="input/tablet-intuos-pts-4x6"
# Convenience links for the common case of a single tablet. We could do just this:
#ATTRS{idVendor}=="056a", SYMLINK+="input/wacom-$env{WACOM_TYPE}"
# but for legacy reasons, we keep the input/wacom link as the generic stylus device.
ATTRS{idVendor}=="056a", ENV{WACOM_TYPE}!="touch", SYMLINK+="input/wacom"
ATTRS{idVendor}=="056a", ENV{WACOM_TYPE}=="touch", SYMLINK+="input/wacom-touch"
# Check and repossess the device if a module other than the wacom one
# is already bound to it.
#
# We probably don't need this one in the Real World anymore ...
# See the old wacom-tools package if we actually do need to resurrect the
# check_driver script for this again.
#ATTRS{idVendor}=="056a", ACTION=="add", RUN+="check_driver wacom $devpath $env{ID_BUS}"
LABEL="wacom_end"
Then I pointed the stylus and eraser entries in /etc/X11/xorg.conf to /dev/input/wacom. If you want touch capability then you'd do so with it too. (I don't like the touch function. I drives me nuts that bumping it with my hand moves the cursor.)
I can't remember if I created the /dev/input/wacom link to /dev/input/event5 or whether the above wacom rules file made them. There are /dev/input/tablet-intuos-pts-4x6 and /dev/input/wacom-touch links to /dev/input/event5 and /dev/input/event6 respectively that I'm pretty sure the rules file created. I don't understand the rules file well enough to know whether the line I added:
Code: Select all
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0302", SYMLINK+="input/tablet-intuos-pts-4x6"
Note that "056a" (the Vendor) represents Wacom, and "0302" represents my Intuos PTS device. You can find the code for your device by using the lsusb command in a terminal or by using the information entry in the main Puppy menu, usually under the System sub-menu. The item is usually called HardInfo or Sys-Info or something like that. Look for the section on USB devices. You'll find the code there.
Here is my /etc/X11/xorg.conf:
Code: Select all
#barry Kauler 2011
#pre-constructed xorg.conf, for use by /usr/sbin/xorgwizard-automatic
#110627 working on mageia1 build, this needs fixing.
#111029 Terryphi reported 1cm screen displacement, changed vert freq range from 56-76 to 59-76.
#120329 more placemarkers for xorgwizard-automatic script.
#121013 change depth from 16 to 24. note, some arm boards need 16.
# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"
# Load "synaptics" #loadsynaptics
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
# This loads the font modules
# Load "type1"
# Load "freetype"
# This loads xtrap extension, used by xrandr
# Load "xtrap"
# This loads the GLX module (if present). xorg 7.4/5, need explicit disable to disable... change "Disable" to "Load" if reqd...
# Disable "glx" #LOADGLX
# This loads dri module (if present). 7.4 loads it by default, have to disable... change "Disable" to "Load" if reqd...
# Disable "dri" #LOADDRI
EndSection
# **********************************************************************
# Files section. This allows default font paths to be set
# **********************************************************************
Section "Files"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#FontPath "/usr/share/fonts/X11/misc/"
#FontPath "/usr/share/fonts/liberation/"
FontPath "/usr/share/X11/fonts/misc/"
FontPath "/usr/share/X11/fonts/Type1/"
FontPath "/usr/share/X11/fonts/TTF/"
EndSection
# **********************************************************************
# Server flags section.
# **********************************************************************
Section "ServerFlags"
# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# Enables mode switching with xrandr
# There is a report that this can cause Xorg not to work on some
# video hardware, so default is commented-out...
# but i want to use it in xorgwizard so leave on...
Option "RandR" "on"
# With this, Xorg won't talk to HAL to add evdev devices and you'll be back
# with the old Xorg behavior (pre-7.4)...
Option "AutoAddDevices" "false"
# For no-Hal, kirk also suggests this...
# Option "AllowMouseOpenFail" "true"
# Xorg 7.4, Ubuntu Jaunty, CTRL-ALT-BACKSPACE is disabled by default...
Option "DontZap" "false"
EndSection
Section "ServerLayout"
# InputDevice "Synaptics Mouse" "AlwaysCore" #serverlayoutsynaptics
Identifier "X.org Configured"
InputDevice "stylus" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
# InputDevice "pad" # For Intuos3/CintiqV5/Graphire4/Bamboo tablets
# InputDevice "cursor" "SendCoreEvents" # For non-LCD tablets only
# InputDevice "touch" "SendCoreEvents" # few TabletPCs support this
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "stylus"
InputDevice "eraser"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc102" #xkbmodel0
Option "XkbLayout" "us" #xkeymap0
#Option "XkbVariant" "" #xkbvariant0
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2" #mouse0protocol
Option "Device" "/dev/mouse"
#Option "Emulate3Buttons"
#Option "Emulate3Timeout" "50"
Option "ZAxisMapping" "4 5" #scrollwheel
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 35-81
VertRefresh 59-76
#UseModes "Modes0" #monitor0usemodes
Option "PreferredMode" "1600x900" #monitor0prefmode
EndSection
Section "Modes"
Identifier "Modes0"
#modes0modeline0
EndSection
#110627 remove...
##server can find BusID automatically, comment out...
#Section "Device"
# Identifier "Card0"
# Driver "vesa" #card0driver
# VendorName "Unknown Vendor"
# BoardName "Unknown Board"
## BusID "PCI:0:2:0" #card0busid
#EndSection
Section "Screen"
Identifier "Screen0"
# Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
#Option "metamodes" "1280x800_60 +0+0" #METAMODES_0
Subsection "Display"
Depth 24
Modes "1600x900" #screen0modes
EndSubsection
EndSection
#PuppyHardwareProfile=ATI_ATOMBIOSSA300_SA350
########################################
# Wacom
########################################
Section "InputDevice"
Identifier "stylus"
Driver "wacom"
Option "Device" "/dev/input/wacom" # USB ONLY
Option "Type" "stylus"
Option "USB" "on" # USB ONLY
Option "GrabDevice" "1"
Option "Mode" "Absolute"
Option "AlwaysCore" "on"
Option "Speed" "1.3"
Option "Threshold" "5"
Option "CursorProx" "5"
## Option "Speed" "5"
## # Option "ForceDevice" "ISDV4" # Serial Tablet PC ONLY
EndSection
Section "InputDevice"
Identifier "eraser"
Driver "wacom"
Option "Device" "/dev/input/wacom" # USB ONLY
Option "Type" "eraser"
Option "USB" "on" # USB ONLY
Option "GrabDevice" "1"
Option "Mode" "Absolute"
EndSection
#Section "InputDevice"
# Identifier "touch"
# Driver "wacom"
## Option "Device" "/dev/input/wacom" # USB ONLY
# Option "Type" "touch"
# Option "USB" "on" # USB ONLY
# Option "GrabDevice" "1"
#EndSection
#Section "InputDevice"
# Identifier "pad"
# Driver "wacom"
## Option "Device" "/dev/input/wacom" # USB ONLY
# Option "Type" "pad"
# Option "USB" "on" # USB ONLY
# Option "GrabDevice" "1"
## Option "SendCoreEvents" "false"
# Option "ButtonsOnly" "on"
# Option "Button9" "2"
# Option "Button13" "3"
# Option "Mode" "Absolute"
#EndSection
#Section "InputDevice"
# Identifier "cursor"
# Driver "wacom"
# Option "Device" "/dev/input/wacom" # USB ONLY
# Option "Type" "cursor"
# Option "USB" "on" # USB ONLY
#EndSection
Note that you should only copy the Wacom related parts to your xorg.config file (the bits in the Section "ServerLayout" and the large part at the end I've marked as Wacom). The other parts will probably mess up your display. Once you've got it working satisfactorily make a copy of the xorg.config (I called my copy "xorg.config.wacom-working") because if you change the display Puppy will make a new xorg.config file without your wacom-related edits. It will back up the file, but you'll have to go through the files to work out which one. Saving it with an informative name makes life easier for you.
I hope this helps and that you have an easier time getting your Wacom tablet working than I did.
I've set up a few different tablets on several of my computers over the years. The old Amiga computer was probably the easiest (that computer was decades ahead of its time). Microsoft Windows was easy, but that's natural as Microsoft has control of the commercial market (hate that OS). Linux has, sadly, been a royal pain in the ass every time trying to get it to even recognise the tablet, let alone use all its capabilities... though it is starting to get easier, thank goodness.
Good luck.
Last edited by miriam on Tue 11 Oct 2016, 23:10, edited 1 time in total.
- charlie6
- Posts: 1230
- Joined: Mon 30 Jun 2008, 04:03
- Location: Saint-Gérard / Walloon part of Belgium
@fernan
@miriam
Hi,
my apologize if late posting
Just bringing up my cent to your posts on pages 25 and 26:
Here at now running a CTF-420 wacom tablet on the latest Tahr64-6.0.6 (it's a Volito2 type one;
fernan's one is a PTH-450 intuos5 serie which type is listed in/var/log/Xorg.0.log if plugged to the PC; restart X if plugged afterwards).
I assume it should run the same way on other recent puppies like Slaco-6.3.2.
On recent puppies, the wacom tablet should work quite OOTB after doing the following (recent Puppies comes with wacom driver embedded):
settings for using a wacom tablet (xorg.conf, udev rules..):
NB: here running a pristine puppy session from a live-cd.
1) udev rules:
here no need to edit the embedded udev rules.
2) xorg.conf settings:
2.1.) the Section "ServerLayout" is edited by ADDING the following just before its "EndSection" line.
After editing, it looks then as:
From having experienced it, no need modifying the other lines. Also, the "SendCoreEvents" string is no longer required for kernels 2.6.35 and later (see linux wacom website documentation).
2.2) Between the next xorg.conf sections:
...just add the following:
2.3.) save xorg.conf and restart X to activate the new xorg.conf settings.
3.) Now be sure the wacom driver is loaded by doing in a terminal:
4.) check that all wacom tablets features are recognized by doing in a terminal:
Now the tablet should run as expected !
HTH,
Charlie
@miriam
Hi,
my apologize if late posting
Just bringing up my cent to your posts on pages 25 and 26:
Here at now running a CTF-420 wacom tablet on the latest Tahr64-6.0.6 (it's a Volito2 type one;
fernan's one is a PTH-450 intuos5 serie which type is listed in/var/log/Xorg.0.log if plugged to the PC; restart X if plugged afterwards).
I assume it should run the same way on other recent puppies like Slaco-6.3.2.
On recent puppies, the wacom tablet should work quite OOTB after doing the following (recent Puppies comes with wacom driver embedded):
settings for using a wacom tablet (xorg.conf, udev rules..):
NB: here running a pristine puppy session from a live-cd.
1) udev rules:
here no need to edit the embedded udev rules.
2) xorg.conf settings:
2.1.) the Section "ServerLayout" is edited by ADDING the following just before its "EndSection" line.
Code: Select all
#from kernel 2.6.35 and later the "SendCoreEvents" after InputDevice is no longer required
InputDevice "stylus"
InputDevice "eraser"
InputDevice "cursor"
InputDevice "pad"
Code: Select all
Section "ServerLayout"
# InputDevice "Synaptics Mouse" "AlwaysCore" #serverlayoutsynaptics
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
#from kernel 2.6.35 and later the "SendCoreEvents" after InputDevice is no longer required
InputDevice "stylus"
InputDevice "eraser"
InputDevice "cursor"
InputDevice "pad"
EndSection
2.2) Between the next xorg.conf sections:
Code: Select all
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc102" #xkbmodel0
Option "XkbLayout" "be" #xkeymap0
#Option "XkbVariant" "" #xkbvariant0
Option "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2" #mouse0protocol
Option "Device" "/dev/mouse"
#Option "Emulate3Buttons"
#Option "Emulate3Timeout" "50"
Option "ZAxisMapping" "4 5" #scrollwheel
EndSection
Code: Select all
Section "InputDevice"
Identifier "stylus"
Driver "wacom"
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "USB" "on"
Option "GrabDevice" "1"
# Option "Mode" "Absolute"
Option "Mode" "Relative"
# Option "AlwaysCore" "on"
Option "Speed" "1.0"
Option "Threshold" "5"
Option "CursorProx" "5"
# Option "Speed" "5"
# # Option "ForceDevice" "ISDV4" # Serial Tablet PC ONLY
EndSection
Section "InputDevice"
Identifier "eraser"
Driver "wacom"
Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "USB" "on"
Option "GrabDevice" "1"
EndSection
Section "InputDevice"
Identifier "cursor"
Driver "wacom"
Option "Device" "/dev/input/wacom" # USB ONLY
Option "Type" "cursor"
Option "USB" "on" # USB ONLY
Option "Mode" "Relative"
Option "GrabDevice" "1"
Option "CursorProx" "5"
Option "Speed" "1.0"
EndSection
Section "InputDevice"
Identifier "pad"
Driver "wacom"
Option "Device" "/dev/input/wacom" # USB ONLY
Option "Type" "pad"
Option "USB" "on" # USB ONLY
Option "GrabDevice" "1"
EndSection
3.) Now be sure the wacom driver is loaded by doing in a terminal:
Code: Select all
root# modprobe wacom
root# lsmod | grep wacom
wacom 42600 0
root#
Code: Select all
root# xsetwacom --list devices
stylus id: 8 type: STYLUS
eraser id: 9 type: ERASER
cursor id: 10 type: CURSOR
pad id: 11 type: PAD
root#
HTH,
Charlie