The Linux Wacom Project
| ![]() |
![]() | |
![]() | |
Main | News | FAQ | Downloads | Documentation | Help | Development | TOC | All | Jun 06, 2007 |
![]() | |
![]() |
Linux Wacom Project HOWTOPermission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. 1.0 - IntroductionThis document began in November 2002 as a HOWTO for setting up a USB Wacom Intuos2 on Redhat 8.0. It has since grown to cover all Wacom tablets, USB and serial, running on various different Linux distributions. As of December 2002, this project has transformed into the Linux Wacom Project. Work on this document is on-going so if you find an error, have a question, or have something to add, please send an email to: linuxwacom-discuss@lists.sf.net. 1.1 - Success Stories
1.2 - How To Use This DocumentIn terms of document organization, if you have not figured it out already, you can browse the document one page at a time, or you can click on the ALL link and view the entire thing in one long page.
Also, it bears mentioning since it's a detail often missed: there are two drivers in the Linux Wacom Project- wacom.o and wacom_drv.o. The first driver is the USB kernel driver. The second driver is the XFree86 Wacom driver. Serial users need only be concerned with the wacom_drv.o driver. USB users need both. If you try to use the wacom_drv.o driver in place of the wacom.o kernel driver or visa-versa, things generally won't work. Next, this document was written with the assumption that you are starting from scratch with a relatively recent distribution of the Linux kernel. Also, if you have already added lines to your XFree86/Xorg configuration file (XF86Config/XF86Config-4 or xorg.conf), you should comment them out and restart X. Since we'll be stepping through the entire process, we need X to ignore the tablet until we're ready. Otherwise, X will just get in the way. Finally, if you know what you're doing, you can leave your X settings intact, print this out, switch to runlevel 3, and follow along from the console. An HTML version of this document can be found in the docs directory at docs.html. 1.3 - Wacom Driver Theory of OperationSerial Tablet Operation - The Short Story USB Tablet Operation - The Long Story Embedded Device Operation - Tablet PC with Wacom Digitizer Refer to Tablet PC page for detail. 2.0 - Getting It TogetherIncidentally, some distributions detect new hardware on boot. If you allow Redhat's "anaconda" for instance to automatically configure (or remove) your USB tablet, it may undo some of the settings you will make here. Until Redhat's installation program recognizes Wacom tablets as non-HID devices by default, you are best off in my opinion to not allow it to configure the device. Just a warning. 2.1 - Before We StartIf you have a USB tablet, you need to check Wacom kernel drvier first The USB Kernel Driver. Serial tablet or Tablet PC users can go directly to the next section Downloading the Code page. 2.2 - Downloading the CodeThe file linuxwacom-0.7.6-4.tar.bz2 is the stable package and contains files that you will need to get your serial or USB tablet working. The current beta package linuxwacom-0.7.7-11.tar.bz2 is also available and may be used by people who are willing to help test new features. I will never put a beta package on this site that I am not running myself on my primary development machine. So you can be certain that if there are any obvious show stoppers, they will be fixed before you get to see them.Unpacking the tarball is usually a one-step process, but I show both steps in case the typical -jxf option doesn't work with tar. Once in the package directory, you need only to configure and build the code. This is described in more detail as you continue. The executables and wacom_drv.o are installed automatically; the kernel drivers have different installation procedures depend on the kernel source you use.[jej@ayukawa jej]$ bunzip2 linuxwacom-0.7.6-4.tar.bz2 [jej@ayukawa jej]$ tar -xf linuxwacom-0.7.6-4.tar [jej@ayukawa jej]$ cd linuxwacom-0.7.6-4 If you are interested, the following tables contain the package contents and release dates. Otherwise, let's continue. Stable files included for linuxwacom-0.7.6-4:
Stable Packages by Version and Date:
Beta Packages by Version and Date:
2.3 - Configuring the PackageThe Configure ScriptBuilding Kernel Modules - USB OnlyIn order to build kernel modules, you will need the kernel source installed on your system. If you are running on Redhat or Mandrake, you can get it by installing the kernel-source RPM.Note, for kernel 2.6.18 and later, no need to build hid any more. Refer to Testing Tablet Detection to see if you need to build hid or not. Module Versioning - USB OnlyThe script attempts to discover if the kernel is using module versioning by detecting the presence of version numbers in the hid.o module of the currently active kernel. Recent package versions also check for hid.o.gz which exist on Mandrake systems. The configure script may not be able to d etermine if kernel module versioning should be enabled or not, in which case it will say "unknown, assuming no." If module versioning is disabled when it should be enabled, depmod will complain about missing symbols but otherwise, things will probably work fine. If it is enabled when it should be disabled, the code may not compile, and it almost certainly will not load properly. If the configure script fails to determine the correct value, the default action of disabling module versioning is the better choice, and you can allows enable it manually and rebuild if depmod complains. The XFree86/Xorg XInput Driver - USB and SerialGenerally, you will not need to build wacom_drv.o since it ships in binary form in the prebuilt directory. There are prebuilt binaries for XFree86 and Xorg corresponding to x86 and x86-64 systems, respectively. If no one works for you, building from source may be your only option. See the Building wacom_drv.o from Scratch page for more information. Library Dependencies - ncurses and XLibVarious utilities in the linuxwacom package require not only specific libraries, but their development header files as well. The ncurses package is one such example. Most distributions install the ncurses libraries by default, but the header files are often located in a separate package. You will need both. On Redhat 8.0, they can be found in the ncurses-devel RPM. Similarly, if you wish to test your tablet using xidump to view XFree86 input events, you will need the XFree86 development headers. On Redhat, they are contained in the XFree86-devel package. If any packages are missing, the configuration will warn you and disable building any programs that depend on them. Processor TypeThe processor type is determined by the script and used to build the kernel modules. If it guesses incorrectly, or you would prefer a different setting, use the --with-arch option described below. Linux Specific FeaturesThe Linux wacom driver uses the Linux input subsystem, as does the USB portions of the XFree86 driver. Consequently, if you are building on a non-Linux system, the USB code will not work for you. This is detected, and a comment to that effect is added to the configuration summary. I recognize that FreeBSD and similar systems have USB support; however, until someone can bridge the gap between the FreeBSD kernel and the XFree86 driver, the problem is largely unsolved. Contributions are of course welcome. The Linux-specific features can be enabled/disabled using the --with-linux argument. Configuration OptionsThe following options are provided as reference. Normally, you will only need a few of these options, but more obscure systems may need all of them. Each section of the document identifies which options are necessary and when.
Configuration SamplesHere is a sample output of the script on a Redhat 8.0 system: [jej@ayukawa linuxwacom]$ ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes ... checking for processor type... i686 checking for kernel module versioning... yes checking for kernel sources... /usr/src/linux checking for XLib include directory... found checking for XLib header files... found ... checking for ncurses.h... yes ... ---------------------------------------- BUILD ENVIRONMENT: architecture - i686 linux kernel - yes 2.4 module versioning - yes kernel source - yes /usr/src/linux XFree86 - no XLib - yes TCL - yes /usr TK - yes /usr ncurses - yes GTK - 2.0.6 BUILD OPTIONS: wacom.o - no wacdump - yes xidump - yes libwacomcfg - yes libwacomxi - yes xsetwacom - yes hid.o - no usbmouse.o - no evdev.o - no mousedev.o - no input.o - no tabletdev.o - no wacom_drv.o - no ---------------------------------------- If the configure script fails to find something that it is looking for, it may disable some options that you previously enabled on the command-line. If this happens, check the output for a warning like the following: *** *** WARNING: *** Unable to compile wacom_drv.o without XF86 build environment *** wacom_drv.o will not be built *** In this particular case, the XFree86 driver was enabled, but the --with-xf86 option was not specified. Without the build environment, the module cannot be compiled and was consequently disabled. The following sample command-line will build everything but wacdump while disabling module versioning. It also has a user-specified kernel source directory: [jej@ayukawa linuxwacom]$ ./configure --enable-hid --enable-usbmouse \ --enable-evdev --enable-moudedev --enable-input --enable-wacom \ --with-xf86=/usr/src/redhat/BUILD/XFree86-4.2.0 \ --with-kernel=/home/jej/src/linux --with-tcl=/usr/local/ActiveTcl \ --disable-modver --disable-wacdump checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes ... checking for processor type... i686 checking for kernel module versioning... yes checking for kernel sources... /usr/src/linux-2.4 checking for valid XFree86 build environment... ok ... ---------------------------------------- BUILD ENVIRONMENT: architecture - i686 linux kernel - yes 2.4 module versioning - no kernel source - yes /home/jej/src/linux XFree86 - yes /usr/src/redhat/BUILD/XFree86-4.2.0 XLib - yes /usr/X11R6/lib TCL - yes /usr/local/ActiveTcl TK - yes /usr/local/ActiveTcl ncurses - yes GTK - 2.0.6 BUILD OPTIONS: wacom.o - yes wacdump - no xidump - yes libwacomcfg - yes libwacomxi - yes xsetwacom - yes hid.o - yes usbmouse.o - yes evdev.o - yes mousedev.o - yes input.o - yes tabletdev.o - no wacom_drv.o - yes ---------------------------------------- Notice that the configure script guessed module versioning was enabled by default, but was disabled by the command-line option --disable-modver. Similarly, the wacdump program which is enabled by default was also disabled. All the kernel modules and the XFree86 wacom driver are enabled. Here is another sample from Red Hat Enterprise Linux ES v.4: [jej@ayukawa linuxwacom-x86-64]$ ./configure --enable-wacom --enable-hid \ --with-xf86=/home/jej/Desktop/X11R6.8 \ --with-tcl=/usr/local/ActiveTcl \ --enable-xserver64 --with-xlib=/usr/X11R6/lib64 checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes ... checking build system type... x86_64-redhat-linux-gnu checking host system type... x86_64-redhat-linux-gnu checking for ld used by g++... /usr/bin/ld -m elf_x86_64 ... ---------------------------------------- BUILD ENVIRONMENT: architecture - x86-64 linux kernel - yes 2.6.9 module versioning - yes -DCONFIG_MODVERSIONS -DMODVERSIONS -include /usr/src/linux/include/linux/modversions.h kernel source - yes /usr/src/linux XFree86 - yes /home/jej/Desktop/X11R6.8 XSERVER64 - yes XLib - yes /usr/X11R6/lib64 TCL - yes /usr/local/ActiveTcl TK - yes /usr/local/ActiveTcl ncurses - yes BUILD OPTIONS: wacom.o - yes wacdump - yes xidump - yes libwacomcfg - yes libwacomxi - yes xsetwacom - yes hid.o - yes usbmouse.o - no evdev.o - no mousedev.o - no input.o - no tabletdev.o - no wacom_drv.o - yes ---------------------------------------- 2.4 - The Root AccountNormal users do not have /sbin in their path, so running modprobe directly fails. Running the program using the full pathname (/sbin/modprobe) will solve this, as will adding /sbin to the path. But there is another problem, as we will see:[jej@ayukawa jej]$ modprobe foo bash: modprobe: command not found [jej@ayukawa jej]$ locate modprobe /sbin/modprobe [jej@ayukawa jej]$ echo $PATH /bin:/usr/bin: ... :/home/jej/bin Normal users are not allowed to run this command. For that, we need to be root. The su command stands for "substitute user" since it can be used to become any user on the system, but it is generally known by the incorrect but very memorable mnemonic "superuser."[jej@ayukawa jej]$ /sbin/modprobe foo foo.o: create_module: Operation not permitted [jej@ayukawa jej]$ su Password: [root@ayukawa jej]# whoami root [root@ayukawa jej]# modprobe foo bash: modprobe: command not found [root@ayukawa jej]# export PATH=$PATH:/sbin [root@ayukawa jej]# modprobe foo [root@ayukawa jej]# [jej@ayukawa src]$ pwd /home/jej/src/linuxwacom/src [jej@ayukawa src]$ su - [root@ayukawa root]# cd /home/jej/src/linuxwacom/src [root@ayukawa src]# echo $PATH /bin:/sbin:/usr/bin: ... :/root/bin So that leaves you with two immediate options, and one potential long-term option: Option One: Become root and add /sbin to the path. Option Two: Become root using root's environment and cd back.[jej@ayukawa src]$ su [jej@ayukawa src]# export PATH=$PATH:/sbin Option Three (recommended): Add /sbin to your personal account's path[jej@ayukawa src]$ su - [root@ayukawa root]# cd /home/jej/src/linuxwacom/src [jej@ayukawa src]$ export PATH=$PATH:/sbin [jej@ayukawa src]$ su [root@ayukawa src]# echo $PATH /bin:/usr/bin: ... :/home/jej/bin:/sbin [root@ayukawa src]# exit [jej@ayukawa src]$ If any of this is not explained clearly, drop me a line and let me know where you got stuck. I'd be happy to clarify directly and update this page for future readers. 3.0 - The USB Kernel DriverSerial tablet users rejoice: you can skip this entire section. Please
go to the Using wacdump page for details on viewing the tablet output.
USB users stay put; we need to tweak your kernel.
Kernel modules must be recompiled for each new kernel so I can't just provide binaries. By the time you read this, my present kernel will be entirely out of date with yours. In any event, many new features are available in the latest drivers from the Linux Wacom Project, so I wholly recommend using them over the drivers provided by your standard distribution. Rest assured, continuous efforts are being made to get these changes merged back into the Linux kernel. However, the changes can normally only merged into the next kernel release, instead of the current one. For those who don't like upgrading kernels, here is a safe statement: if you are not using a newly released tablet model and you are running a recently released kernel version, chances are that you don't need to update your kernel driver from linuxwacom. Note: If your system is running a 2.4 kernel and you don't have any application required to run on kernel 2.4, upgrading your kernel to version 2.6 (preferablely 2.6.8 or later) may save you the steps to update wacom kernel related modules. 3.1 - Testing Tablet Detection[jej@ayukawa wacom]$more /proc/bus/usb/devices T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=056a ProdID=0042 Rev= 1.15 S: Manufacturer=Tablet S: Product=XD-0608-U C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=140mA I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=wacom E: Ad=81(I) Atr=03(Int.) MxPS= 10 Ivl=5ms On newer 2.6 systems, more /proc/bus/input/devices gives you [jej@ayukawa wacom]$more /proc/bus/input/devices I: Bus=0003 Vendor=056a Product=0042 Version=1.15 N: Name="Wacom Intuos2 6x8" P: Phys=usb-0000:00:1d.1-2/input0 H: Handlers=event3 B: EV=1f B: KEY=1cff 0 1f00ff 0 0 0 0 0 0 0 0 B: REL=100 B: ABS=f00017b B: MSC=1 This is Redhat 8.0 (2.4.18-17.8.0): If all went well like above, the USB device was successfully detected and handled by the wacom driver. This presumably means that information like pressure and tilt will be received on /dev/input/event0. You are ready to configure the X driver Downloading the Code. If instead you got any of the following lines in your log, the wacom driver did not get control. Either hid or usbmouse did. input0,hiddev0: USB HID v1.00 Mouse [Tablet XD-0608-U] on usb1:5.0 input0: Tablet XD-1212-U on usb2:2.0 3.2 - Updated wacom.cThe wacom.c driver that is available in linuxwacom-0.7.6-4.tar.bz2 supports Intuos3 4x6, which will be available in kernel version 2.6.19.The driver also added a few new xsetwacom commands that help you change X driver settings from user space.
On newer kernel versions, 2.6.8 or later, you can link Wacom USB tablet
to "/dev/input/wacom#", where # is a number when you have more than one
Wacom tablet on the system. It can be done by adding the following
rules in /etc/udev/rules.d/10-wacom.rules. Some distributions use a
different number for the file name. Please look for proper one with
wacom under /etc/udev/rules.d.
Some fedore Core and RHEL releases use SYSFS{manufacturer}="WACOM" instead of SYSFS{idVendor}=="056a" in the file, which is wrong. You need to modify it. If you only have one Wacom tablet, SYMLINK="input/wacom" instead of SYMLINK="input/wacom%e" to avoid port changes after hot-plugging the device. If you have more than one Wacom tablets plugged on the system, specify the link with product id is recommanded:KERNEL="event*", SYSFS{idVendor}=="056a", NAME="input/%k", SYMLINK="input/wacom%e" KERNEL="event*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="00b5", NAME="input/%k", SYMLINK="input/intuos3" KERNEL="event*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0015", NAME="input/%k", SYMLINK="input/graphire4" 3.3 - Building wacom.c (for kernel 2.4)To build the wacom.o kernel module, you need configure the package with --enable-wacom option. The kernel sources are required as described on the configuration page. Here's how the configuration should generally look:[jej@ayukawa linuxwacom]$ ./configure --enable-wacom ... checking for valid kernel source tree... ok ... ---------------------------------------- BUILD ENVIRONMENT: architecture - i686 linux kernel - yes 2.4 module versioning - yes kernel - yes /usr/src/linux XFree86 - no XLib - yes /usr/X11R6 TCL - yes /usr TK - yes /usr ncurses - yes GTK - 2.0.6 BUILD OPTIONS: wacom.o - yes wacdump - yes xidump - yes libwacomcfg - yes libwacomxi - yes xsetwacom - yes hid.o - no usbmouse.o - no evdev.o - no mousedev.o - no input.o - no tabletdev.o - no wacom_drv.o - no ---------------------------------------- As shown above, the kernel directory was detected and the wacom.o module will be built. If the kernel option shows "no", you will need to specify the --with-kernel option and the correct directory. To build the driver, just run make. The output will be a file called wacom.o. It is located in the linuxwacom package's src/2.4 directory for versions older than 2.4.22. For versions 2.4.22 or newer, it is in src/2.4.22 directory. This is your replacement driver. 3.4 - Building wacom.c (for kernel 2.6)To build the wacom.ko kernel module, you need to configure wacom as a kernel module under your kernel source tree first. The kernel sources are required as described on the configuration page.Then, you need to configure the package with --enable-wacom option. Here's how the configuration should generally look: [jej@ayukawa linuxwacom]$ ./configure --enable-wacom ... checking for valid kernel source tree... ok ... ---------------------------------------- BUILD ENVIRONMENT: architecture - i686 linux kernel - yes 2.6.9 module versioning - yes kernel - yes /usr/src/linux XFree86 - no XLib - yes /usr/X11R6 TCL - yes /usr TK - yes /usr ncurses - yes GTK - 2.0.6 BUILD OPTIONS: wacom.o - yes wacdump - yes xidump - yes libwacomcfg - yes libwacomxi - yes xsetwacom - yes hid.o - no usbmouse.o - no evdev.o - no mousedev.o - no input.o - no tabletdev.o - no wacom_drv.o - no ---------------------------------------- As shown above, the kernel directory was detected and the wacom.o module will be built. If the kernel option shows "no", you will need to specify the --with-kernel option and the correct directory.
To build the driver, just run make. If everything works properly, you'll see the following from the make: [jej@ayukawa linuxwacom]$ make ... Making all in 2.6.9 make[3]: Entering directory `/home/jej/linuxwacom/src/2.6.9' Building linuxwacom drivers for 2.6 kernel. make -C /usr/src/linux M=/home/jej/linuxwacom/src/2.6.9 make[4]: Entering directory `/home/jej/linux-2.6.9' LD /home/jej/linuxwacom/src/2.6.9/built-in.o CC [M] /home/jej/linuxwacom/src/2.6.9/wacom.o Building modules, stage 2. MODPOST CC /home/jej/linuxwacom/src/2.6.9/wacom.mod.o LD [M] /home/jej/linuxwacom/src/2.6.9/wacom.ko make[4]: Leaving directory `/usr/src/linux' make[3]: Leaving directory `/home/jej/linuxwacom/src/2.6.9' ... This part is for those who want to manually
build the wacom kernel driver in source tree. If you already followed
the steps above, you can move on to next page.
Please backup wacom.c in your kernel tree first. Then copy wacom.c (or wacom_wac.c, wacom_wac.h, wacom_sys.c, and wacom.h if defined) from the related linuxwacom directory to the source tree (if 4 files were copies, you need to add wacom-objs := wacom_sys.o wacom_wac.o to the Makefile under your kernel source input directory) and rebuild the kernel. An example for kernel 2.6.9 is as following: [jej@ayukawa linuxwacom]$ cp /usr/src/linux/drivers/usb/input/wacom.c /usr/src/linux/drivers/usb/input/wacom.c.2.6.9 [jej@ayukawa linuxwacom]$ cp src/2.6.9/wacom.c /usr/src/linux/drivers/usb/input/ [jej@ayukawa linuxwacom]$ cd /usr/src/linux [jej@ayukawa linux]$ make [jej@ayukawa linux]$ su [jej@ayukawa linux]#make install [jej@ayukawa linux]#make modules_install [jej@ayukawa linux]#reboot 3.5 - Testing If wacom.(k)o Will LoadBefore we install the wacom driver, we need to test that it will load properly. We do this by loading the driver manually. We will also need to be root to do this. WARNING: there is a small chance that this will bomb your kernel, so we run sync to write all the stale buffers to the disk. People using ext3 have little to worry about, but it's always good to be prepared for the worst. At the very least, save your work. [root@ayukawa linuxwacom]# sync From the package's associated kernel directory, we unload any previous modules and load the new one. The following example is from a kernel 2.4.22 system.
[root@ayukawa linuxwacom]# cd src/2.4.22 [root@ayukawa 2.4.22]# /sbin/rmmod wacom [root@ayukawa 2.4.22]# /sbin/insmod ./wacom.o # for those about to rock, we salute you. Well, if you did not bomb, then good. And if you did, well, sorry. So far, we have not had any reports of this happening, so please send in yours. Incidentally, if you run "/sbin/insmod wacom.o" and happen to be in the wrong directory, the old driver reloads, sometimes without warning. I therefore changed this to read "/sbin/insmod ./wacom.o" which seems to prevent this from happening. To be certain, you can check the log file for the correct version number. [root@ayukawa src]# tail /var/log/messages Jun 06 20:34:41 ayukawa kernel: usb.c: registered new driver wacom Jun 06 20:34:41 ayukawa kernel: Reporting max 30480, 31680 Jun 06 20:34:41 ayukawa kernel: wacom.c: Setting tablet report for tablet data Jun 06 20:34:41 ayukawa kernel: input0: Wacom Intuos2 12x12 on usb2:3.0 Jun 06 20:34:41 ayukawa kernel: wacom.c: $1.43-0.7.6-4 Vojtech Pavlik <vojtech@suse.cz> Jun 06 20:34:41 ayukawa kernel: wacom.c: USB Wacom Graphire and Wacom Intuos tablet driver (MODIFIED-DEBUG) The important detail is the version number. A version number like "1.30" is an original kernel version and not from the linuxwacom package. The correct version should also have the -0.7.6-4 portion as well. Also, future versions of the driver will say "LINUXWACOM-DEBUG" or similar rather than "MODIFIED-DEBUG" as shown above. This is to help differentiate between the stock kernel driver and those available from the Linux Wacom Project. If you get errors inserting the module, then you may need to reconfigure and build with module versioning disabled. If it loads without a hitch, move on to the next part. 3.6 - Installing wacom.(k)o
When should I install the driver? When you're comfortable that the driver will not crash your system. If you really know what you're doing, just load the drivers manually like in the previous section Testing If wacom.(k)o Will Load. On some distributions, Mandriva (a.k.a Mandrake) included, the wacom.ko driver that appears in the kernel modules directory appears to be compressed. If you cannot find wacom.ko using the method below, try locating wacom.ko.gz instead. People who encountered this problem were able to run gzip on the module and copy that instead. Installing the driver requires knowing where it belongs. A little research will help here. By using the locate command, you can find all copies of the original driver on the computer. On this computer, there are two kernels installed. uname identifies the currently active kernel as 2.6.17-1.2157_FC5. The correct driver to replace is therefore at /lib/modules/2.6.17-1.2157_FC5/kernel/drivers/usb/input/wacom.ko. You will need to be root to replace this file, and it is a very good idea to make a backup copy.jej@ayukawa wacom]$ locate wacom.ko /lib/modules/2.6.17-1.2157_FC5/kernel/drivers/usb/input/wacom.ko /lib/modules/2.6.17-1.2174_FC5/kernel/drivers/usb/input/wacom.ko [jej@ayukawa wacom]$ uname -r 2.6.17-1.2157_FC5 Here, I've saved the original to wacom_old.ko and copied my new driver over it. You should substitute directory names as appropriate.[jej@ayukawa wacom]$ su - [jej@ayukawa root]# cd /lib/modules/2.6.17-1.2157_FC5/kernel/drivers/usb/input [jej@ayukawa usb]# cp wacom.ko /home/jej/linuxwacom/src/2.6.16/wacom_old.ko [jej@ayukawa usb]# cp /home/jej/linuxwacom/src/2.6.16/wacom.ko wacom.ko NOTE: Don't leave the backup copy in the same directory as the original. depmod will treat both as valid drivers, regardless of their names. Copy the original somewhere outside of the kernel module directory to ensure that this does not happen. In at least one case, the backup driver was loaded instead of the new one due to a curious dependency issue. Finally, it is always a good thing to update the module dependencies. This is where you find out if the module was compiled without kernel module versioning. The following command, even if it generates errors is relatively benign. If it fails, then there is no harm done. It just means that you will have to load modules in the correct order since the system will not be able to guess for you. [jej@ayukawa usb]# depmod -e If you get no errors and no output, everything is fine, and the module was compiled, linked, and installed properly. If you received unresolved symbols like usb_set_idle or printk, then you need to reconfigure with module versioning enabled and recompile.
3.7 - Loading the wacom Driver
[jej@ayukawa usb]# rmmod wacom [jej@ayukawa usb]# modprobe usb-uhci (or usb-ohci) [jej@ayukawa usb]# modprobe input [jej@ayukawa usb]# modprobe mousedev [jej@ayukawa usb]# modprobe wacom (or insmod mydir/src/wacom.o) [jej@ayukawa usb]# modprobe evdev [jej@ayukawa usb]# grep -i wacom /var/log/messages | tail Jun 06 21:23:35 ayukawa kernel: usb.c: registered new driver wacom Jun 06 21:23:35 ayukawa kernel: wacom.c: v1.43-0.7.6-4 Vojtech Pavlik <vojtech@suse.cz> Jun 06 21:23:35 ayukawa kernel: wacom.c: USB Wacom Graphire and Wacom Intuos tablet driver (MODIFIED) 3.8 - Building usbmouse.o, evdev.o, mousedev.o, and hid.o (for kernel 2.4)In the linuxwacom-0.7.6-4.tar.bz2 file, you will find mousedev.c, usbmouse.c, hid-core.c, evdev.c, and input.c files which have special exceptions for wacom. These files are not built by default, so you will need to reconfigure the package and run make again. If your kernel is older than 2.4.22, the modules will be built using the sources at src/2.4. If your kernel is 2.4.22 or newer, the modules will be built using the sources at src/2.4.22. input.o is only needed for kernels older than 2.4.22. [jej@ayukawa wacom]$./configure --enable-hid --enable-usbmouse --enable-mousedev --enable-evdev --enable-input --with-kernel=your-kernel-src-dir ... BUILD OPTIONS: hid.o - yes usbmouse.o - yes evdev.o - yes mousedev.o - yes input.o - yes ... [jej@ayukawa wacom]$ make First off, if the code does not build, and you cannot chase the problem down yourself, send me a line. If your kernel is much older than 2.4.18, then you may have to resign yourself to the fact that the 2.4.19 drivers are not going to work for you. I would recommend upgrading your kernel. Before installing the drivers, please backup the originals. Then, use the following steps to install the drivers into the proper directories. Use locate as you did for the wacom.o file if necessary. For systems with kernel 2.4 and older than kernel 2.4.22: [jej@ayukawa wacom]$su [jej@ayukawa wacom]#cd src/2.4 [jej@ayukawa 2.4]#cp hid.o /lib/modules/your-kernel-ver/kernel/drivers/usb [jej@ayukawa 2.4]#cp usbmouse.o /lib/modules/your-kernel-ver/kernel/drivers/usb [jej@ayukawa 2.4]#cp evdev.o /lib/modules/your-kernel-ver/kernel/drivers/input [jej@ayukawa 2.4]#cp mousedev.o /lib/modules/your-kernel-ver/kernel/drivers/input [jej@ayukawa 2.4]#cp input.o /lib/modules/your-kernel-ver/kernel/drivers/input [jej@ayukawa 2.4]#reboot For systems with kernel 2.4.22 or newer: As before with some other distributions, if the files in the kernel module directory are compressed, you'll need to run gzip on the .o files to get .o.gz files.[jej@ayukawa wacom]$su [jej@ayukawa wacom]#cd src/2.4.22 [jej@ayukawa 2.4.22]#cp hid.o /lib/modules/your-kernel-ver/kernel/drivers/usb [jej@ayukawa 2.4.22]#cp usbmouse.o /lib/modules/your-kernel-ver/kernel/drivers/usb [jej@ayukawa 2.4.22]#cp evdev.o /lib/modules/your-kernel-ver/kernel/drivers/input [jej@ayukawa 2.4.22]#cp mousedev.o /lib/modules/your-kernel-ver/kernel/drivers/input [jej@ayukawa 2.4.22]#reboot 3.9 - Building (usb)hid.ko (for kernel 2.6)In the linuxwacom-0.7.6-4.tar.bz2 file, you will find hid-core.c, which have special exceptions for wacom. This file is not built by default, so you will need to reconfigure the package and run make again. Note, for kernel 2.6.18 and later, no need to build hid any more. For other kernels, refer to Testing Tablet Detection to see if you need to build hid or not. As for wacom.c, you need to configure usbhid as a module under your kernel source tree before configuring linuxwacom. On some distributions, Mandrake or Mandriva included, the (usb)hid.ko driver that located in the kernel modules directory appears to be compressed. You need to run gzip on the module and copy (usb)hid.ko.gz instead. [jej@ayukawa wacom]$./configure --enable-hid --with-kernel=your-kernel-src-dir ... BUILD OPTIONS: hid.o - yes ... Kernel 2.6.11 and 2.6.12 are in src/2.6.11. Kernels 2.6.16 and 2.6.17 are handled in src/2.6.16. All the other kernels are processed in its own src/2.6.x. New 2.6 directories will be created when compatibility issue occurs.
If everything works properly, you'll see the following from the make: [jej@ayukawa linuxwacom]$ make ... Making all in 2.6.9 make[3]: Entering directory `/home/jej/linuxwacom/src/2.6.9' Building linuxwacom drivers for 2.6 kernel. make -C /usr/src/linux M=/home/jej/linuxwacom/src/2.6.9 make[4]: Entering directory `/home/jej/linux-2.6.9' LD /home/jej/linuxwacom/src/2.6.9/built-in.o CC [M] /home/jej/linuxwacom/src/2.6.9/hid-core.o CC [M] /home/jej/linuxwacom/src/2.6.9/hid-input.o LD [M] /home/jej/linuxwacom/src/2.6.9/usbhid.o Building modules, stage 2. MODPOST CC /home/jej/linuxwacom/src/2.6.9/usbhid.mod.o LD [M] /home/jej/linuxwacom/src/2.6.9/usbhid.ko make[4]: Leaving directory `/usr/src/linux' ... Then, use the following steps to install the driver: [jej@ayukawa linuxwacom]$su [jej@ayukawa linuxwacom]#cd src/2.6.9 [jej@ayukawa 2.6.9]#cp usbhid.ko /lib/modules/your-kernel-ver/kernel/drivers/usb/input [jej@ayukawa 2.6.9]#reboot This part is for those who want to manually build the kernel drivers from source tree.
If you already followed the steps above, you can move on to next page.
Please backup your related kernel files first then copy the source from the related linuxwacom directory to the source tree and rebuild the kernel. An example for kernel 2.6.9 is as following: [jej@ayukawa linuxwacom]$ cp /usr/src/linux/drivers/usb/input/hid-core.c /usr/src/linux/drivers/usb/input/hid-core.c.2.6.9 [jej@ayukawa linuxwacom]$ cp src/2.6.9/hid-core.c /usr/src/linux/drivers/usb/input/ [jej@ayukawa linuxwacom]$ cd /usr/src/linux [jej@ayukawa linux]$ make [jej@ayukawa linux]$ su [jej@ayukawa linux]# make install [jej@ayukawa linux]# make modules_install [jej@ayukawa linux]# reboot 3.10 - Unknown Tablet?To determine whether your device is listed in the driver, we need to determine the device identifier. It can be discovered by doing the following:[root@ayukawa root]# grep -i 56a /var/log/messages | tail -10 Jun 06 21:03:09 ayukawa /etc/hotplug/usb.agent: Setup mousedev for USB product 56a/44/115 Jun 06 21:27:48 ayukawa kernel: usb.c: USB device 2 (vend/prod 0x56a/0x44) is not claimed by any active driver. The next section assumes you have things working up to this point. 3.11 - Viewing the Raw Data[root@ayukawa usb]# cd /dev/input [root@ayukawa input]# xxd event0 0000000: e65d c33d 597d 0100 0100 4101 0100 0000 .].=Y}....A..... 0000010: e65d c33d 5c7d 0100 0400 0000 b701 2800 .].=\}........(. 0000020: e65d c33d d9bb 0100 0100 4101 0000 0000 .].=......A..... 0000030: e65d c33d dcbb 0100 0400 0000 b701 2800 .].=..........(. (Ctrl-C) [jej@sasami root]# /sbin/rmmod wacom [jej@sasami root]# /sbin/modprobe wacom (or /sbin/insmod mydir/src/wacom.o) [jej@sasami root]# tail /var/log/messages Jun 06 17:31:31 sasami kernel: usb.c: deregistering driver wacom Jun 06 17:31:34 sasami kernel: usb.c: registered new driver wacom Jun 06 17:31:35 sasami kernel: input0: Wacom Intuos2 12x12 on usb1:2.0 Jun 06 17:31:35 sasami kernel: wacom.c: v1.43-0.7.6-4 Vojtech Pavlik <vojtech@suse.cz> You should also try running xxd on /dev/input/mouse0. You should get streams of data when the mouse and pen are moved around the surface of the tablet. It is this device that X will look at for mouse movement. Use Ctrl-C to exit xxd. 4.0 - Using wacdump[jej@ayukawa linuxwacom]$ ./configure ... ---------------------------------------- BUILD OPTIONS: wacom.o - no wacdump - yes hid.o - no usbmouse.o - no wacom_drv.o - no ---------------------------------------- The command line usage of wacdump is pretty simple: Usage: wacdump [options] device Options: -h, --help - usage -c, --class device_cls - use specified class (see below) -f, --force device_name - use specified device (see below) -l, --list - list all supported devices -v, --verbose - increase log output; multiple OK -V, --version - display version number --logfile log_file - output log to file Example devices: /dev/input/event0 - usb tablet device /dev/ttyS0 - serial tablet on com1 /dev/ttyUSB0 - serial tablet on USB adapter Supported device classes: serial, usb Supported device names: serial: art, art2, dig, dig2, pp, gr, pl, int, int2, c100 usb: pp, gr, gr2, int, int2, pl, vol Older versions of wacdump assumed the device to be /dev/input/event0. This is now deprecated. You should instead specify which device to use on the command line directly. If you get an end-of-file error or the device does not exist, then the wacom may be attached to a different event. Serial users may experience a timeout error which indicates that either the tablet is not responding or XFree86 has it open. Access denied errors probably indicate that you are not root. If you get different types of errors, let me know so we can get them documented. Serial users are advised that now is a good time to plug in your tablet, if you haven't already. Let's run wacdump. Here are some command line examples: [jej@ayukawa src]$ ./wacdump /dev/input/event0 # typical USB tablet [jej@ayukawa src]$ ./wacdump /dev/input/event1 # USB tablet on event1 When you run wacdump, it will attempt to initialize and query the tablet. For a number of reasons, it may not display anything immediately, but if you place a mouse or pen near the surface, the screen should update. You will then be presented with a screen similar to the following: wacdump v0.4.0 MODEL=Wacom Intuos2 12x12 ROM=1.1-5 CLS=USB VNDR=Wacom DEV=Intuos2 SUB=XD-1212-U TOOLTYPE=NONE SERIAL=0x00000000 IN_PROX=+00000 (+00000 .. +00000) BUTTON=+00000 (+00000 .. +00000) POS_X=+00000 (+00000 .. +30480) POS_Y=+00000 (+00000 .. +31680) ROT_Z=+00000 (-00900 .. +00899) DISTANCE=+00000 (+00000 .. +00015) PRESSURE=+00000 (+00000 .. +01023) TILT_X=+00000 (+00000 .. +00127) TILT_Y=+00000 (+00000 .. +00127) ABSWHEEL=+00000 (+00000 .. +01023) RELWHEEL=+00000 (-00001 .. +00001) THROTTLE=+00000 (-01023 .. +01023) LEFT= MIDDLE= RIGHT= EXTRA= SIDE= TOUCH= STYLUS= STYLUS2= The top portion identifies the tablet, and unless you specifically override the device type with the -f option, it should be auto-detected from the tablet directly. In this case, the model is XD-1212-U, a USB Intuos2 12x12. The next section describes the dynamic attributes of the tablet, including the current position of the pointer, the type of tool in proximity to the surface, its pressure, and tilt. Some tablets (Protocol V tablets, such as Intuos 1, 2, and 3 as well as Cintiq 21UX) provide serial numbers for their tools. When a button is pressed, the button heading will change to something like "STYLUS=DOWN". Some tablet tools report wheel movements as single increments forward and reverse, while others provide absolute positions. The 4D mouse has a throttle instead of a wheel. All three cases are reported independently. Different tablets will have different options. Here is the lowly ArtPadII for comparison. wacdump v0.4.0 MODEL=Wacom ArtPadII 4x5 ROM=1.3-6 CLS=Serial VNDR=Wacom DEV=ArtPadII SUB=KT-0405-R TOOLTYPE=NONE IN_PROX=+00000 (+00000 .. +00000) BUTTON=+00000 (+00000 .. +00000) POS_X=+00000 (+00000 .. +06400) POS_Y=+00000 (+00000 .. +04800) PRESSURE=+00000 (+00000 .. +00255) LEFT= MIDDLE= RIGHT= EXTRA= SIDE= TOUCH= STYLUS= STYLUS2= Notice that this tablet has no tilt, and the pressure range is considerably reduced. This version of wacdump does not distinguish between tablets with mice, so the left, right, and middle buttons are present, even though the tablet itself has no mouse. This will likely change in the future. 5.0 - Configuring X11Two steps must be completed to get X to recognize your tablet. First, you need to add some lines to XF86Config to inform X of the tablet's existence. Second, you need to update the XInput driver that pertains to the tablet since the one that ships with XFree86 is not very functional. Neither driver holds a candle to the windows driver though, so you'll have to take what you get for the time being. Updates to the XFree86 driver are available in the stable and beta releases on the Downloading the Code page.5.1 - Adding the InputDevicesSection "InputDevice" Driver "wacom" Identifier "stylus" Option "Device" "/dev/ttyS0" # SERIAL ONLY Option "Device" "/dev/input/event0" # USB ONLY Option "Type" "stylus" Option "USB" "on" # USB ONLY Option "ForceDevice" "ISDV4" # Tablet PC ONLY EndSection Section "InputDevice" Driver "wacom" Identifier "eraser" Option "Device" "/dev/ttyS0" # SERIAL ONLY Option "Device" "/dev/input/event0" # USB ONLY Option "Type" "eraser" Option "USB" "on" # USB ONLY Option "ForceDevice" "ISDV4" # Tablet PC ONLY EndSection Section "InputDevice" Driver "wacom" Identifier "cursor" Option "Device" "/dev/ttyS0" # SERIAL ONLY Option "Device" "/dev/input/event0" # USB ONLY Option "Type" "cursor" Option "USB" "on" # USB ONLY Option "ForceDevice" "ISDV4" # Tablet PC ONLY EndSection # This section is for Intuos3, Cintiq 21UX, or Graphire4 only Section "InputDevice" Driver "wacom" Identifier "pad" Option "Device" "/dev/ttyS0" # SERIAL ONLY Option "Device" "/dev/input/event0" # USB ONLY Option "Type" "pad" Option "USB" "on" # USB ONLY EndSection WACOM(4) WACOM(4) NAME wacom - Wacom input driver SYNOPSIS Section "InputDevice" Identifier "idevname" Driver "wacom" Option "Device" "devpath" ... EndSection DESCRIPTION wacom is an X input driver for Wacom devices. The wacom driver functions as a pointer input device, and may be used as the X server's core pointer. SUPPORTED HARDWARE This driver supports the Wacom IV and Wacom V protocols. Serial tablets only need this driver. USB tablet support is available on some Linux platforms. USB tablets needs wacom Linux kernel driver being loaded before this driver starts. Please check linuxwacom.sf.net for latest updates of Wacom X and kernel drivers. CONFIGURATION DETAILS Please refer to xorg.conf(5x) for general configuration details and for options that can be used with all input drivers. This section only covers configuration details specific to this driver. Multiple instances of the Wacom devices can cohabit. It can be useful to define multiple devices with different active zones. Each device supports the following entries: Option "Type" "stylus"|"eraser"|"cursor"|"pad" sets the type of tool the device represents. This option is mandatory. "pad" is for Intuos 3, Cintiq 21UX, or Graphire 4 ExpressKeys only. It is required for Intuos 3, Cintiq 21UX, and Graphire 4 if your application supports ExpressKeys features. "pad" is reported as a second tool in the driver. Since it will not move the system's cursor, IT SHOULD NOT have any of those core options, such as "SendCoreEvents" or "AlwaysCore". Option "Device" "path" sets the path to the special file which represents serial line where the tablet is plugged. You have to specify it for each subsection with the same value if you want to have multiple devices with the same tablet. This option is mandatory. Option "USB" "on" tells the driver to dialog with the tablet the USB way. This option is mandatory for USB tablets. Option "ForceDevice" "ISDV4" tells the driver to dialog with the tablet the Tablet PC way. Tablet PC is a serial tablet using a special Wacom IV protocol, called ISDV4 protocol. This option is mandatory for Tablet PC. Option "DeviceName" "name" sets the name of the X device. Option "Suppress" "number" sets the position increment under which not to transmit coordinates. This entry must be specified only in the first Wacom subsection if you have multiple devices for one tablet. The default value is 2. If you don't specify this entry or your value is less than the default vaule or greater than 6, the default value will be used. To disable suppression, the entry should be specified as 0. When suppress is defined, an event will be sent only when at least one of the following conditions is met: the change between the current X coordinate and the previous one is greater than suppress; the change between the current Y coordinate and the previous one is greater than suppress; the change between the current pressure and the previous one is greater than suppress; the change between the current degree of rotation and the previous one of the transducer is greater than suppress; the change between the current wheel value and the previous one is equal to or greater than suppress; button value has changed; proximity has changed. Option "Mode" "Relative"|"Absolute" sets the mode of the device. Option "TopX" "number" X coordinate of the top corner of the active zone. Option "TopY" "number" Y coordinate of the top corner of the active zone. Option "BottomX" "number" X coordinate of the bottom corner of the active zone. Option "BottomY" "number" Y coordinate of the bottom corner of the active zone. Option "ButtonsOnly" "on" disables the device's motion events. Option "ButtonM" "AC" reports an action AC when button M is pressed, where M is one of the device supported button numbers, it can be 1 to 32. The default action reported to Xinput is mouse button M click. To assign it to a left-double-click, use "dblclick 1". To ignore the button click, i.e., to not report any button click event to Xinput, use "0" or "button 0". Use "modetoggle" to assign it to switching between relative and absolute mode, which is useful to switch windows in a multi-monitor environment. Option "TPCButton" "on" enables the stylus buttons as Tablet PC buttons, i.e., reports stylus button event only when its tip is pressed. Default to "on" for Tablet PC; "off" for all the other models Option "Speed" "Rspeed" sets the cursor's relative movement speed to Rspeed. The default value is 1.0. A Rspeed greater than 1.0 will speed up the cursor's relative movement. A Rspeed less than 1.0 but greater than 0 will slow down the cursor's relative movement. A Rspeed too close to 0 is not recommanded. Option "Twinview" "horizontal"|"vertical"|"none" sets the orientation of TwinView to map the tablet to one screen and to be able to move the screen cursor from one screen to the other when tool reaches the edge of the tablet. The cursor can be constrained in a specific screen if "ScreenNo" option is added. If you want to map the tablet to the whole desktop, you should NOT add this option. The default is "none". Option "TVResolution" "res1,res2" specifies different resolutions for the two screens in TwinView setup. For example, if the resolution of screen 1 (res1) is 1024x768 and screen 2 (res2) is 1280x1024, the option will be set to: Option "TVResolution" "1024x768,1280x1024" This option is used only when TwinView option is not none. It is unnecessary to add this option if your screens are displaying in the same resolutions. Option "ScreenNo" "n" In a multi-monitor environment, specifies the screen number in which the cursor can move. Option "Rotate" "CW"|"CCW"|"HALF"|"NONE" rotates the tablet orientation clockwise (CCW) or anti- clockwise (CW) or 180 degrees (HALF). The default is "NONE". Option "PressCurve" "x1,y1,x2,y2" sets pressure curve by control points x1, y1, x2, and y2. Their values are in range from 0..100. The input for linear curve (default) is "0,0,100,100"; slightly depressed curve (firmer) might be "5,0,100,95"; slightly raised curve (softer) might be "0,5,95,100". Option "KeepShape" "on" When this option is enabled, the active zone begins according to TopX and TopY. The bottom corner is adjusted to keep the ratio width/height of the active zone the same as the screen while maximizing the area described by TopX, TopY, BottomX, BottomY. Option "DebugLevel" "number" sets the level of debugging info reported. There are 12 levels, specified by the integers between 1 and 12. Once it is defined, all the debug messages with a level less than or equal to the "number" will be logged into /etc/X11/XFree86.0.log. Option "CursorProx" "number" sets the max distance from tablet to stop reporting movement for cursor in relative mode. Default for Intuos series is 10, Graphire series (including Volitos) is 42. Option "Serial" "number" sets the serial number associated with the physical device. This allows to have multiple devices of the same type (i.e. multiple pens). This option is only available on wacom V devices (Intuos series and Cintiq 21UX). To see which serial number belongs to a device, you have to set the DebugLevel to 6 and watch the output of the X log. Option "Threshold" "number" sets the pressure threshold used to generate a button 1 events of stylus. The default is MaxPressure*3/50. SEE ALSO Xorg(1x), xorg.conf(5x), xorgconfig(1x), Xserver(1x), X(7). AUTHORS Frederic Lepied <lepied@xfree86.org>, Ping Cheng <pingc@wacom.com>, John E. Joganic <jej@jâ€arkadia.com> X Version 11 linuxwacom 0.7.6 WACOM(4) 5.2 - Mouse1 (for all kernel 2.4 systems and some 2.6 systems)There is one exception however. If you have no other mouse device in your ServerLayout section, do not remove Mouse1. XFree86 will not start without at least one core pointer, and the tablet does not count unless it is specifically identified as a "CorePointer" rather than merely "SendCoreEvents." 5.3 - ServerLayoutSection "ServerLayout" Identifier "Default Layout" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" InputDevice "stylus" "SendCoreEvents" InputDevice "eraser" "SendCoreEvents" InputDevice "cursor" "SendCoreEvents" # For non-LCD tablets only InputDevice "pad" # For Intuos3/Cintiq 21UX/Graphire4 tablets. It should NOT send core event EndSection pad should not send core events. So, it should not include "SendCoreEvents" or "AlwaysCore". You have completed the XF86Config file changes. By aware that if you reboot your computer with the Wacom plugged in and Redhat's Anaconda program notices, it will treat the tablet as a USB mouse and reconfigure this file incorrectly. You may need to go back and check the file to ensure that everything is still correct afterwards. Rebooting with the device detached seems to reverse the process, but again, you should check the file to be certain. My recommendation is to tell Anaconda to ignore the tablet until the device detection works properly. 5.4 - Updating wacom_drv.(s)oThe Downloading the Code page currently offers source and binary for 47-0.7.6-4 in the stable package and 47-0.7.7-11 in the beta version. I recommend using the X driver and the Wacom Control Panel in the package that you get the kernel drivers ( if you use a USB tablet ) since they are in sync on supporting new functionality and new tablet models. Note: the binary wacom_drv.(s)o file is located in the prebuilt directory of the stable and beta packages. Instructions for rebuilding from source are available in the Appendix under Building wacom_drv.o from Scratch if you are a developer yourself or the binary is not compatible with your system. With that said, locate and replace wacom_drv.(s)o. Using locate, we find the driver in the X11R6 tree. This directory is pretty standard, so it is unlikely that your file will be located elsewhere. Note the assumption is that you are using XFree86 4.x or X11R6.x. [root@ayukawa root]# locate wacom_drv.o /usr/X11R6/lib/modules/input/wacom_drv.o [root@ayukawa root]# cd /usr/X11R6/lib/modules/input [root@ayukawa input]# cp wacom_drv.o /home/jej/linuxwacom-47-0.7.6-4/src/xdrv/wacom_drv_old.o [root@ayukawa input]# cp /home/jej/linuxwacom-47-0.7.6-4/prebuilt/wacom_drv.o_x wacom_drv.o where _x stands for _x86-64 if you are running an x86-64 system. If you are using X11R7.x, you need to locate wacom_drv.so: [root@ayukawa root]# locate wacom_drv.so /usr/lib/xorg/modules/input/wacom_drv.so The old file is copied away, and replaced with the newer version. If it does not load on your system, please let me know. 5.5 - Restart XFinally, restart X. You may wish to do this from runlevel 3 for testing purposes. If the X server dies, you can always back-out the changes to the XF86Config file and try again. Worse case, copy the wacom_drv_old.o file back to its original place. But first, look at the XFree86 log file for clues. You might want to do this even if everything works correctly. When things are running right, the following lines appear in my log file.[root@ayukawa root]# init 3 ...processes starting and stopping... [root@ayukawa root]# startx Notice the driver version 47-0.7.6-4 above. This is the new stable wacom_drv.o driver. The beta driver is currently 47-0.7.7-11.[root@ayukawa root]# grep -i wacom /var/log/XFree86.0.log (II) LoadModule: "wacom" (II) Loading /usr/X11R6/lib/modules/input/wacom_drv.o (II) Module wacom: vendor="The XFree86 Project" (II) Wacom driver level: 47-0.7.6-4 $ (II) XINPUT: Adding extended input device "eraser" (type: Wacom Eraser) (II) XINPUT: Adding extended input device "stylus" (type: Wacom Stylus) (II) XINPUT: Adding extended input device "cursor" (type: Wacom Cursor) (==) Wacom Kernel Input device name: "Wacom Intuos2 12x12" (==) Wacom tablet maximum X=30480 maximum Y=30480 X resolution=0 Y resolution=0 suppress=0 (==) Wacom Cursor top X=0 top Y=0 bottom X=30480 bottom Y=30480 (==) Wacom Stylus top X=0 top Y=0 bottom X=30480 bottom Y=30480 (==) Wacom Eraser top X=0 top Y=0 bottom X=30480 bottom Y=30480 Lastly, if you would like more logging, the parameter "DebugLevel" can be set to values between 1 and 11, with 11 being way too much, and 1 being fairly useful. 5.6 - Check the Pointer Status[root@ayukawa log]# xsetpointer -l "eraser" [XExtensionDevice] "stylus" [XExtensionDevice] "cursor" [XExtensionDevice] "Mouse0" [XPointer] "keyboard" [XKeyboard] 6.0 - Using xidump[jej@ayukawa linuxwacom]$ ./configure checking for XLib include directory... found checking for XLib header files... found checking for ncurses.h... yes ... ---------------------------------------- BUILD ENVIRONMENT: ... XLib - yes ncurses - yes ... BUILD OPTIONS: ... xidump - yes ... ---------------------------------------- [jej@ayukawa src]$ ./xidump -l eraser extension stylus extension cursor extension Mouse0 disabled keyboard keyboard [jej@ayukawa src]$ ./xidump -l -v eraser eraser extension key: min=8, max=39, num=32 btn: num=1 val: axes=6 mode=abs buf=0 axis[0]: res=2540, min=0, max=30480 axis[1]: res=2540, min=0, max=30480 axis[2]: res=1, min=0, max=1023 axis[3]: res=1, min=-64, max=63 axis[4]: res=1, min=-64, max=63 axis[5]: res=1, min=0, max=1023 [jej@ayukawa src]$ ./xidump -u raw stylus 14.56291895: Proximity In 14.56305595: Motion: x= +5978 y=+28728 p= 0 tx= +64 ty= +64 w= +0 ID: 2323 Serial: -60 ... 16.87158095: Motion: x= +4941 y=+27842 p= 225 tx= +41 ty= +67 w= +0 ID: 2323 Serial: -60 16.87164395: Button: 1 DOWN 16.87169595: Motion: x= +4964 y=+27844 p= 398 tx= +42 ty= +66 w= +0 ID: 2323 Serial: -60 ... 17.27328395: Motion: x= +5261 y=+27543 p= 3 tx= +48 ty= +64 w= +0 ID: 2323 Serial: -60 17.27334395: Button: 1 UP 17.27515995: Motion: x= +5348 y=+27451 p= 4 tx= +48 ty= +63 w= +0 ID: 2323 Serial: -60 ... 17.35933795: Motion: x= +7089 y=+27061 p= 4 tx= +48 ty= +63 w= +0 ID: 2323 Serial: -60 17.37444395: Proximity Out <Ctrl-C> [jej@ayukawa src]$ ./xidump stylus InputDevice: stylus Valuators: Absolute ID: 2323 Serial Number: -60 x-axis y-axis pressure x-tilt y-tilt wheel data: +10826 +09919 +00084 +00058 +00065 +00000 min: +00000 +00000 +00000 -00064 -00064 +00000 max: +30480 +30480 +01023 +00063 +00063 +01023 res: +00000 +00000 +00039 +00001 +00001 +00001 ******** Proximity: IN Focus: Buttons: 1-DOWN Keys: For completeness sake, here are the command line options: Usage: xidump [options] input_device -h, --help - usage -v, --verbose - verbose -V, --version - version -l, --list - list available input devices -u, --ui ui_type - use specified ui, see below Use --list option for input_device choices UI types: curses, raw There are not many options, but the --list option is helpful for identifying devices, and the --ui option allows you to switch between curses and raw modes. Adding the --verbose option increases the amount of output, and when used in conjunction with --list, displays the device capabilities. 7.0 - Tablet PC[jej@ayukawa ~]$su Password: [jej@ayukawa ~]# xxd /dev/ttyS0 Move your pen on your tabletPC. If you see output from the terminal while you move the pen, your tablet has been mapped to port 1. Quit xxd by Ctrl+c. Then ignore the rest of this page and go to(see Configuring X11) page. Otherwise, apply xxd to port 1 to 4. If none of them show output, you need to manually map the tablet to a serial port. Here is a sample command. The IO port may be different for your Tablet PC. [jej@ayukawa src]$ setserial /dev/ttyS2 port 0x93f8 autoconfig This command needs to be excuted with each reboot before X server starts. You can add the command into one of your favorite start script. I normally add it into /etc/rc.d/rc.local. Here is my rc.local: #!/bin/sh # # This script will be executed *after* all the other init scripts. # You can put your own initialization stuff in here if you don't # want to do the full Sys V style init stuff. touch /var/lock/subsys/local setserial /dev/ttyS2 port 0x93f8 autoconfig After installing wacom_drv.o and other programs, such as wacomcpl and wacdump, restart X server. Now you can view raw tablet data by: [jej@ayukawa util]$ ./wacdump -f tpc /dev/ttyS2 # Wacom digitizer on fake COM3 If everything looks right from wacdump (see Using wacdump), you can update /etc/X11/XF86Config or /etc/X11/xorg.conf to load wacom X driver (see Configuring XFree86/X11R6). Please notice that in Wacom InputDevice section, the following 2 options are required for Tablet PC: Option "Device" "/dev/ttyS2" # SERIAL ONLY Option "ForceDevice" "ISDV4" # Tablet PC ONLY Refer to Adding the InputDevices for details.
8.0 - Using xsetwacomHowever, it is reported that there are systems on which you can not run xsetwacom due to some XFree86 interface error. We did not figure out the root cause of this problem yet. Please check Success Stories page to see if your system is in question. If it is, you'll have to add the configuration options to your /etc/X11/XF86Config file. Please refer Configuring XFree86 for details. Building xsetwacom xsetwacom uses libwacomcfg.so to communicate with Wacom XFree86 driver, wacom_drv.o. So, libwacomcfg.so should be built and installed. libwacomcfg.so relies on Xlib. In the configure script, it will default the Xlib path to /usr/X11R6. If your Xlib is not installed under /usr/X11R6, you'll need to specify the path (dir) by --with-xlib=dir. Let's see what we get from configure: [jej@ayukawa linuxwacom]$./configure ... ---------------------------------------- BUILD ENVIRONMENT: architecture - i686 linux kernel - yes 2.4 module versioning - yes -DONFIG_MODVERSIONS -DMODVERSIONS -include /usr/src/linux/include/linux/modversions.h kernel source - yes /usr/src/linux XFree86 - no XLib - yes /usr/X11R6 TCL - yes /usr TK - yes /usr ncurses - yes GTK - 2.0.6 BUILD OPTIONS: wacom.o - no wacdump - yes xidump - yes libwacomcfg - yes libwacomxi - yes xsetwacom - yes hid.o - no usbmouse.o - no evdev.o - no mousedev.o - no input.o - no tabletdev.o - no wacom_drv.o - no ---------------------------------------- As shown above, the build options indicate that libwacomcfg and xsetwacom will be built. If not, then scroll back through the configuration to see if there aren't any errors or warnings that would explain this. Next, run make. The output will be stored in the linuxwacom package's src and src/.libs directory. They will be installed by running make install (you need to switch to superuser to run this command). If wacom_drv.o was running while installing xsetwacom, xsetwacom can be launched immediately after make install and exit (switch back to your own account). If wacom_drv.o is installed by the same make install as xsetwacom is, restarting X server is required to use the newly built wacom_drv.o. We strongly recommand to build and install the wacom_drv.o and xsetwacom from the same release package since the out of sync wacom_drv.o and xsetwacom may crash your X server. Running xsetwacom [jej@ayukawa linuxwacom]$xsetwacom Usage: xsetwacom [options] [command [arguments...]] Options: -h, --help - usage -v, --verbose - verbose output -V, --version - version info -d, --display disp_name - override default display -s, --shell - generate shell commands for 'get' -x, --xconf - generate X.conf lines for 'get' Commands: list [dev|param] - display known devices, parameters set dev_name param [values...] - set device parameter by name get dev_name param [param...] - get device parameter(s) by name getdefault dev_name param [param...] - get device parameter(s) default value by name The most used xsetwacom command is xsetwacom set dev_name param [values...], where param is an option which will be set to values in wacom_drv.o after excuting xsetwacom. To better understand the use of this command, let's see some examples. Assume that you use Stylus as your Wacom tool's Identifier, which is considered is considered as dev_name in xsetwacom command. If you want to change Stylus's mode from absolute (default) to relative, then: [jej@ayukawa linuxwacom]$xsetwacom set Stylus mode relative If you want to change button 2 to left-double-click, then: [jej@ayukawa linuxwacom]$xsetwacom set Stylus button2 "dblclick 1" If you want to change button 2 to button 5, then: [jej@ayukawa linuxwacom]$xsetwacom set Stylus Button2 "button 5" or [jej@ayukawa linuxwacom]$xsetwacom set Stylus Button2 5 If you want to change button 3 to ModeToggle, then: [jej@ayukawa linuxwacom]$xsetwacom set Stylus button3 modetoggle If you want to know what the current (or default) pressure sensitivity setting is, then: [jej@ayukawa linuxwacom]$xsetwacom -s get Stylus PressCurve (output in xsetwacom format) xsetwacom set stylus PressCurve "0 15 85 100" or [jej@ayukawa linuxwacom]$xsetwacom -x get Stylus PressCurve (output in xorg.conf Option format) Option "PressCurve" "0,15,85,100" [jej@ayukawa linuxwacom]$xsetwacom -x getdefault Stylus PressCurve Option "PressCurve" "0,0,100,100" If you want to set the pressure sensitivity a bit softer, then: [jej@ayukawa linuxwacom]$xsetwacom set Stylus PressCurve 0 15 85 100 If you want the buttons behave the Tablet PC way, i.e., sending button event only when button1 (the tip) is pressed, then: [jej@ayukawa linuxwacom]$xsetwacom set Stylus TPCButton on If you want to change pad's button 1 to ctrl alt F2, then: [jej@ayukawa linuxwacom]$xsetwacom set pad Button1 "core key ctrl alt F2" If you want to change pad's button 2 to ctrl alt backspace, then: Below is a list of the parameters and their values used by xsetwacom command (a similar output can be get from xsetwacom list param):[jej@ayukawa linuxwacom]$xsetwacom set pad Button2 "core key ctrl alt backspace" param [values...] results ------------------------------------------------------------------ Mode Relative|Absolute sets the mode of the device TopX integer sets the X coordinate of the top corner of the active zone TopY integer sets the Y coordinate of the top corner of the active zone BottomX integer sets the X coordinate of the bottom corner of the active zone BottomY integer sets the Y coordinate of the bottom corner of the active zone ButtonM integer sets button M to button integer click ButtonM dblclick sets button M to left-double-click ButtonM 0 ignores button M click ButtonM modetoggle sets button M to Mode Toggle PressCurve i1 i2 i3 i4 sets the pressure bezier curve, where i1+i4=100; i2+i3=100 DebugLevel integer (1 - 12) sets the level of debugging trace SpeedLevel integer (1 - 11) sets relative cursor movement speed ClickForce integer (1 - 21) sets tip/eraser pressure threshold xyDefault resets the bounding coordinates to default in tablet units mmonitor on|off turns on/off across monitor movement on (non-TwinView) multi-monitor desktop TPCButton on|off turns on/off the buttons as Tablet PC buttons CursorProx distance sets cursor distance margin for proximity-out in distance from the tablet surface Rotate none|cw|ccw|half sets the rotation of the tablet. GetTabletID returns the USB tablet ID of the associated device. GetModel writes tablet models to /etc/wacom.dat ------------------------------------------------------------------ Event description format: [CORE] [EVENT TYPE] [MODIFIERS] [CODE] CORE: Emit core events irrespective of the SendCoreEvents setting EVENT TYPE: the type of event to emit: KEY: Emit a key event BUTTON: Emit a button event DBLCLICK: Emit a double-click button event MODETOGGLE: Toggle absolute/relative tablet mode MODIFIERS: Key modifiers: any combination of: SHIFT, CONTROL, ALT, META, HYPER, SUPER CODE: Button number or key code (see /usr/include/X11/keysymdef.h) The xsetwacom commands can be added to the .xinitrc under your home directory so next time when you login as yourself, the driver will be set to the options you choose. Below is an example of my .xinitrc: [jej@ayukawa jej]$more .xinitrc xsetwacom set Stylus0 TopX 10 xsetwacom set Stylus0 TopY 67 xsetwacom set Stylus0 BottomX 7170 xsetwacom set Stylus0 BottomY 5778 xsetwacom set Stylus0 TPCButton 1 # run the primary system script . /etc/X11/xinit/xinitrc If your system doesn't execute .xinitrc at login, you can add those xsetwacom commands into the startup script (.bashrc, .cshrc, .profile, etc.) that your system launches. It has been suggested that on debian, .Xsession should be used instead of .xinitrc. To see what's under your home directory, use ls -al ~. 9.0 - Using wacomcplHowever, it is reported that there are systems on which can not run wacomcpl due to some XFree86 interface error. We did not figure out the root cause of this problem yet. Please check Success Stories page to see if your system is in question. If it is, you'll have to add the configuration options to your /etc/X11/XF86Config file. Please refer Configuring XFree86 for details. Building wacomcpl wacomcpl is written in tcl/tk. It uses libwacomxi.so and xsetwacom to communicate with Wacom XFree86 driver, wacom_drv.o. So, to run wacomcpl, tcl/tk should be installed, libwacomxi.so and xsetwacom should be built and installed. libwacomxi.so and xsetwacom are enabled by default in the configure script. By default, the script will assume that tcl/tk is installed under /usr. That is, tcl.h and tk.h should be under /usr/include; libtcl.so.0 and libtk.so.0 should be under /usr/lib. Let's see what we get from configure: [jej@ayukawa linuxwacom]$./configure ... ---------------------------------------- BUILD ENVIRONMENT: architecture - i686 linux kernel - yes 2.4 module versioning - yes kernel source - yes /usr/src/linux XFree86 - no XLib - yes /usr/X11R6 TCL - yes /usr TK - yes /usr ncurses - yes GTK - 2.0.6 BUILD OPTIONS: wacom.o - no wacdump - yes xidump - yes libwacomcfg - yes libwacomxi - yes xsetwacom - yes hid.o - no usbmouse.o - no evdev.o - no mousedev.o - no input.o - no tabletdev.o - no wacom_drv.o - no ---------------------------------------- As shown above, the build options indicate that libwacomxi and xsetwacom will be built. If not, then scroll back through the configuration to see if there aren't any errors or warnings that would explain this. For example, on another system, I have installed tcl/tk under /usr/local/ActiveTcl. That is, tcl.h and tk.h are under /usr/local/ActiveTcl/include. If I run configure without options, I get: [jej@ayukawa linuxwacom]$./configure ... ---------------------------------------- BUILD ENVIRONMENT: architecture - i686 linux kernel - yes 2.4 module versioning - yes kernel source - yes /usr/src/linux XFree86 - no XLib - yes /usr/X11R6 TCL - no TK - no ncurses - yes GTK - 2.0.6 BUILD OPTIONS: wacom.o - no wacdump - yes xidump - yes libwacomcfg - yes libwacomxi - no xsetwacom - yes hid.o - no usbmouse.o - no evdev.o - no mousedev.o - no input.o - no tabletdev.o - no wacom_drv.o - no ---------------------------------------- The build options show that libwacomxi will not be built. When I scroll back through the configuration, I see: ... checking for tcl header files... not found; tried /usr/include/tcl.h *** *** WARNING: *** The tcl development environment does not appear to *** be installed. The header file tcl.h does not appear *** in the include path. Do you have the tcl rpm or *** equivalent package properly installed? Some build *** features will be unavailable. *** checking for tk header files... not found; tried /usr/include/tk.h and /include/tk.h *** *** WARNING: *** The tk development environment does not appear to *** be installed. The header file tk.h does not appear *** in the include path. Do you have the tk rpm or *** equivalent package properly installed? Some build *** features will be unavailable. *** checking ncurses.h usability... yes checking ncurses.h presence... yes checking for ncurses.h... yes *** *** WARNING: *** libwacomxi requires tcl environment; libwacomxi will not be built. *** ... Then I run configure with option --with-tcl=/usr/local/ActiveTcl: [jej@ayukawa linuxwacom]$./configure --with-tcl=/usr/local/ActiveTcl ... ---------------------------------------- BUILD ENVIRONMENT: architecture - i686 linux kernel - yes 2.4 module versioning - yes kernel source - yes /usr/src/linux XFree86 - no XLib - yes /usr/X11R6 TCL - yes /usr/local/ActiveTcl TK - yes /usr/local/ActiveTcl ncurses - yes GTK - 2.0.6 BUILD OPTIONS: wacom.o - no wacdump - yes xidump - yes libwacomcfg - yes libwacomxi - yes xsetwacom - yes hid.o - no usbmouse.o - no evdev.o - no mousedev.o - no input.o - no tabletdev.o - no wacom_drv.o - no ---------------------------------------- Note: You may need to issue the following commands before running wacomcpl: [jej@ayukawa linuxwacom]$export LD_LIBRARY_PATH=/usr/local/ActiveTcl/lib:$LD_LIBRARY_PATH [jej@ayukawa linuxwacom]$su [jej@ayukawa linuxwacom]#cd /usr/local/ActiveTcl/lib [jej@ayukawa lib]#ln -s libtcl.8.4.so libtcl.so.0 [jej@ayukawa lib]#ln -s libtk.8.4.so libtk.so.0 If your tcl and tk are installed on different paths, you'll need to specify them separately. Suppose that your tcl is under /usr/local/tcl8.4 and your tk is under /usr/local/tk8.4, the proper configuration and setup commands will be: [jej@ayukawa linuxwacom]$./configure --with-tcl=/usr/local/tcl8.4 --with-tk=/usr/local/tk8.4 [jej@ayukawa linuxwacom]$export LD_LIBRARY_PATH=/usr/local/tcl8.4/lib:/usr/local/tk8.4/lib:$LD_LIBRARY_PATH [jej@ayukawa linuxwacom]$su [jej@ayukawa linuxwacom]#cd /usr/local/tcl8.4/lib [jej@ayukawa lib]#ln -s libtcl.8.4.so libtcl.so.0 [jej@ayukawa lib]#cd /usr/local/tk8.4/lib [jej@ayukawa lib]#ln -s libtk.8.4.so libtk.so.0 Next, run make. The output will be stored in the linuxwacom package's src, src/.libs, src/wacomxi, and src/wacomxi/.libs directories. They will be installed by running make install (you need to switch to superuser to run this command). Running wacomcpl If wacom_drv.o was running while installing wacomcpl, wacomcpl can be launched immediately after make install and exit (switch back to your own account). If wacom_drv.o is installed by the same make install as wacomcpl is, restarting X server is required to use the newly built wacom_drv.o. We strongly recommand to build and install the wacom_drv.o and wacomcpl from the same release package since the out of sync wacom_drv.o and wacomcpl may crash your X server. 10.0 - Working With Gimp11.0 - ContactsPing Cheng can be contacted at the following email address: pingc@wacom.com. 12.0 - AppendixThis section is for everything that is either not critical or simply too complex to describe in the document above without becoming overly distracting. 12.1 - Building wacom_drv.o from ScratchIntroductionI should tell you out-right that this is a time consuming process.
You will need the X source code to rebuild the wacom_drv.o driver. The build configuration for X generates a number of header files that are necessary but not installed by default on most distributions. Consequently, you will need to not only get the source, but build it, practically in its entirety. Then, after all that, the configure script can be instructed to hook into the X build tree and rebuild wacom_drv.o at any time without having to rebuild X again. Since I am running Redhat 8.0 and cannot really pull down the original XFree86 4.2.0 source code, compile it, and expect it to work on my system, I need to instead use the source RPM provided by Redhat. If you choose to go this route, I provide pretty detailed instructions for making this work. If your distribution works differently, or you are using Gentoo where most everything is source code by default, you'll need to handle this as best as possible according to your particular situation. Step One: Get The SourceOn Redhat 8.0, I discovered the version number for my currently installed XFree86 packages by running rpm -q XFree86. This reported version 4.2.0-72, therefore the source package is XFree86-4.2.0-72.src.rpm. I downloaded the package from Redhat directly and installed it to the system as follows: [root@sen src]# rpm -ivh XFree86-4.2.0-72.src.rpm 1:XFree86 ########################################### [100%] This installs a number of files to the /usr/src/redhat directory, particularly in the SOURCES and SPECS subdirectories. Other distributions undoubtedly install elsewhere. Look for the XFree86.spec file which should be located in the SPECS directory. This file contains all the information necessary to patch the orginal XFree86-4.2.0 source code to the level that Redhat is distributing in their regular binary package. The source code and patch files are located in SOURCES. Step Two: Build the SourceThis step describes how to build the source from the RPM itself. If you are building from some other mechanism, I honestly cannot offer much assistance since I generally don't build my X system from scratch. If you'd like to write up a short section on building the server for your particular distribution, I would be happy to include it here. Next, you don't actually have to build the entire thing. The point at which the xf86Wacom.c driver can be built however, is not until somewhere in the middle of the build process. The driver depends on a number of header files that are created dynamically so until they are generated, wacom_drv.o cannot be compiled. My solution was to open a separate terminal in the wacom driver directory and periodically attempt to build it. When it successfully built, I stopped the X build process. Here's how to build the source for an RPM that's been exploded out into the SPECS and SOURCES directories. [root@sen root]# cd /usr/src/redhat [root@sen redhat]# rpmbuild -bc SPECS/XFree86.spec Not every distribution has rpmbuild; try using just rpm instead. At some point, Redhat split the build functionality into separate programs. If after looking through the rpm man page, you still cannot get this to work, send me some email, and I'll look into it. The important item is the "-bc" option of rpmbuild which unpacks, patches, and builds the source without actually installing. While it is also possible to simply unpack and patch using the "-bp" option, there does not seem to be a way to just build. The "-bc" option simply deletes all the files provided by "-bp" and recreates them again. The downside of this is that if you wanted to simply unpack, patch, and then copy the new xf86Wacom.c file over the old one, you'll find that the build step deletes it and starts over again. I have gotten this to work by creating a new patch file, but this requires a bit more effort, so I don't recommend it right off. Step Three: Build the Original DriverThe xf86Wacom.c file is buried pretty deep in the X build tree. If it is in a different location than the one I have provided below, try using find . -name xf86Wacom.c from the BUILD directory. The "a25-update" file is the original xf86Wacom.c file before Redhat's patch. If you open xf86Wacom.c, you'll find that it is version 25, at least as of this writing and this distribution. The presence of the Makefile means that the configuration has at least been run for this directory. If you have built a sufficient portion of the X source files, then all the header files that you need have been generated, and you can build xf86Wacom.c. Try it, and if it does not build, wait a bit. The absence of xf86Version.h for instance, is a good indication that the build process is not ready.[root@sen redhat]# cd BUILD/XFree86-4.2.0/xc/programs/Xserver/hw/xfree86/input/wacom [root@sen wacom]# ls Imakefile wacom.man xf86Wacom.c.Wacom-USB-driver-a25-update Makefile xf86Wacom.c [root@sen wacom]# make rm -f xf86Wacom.o gcc -O2 -march=i386 ... -c xf86Wacom.c ld -r xf86Wacom.o -o wacom_drv.o Step Four: Automating the Build ProcessBy configuring the package with the --with-xf86 option set to the XFree86 build tree, you can build the driver outside of the X build tree. [jej@ayukawa wacom]$ ./configure \ --with-xf86=/usr/src/redhat/BUILD/XFree86-4.2.0 ... BUILD ENVIRONMENT: XFree86 - yes BUILD OPTIONS: wacom_drv.o - yes [jej@ayukawa wacom]$ make The makefile rule which builds the driver is contained within src/Makefile.am and is modified according to the configuration to generate a rule similar to this in src/Makefile: xf86Wacom.o: xf86Wacom.c gcc -O2 -march=i386 -mcpu=$(ARCHITECTURE) -pipe -ansi \ -pedantic -Wall -Wpointer-arith -fno-merge-constants \ -I. -I$(XF86_DIR)/programs/Xserver/hw/xfree86/common \ -I$(XF86_DIR)/programs/Xserver/hw/xfree86/loader \ -I$(XF86_DIR)/programs/Xserver/hw/xfree86/os-support \ -I$(XF86_DIR)/programs/Xserver/include \ -I$(XF86_DIR)/programs/Xserver/mi \ -I$(XF86_DIR)/exports/include/X11 \ -I$(XF86_DIR)/include/extensions \ -I$(XF86_DIR) \ -I$(XF86_DIR)/exports/include \ -Dlinux -D__i386__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE \ -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE \ -DSHAPE -DXINPUT -DXKB -DLBX -DXAPPGROUP -DXCSECURITY \ -DTOGCUP -DXF86BIGFONT -DDPMSExtension -DPIXPRIV -DPANORAMIX \ -DRENDER -DGCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV \ -DSINGLEDEPTH -DXFreeXDGA -DXvExtension -DXFree86LOADER \ -DXFree86Server -DXF86VIDMODE -DXvMCExtension \ -DSMART_SCHEDULE -DBUILDDEBUG -DXResExtension \ -DX_BYTE_ORDER=X_LITTLE_ENDIAN -DNDEBUG -DFUNCPROTO=15 \ -DNARROWPROTO -DIN_MODULE -DXFree86Module -DLINUX_INPUT \ -o xf86Wacom.o -c xf86Wacom.c
The options and directories specified come directly from the output of the make command in the previous step. All the root and parent directories have been replaced with the macro XF86_DIR which in this case is set by the configuration script to /usr/src/redhat/BUILD/XFree86-4.2.0/xc. If the options that you see in your build are identical to those above, then the default rule will work for you now. If not, you'll need to make some alterations. You can update the Makefile.am file and rerun automake, update the Makefile.in and rerun configure, or just update the Makefile directly. So long as the X build tree exists, the include directories will point to the correct locations, and the driver will build. If space is an issue, you can probably remove all the non-essential directories, but be careful; the dependency tree in X is huge. 12.2 - Installing wacom driver On DebianThe following documentation for building wacom driver on Debian was written by Olivier Lecarme. You can also refer to Olivier's page here for updates.Copyright (C) June 14, 2005 Olivier Lecarme. I'm using the Sid version of Debian, but I was told that the Sarge distribution, recently become the stable one, already contains what is necessary. Version 2.6.11 of the kernel is the highly preferred one by people maintaining the Linux Wacom software. Download the 2.6.11 kernel I was completely unsuccessful when trying to configure and compile my own kernel: certainly I omitted some capital module, but I could not decide what it was. Thus, I chose the last pre-compiled kernel. 1. apt-get kernel-image-2.6.11-1-686 2. apt-get kernel-headers-2.6.11-1-686 If you use Lilo, configure your /etc/lilo.conf file, taking into account that this kernel needs an initrd= line. Optionally If your case is irrelevant, please skip this section and the following one. 1. I Have a Broadcom NetXtreme BCM5751 Ethernet card, which needs the tigon3 driver, unavailable in Debian kernel 2.6.11. The solution is here. Thus I got the package: 1. cd /usr/src 2. wget http://www.acm.rpi.edu/~dilinger/kernel-source-nonfree-2.6.11 /kernel-nonfree-modules-2.6.11-1-686-2.6.11-1_i386.deb 2. I have an ATI X 300 video card, whose driver is not available in Debian kernel 2.6.11. The solution is here. Thus I got the packages: 1. for the driver: wget http://www.stanchina.net/~flavio/ debian-fglrx-xfree86/fglrx-driver_8.12.10-1_i386.deb 2. and for the kernel module: wget http://www.stanchina.net/~flavio /debian-fglrx-modules/fglrx-kernel-2.6.11-1-686-smp_8.12.10-1+2.6.11-2_i386.deb Install the optional packages 1. cd /usr/src 2. dpkg -i kernel-nonfree-modules-2.6.11-1-686_2.6.11-1_i386.deb 3. dpkg -i fglrx-driver_8.12.10-1_i386.deb 4. dpkg -i fglrx-kernel-2.6.11-1-686_8.12.10-1+2.6.11-2_i386.deb Install the wacom tools package 1. apt-get install wacom-tools 2. dpkg-reconfigure wacom-kernel-source Since your debconf configuration probably did not ask for the lowest priority questions, this step is needed. You might also use it later if you update your kernel, for instance. When asked whether you want to build the modules, answer yes, and tell where the headers are located (normally /usr/src/kernel-headers-2.6.11-1-686). Prepare for the /dev/input/wacom link In /etc/udev/rules.d/10-wacom.rules, add the following line: KERNEL="event*", SYSFS{idVendor}="056a", NAME="input/%k", SYMLINK="input/wacom%e" Thus the drivers will find the Wacom tablet, whatever its /dev/input/eventX address is. Change your XF86Config-4 file The important sections are: 1. The ServerLayout section: Section "ServerLayout" [ ... ] InputDevice "stylus" "SendCoreEvents" InputDevice "eraser" "SendCoreEvents" InputDevice "cursor" "SendCoreEvents" InputDevice "pad" EndSection 2. The InputDevice sections: Section "InputDevice" Identifier "stylus" Driver "wacom" Option "Type" "stylus" Option "USB" "on" Option "Threshold" "10" Option "Device" "/dev/input/wacom" EndSection Section "InputDevice" Identifier "eraser" Driver "wacom" Option "Type" "eraser" Option "USB" "on" Option "Threshold" "10" Option "Device" "/dev/input/wacom" EndSection Section "InputDevice" Identifier "cursor" Driver "wacom" Option "Type" "cursor" Option "USB" "on" Option "Threshold" "10" Option "Device" "/dev/input/wacom" EndSection Section "InputDevice" Identifier "pad" Driver "wacom" Option "Device" "/dev/input/wacom" Option "Type" "pad" Option "USB" "on" EndSection 3. The section dealing with your normal mouse must be considered too. See Mouse1 (for all kernel 2.4 systems and some 2.6 systems). I didn't use /dev/psaux nor /dev/input/mice. /dev/input/mouse0 works for a PS/2 mouse. For a USB mouse, there is a problem mentioned in the Remaining problems. 4. If you use the ATI X300 card, you need to change also the Device section: Section "Device" Identifier "ATI" Driver "fglrx" Option "VideoOverlay" "on" Option "OpenGLOverlay" "off" Option "UseInternalAGPGART" "no" EndSection Final steps 1. Reboot. This will also restart the X server, of course. 2. Enjoy! If you want to use the expresskeys of your Intuos tablet If you do nothing more, the pad is not usable at all. However, you will find here a specific tool for having the pad available in various programs, for example XTerm, Gimp, or Blender. This tool is very easy to compile, install, and use. If you want to use the pad in Gimp, do not enable it in "Preferences -> Input Devices -> Configure the extended input devices", contrarily to the three other tools (stylus, eraser, and cursor). You can easily configure what the expresskeys send, according to your tastes, and use only them for the tasks that need a good control of the stylus or eraser. Remaining problems If your tablet is always plugged, everything works perfectly. If you want to plug it out, for example in order to move it onto another computer, and then to plug it back later, problems begin. For the present, you must take care of the following things: 1. If you plug in the tablet again, the corresponding driver is not informed of this, thus you must restart the X server. 2. If the tablet is plugged when you reboot, and you have an USB mouse, maybe the /dev/input address of this mouse is not the same as the previous time. Thus you will have to change this in your XF86Config-4 file. 3. If you use GDM or KDM or XDM, you should plug in the tablet after rebooting, but before the X server starts, which is somewhat difficult! Thus you will be forced to restart the X server, i.e. kill it (Ctrl+Alt+Backspace) and not simply logging out. Final remarks I would like to thank all persons who helped me, on the LinuxWacom or the Gimp-user discussion lists, especially Carol Spears, Karine Delvare, Ping Cheng, and Ron. 12.3 - Building wacom driver On PowerMacThe following documentation for building wacom driver on PowerMac [silver] was written by Joseph E. Sacco. If you have any problems or questions, go ahead and post them to the list, or send email to me directly. I'll forward your email on to Joseph.Copyright (C) 2004 Joseph E. Sacco System: << Hardware >> * PowerMac [silver] with dual 533 MHz G4 [7410] CPU's, 1GB RAM, (3) 73 GB SCSI drives * Contour UniMouse [USB, optical, three button] * Wacom Intuos Tablet [USB]: GD-1218-U * 4-d mouse * pen * air brush << Software >> * Yellow Dog Linux 3.0.1 [Redhat variant for PPC] * kernel: 2.4.25-ben1 * linuxwacom-0.6.1 * XFree86-4.3.0-2.1e * atk-1.6.0-1 * freetype-2.1.3-4 * gcc-3.3 * gtk+-2.4.0 * glib2-2.4.0 * ncurses-5.2-28 * pango-1.4.0 ============================================================ I have a Wacom Intuos tablet "working" [after a fashion] on a PPC running Yellow Dog Linux 3.0.1. << What works >> * input devices: * cursor movement * button clicks * wheel rotation [as seen from wacdump] * pressure [as seen from wacdump & gimp] * tilt [as seen from wacdump] * applications: * wacdump * xidump * xev * xinput-1.2 * gimp-1.25 & gimp-2.0 * dia-0.9.2 < What does *not* work >> * input devices: * Mode "Relative" for pen & air brush [should it???] * applications: * xsetwacom * wacomcpl [because of xsetwacom] There are some issues I would like to report. ---------------------------------------------------------------------------------------------------------------------------------------- * Makefiles The makefiles are set up for Intel architecture. Some options are not applicable for PPC's. [ from ./src/2.4.22/Makefile.in ] KCFLAGS = -Wall $(DEBUG_FLAGS) -D__KERNEL__ \ -DMODULE -DEXPORT_SYMTAB $(MODS) \ -Wstrict-prototypes -Wno-trigraphs -O2 \ -fno-strict-aliasing \ -fno-common -fomit-frame-pointer -pipe \ ===> -mpreferred-stack-boundary=2 \ ===> -march=$(ARCHITECTURE) The last two options are not applicable to a PPC. A more appropriate set of flags, taken from building the 2.4.25 kernel modules, might be: KCFLAGS = -Wall $(DEBUG_FLAGS) -D__KERNEL__ \ -Wstrict-prototypes -Wno-trigraphs -O2 \ -fno-strict-aliasing -fno-common -fomit-frame-pointer \ -fsigned-char -msoft-float -pipe -ffixed-r2 \ -Wno-uninitialized -mmultiple -mstring \ -DMODULE -DMODVERSIONS -iwithprefix [ from ./src/Makefile.in ] $(XF86OBJS): xf86Wacom.c Makefile ==> gcc -O2 $(DEPFLAGS) -march=i386 -mcpu=$(ARCHITECTURE) -pipe -ansi \ -pedantic -Wall -Wpointer-arith $(NO_MERGE_CONSTANTS) \ -I. -I$(XF86_DIR)/programs/Xserver/hw/xfree86/common \ -I$(XF86_DIR)/programs/Xserver/hw/xfree86/loader \ -I$(XF86_DIR)/programs/Xserver/hw/xfree86/os-support \ -I$(XF86_DIR)/programs/Xserver/include \ -I$(XF86_DIR)/programs/Xserver/mi \ -I$(XF86_DIR)/exports/include/X11 \ -I$(XF86_DIR)/include/extensions \ -I$(XF86_DIR) \ -I$(XF86_DIR)/exports/include \ ==> -Dlinux -D__i386__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE \ -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE \ -DSHAPE -DXINPUT -DXKB -DLBX -DXAPPGROUP -DXCSECURITY \ -DTOGCUP -DXF86BIGFONT -DDPMSExtension -DPIXPRIV -DPANORAMIX \ -DRENDER -DGCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV \ -DSINGLEDEPTH -DXFreeXDGA -DXvExtension -DXFree86LOADER \ -DXFree86Server -DXF86VIDMODE -DXvMCExtension \ -DSMART_SCHEDULE -DBUILDDEBUG -DXResExtension \ -DX_BYTE_ORDER=X_LITTLE_ENDIAN -DNDEBUG -DFUNCPROTO=15 \ -DNARROWPROTO -DIN_MODULE -DXFree86Module $(LINUX_INPUT) \ -o $@ -c $(subst .o,.c,$@) A more appropriate set of flags, taken from building XFree86-4.3.0, might be: $(XF86OBJS): xf86Wacom.c Makefile gcc -O2 $(DEPFLAGS) -mcpu=$(ARCHITECTURE) -pipe -ansi \ -pedantic -Wall -Wpointer-arith $(NO_MERGE_CONSTANTS) \ -I. -I$(XF86_DIR)/programs/Xserver/hw/xfree86/common \ -I$(XF86_DIR)/programs/Xserver/hw/xfree86/loader \ -I$(XF86_DIR)/programs/Xserver/hw/xfree86/os-support \ -I$(XF86_DIR)/programs/Xserver/include \ -I$(XF86_DIR)/programs/Xserver/mi \ -I$(XF86_DIR)/exports/include/X11 \ -I$(XF86_DIR)/include/extensions \ -I$(XF86_DIR) \ -I$(XF86_DIR)/exports/include \ -Dlinux -D__powerpc__ -D_POSIX_C_SOURCE=199309L \ -D_POSIX_SOURCE \ -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE \ -DSHAPE -DXINPUT -DXKB -DLBX -DXAPPGROUP -DXCSECURITY \ -DTOGCUP -DXF86BIGFONT -DDPMSExtension -DPIXPRIV -DPANORAMIX \ -DRENDER -DGCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV \ -DSINGLEDEPTH -DXFreeXDGA -DXvExtension -DXFree86LOADER \ -DXFree86Server -DXF86VIDMODE -DXvMCExtension \ -DSMART_SCHEDULE -DBUILDDEBUG -DXResExtension \ -DX_BYTE_ORDER=X_BIG_ENDIAN -DNDEBUG -DFUNCPROTO=15 \ -DNARROWPROTO -DIN_MODULE -DXFree86Module $(LINUX_INPUT) \ -o $@ -c $(subst .o,.c,$@) where $(ARCHITECTURE) = powerppc [ppc will not work] * Kernel modules I experimented with different ways of building [and loading] the kernel modules: * evdev.o * hid.o * mousedev.o * wacom.o I settled on building the modules within the existing framework for building the Linux kernel rather than using the makefiles provided by linuxwacom-0.6.1. I did so to insure that I got all the PPC dependency stuff right. * Hotplug kernel module issues I had some issues using 'modprobe' to load the wacom kernel module that forced me to reconfigure and rebuild the 2.4.25-ben1 kernel. A typical YDL kernel build for a PowerMac statically links most of the input core support into the kernel: [from .config file provided by YDL] # Input core support # CONFIG_INPUT=y CONFIG_INPUT_KEYBDEV=y CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_JOYDEV=m CONFIG_INPUT_EVDEV=y I had initially built only wacom.o as a loadable module. The other modules were statically linked into the kernel. When wacom.o was loaded using: $ /sbin/insmod wacom.o all went well: [output from /var/log/messages] Mar 24 10:26:33 plantain kernel: usb.c: registered new driver wacom Mar 24 10:26:33 plantain kernel: Reporting max 45720, 31680 Mar 24 10:26:33 plantain kernel: wacom.c: Setting tablet report for tabletdata Mar 24 10:26:33 plantain kernel: input4: Wacom Intuos 12x18 on usb2:3.0 Mar 24 10:26:33 plantain kernel: wacom.c: v1.30-j0.6.1 Vojtech Pavlik 12.4 - Building wacom driver On Fedora Core 3The following documentation for building wacom kernel modules and x.org driver on Fedora Core 3 was written by Paul Duffy. If you have any problems or questions, go ahead and post them to the list, or send email to me directly. If I cannot provide a satisfactory answer, I'll forward your email on to Paul.Copyright (C) 2005 Paul Duffy Procedure for building linuxwacom package on Fedora Core 3 with 2.6 series kernel. These instructions are current as of May 23, 2005. There are several reasons why FC3 is different. The two main reasons being: - evdev, hid-core and mousedev are compiled into the kernel core so you can't just recompile them as modules. - the Fedora Core kernel is heavily patched, which I don't mind as it means my Creative Live! Drive II works, but it does mean that compiling the kernel from www.kernel.org may lose you some hardware support. Additionally, Red Hat no longer supply a simple linux-source rpm so if you want the official kernel source for Fedora Core 3 you're going to have to use the source RPM. At this stage, I am assuming that you have a fully updated system and are using kernel 2.6.11-1.14_FC3 What you will need: At this stage you're going to need all of the development packages required to compile the kernel (gcc, automake, etc) and the xorg-x11-sdk package installed (under Development >> X Software Development). If you're unsure where this all is, you can select the hat menu in KDE or Gnome and you want to select System Settings >> Add/Remove Applications. If you're unsure as to exactly what you need to install, install everything (except gcc-java, it causes problems with Sun or IBM java installs) assuming you have the hard drive space. Also the vast majority of this will require you to be in SuperUser mode so you might as well 'su' from the start; not normally advice I'd be giving anyone but it's kinda necessary in this case. You have two choices for the first step; you can either download the kernel SRPM from one of the mirrors at http://fedora.redhat.com/download/mirrors.html where you can find the correct package as updates/3/SRPMS/kernel-2.6.11-1.14_FC3.src.rpm and install it with rpm -ivh kernel-2.6.11-1.14_FC3.src.rpm or you can use up2date --get-source kernel Either method should leave you with a lot of files in /usr/src/redhat/SOURCES and the file /usr/src/redhat/SPECS/kernel-2.6.spec At this stage, don't worry about all the files starting linux-2.6.9... the main file you are looking for is linux-2.6.11.tar.bz2. As long as that's there you should be fine. Now, to actually get all the kernel sources setup in a compilable form you need to run the command rpmbuild -bp --target= 12.5 - Building wacom driver On Suse 9.2Nico Kadel-Garcia has provided a changed SPEC file for SuSE 9.2. You can download the spec here."There are only a few needed changes: use the new software, throw out an old patch, teach it to use the right options for x86_64 compilation, and stop it from generating symlinks into /usr/include/X11 at compilation time, and it's done. ". Nico said on Mar 21 2005. 12.6 - Laptop Suspend/Resume TipsThomas Netter (tnetter at iniDOTunizhDOTc) kindly provided a solution to the following problem:The peoblem lies in the step that when unplugging tablet cable while the laptop is entering Suspend Mode. The proper steps to plug/unplug, suspend/resume a Wacom tablet on a laptop are:When laptop recovers from suspend/resume, XFree86/X.org no longer registers the tablet. The laptop, however, receives all the tablet data (I can "cat /dev/input/event2" and see the data). The only way I know for X to recover the tablet is to restart X. - Fold the laptop's screen - Wait 4 or 5 seconds for the tablet's orange LED to extinguish - Unplug the tablet's USB cable THEN you can recover the tablet functionalities after resuming the laptop and repluging the tablet. However, If you: - Fold the laptop's screen - Immediately unplug the tablet's USB cable before the LED extinguishes THEN you cannot recover the tablet functionalities after resuming the laptop and replugging the tablet, even if you replug the tablet before resuming the laptop. Therefore, old airline operations apply: Extinguish LEDs before take-off! -Thomas 12.7 - GNU Free Document LicenseVersion 1.2, November 2002Copyright (C) 2000,2001,2002 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. 0. PREAMBLE 1. APPLICABILITY AND DEFINITIONS
7. AGGREGATION WITH INDEPENDENT WORKS 10. FUTURE REVISIONS OF THIS LICENSE HOW TO USE THIS LICENSE FOR YOUR DOCUMENTS Copyright (c) YEAR YOUR NAME. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. |