HOWTO: Enable your Wacom Intous/Graphire Tablet with Pressure Sensitivity

[nemesis8601]

How do you know what event to put instead of "wacom" for "dev/input/wacom"? I read on a previous post that those lines had to be changed. For example, some people changed it to "dev/input/event2" but I'm not sure why they put event 2 instead of something else. Can anyone help? That may be the problem I'm having.

[gertvdijk]

Great that Wacom tablets are supported in Linux, but I have one, 18 months old, but I can't find anything about it regarding Linux support! :confused:
My model is de Graphire BT (Bluetooth, CTE-630BT). It is being identified as a standard HID input device in Windows and a Wacom service is running for the features and absolute positioning for the pen.
Does anybody have a Graphine BT or Wireless Pen Tablet (same thing, but new model no)? Or can anyone give me any hints about how to get it to work?
Any help appreciated. :)

[drummingpariah]

Great that Wacom tablets are supported in Linux, but I have one, 18 months old, but I can't find anything about it regarding Linux support! :confused:
My model is de Graphire BT (Bluetooth, CTE-630BT). It is being identified as a standard HID input device in Windows and a Wacom service is running for the features and absolute positioning for the pen.
Does anybody have a Graphine BT or Wireless Pen Tablet (same thing, but new model no)? Or can anyone give me any hints about how to get it to work?
Any help appreciated. :)

I'm not sure if it's officially supported or not, but if it's not we can probably fix that. What is your wacdump output and where is the input from the tablet going?

How do you know what event to put instead of "wacom" for "dev/input/wacom"? I read on a previous post that those lines had to be changed. For example, some people changed it to "dev/input/event2" but I'm not sure why they put event 2 instead of something else. Can anyone help? That may be the problem I'm having.

Depending on your driver and how you're mapping the input, it may just be /dev/input/wacom (by default) or something screwy, like what I'm doing (/dev/ttyUSB0 because I have a serial->usb converter). Check the documentation (man docs especially) and it should tell you specifically what to use for your model.

I'm still having a problem with cursor offset in GIMP when using two screens. I'm fairly sure that it's not a driver problem, but instead a "relative" or "absolute" positioning problem. I've recompiled the driver with totalWidth reconfigured, as mentioned earlier (I'll quote it if I remember to look again) but is anybody else running into this same problem? It seems to be less of a problem if I set "stylus" and "cursor" to different map values in GIMP (such as screen/window). More on that later, but has anybody solved this elusive issue?

[caelcynndarr]

worked awesome Thanks

[june.itech]

Thank you very much for this!

[yitzle]

When I add the line(s) to the ServerLayout section, gdm crashes when I log in.
Section "InputDevice"
Identifier "stylus"
Driver "wacom"
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "USB" "on"
# Option "PressCurve" "50,0,100,50"
# Option "Mode" "relative"
EndSection
Section "ServerLayout"
InputDevice "stylus" "SendCoreEvents"
/dev/input
crw-rw---- 1 root root 13, 64 2008-01-13 19:07 event0
crw-rw---- 1 root root 13, 65 2008-01-13 19:07 event1
crw-rw---- 1 root root 13, 66 2008-01-13 19:07 event2
crw-rw---- 1 root root 13, 67 2008-01-13 19:07 event3
crw-rw---- 1 root root 13, 63 2008-01-13 19:06 mice
crw-rw---- 1 root root 13, 32 2008-01-13 19:07 mouse0
crw-rw---- 1 root root 13, 33 2008-01-13 19:07 mouse1
lrwxrwxrwx 1 root root 6 2008-01-13 19:07 tablet-graphire3 -> event2
lrwxrwxrwx 1 root root 6 2008-01-13 19:07 wacom -> event2

[patchido]

i followed this and all it did was damage my xorg file... i had to use

sudo dpkg-reconfigure -phigh xserver-xorg

so i could run xorg again.... i have a intuos3 and would like for it to work.. how does my xorg need to look??

oo btw when i used yum it told me an error.. that i was missing a package.. but i installed it and still told me the same

[yitzle]

Making a dated backup before playing around with files is always smart...

[the lah]

Great HOWTO, Everything worked out great on my Wacom Graphire 2! :)

[drummingpariah]

i followed this and all it did was damage my xorg file... i had to use

sudo dpkg-reconfigure -phigh xserver-xorg

so i could run xorg again.... i have a intuos3 and would like for it to work.. how does my xorg need to look??

oo btw when i used yum it told me an error.. that i was missing a package.. but i installed it and still told me the same

well, what package? What does your xorg.conf look like before modifying it? Give us information to work with, and we'll be happy to help.

[Robynsveil]

I've noticed a few people add their issues with wacom Bamboo, and so I thought I might too. I must say, first off, that this is a great forum with a keen group of people, keen on making their computers do what they want it to, as opposed to having some company make that decision for them... and stimulates grey matter in the process.

I've had a few trials getting my USB wacom Bamboo to work so far: must have re-compiled the drivers and stuff eight or nine times until I figured out what the problem was. In the process, I have become on intimate terms with /etc/X11/xorg.conf, tweaking this and that until I've finally gotten not only the tablet essentially working, but have removed some redundant entries as well.

The instructions to get a set of drivers working so that your Bamboo will show up I found here:
http://ubuntuforums.org/showthread.php?t=631881

The last issue I have is with a cursor/draw-point offset in The GIMP. That is, my cursor is down and to the right of where my brush is, which makes drawing awkward if not impossible. BTW, I've got stylus, cursor and eraser set to 'screen', as per recommendation.

I've carefully read through this thread and there seem to be two schools of thought on how to best address this.
Saxofoner suggested:
OKAY, I want some love for this one! I managed to get it to map to one monitor perfectly, with the cursor and the paintbrush matching locations. SCORE!!!!
Quote:
Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/input/wacom" #USB ONLY
Option "Type" "stylus"
Option "USB" "on" #USB ONLY
Option "TwinView" "horizontal"
Option "ScreenNo" "0"
Option "TVResolution" "1024x768,1024x768"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/input/wacom" #USB ONLY
Option "Type" "eraser"
Option "USB" "on" #USB ONLY
Option "TwinView" "horizontal"
Option "ScreenNo" "0"
Option "TVResolution" "1024x768,1024x768"

EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/input/wacom" #USB ONLY
Option "Type" "cursor"
Option "Mode" "relative"
Option "USB" "on" #USB ONLY
Option "Twinview" "horizontal"
Option "ScreenNo" "0"
EndSection
In Gimp I set it to "Screen", and my problems were solved. The trick was that the "TVResolution" option was necessary, even though it shouldn't be. Can someone tell me if it works for them?


whilst AlumaSqrl was pretty sure that:
In case anyone else was having issues with the improper mapping of multi-head layouts when using GIMP (cursor offset problems), I decided to post the means by which I solved this on my computer. I certainly cannot understand how exactly other people get this to work through simple edits of the config file, because I eventually had to resort to altering the xorg wacom driver. Working back from the gdk cursor handling all the way to wcmCommon.c, the numbers are bogus for the axis across which the desktops span. This is because the driver sums the widths of the screens whenever the absolute flag isn't set. Simply setting
Code:

totalWidth = screenInfo.screens[priv->currentScreen]->width;

and commenting out the original assignment fixed this problem. I haven't bothered looking into exactly WHY the math is being done like that, and I'm not entirely sure there isn't a particular reason for it.... but this method fixed the operation of the driver for my application and would serve as a solution for anybody else with a similar problem and a lack of patience.

was going to be the only way to go. I'm not above rebuilding (compiling) a .c file if that will fix it, but might need a bit of hand-holding... anyone willing to give some pointers, or has someone arrived at another, more definitive solution?

[Robynsveil]

OKAY, I want some love for this one! I managed to get it to map to one monitor perfectly, with the cursor and the paintbrush matching locations. SCORE!!!!


In Gimp I set it to "Screen", and my problems were solved. The trick was that the "TVResolution" option was necessary, even though it shouldn't be. Can someone tell me if it works for them?

Sorry to say, Saxofoner, I did try it and it didn't work for me. I actually even set my monitor resolution to 1024 x 768 (which is almost as bad as 640 x 480 is now) and my xorg.conf was like:
# xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
Option "XkbOptions" "lv3:ralt_switch"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
Option "USB" "on"
Option "Mode" "Absolute"
Option "PressCurve" "50,0,100,50"
Option "ScreenNo" "0"
Option "TVResolution" "1024x768,1024x768"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
Option "Mode" "Absolute"
Option "USB" "on"
Option "ScreenNo" "0"
Option "TVResolution" "1024x768,1024x768"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/input/wacom"
Option "Type" "cursor"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
Option "USB" "on"
EndSection

Section "Device"
Identifier "nVidia Corporation NV43 [GeForce 6600 GT]"
Boardname "NVIDIA GeForce FX (generic)"
Busid "PCI:1:0:0"
Driver "nvidia"
Screen 0
Vendorname "NVIDIA"
EndSection

Section "Monitor"
Identifier "CM753"
Option "DPMS"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "nVidia Corporation NV43 [GeForce 6600 GT]"
Monitor "CM753"
DefaultDepth 24
SubSection "Display"
Modes "1600x1280" "1600x1200" "1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"

# Uncomment if you have a wacom tablet
InputDevice "stylus" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
EndSection

...but the offset was as bad as ever... no change at all. Thinking of barking up the altering-the-xorg-wacom-driver tree.

[Robynsveil]

In case anyone else was having issues with the improper mapping of multi-head layouts when using GIMP (cursor offset problems), I decided to post the means by which I solved this on my computer. I certainly cannot understand how exactly other people get this to work through simple edits of the config file, because I eventually had to resort to altering the xorg wacom driver. Working back from the gdk cursor handling all the way to wcmCommon.c, the numbers are bogus for the axis across which the desktops span. This is because the driver sums the widths of the screens whenever the absolute flag isn't set. Simply setting
totalWidth = screenInfo.screens[priv->currentScreen]->width;
and commenting out the original assignment fixed this problem. I haven't bothered looking into exactly WHY the math is being done like that, and I'm not entirely sure there isn't a particular reason for it.... but this method fixed the operation of the driver for my application and would serve as a solution for anybody else with a similar problem and a lack of patience.

I've found wcmCommon.c and brought it up in Bluefish. Although I program a bit, I've never been able to get my head around c. There appear to be a fair few references to Totalwidth = ... do we comment out and replace with "screenInfo.screens[priv->currentScreen]->width" all instances? or is there a particular line number I need to be at? or in a specific function?
Once I've made this change, do I just re-issue a ./configure ... make ... sudo make install as before? Please excuse the noob questions... a lot of people seem to be asking the same questions not only on this board but also on the GIMPTalk board, so it would be nice to maybe create a HOWTO for utter noobs to be able to follow, along the lines of the one at the beginning of this thread. Seems a pity to have the bloody thing working finally and yet still have this cursor/draw-point offset issue plaguing so many.

[megadeus]

Okay, this one might have been brought up, but my searching was not able to find it:

I'm using a Graphire 2 and through xsetwacom and editing xorg.conf I've managed to get the tablet mostly working.

The problems:

(1) The tablet registers a "click" whenever the tip gets within sensing range of the tablet. Normally, this would be the area you'd hover in if you wanted to move the cursor onscreen without actually drawing (or clicking and dragging or whatever). This can be solved with TPCButton set to 1, but it doesn't solve the next problem.

(2) Whenever the tablet registers a "click" (either by hovering when TPCButton is set to 0 or when the tip touches the tablet when TPCButton is 1) the action is that of a right-click, not a left-click. I've tried changing Button1 to various values with xsetwacom, but none have remedied the right-click problem.

I can work with the latter problem, but it is REALLY annoying sometimes, so I'm hoping for a good solution. Any advice?

[Robynsveil]

In case anyone else was having issues with the improper mapping of multi-head layouts when using GIMP (cursor offset problems), I decided to post the means by which I solved this on my computer. I certainly cannot understand how exactly other people get this to work through simple edits of the config file, because I eventually had to resort to altering the xorg wacom driver. Working back from the gdk cursor handling all the way to wcmCommon.c, the numbers are bogus for the axis across which the desktops span. This is because the driver sums the widths of the screens whenever the absolute flag isn't set. Simply setting
totalWidth = screenInfo.screens[priv->currentScreen]->width;
and commenting out the original assignment fixed this problem. I haven't bothered looking into exactly WHY the math is being done like that, and I'm not entirely sure there isn't a particular reason for it.... but this method fixed the operation of the driver for my application and would serve as a solution for anybody else with a similar problem and a lack of patience.

Impatient cow that I am, I'm going to have a go at fixing this myself. The above post left me with a few questions that perhaps another guru might be able to answer for me. First off:
numbers are bogus for the axis across which the desktops span
By that would be meant those x, y coordinates that define, what, screen size in pixels? Like in that comment in wcmCommon.c for the xf86WcmSetScreen function:
/******************************************
* xf86WcmSetScreen --
* set to the proper screen according to the converted (x,y).
* this only supports for horizontal setup now.
* need to know screen's origin (x,y) to support
* combined horizontal and vertical setups
*************************************************/

Converted *where*?
Somehow I think AlumaSqrl's issue and the developer's note are related.

Anyway, I brought up wcmCommon.c in Bluefish, and went to the xf86WcmSetScreen function in the static functions group. I found a reference to that totalWidth = statement, which seems to be one of those weird (to me) situations where the variable takes on its original value plus what's after the equal sign (which I understand means assignment, as in: var1 = var2 means var1 takes on the value of var2). I commented it out and replaced it with Aluma's code... like so:
/*... An effort of resolve the cursor-drawpoint offset...
from AlumaSqrl in Ubuntuforum post:

totalWidth += screenInfo.screens[i]->width;
...*/
totalWidth = screenInfo.screens[priv->currentScreen]->width;
/*... end mod ...*/


There aren't many more references to this variable. This one I left alone...:

if (priv->screen_no == -1)
{
for (i = 0; i < priv->numScreen; i++)
{
totalWidth += screenInfo.screens[i]->width;
if (maxHeight < screenInfo.screens[i]->height)
maxHeight = screenInfo.screens[i]->height;
}
for (i = 0; i < priv->numScreen; i++)
{
if (v0 * totalWidth <= (leftPadding +
screenInfo.screens[i]->width) * sizeX)
{
screenToSet = i;
break;
}
leftPadding += screenInfo.screens[i]->width;
}
}
else

Not sure if this also needs to be modified.
Thanks to all who reply...

[Robynsveil]

I'm not sure if it's officially supported or not, but if it's not we can probably fix that. What is your wacdump output and where is the input from the tablet going?



Depending on your driver and how you're mapping the input, it may just be /dev/input/wacom (by default) or something screwy, like what I'm doing (/dev/ttyUSB0 because I have a serial->usb converter). Check the documentation (man docs especially) and it should tell you specifically what to use for your model.

I'm still having a problem with cursor offset in GIMP when using two screens. I'm fairly sure that it's not a driver problem, but instead a "relative" or "absolute" positioning problem. I've recompiled the driver with totalWidth reconfigured, as mentioned earlier (I'll quote it if I remember to look again) but is anybody else running into this same problem? It seems to be less of a problem if I set "stylus" and "cursor" to different map values in GIMP (such as screen/window). More on that later, but has anybody solved this elusive issue?

I'm still working on this as well. Quick question: did you change both references of:
totalWidth += screenInfo.screens[i]->width;
to
totalWidth = screenInfo.screens[priv->currentScreen]->width;

Almost wondering whether that plus sign needs to be there... as in:

totalWidth += screenInfo.screens[priv->currentScreen]->width;

Not sure if that makes sense, since I can't really figure out what this code is trying to do, exactly. The statement occurs in a 'for' loop, where the 'i' variable value is incremented while its value is less than that of priv->numScreen... and I can't find where priv->numScreen is initialized. Maybe in the calling program...

[fenrisswolf]

Thanks for the how to!

Just one quick note to noobs (like me!) when using a serial tablet, and editing the xorg file, make sure your /dev/ttyS0 line includes that capital "S."

I was having the hardest time setting up my tablet until I noticed that typo! :lolflag:

[cipher_nemo]

Thank you everyone for helping with this! I currently use WinXP for working with Photoshop, etc., and am looking into getting a Cintiq 12WX or other Wacom tablet. It's good to know that there is hope for using it in GIMP with pressure sensitivity.

I prefer Photoshop (just because I'm use to it), but I don't mind GIMP if I get a little more comfortable with it. This will help make my eventual transition to exclusively use Ubuntu as my main desktop.

Thanks again everyone! :D

[markhammill]

I got a Toshiba Tecra M7 tablet PC and the pen is actually working, thanks to this howto. Thanks!

But I also want the button on my pen to do something. I would like it to work as a right mouse button. Now it just doesn't have any real function.

Any idea how I can activate it? Thanks in advance!

Hi FrankL,

I also have a Tecra M7 running Gutsy Gibbon but I haven't managed to get the stylus to work at all yet.

Could you tell me how to do it. Each time I try I can't boot the log in screen for some reason.

I have the intel graphics rather then the nvidia one if this makes a difference.

Have you got your headphones without the speakers, bluetooth, figure print reader or any of the other buttons working that you could help me on.

Thanks in advance.

[KaiserM]

Does anyone have the Xorg for the CTE-630 BT to get the pad buttons working?

This isn't correct:

Section "InputDevice"
Driver "wacom"
Identifier "pad"
Option "Device" "/dev/input/wacom"
Option "Type" "pad"
Option "ButtonsOnly" "on"
Option "Button9" "2"
Option "Button13" "3"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
Option "USB" "on"
Option "TVResolution" "1024x768,1024x768"
Option "ScreenNo" "0"
Option "Twinview" "horizontal"
EndSection

As you can see; I've tried near everything; at the moment I have pressure sensitivity working, just 2 bugs really.

When I power the tablet off and then back on, it gets all uncalibrated and functions hyperactively.

The two pad top buttons uh...don't work.

Any help would be appreciated.

Edit: I just changed dev/input/wacom to dev/input/event10; it didn't fix my buttons either

[waggingwabbit]

how do you guys find out about all those options you can input for the tablet?

[ERICwithanH]

Here: http://linuxwacom.sourceforge.net/index.php/howto/inputdev

My Wacom Intuos3 tablet works, but I'm having a a couple of problems. Some mouse clicks register, some don't -- it's super annoying. Also, the cursor moves two pixels at a time, rather than one, which sucks when I'm in Photoshop trying to do super precise work. When I use my pen, the cursor behaves exactly as it should; the cursor moves one pixel at a time and every click registers.

Does anyone have any advice they could give me?

I'm running Ubuntu 8.04 Hardy.

I tried multiple values for the Supress option and had little success.

Here's my xorg.conf file:


# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
Option "AddARGBGLXVisuals" "True"
Defaultdepth 24
Option "TwinView"
Option "MetaModes" "1680x1050 1680x1050"
EndSection

Section "Device"
Identifier "Configured Video Device"
Driver "nvidia"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
EndSection

Section "ServerLayout"
Identifier "Default Layout"
screen "Default Screen"
InputDevice "stylus" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents"
InputDevice "pad"
EndSection

Section "Monitor"
Identifier "Configured Monitor"
EndSection

Section "Extensions"
Option "Composite" "Enable"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "USB" "on"
Option "PressCurve" "50,0,100,50"

Option "KeepShape" "on"
Option "Suppress" "0"
Option "Twinview" "horizontal"
Option "ScreenNo" "0"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "USB" "on"

Option "KeepShape" "on"
Option "Twinview" "horizontal"
Option "ScreenNo" "0"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/input/wacom"
Option "Type" "cursor"
Option "Mode" "relative"
Option "USB" "on"

Option "Speed" "2"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "pad"
Option "Device" "/dev/input/wacom"
Option "Type" "pad"
Option "USB" "on"
EndSection

[baylessiii]

Hello. I'm completely new to Ubuntu, a professional artist who desperately wants to get this tablet working. I'm cringing as I ask this because I know it's probably simple: Where do I input that code you suggested? How do I get to a screen that accepts those lines you provided? Thank you so much in advance and I hope I made some sort of sense.

[xdarkday]

Hello. I'm completely new to Ubuntu, a professional artist who desperately wants to get this tablet working. I'm cringing as I ask this because I know it's probably simple: Where do I input that code you suggested? How do I get to a screen that accepts those lines you provided? Thank you so much in advance and I hope I made some sort of sense.

open terminal
sudo gedit /etc/X11/xorg.conf

[baylessiii]

open terminal
sudo gedit /etc/X11/xorg.conf

Hey, thank you so very much. My second day with Ubuntu and I love the interface already. I'm doubly impressed by the immense knowledge and helpfulness of the people here. If there are any reading suggestions and in what order for a totally green Ubuntu user, please let me know. I'd really like to be able to contribute as much as I can to this freeware effort. This stuff is wonderful!

[baylessiii]

Yikes! Stuck in low graphics mode. Any idea how to get out of this pickle? Thank you.

[baylessiii]

Okay!! Time for some pizza! It all worked out great, gang. Thanks again. I just opened up the xorg.conf console, made the modifications steps 8 - 12 called for and told Gimp about it. Intous 2 working perfectly! The mistake I made was leaving in
Option "ForceDevice" "ISDV4" #Tablet PC ONLY
My first clue should have been that I don't have a tablet pc, but hey, I'm catching on. Hungry to learn all I can about this stuff, and for pizza. Again, totally amazed and thankful there are people here sharp enough to make this happen and kind enough to share it.

[drummingpariah]

Again, totally amazed and thankful there are people here sharp enough to make this happen and kind enough to share it.

Isn't that what makes linux what it is? Share the love, whenever you find something good or have a good idea, pass it along.

[bonfire89]

I've tried the Twinview and ScreenNo options with and without xinerama.
They don't seem to have any effect on the problem in my case. As the effectiveness of stable solutions seems to vary so widely, I'm beginning to suspect it might be something else... like the xorg video drivers for my geriatric Voodoo5. I've sorted through - and updated - all the relevant wacom-related files and drivers i know about. Either there's something else that controls how xorg handles events, or there's something interfering.

That's just my suspicion.

screenNO has no effect with me either :(

[RemcoBoerma]

Thanks for the great recipe on how to set up the tablet!

I've got mine working, with pressure sensitivity, but also with some problem. I've used an old Wacom ET-0405-R (serial interface only) apparantly from the Graphire series.

All functionality is there, but the problem is that i get more functionality then i bargained for. . . It seems to me some kind of clock-tick is in the way "pressing" my tablet. . . A graphic example will show this best. See the screenshot.

I've tried setting something like Option "PressCurve" "50,0,100,50 but that also didn't help a thing.

Any help is appreciated - TIA

Xorg.conf:

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Default Screen" 0 0
InputDevice "Generic Keyboard" "CoreKeyboard"
InputDevice "Configured Mouse" "CorePointer"
InputDevice "stylus" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents" #For non-LCD tablets only
EndSection

Section "Module"
Load "glx"
Load "v4l"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/ttyS0" #SERIAL ONLY
Option "Type" "stylus"
Option "PressCurve" "0,0,100,100"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/ttyS0" #SERIAL ONLY
Option "Type" "eraser"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/ttyS0" #SERIAL ONLY
Option "Type" "cursor"
Option "Mode" "relative"
EndSection


Section "Monitor"
Identifier "Configured Monitor"
VendorName "Plug 'n' Play"
ModelName "Plug 'n' Play"
Gamma 1
ModeLine "1280x1024@75" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
ModeLine "1280x1024@60" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
EndSection

Section "Device"
Identifier "Configured Video Device"
Driver "nvidia"
BoardName "vesa"
Screen 0
EndSection

Section "Screen"
Identifier "Default Screen"
Device "Configured Video Device"
Monitor "Configured Monitor"
DefaultDepth 24
SubSection "Display"
Virtual 1280 1024
Depth 24
Modes "1280x1024@75" "1280x1024@60"
EndSubSection
EndSection

[Pokkulompus]

Works great!

[paradexes]

FYI Manga Studio EX 3.0 works under WINE. I followed this guide for pressure sensing and it works great!! Thanks :D

[Pokkulompus]

I managed to get the pen to work, but it moves slow and only when i press it against the tablet. Is it supposed to work like that or what did i do wrong? Help me, please!

[savanik]

I'm still having problems getting my tablet PC's stylus working. I've been following the instructions outlined on The Linux Wacom Project.

So far I have:

Verified that I am running with current updates
Have all the proper libraries loaded
Verified that the prebuilt modules will work with my kernel version (2.6.27-9-generic)
Installed the Wacom driver with the install script from linuxwacom-0.8.2 (most recent I could find)
Confirmed with 'wacdump' that it is picking up my stylus
Identified my stylus as /dev/ttyS1
Edited /etc/X11/xorg.conf in what should be the proper manner
Restarted X in the shell to watch error messages

And I'm still getting this:
(II) LoadModule: "wacom"
(II) Loading /usr/lib/xorg/modules/input//wacom_drv.so
dlopen: /usr/lib/xorg/modules/input//wacom_drv.so: undefined symbol: xf86errno
(EE) Failed to load /usr/lib/xorg/modules/input//wacom_drv.so

From what I understand, people are saying that the extra // doesn't matter, it's the xf86errno that matters. I've tried compiling and installing the module myself, but that doesn't seem to change matters. What output could I post up for people to help me? I'm tossing up my xorg.conf as a text file to start with.

It's a Gateway m275 Tablet PC, btw.

Sincerely,
Savanik

[Favux]

Hi savanik,

Another M275 owner, MGaddict2000, has been struggling to get going too at:

http://ubuntuforums.org/showthread.php?t=967147&page=8

You should get in touch. Also it's always worth trying these sites:

https://wiki.ubuntu.com/LaptopTestingTeam/

http://www.linux-on-laptops.com/

http://tuxmobil.org/

And Loic2's wiki on wacom drivers:

https://help.ubuntu.com/community/Wacom/LatestDriver

I've included MGaddict2000's xorg.conf to show where he was. You folks (M275) owners might want to start your own thread, if there isn't one already.

Found a good thread, this guy would be good to get into contact with:

http://ubuntuforums.org/showthread.php?t=984634&highlight=tablet+pc

[savanik]

I took another crack at it with my M275 and found that the module I had in the directory wasn't the one I compiled! It appears the install script flubbed somehow. After copying the compiled module into the proper directory, everything started working perfectly.

Then I just had to write some scripts with xrandr and xsetwacom to rotate the screen and rotate the stylus input properly. It's too bad it doesn't automatically do that, but I can deal with clicking on an icon.

savanik

[Loghtyrian]

Hi:

I'm a new user of Ubuntu, I'm trying to get my Bamboo Tablet set up to work with it and i've followed the instructions found in this thread but after changing my xorg.conf and rebooting I get an error and Ubuntu starts at low graphics mode plus the tablet doesn't respond. Any idea or what the problem may be?

This is how my xorg looks like now without any change:

# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# Note that some configuration settings that could be done previously
# in this file, now are automatically configured by the server and settings
# here are ignored.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Monitor"
Identifier "Configured Monitor"
EndSection

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
DefaultDepth 24
EndSection

Section "Module"
Load "glx"
EndSection

Section "Device"
Identifier "Configured Video Device"
Driver "nvidia"
Option "NoLogo" "True"
EndSection

[Favux]

Hi Loghtyrian,

I'm going to assume you are using Intrepid from your xorg.conf. The attached xorg.conf should work for you. Be sure to back up your current xorg.conf. Also compare the two before using so you can review the changes and can correct any obvious mistakes I made.

Since you are new ask me if you have any questions about backing up, etc.

[Loghtyrian]

Hi Favux,

Thanks for the aid, I have my pen working now with Ubuntu, but now the mouse of the tablet doesn't respond :lolflag: any idea if I can get the mouse to work too?

THANKS ! ! !

[Favux]

Hi Loghtyrian,

Sorry, I didn't realize it came with a Wacom mouse. Are there different Bamboo models or was it an option?

Also to set up your tablet buttons see post #7 here: http://ubuntuforums.org/showthread.php?t=1098822

Anyway try this xorg.conf. Same cautions as before.

[Loghtyrian]

It's a Bamboo Fun Tablet, it comes with the mouse. Thanks for your help Favux now i got my tablet fully functional. I tried with the Gimp and works fine.

I really apreciate your help.

THX ! ! !

[Favux]

You're welcome. Have fun.

[Jordanwb]

I was thinking of getting on of these so I just might. Bookmarked.

[loklaan]

I have a Bamboo Fun small 4x5, and took the instructions from the first page and had them work for me in GIMP, but the problem is when I dont have the tablet plugged in, errors come up about not finding the tablet and being unable to start X...

I have a Bamboo Fun

[Favux]

Hi BuNsiE,

Jaunty uses the HAL/.fdi method. So you don't need to add the Wacom sections to xorg.conf like the tutorial up front does. The Wacom stuff is in 10-wacom.fdi. So if you changed your xorg.conf that may be the problem.

[loklaan]

Oh ok, I changed my xorg.conf then, and I'll look into what you said. Thanks Favux!

[loklaan]

Hi BuNsiE,

Jaunty uses the HAL/.fdi method. So you don't need to add the Wacom sections to xorg.conf like the tutorial up front does. The Wacom stuff is in 10-wacom.fdi. So if you changed your xorg.conf that may be the problem.

I reinstalled my hal packages and wacom-tools, but my bamboo fun still acts like a mouse - no pressure sensitivity etc...

[Favux]

Hi BuNsiE,

But the warnings are gone, correct?

In Gimp when you configured input devices did you tell it when doing stylus that mode was screen? That should get pressure.

The Wacom wiki: https://help.ubuntu.com/community/Wacom

has a link to: https://help.ubuntu.com/community/Wacom.fdi

The 10-wacom.fdi is in /usr/share/hal/fdi/policy/20thirdparty/. Right now there is a problem with the way linuxwacom 0.8.2-2 drivers and wacom-tools are implemented in Jaunty. We've figured out a couple work arounds but it looks like they (Ubuntu) are getting ready to fix things. But I admit I don't know when that will happen. So I don't know if you want to put a lot of time into it right now.

[loklaan]

I only get three devices when trying to configure Gimp, and they are my mouse, touchpad and mac mouse emulation. The stylus and eraser options are not there...

What should I do to the .fdi to get them working on hotplugging the tablet?

[Favux]

Hi again BuNsiE,

I'm not sure what's going on. Even with the problems I think you should have stylus (maybe not eraser). So is something else going on also? Problem with your tablet hot plugging? Have you tried booting with it plugged in? Have you checked that your .fdi file is there? In Synaptics do you see 0.8.2-2 xorg-xserver-wacom-input and wacom-tools are installed?

I'll point you to the work arounds so at least you have an explanation. But I think you may be looking at a separate problem. Read Jaunty Users near the top here: http://ubuntuforums.org/showthread.php?t=1038949 It is possible that you need to do the substitution of the 0.8.3-2 wacom.ko for the 0.8.2-2 one as described in work around 1. The Bamboo is usb correct? But be careful and read things through before deciding to do anything.

[tjb_15]

Great instructions. I was trying to get it to work with the instructions off of the wacom-tools site but that just screwed up the mouse fuction. I reinstalled and now it works exactly like it did in windows!!!!!! Thanks so much..

Also I sat here for about 3-4 hours trying to get the eraser and pen to work right in gimp before I realized that I was following your directions incorrectly. I was going into the Input Controllers (and using Linux Inputs) instead of the Input Devices (and using Configure Extended Input Devices...). ](*,)

Now I just need to get my G15 working. ;-)

[sunite]

hey guys, thanks for all the great info.

However I found something interesting, which finally solved my problem:
https://wiki.ubuntu.com/LaptopTestingTeam/ToshibaPortegeM700

[jisaac]

Hi,

Someone manage to get the pressure working under a recent wine (>= 1.1.23)?

Please let me know,

Thanks.

[hjvv]

Hello UbuntuHeads,

I've done this

sudo apt-get install wacom-toolsBut.... sorry, newby here.... struggling with Ubuntu 9.10 and Wacom Bamboo tablet.... where do I enter the rest of the code? I would really appeciate a hint :)

[MechanteAnemone]

Another set of thanks for the instructions. I'm new to Linux, installed Ubuntu 10,04, followed the instructions on configuring The GIMP, and Bob's your uncle! I'm in business again with my Wacom tablet, with buttons remapped to suit my preferences. I also installed MyPaint, which works really nicely with Wacom devices.

[cr0max]

Hello,

I just can't get this damn thing to work. I'm using Ubuntu 9.10. The stylus doesn't work as a mouse, It's not even recognized, xsetwacom list returns nothing. The only thing thats happening when I plug it in is that the LED of the tablet shines and changes it's color when the stylus is brought near the surface. What's the problem? I have, of course, installed the wacom-tools and the xorg-xserver-input-wacom package.

This is my xorg.conf:
Section "Screen"
Identifier "Default Screen"
DefaultDepth 24
Option "AddARGBGLXVisuals" "True"
SubSection "Display"
Depth 24
Modes "1024x786"
EndSubSection
EndSection

Section "Module"
Load "glx"
Disable "dri2"
EndSection

Section "Device"
Identifier "Default Device"
Driver "nvidia"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mouse1"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/input/event0"
Option "Type" "stylus"
Option "USB" "on"
Option "PressCurve" "50,0,100,50"
Option "Mode" "Absolute"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/input/event0"
Option "Type" "eraser"
Option "USB" "on"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/input/event0"
Option "Type" "cursor"
Option "Mode" "relative"
Option "USB" "on"
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "stylus" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents"
InputDevice "pad"
EndSectionAdditionally, xserver returns following error when started with that config.
(EE) Problem parsing the config file
(EE) Error parsing the config file

Fatal server error:
no screens foundI have already tried it with an empty xorg.conf - nothing. xserver-xorg-input-wacom is version 1:0.8.4.1-0

xinput --list shows
"Virtual core pointer" id=0 [XPointer]
Num_buttons is 32
Num_axes is 2
Mode is Relative
Motion_buffer is 256
Axis 0 :
Min_value is -1
Max_value is -1
Resolution is 0
Axis 1 :
Min_value is -1
Max_value is -1
Resolution is 0
"Virtual core keyboard" id=1 [XKeyboard]
Num_keys is 248
Min_keycode is 8
Max_keycode is 255
"Power Button" id=2 [XExtensionKeyboard]
Type is KEYBOARD
Num_keys is 248
Min_keycode is 8
Max_keycode is 255
"Power Button" id=3 [XExtensionKeyboard]
Type is KEYBOARD
Num_keys is 248
Min_keycode is 8
Max_keycode is 255
"ImPS/2 Logitech Wheel Mouse" id=4 [XExtensionPointer]
Type is MOUSE
Num_buttons is 7
Num_axes is 2
Mode is Relative
Motion_buffer is 256
Axis 0 :
Min_value is -1
Max_value is -1
Resolution is 1
Axis 1 :
Min_value is -1
Max_value is -1
Resolution is 1
"AT Translated Set 2 keyboard" id=5 [XExtensionKeyboard]
Type is KEYBOARD
Num_keys is 248
Min_keycode is 8
Max_keycode is 255
"Macintosh mouse button emulation" id=6 [XExtensionPointer]
Type is MOUSE
Num_buttons is 5
Num_axes is 2
Mode is Relative
Motion_buffer is 256
Axis 0 :
Min_value is -1
Max_value is -1
Resolution is 1
Axis 1 :
Min_value is -1
Max_value is -1
Resolution is 1
xidump -l shows:
Virtual core pointer disabled
Virtual core keyboard keyboard
Power Button extension
Power Button extension
ImPS/2 Logitech Wheel Mouse extension
AT Translated Set 2 keyboard extension
Macintosh mouse button emulation extension
more /proc/bus/input/devices
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
U: Uniq=
H: Handlers=kbd event0
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1
U: Uniq=
H: Handlers=kbd event1
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0017 Vendor=0001 Product=0001 Version=0100
N: Name="Macintosh mouse button emulation"
P: Phys=
S: Sysfs=/devices/virtual/input/input2
U: Uniq=
H: Handlers=mouse0 event2
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input3
U: Uniq=
H: Handlers=kbd event3
B: EV=120013
B: KEY=4 2000000 3803078 f800d001 feffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0011 Vendor=0002 Product=0005 Version=0051
N: Name="ImPS/2 Logitech Wheel Mouse"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input4
U: Uniq=
H: Handlers=mouse1 event4
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=103



Thanks

[cr0max]

Update:
I've compiled and installed the linuxwacom wacom.ko 0.8.8.8 as described here (http://frankgroeneveld.nl/2010/04/12/get-wacom-bamboo-pen-working-in-ubuntu-karmic/). Now the tablet is at least recognized by xsetwacom list as
xsetwacom list
Wacom_Bamboo_Craft_Finger stylus


grep -i wacom /var/log/messages | tail returns:
Jul 28 21:19:02 LHC kernel: [ 2427.704145] input: Wacom Bamboo Craft Pen as /devices/pci0000:00/0000:00:02.1/usb3/3-1/3-1:1.0/input/input11
Jul 28 21:19:02 LHC kernel: [ 2427.789496] input: Wacom Bamboo Craft Finger as /devices/pci0000:00/0000:00:02.1/usb3/3-1/3-1:1.1/input/input12


and cat /var/log/Xorg.0.log
(II) config/hal: Adding input device Wacom Bamboo Craft Finger
(II) Synaptics touchpad driver version 1.1.2
(**) Option "Device" "/dev/input/event6"
(II) Wacom Bamboo Craft Finger: x-axis range 0 - 480
(II) Wacom Bamboo Craft Finger: y-axis range 0 - 320
(II) Wacom Bamboo Craft Finger: pressure range 0 - 1023
(II) Wacom Bamboo Craft Finger: finger width range 0 - 0
(II) Wacom Bamboo Craft Finger: buttons: double triple
(--) Wacom Bamboo Craft Finger: touchpad found
(**) Wacom Bamboo Craft Finger: always reports core events
(II) XINPUT: Adding extended input device "Wacom Bamboo Craft Finger" (type: TOUCHPAD)
(**) Wacom Bamboo Craft Finger: (accel) keeping acceleration scheme 1
(**) Wacom Bamboo Craft Finger: (accel) filter chain progression: 2.00
(**) Wacom Bamboo Craft Finger: (accel) filter stage 0: 20.00 ms
(**) Wacom Bamboo Craft Finger: (accel) set acceleration profile 0
(--) Wacom Bamboo Craft Finger: touchpad found


STILL the stylus doesn't do anything. any idea?

[Favux]

Hi cr0max,

Welcome to Ubuntu forums!

What tablet model do you have? Your xorg.conf in the first post is missing the pad section which is probably the parse error. Are you also using a 10-linuxwacom.fdi? That should be located at /usr/share/hal/fdi/policy/20thirdparty/. You should use one or the other. The .fdi let's you hot plug.

[cr0max]

Thanks Favux,

yes I'm using /usr/share/hal/fdi/policy/20thirdparty/10-linuxwacom.fdi from linuxwacom 0.8.8-8 and in the xorg.conf right now only
Section "Screen"
Identifier "Default Screen"
DefaultDepth 24
Option "AddARGBGLXVisuals" "True"
SubSection "Display"
Depth 24
Modes "1024x786"
EndSubSection
EndSection

Section "Module"
Load "glx"
Disable "dri2"
EndSection

Section "Device"
Identifier "Default Device"
Driver "nvidia"
EndSectionNo movement though. This really really sucks :(

Strange thing:
xsetwacom list returns nothing (it did yesterday). though wacdump /dev/input/event4 shows some rightish input from the stylus.

I got a bamboo and after rereading first page, I reckon I don't need the pad record. Seemingly you were right about the error either. No movement, though. Do I actually need the xorg.conf under Karmic ?

[Favux]

In Karmic you need the xorg.conf for the Nvidia video sections if you are using the proprietary drivers. I think you have the Bamboo Fun (CTH661). Try the .fdi in post #384 (http://ubuntuforums.org/showpost.php?p=8165182&postcount=384).

Also you want to see if the usb kernel driver wacom.ko is auto-loading:
lsmod | grep wacom
If you don't see wacom try adding it the the modules file in /etc/

[cr0max]

In Karmic you need the xorg.conf for the Nvidia video sections if you are using the proprietary drivers. I think you have the Bamboo Fun (CTH661). Try the .fdi in post #384 (http://ubuntuforums.org/showpost.php?p=8165182&postcount=384).

Also you want to see if the usb kernel driver wacom.ko is auto-loading:
lsmod | grep wacomIf you don't see wacom try adding it the the modules file in /etc/
Oh pardon me, the model is CTH-461.
Does the xorg-entry for the nvidia drivers interfere with the .fdi ? I now have your .fdi in use, but xsetwacom list returns

touch touch
no stylus.
xinput --list only returns touth too:
"touch" id=6 [XExtensionPointer]
Type is TOUCHPAD
Num_buttons is 12
Num_axes is 2
Mode is Relative
Motion_buffer is 256
Axis 0 :
Min_value is 0
Max_value is 480
Resolution is 1
Axis 1 :
Min_value is 0
Max_value is 320
Resolution is 1


lsmod | grep wacom returns
wacom 33660 0


thanks

[Favux]

Hi cr0max,

OK, it looks like your linuxwacom drivers aren't working. The touchpad is either coming from the Synaptic .fdi/driver, in which case we need to fix the Synaptic .fdi, or the evdev .fdi/driver. Once 'xinput --list' shows stylus, eraser, touch, and pad and 'xsetwacom list' agrees with it you should be good to go.

The way to find out what's going on is to look at Xorg.0.log in /var/log. Go ahead and post it as an attachment.

Do you have a 64-bit install? Is your kernel something other than the generic?

[cr0max]

Hello Favux,

The kernel is the normal 32 bit.

I think here we really have the problem...
(II) config/hal: Adding input device stylus
(II) LoadModule: "wacom"
(WW) Warning, couldn't open module wacom
(II) UnloadModule: "wacom"
(EE) Failed to load module "wacom" (module does not exist, 0)
(EE) No input driver matching `wacom'As mentioned it's the 0.8.8-8 linuxwacom wacom.ko

modinfo -n wacom
/lib/modules/2.6.31-22-generic/kernel/drivers/input/tablet/wacom.ko
Thanks for your efforts.

[Favux]

Sure.

You're right. That could mean there's something wrong with the linuxwacom X driver. Synaptic is showing up. I'm not sure if it's causing a problem or not but let's fix it first. The changes to it's .fdi won't hurt anything and it'll eliminate a variable. Don't worry if touch disappears from 'xinput --list' afterwords. See: http://ubuntuforums.org/showpost.php?p=8372380&postcount=22

[cr0max]

Sure.

You're right. That could mean there's something wrong with the linuxwacom X driver. Synaptic is showing up. I'm not sure if it's causing a problem or not but let's fix it first. The changes to it's .fdi won't hurt anything and it'll eliminate a variable. Don't worry if touch disappears from 'xinput --list' afterwords. See: http://ubuntuforums.org/showpost.php?p=8372380&postcount=22

Ok the .fdi looks like this now:
<?xml version="1.0" encoding="ISO-8859-1"?>
<deviceinfo version="0.2">
<device>
<match key="info.capabilities" contains="input.touchpad">
<match key="info.product" contains="Synaptics">
<merge key="input.x11_driver" type="string">synaptics</merge>
<match key="/org/freedesktop/Hal/devices/computer:system.hardware.product" string="Inspiron 1011">
<merge key="input.x11_options.JumpyCursorThreshold" type="string">90</merge>
<merge key="input.x11_options.AreaBottomEdge" type="string">4100</merge>
</match>
<match key="/org/freedesktop/Hal/devices/computer:system.hardware.product" string="Inspiron 1012">
<merge key="input.x11_options.JumpyCursorThreshold" type="string">90</merge>
<merge key="input.x11_options.AreaBottomEdge" type="string">4100</merge>
</match>
<match key="/org/freedesktop/Hal/devices/computer:system.hardware.product" string="HP MiniNote 1000">
<merge key="input.x11_options.JumpyCursorThreshold" type="string">200</merge>
</match>
</match>
</match>
</device>
</deviceinfo>

[cr0max]

After a restart the Xorg.0.log still contains the same error message.
By the way: shouldnt modprobe -v wacom return an error too ?

[Favux]

Alright. The question is, is it the right wacom.ko? When I lsmod the 0.8.8-8 I get:
wacom 45568 0
Notice the size difference from what you posted. So either you didn't copy the compiled wacom.ko correctly or something went wrong with the compile. Like not including the right dependencies. Did you need hid-ids.h? Karmic is unique in requiring that. That's the alternate step 3 in Section 1. See the linuxwacom HOW TO (http://ubuntuforums.org/showpost.php?p=6546012&postcount=1).

[cr0max]

Is that ok?
./configure --enable-wacom --prefix=/usr | grep no
checking for gawk... no
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether we are cross compiling... no
checking for gcc option to accept ISO C89... none needed
checking for a sed that does not truncate output... /bin/sed
checking for g77... no
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... no
checking for g95... no
checking for xlf95... no
checking for f95... no
checking for fort... no
checking for ifort... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for ftn... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking if gcc supports -fno-rtti -fno-exceptions... no
checking whether -lc should be explicitly linked in... no
checking for xserver libc-wrapper header-files... no
checking if scaling tablet to screen size is needed... no
checking if Xorg is 7.3 or earlier... no
checking if Xorg server is version 1.7 or later... no
checking if wacomxrrd should be built... checking X11/extensions/Xrandr.h usability... no
checking X11/extensions/Xrandr.h presence... no
checking for X11/extensions/Xrandr.h... no
no
checking if gcc accepts -fno-merge-constants... yes
checking if gcc accepts -fno-stack-protector... yes
XFree86 source - no
XSERVER64 - no
xf86config - no
wacomxrrd - no
hid.o - no
wacom_drv.o - no
You write
For Karmic use:sudo cp ./src/2.6.31/wacom.ko /lib/modules/`uname -r`/kernel/drivers/input/tablet/wacom.kothe linuxwacom 0.8.8-8 doesn't have /src/2.6.31/ so I'm using /src/2.6.30/ is that ok ? I don't know if I needed hid-ids.h, I just downloaded it following your instructions.

[Favux]

Looks OK so far. I need to see the section where it tells us what it'll build after:
checking if gcc accepts -fno-stack-protector... yes
XFree86 source - no
XSERVER64 - no
xf86config - no
wacomxrrd - no
hid.o - no
wacom_drv.o - no
But if there is a wacom.ko now in /src/2.6.30/ you should be OK. If it didn't compile it wouldn't be there. They've been consolidating the folders where the wacom.ko is placed, which is why it's so confusing. But /src/2.6.30/ should be the right place now.

[cr0max]

I better post the whole thing:
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for gawk... (cached) mawk
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognize dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... no
checking for g95... no
checking for xlf95... no
checking for f95... no
checking for fort... no
checking for ifort... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for ftn... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking the maximum length of command line arguments... 1572864
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
(cached) (cached) checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for HAL... yes
checking for arch type... i486-linux-gnu
checking for kernel type... Linux
checking for linux-based kernel... yes
checking for kernel source/headers... /lib/modules/2.6.31-22-generic/build
checking kernel version... 2.6.31-22-generic
checking for kernel module support... yes
checking for Xlib... yes
checking for XSERVER... yes
checking for xserver libc-wrapper header-files... no
checking if scaling tablet to screen size is needed... no
checking if Xorg server is version 1.4 or later... yes
checking if Xorg is 7.3 or earlier... no
checking if Xorg server is version 1.5.2 or later... yes
checking if Xorg server is version 1.6 or later... yes
checking if Xorg server is version 1.7 or later... no
checking if Xorg SDK defined IsXExtensionPointer... yes
checking if Xorg SDK defines dixScreenOrigins... yes
checking XInput extension version... >= 2.0
checking for lib xf86config... checking for X... libraries , headers
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for tclsh... /usr/bin/tclsh
checking for tcl version... 8.4
checking for tcl header files... found, /usr/include/tcl8.4
checking for tk header files... found, /usr/include/tcl8.4
checking ncurses.h usability... yes
checking ncurses.h presence... yes
checking for ncurses.h... yes
checking if libwacomcfg should/can be built... yes
checking if libwacomxi should/can be built... yes
checking if wacdump should/can be built... yes
checking if xidump should/can be built... yes
checking if xsetwacom should be built... yes
checking if wacomxrrd should be built... checking X11/extensions/Xrandr.h usability... no
checking X11/extensions/Xrandr.h presence... no
checking for X11/extensions/Xrandr.h... no
no
checking for Wacom X driver module path... /usr/lib/xorg/modules/input
checking for dynamic driver loading support... yes
checking if wacom_drv.{o,so} should be compiled... yes
checking if gcc accepts -fno-merge-constants... yes
checking if gcc accepts -fno-stack-protector... yes

configure: creating ./config.status
config.status: creating Makefile
config.status: creating mkxincludes
config.status: creating src/Makefile
config.status: creating src/util/Makefile
config.status: creating src/xdrv/Makefile
config.status: creating src/2.6.16/Makefile
config.status: creating src/2.6.18/Makefile
config.status: creating src/2.6.24/Makefile
config.status: creating src/2.6.30/Makefile
config.status: creating src/wacomxi/Makefile
config.status: creating src/wacomxi/wacomcpl
config.status: creating src/include/xdrv-config.h
config.status: src/include/xdrv-config.h is unchanged
config.status: creating src/include/kernel-config.h
config.status: src/include/kernel-config.h is unchanged
config.status: creating src/include/util-config.h
config.status: src/include/util-config.h is unchanged
config.status: executing depfiles commands

----------------------------------------
BUILD ENVIRONMENT:
architecture - i486-linux-gnu
linux kernel - yes 2.6.30
kernel source - yes /lib/modules/2.6.31-22-generic/build
XFree86 source - no
Xorg SDK - yes /usr/include/xorg
XSERVER64 - no
dlloader - yes
XLib - yes /usr/lib
xf86config - no
TCL - yes /usr/include/tcl8.4
TK - yes /usr/include/tcl8.4
ncurses - yes

BUILD OPTIONS:
wacom.o - yes
wacdump - yes
xidump - yes
libwacomcfg - yes
libwacomxi - yes
xsetwacom - yes
wacomxrrd - no
hid.o - no
wacom_drv.so - yes /usr/lib/xorg/modules/input
wacom_drv.o - no
wacom*_drv quirks - hal IsXExtensionPointer key-events dixScreenOrigins
----------------------------------------


Your wacom.ko will be available under
/home/mux/linuxwacom-0.8.8-8/src/2.6.30
thanks

btw, take a look at this modinfo -d wacom
USB Wacom tablet driver
USB Wacom tablet driver

= two drivers ?

[cr0max]

lsmod | grep wacom
wacom 33660 0
/lib/modules/2.6.31-22-generic/kernel/drivers/input/tablet$ ls -l | grep wacom
-rw-r--r-- 1 root root 46915 2010-07-29 19:47 wacom.ko
Isn't this strange ?

After another compilation of linuxwacom 0.8.8-8 xsetwacom lists the stylus, at least. nothing more, though. and no movement.

[Favux]

Good.
BUILD ENVIRONMENT:
architecture - i486-linux-gnu
linux kernel - yes 2.6.30
kernel source - yes /lib/modules/2.6.31-22-generic/build
XFree86 source - no
Xorg SDK - yes /usr/include/xorg
XSERVER64 - no
dlloader - yes
XLib - yes /usr/lib
xf86config - no
TCL - yes /usr/include/tcl8.4
TK - yes /usr/include/tcl8.4
ncurses - yes

BUILD OPTIONS:
wacom.o - yes
wacdump - yes
xidump - yes
libwacomcfg - yes
libwacomxi - yes
xsetwacom - yes
wacomxrrd - no
hid.o - no
wacom_drv.so - yes /usr/lib/xorg/modules/input
wacom_drv.o - no
wacom*_drv quirks - hal IsXExtensionPointer key-events dixScreenOrigins

Is telling you it is ready to build the usb kernel driver wacom.ko:
wacom.o - yes
and the X driver:
wacom_drv.so - yes /usr/lib/xorg/modules/input

Don't worry about the 'modinfo -d wacom'. That's what it's returning now, instead of the more informative output. I don't know why.

[cr0max]

So the error is gone

X.Org X Server 1.6.4
Release Date: 2009-9-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-27-server i686 Ubuntu
Current Operating System: Linux LHC 2.6.31-22-generic #60-Ubuntu SMP Thu May 27 00:22:23 UTC 2010 i686
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.31-22-generic root=UUID=b108434f-97f8-44cf-a06b-b52f0889e0c8 ro quiet splash
Build Date: 06 May 2010 09:30:46PM
xorg-server 2:1.6.4-2ubuntu4.3 (buildd@)
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Jul 29 19:49:53 2010
(==) Using config file: "/etc/X11/xorg.conf"
(==) No Layout section. Using the first Screen section.
(**) |-->Screen "Default Screen" (0)
(**) | |-->Monitor "<default monitor>"
(==) No device specified for screen "Default Screen".
Using the first device section listed.
(**) | |-->Device "Default Device"
(==) No monitor specified for screen "Default Screen".
Using a default monitor configuration.
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
Entry deleted from font path.
(==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
built-ins
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
If no devices become available, reconfigure HAL or disable AllowEmptyInput.
(II) Loader magic: 0x3bc0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 5.0
X.Org XInput driver : 4.0
X.Org Server Extension : 2.0
(II) Loader running on linux
(++) using VT number 7

(--) PCI:*(0:3:0:0) 10de:0201:1043:4057 nVidia Corporation NV20 [GeForce3 Ti 200] rev 163, Mem @ 0xd0000000/16777216, 0xd8000000/67108864, 0xdc000000/524288, BIOS @ 0x????????/65536
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(WW) "dri2" will not be loaded unless you've specified it to be loaded elsewhere.
(II) "extmod" will be loaded by default.
(II) "dbe" will be loaded by default.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "record" will be loaded by default.
(II) "dri" will be loaded by default.
(II) "dri2" will be loaded even though the default is to disable it.
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
(II) NVIDIA GLX Module 96.43.13 Thu Jun 25 18:56:56 PDT 2009
(II) Loading extension GLX
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.6.4, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.6.4, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.6.4, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.6.4, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers//nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) NVIDIA dlloader X Driver 96.43.13 Thu Jun 25 18:45:26 PDT 2009
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 03@00:00:0
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.6.4, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "AddARGBGLXVisuals" "True"
(**) NVIDIA(0): Enabling RENDER acceleration
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0): enabled.
(II) NVIDIA(0): NVIDIA GPU GeForce3 Ti 200 at PCI:3:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 65536 kBytes
(--) NVIDIA(0): VideoBIOS: 03.20.00.18.00
(II) NVIDIA(0): Detected AGP rate: 4X
(--) NVIDIA(0): Interlaced video modes are not supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce3 Ti 200 at PCI:3:0:0:
(--) NVIDIA(0): LKM (CRT-0)
(--) NVIDIA(0): Philips 7108 TV Encoder (TV-0)
(--) NVIDIA(0): LKM (CRT-0): 350.0 MHz maximum pixel clock
(--) NVIDIA(0): Philips 7108 TV Encoder (TV-0): 165.0 MHz maximum pixel clock
(--) NVIDIA(0): TV encoder: Philips 7108
(II) NVIDIA(0): Assigned Display Device: CRT-0
(WW) NVIDIA(0): No valid modes for "1024x786"; removing.
(WW) NVIDIA(0):
(WW) NVIDIA(0): Unable to validate any modes; falling back to the default mode
(WW) NVIDIA(0): "nvidia-auto-select".
(WW) NVIDIA(0):
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "nvidia-auto-select"
(II) NVIDIA(0): Virtual screen size determined to be 640 x 400
(--) NVIDIA(0): DPI set to (50, 42); computed from "UseEdidDpi" X config
(--) NVIDIA(0): option
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(II) NVIDIA(0): Initialized GART.
(II) NVIDIA(0): Built-in logo is bigger than the screen.
(II) NVIDIA(0): Setting mode "nvidia-auto-select"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(II) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(==) RandR enabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing extension GLX
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
compiled for 1.6.4, module version = 2.2.5
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 4.0
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT Translated Set 2 keyboard: Device: "/dev/input/event3"
(II) AT Translated Set 2 keyboard: Found keys
(II) AT Translated Set 2 keyboard: Configuring as keyboard
(II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc105"
(**) Option "xkb_layout" "de"
(II) config/hal: Adding input device Power Button
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event1"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc105"
(**) Option "xkb_layout" "de"
(II) config/hal: Adding input device Power Button
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event0"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc105"
(**) Option "xkb_layout" "de"
(II) config/hal: Adding input device ImPS/2 Logitech Wheel Mouse
(**) ImPS/2 Logitech Wheel Mouse: always reports core events
(**) ImPS/2 Logitech Wheel Mouse: Device: "/dev/input/event6"
(II) ImPS/2 Logitech Wheel Mouse: Found 3 mouse buttons
(II) ImPS/2 Logitech Wheel Mouse: Found x and y relative axes
(II) ImPS/2 Logitech Wheel Mouse: Found scroll wheel(s)
(II) ImPS/2 Logitech Wheel Mouse: Configuring as mouse
(**) ImPS/2 Logitech Wheel Mouse: YAxisMapping: buttons 4 and 5
(**) ImPS/2 Logitech Wheel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "ImPS/2 Logitech Wheel Mouse" (type: MOUSE)
(**) ImPS/2 Logitech Wheel Mouse: (accel) keeping acceleration scheme 1
(**) ImPS/2 Logitech Wheel Mouse: (accel) filter chain progression: 2.00
(**) ImPS/2 Logitech Wheel Mouse: (accel) filter stage 0: 20.00 ms
(**) ImPS/2 Logitech Wheel Mouse: (accel) set acceleration profile 0
(II) ImPS/2 Logitech Wheel Mouse: initialized for relative axes.
(II) config/hal: Adding input device Wacom Bamboo Craft Finger
(II) LoadModule: "synaptics"
(II) Loading /usr/lib/xorg/modules/input//synaptics_drv.so
(II) Module synaptics: vendor="X.Org Foundation"
compiled for 1.6.4, module version = 1.1.2
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 4.0
(II) Synaptics touchpad driver version 1.1.2
(**) Option "Device" "/dev/input/event5"
(II) Wacom Bamboo Craft Finger: x-axis range 0 - 480
(II) Wacom Bamboo Craft Finger: y-axis range 0 - 320
(II) Wacom Bamboo Craft Finger: pressure range 0 - 1023
(II) Wacom Bamboo Craft Finger: finger width range 0 - 0
(II) Wacom Bamboo Craft Finger: buttons: double triple
(--) Wacom Bamboo Craft Finger: touchpad found
(**) Wacom Bamboo Craft Finger: always reports core events
(II) XINPUT: Adding extended input device "Wacom Bamboo Craft Finger" (type: TOUCHPAD)
(**) Wacom Bamboo Craft Finger: (accel) keeping acceleration scheme 1
(**) Wacom Bamboo Craft Finger: (accel) filter chain progression: 2.00
(**) Wacom Bamboo Craft Finger: (accel) filter stage 0: 20.00 ms
(**) Wacom Bamboo Craft Finger: (accel) set acceleration profile 0
(--) Wacom Bamboo Craft Finger: touchpad found
(II) config/hal: Adding input device Wacom Bamboo Craft Pen
(II) LoadModule: "wacom"
(II) Loading /usr/lib/xorg/modules/input//wacom_drv.so
(II) Module wacom: vendor="X.Org Foundation"
compiled for 1.6.4, module version = 1.0.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 4.0
(II) Wacom driver level: 47-0.8.8-7 $
(**) Option "Device" "/dev/input/event4"
Wacom got Pid oxd2
Wacom got Pid oxd2 again
(EE) PreInit returned NULL for "Wacom Bamboo Craft Pen"
(EE) config/hal: NewInputDeviceRequest failed (8)
(II) config/hal: Adding input device Macintosh mouse button emulation
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event2"
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
(**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1
(**) Macintosh mouse button emulation: (accel) filter chain progression: 2.00
(**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
(**) Macintosh mouse button emulation: (accel) set acceleration profile 0
(II) Macintosh mouse button emulation: initialized for relative axes.
(II) NVIDIA(0): Setting mode "CRT-0:1024x768@1024x768+0+0"

But why doesn't it recognize the eraser and cursor ?

the output of xinput --list
"Wacom Bamboo Craft Finger" id=6 [XExtensionPointer]
Type is TOUCHPAD
Num_buttons is 12
Num_axes is 2
Mode is Relative
Motion_buffer is 256
Axis 0 :
Min_value is 0
Max_value is 480
Resolution is 1
Axis 1 :
Min_value is 0
Max_value is 320
Resolution is 1


bye

[Favux]

OK, I'm confused. It looked good. You used:
sudo cp ./src/2.6.30/wacom.ko /lib/modules/`uname -r`/kernel/drivers/input/tablet/wacom.ko
to copy the wacom.ko into place?

[cr0max]

OK, I'm confused. It looked good. You used:
sudo cp ./src/2.6.30/wacom.ko /lib/modules/`uname -r`/kernel/drivers/input/tablet/wacom.koto copy the wacom.ko into place?
positive.

edit: as stated, modinfo returns two drivers if I'm not totally misunderstanding it, this would explain the different sizes.
modinfo -d wacom
USB Wacom tablet driver
USB Wacom tablet driver

[Favux]

Well, the only one that should matter would be at /lib/modules/`uname -r`/kernel/drivers/input/tablet/. You could do a find on your drive for wacom.ko and see if there's another one (not in the linuxwacom source code) I suppose.

I'm wondering if you have more than one 10-linuxwacom.fdi at this point. The duplicate called 10-wacom.fdi maybe? You only want one.

[cr0max]

No, only one .fdi. :(

[Favux]

And its contents are just the those in the new-working .fdi?

[cr0max]

yes, the one I posted.
what exactly does it actually do, if I may ask ?

[Favux]

yes, the one I posted.
what exactly does it actually do, if I may ask ?
Ahh. That's the Synaptic .fdi (5-synaptic.fdi?), not the wacom .fdi (10-linuxwacom.fdi). The wacom .fdi is at post #384 that I linked you to. It's the new-working one attached to the post.

Well .fdi stands for device information file. It matches to a device and then configures the device. The HAL/.fdi stuff was a temporary detour to get usb hotplugging. You couldn't do hot plugging with the old udev/xorg.conf. Now with the new udev and .conf files HAL/.fdi is no longer needed for hot plugging. That starts with Lucid.

[cr0max]

Oh I'm sorry, I thought I had posted the 10-linuxwacom.fdi, but it was indeed the synaptics.fdi. I tried both your 10-linuxwacom and the .fdi from the linuxwacom 0.8.8-8 folder. nothing. If I use yours, it doesn't even show the stylus. :(

[cr0max]

I am now using the 0.8.6-2 driver and your 10-linuxwacom.fdi and at least I can now use the stylus as a mouse. The eraser is still not recognized by xinput and xsetwacom. Also, if I set the stylus to relative instead of absolute, that slows my system down a bit and the lines are a bit zig zag. Is that "normal" ?

[Favux]

I am now using the 0.8.6-2 driver and your 10-linuxwacom.fdi and at least I can now use the stylus as a mouse. The eraser is still not recognized by xinput and xsetwacom.
Checking Xorg.0.log in /var/log will tell you which driver has the tablet, stylus and eraser.
Also, if I set the stylus to relative instead of absolute, that slows my system down a bit and the lines are a bit zig zag. Is that "normal" ?
Don't know. Sounds like more events are being generated in relative. If you have an older CPU that could/would slow you down. You could increase the RawSample rate for the stylus.

[artik1024]

MetalMusicAddict, many thanks for this HOWTO ! But, how to get pressure sensitivity in photoshop CS5 under wine ? it works under Gimp, but not Photoshop ;)

[CanopusArchives]

Absolutely new to Linux, but, my Wacom seems to be working OK except for one thing. Mouse wheel will only scroll down page no matter which way I turn it. There seems to be no way to configure mouse wheel. Even tried installing Pointing Devices from Ubuntu Software Center, but, it won't even launch.

[mhope]

MetalMusicAddict, many thanks for this HOWTO ! But, how to get pressure sensitivity in photoshop CS5 under wine ? it works under Gimp, but not Photoshop ;)

I am also experiencing the "no pen pressure" issue with both Photoshop CS5 (installed by copying registry items and folders from Windows) and Photoshop CS5 Extended Portable.

As stated by the previous poster, pressure sensitivity works fine in other programs: Gimp, MyPaint, Photoshop CS2 (via Wine). Any thoughts?

[Psyphre]

I am also experiencing the "no pen pressure" issue with both Photoshop CS5 (installed by copying registry items and folders from Windows) and Photoshop CS5 Extended Portable.

As stated by the previous poster, pressure sensitivity works fine in other programs: Gimp, MyPaint, Photoshop CS2 (via Wine). Any thoughts?

Exactly the same issue! Its frustrating that I've got photoshop working flawlessly, yet the one thing i need to use in is pen pressure and that doesnt work!

[graphius]

I am also experiencing the "no pen pressure" issue with both Photoshop CS5 (installed by copying registry items and folders from Windows) and Photoshop CS5 Extended Portable.

As stated by the previous poster, pressure sensitivity works fine in other programs: Gimp, MyPaint, Photoshop CS2 (via Wine). Any thoughts?

Add another user with this issue.

[graphius]

-bump -
any ideas on this yet? I have asked over at the wine forums, but they seem to be focused on getting it to work. It works, curser, eraser and buttons, but no pressure sensitivity....:(

[Ultra Cronic]

This HOW-TO is written for USB Wacom Tablet devices.


The GIMP
- File-> Preferences-> Input Devices-> "Configure Extended Input Devices".
- Under "Device" you will have 3 settings: Cursor, Eraser and Stylus. Set them from "Disabled" to "Screen".

Now you should have pressure sensitivity in The GIMP. :)

Also, a useability note with Gimp:
Each input device (stylus,cursor,eraser) has a completely different set of attributes in Gimp, and in theory, you can even assign a unique serial number to different pens to get even more granularity. You will experience this when you try to use your eraser for the first time. Rather than selecting the eraser tool, you get the rectangle selection tool instead. This is by design, believe it or not. Gimp does not care that its an eraser, just that it's not the pen you were just using. If you choose the eraser tool now, it will remember that for the next time you try to use it. On the plus side, you can set the eraser to be anything, including the Airbrush tool or Clone tool.
-Taken from The Wacom Help Page. (http://linuxwacom.sourceforge.net/index.php/howto/main)

;)
:guitar::popcorn::P
Kudos to you man, I've been at it all night break and fix crash and burn compiling drivers and YOUR suggestions are the ones that fired it up. Especialy the gimp input settings quoted above.
Many thanx :biggrin: