You are not logged in.

#1 2009-04-01 19:03:06

Arjann
Member
From: The Netherlands
Registered: 2008-09-26
Posts: 21

Getting Wacom tablet working on arch testing

Hey all,

I'd like to keep arch testing (64bit, kernel 2.6.29), but i also like to have my wacom tablet working.
The current linuxwacom package in aur doesn't work with xorg 1.6.0 and the dev version (0.8.3-1) of linuxwacomproject@Sourceforge will not compile because of hal errors.
Are there Archers on this testing forum that have this combination working? and can give me tips on getting this to work?

Greets,

Arjann

Offline

#2 2009-04-01 21:59:27

Arjann
Member
From: The Netherlands
Registered: 2008-09-26
Posts: 21

Re: Getting Wacom tablet working on arch testing

Forall who like to try it in future, i also posted a topic on the help forum of linuxwacom and got a answer that presumable this friday a new dev-version (0.8.3-2) will be out that should work.

Offline

#3 2009-04-02 21:49:19

Ulf
Member
Registered: 2007-08-26
Posts: 43

Re: Getting Wacom tablet working on arch testing

Yippie!

Offline

#4 2009-04-04 10:46:09

Arjann
Member
From: The Netherlands
Registered: 2008-09-26
Posts: 21

Re: Getting Wacom tablet working on arch testing

i made a package from 0.8.3-2, so now there is a linuxwacom-dev package in AUR! it compiled and installed out-of-the-box
only i have some issues with it.

1. Eraser isn't working after connecting my tablet using hot-swappable fdi file. Is a hal issue because it can't add multiple devices although there is a xorg1.6 hack-patch which isn't in 0.8.3-2.
2. restarting x-server without tablet connected made my x-server to abort and therefore fail to start on my old (xorg1.5.3) stylus, eraser and cursor inputdevices that i still had in xorg.conf. I commented them out in xorg.conf for now, it is a xorg 1.6.0 autoAddDevices and autoEnabledevices issue. Does anyone have some ideas on how to fix this without setting these flags to false??

Last edited by Arjann (2009-04-05 09:55:28)

Offline

#5 2009-04-04 15:57:56

Megamixman
Member
Registered: 2008-05-04
Posts: 73

Re: Getting Wacom tablet working on arch testing

For the eraser problem, look at the rejected maxX maxY patch by the fedora dev's in the tracker. Apply that and the eraser works.
In reality, the eraser already works, it's just getting it's maxX and maxY set to 0 for some reason.

The other option is to just not use the HAL fdi and go back to the an xorg.conf that allows hal to auto-setup all the other devices. The HAL way doesn't give the devices the standard stylus/eraser names. So they don't show up in wacomcpl and xsetwacom. This means no rotation, which for me using a Tablet PC, is pretty important.

Offline

#6 2009-04-05 07:28:26

Arjann
Member
From: The Netherlands
Registered: 2008-09-26
Posts: 21

Re: Getting Wacom tablet working on arch testing

Ehm, on the linuxwacom site there is a comment on the maxX and maxY patch that it is patched within 0.8.3-2. So i think its the hal-setup patch within the same fedora dev path which wasn't patched because its a xserver 1.6.0 hack and not general applicable.

Last edited by Arjann (2009-04-05 07:39:06)

Offline

#7 2009-04-10 20:29:07

Cheesebaron
Member
From: Denmark
Registered: 2008-10-31
Posts: 65
Website

Re: Getting Wacom tablet working on arch testing

Awesome, I got this to work smile

Though I never use the eraser, since it is too much hassle turn over the pen every time I need to erase something.

Offline

#8 2009-04-11 17:45:19

sfauzia
Member
Registered: 2009-01-11
Posts: 88

Re: Getting Wacom tablet working on arch testing

Now that the new X server just came out of testing, my tablet pen and touch both aren't working. I installed the developmental version of linuxwacom, but there's no change. Any suggestions?

Last edited by sfauzia (2009-04-11 17:58:08)

Offline

#9 2009-04-12 01:12:22

lynucs
Member
Registered: 2008-05-05
Posts: 67
Website

Re: Getting Wacom tablet working on arch testing

same here, wacom on x41t isn't working anymore since update on hardware enabled xorg 1.6 and kernel 2.6.29. adding .fdi file for wacom as mentioned in wiki didn't do the trick. really curious is, wacom isn't showing up in /proc/bus/input/devices..

so maybe it's a kernel issue?

tried to install the wacom-dev package from aur. no success.
_any_ help would be really great.

here's some xorg log which might be interesting:

(II) LoadModule: "wacom"
(II) Loading /usr/lib/xorg/modules/input//wacom_drv.so
(II) Module wacom: vendor="X.Org Foundation"
        compiled for 4.3.99.902, module version = 1.0.0
        Module class: X.Org XInput Driver
        ABI class: X.Org XInput driver, version 2.1
(EE) module ABI major version (2) doesn't match the server's version (4)
(II) UnloadModule: "wacom"
(II) Unloading /usr/lib/xorg/modules/input//wacom_drv.so
(EE) Failed to load module "wacom" (module requirement mismatch, 0)

Last edited by lynucs (2009-04-12 01:24:14)


Pinky, are you pondering what I'm pondering?

Offline

#10 2009-04-12 06:52:44

sfauzia
Member
Registered: 2009-01-11
Posts: 88

Re: Getting Wacom tablet working on arch testing

I don't think it's the kernel. I had the kernel update yesterday I think, and it worked perfectly. I'm pretty sure it's the new xserver-xorg package (1.6), because another person, who was using this when it was in the testing repo (there's a thread here on it), had the same problem.

[edit] Oh, right, this is the thread started by the person using the testing repo! I must be too tired. [/edit]

Last edited by sfauzia (2009-04-12 06:53:43)

Offline

#11 2009-04-12 10:40:25

lynucs
Member
Registered: 2008-05-05
Posts: 67
Website

Re: Getting Wacom tablet working on arch testing

should i report it somewhere maybe on a bugtracker? just still not sure where to put it.. xorg or kernel.


Pinky, are you pondering what I'm pondering?

Offline

#12 2009-04-12 14:49:50

Ulf
Member
Registered: 2007-08-26
Posts: 43

Re: Getting Wacom tablet working on arch testing

Lynucs, i got the same message after installing xorg-server 1.6. I deinstalled linuxwacom and installed linuxwacom-dev. That solved the issue. I also removed all the InputSections in xorg.conf concering the wacom tablet. Well works perfectly...i want to have the stylus in relative mode, going to fiddle a bit with /usr/share/hal/fdi/policy/20thirdparty/10-linuxwacom.fdi to see if i can add some settings there.

I am running kernel 2.6.28 though but it shouldn't be a kernel issue (else you would see something with dmesg or in /var/log/messages.log).

Offline

#13 2009-04-12 15:16:22

Ulf
Member
Registered: 2007-08-26
Posts: 43

Re: Getting Wacom tablet working on arch testing

*sigh* in relative mode still this weird behaviour that once you lift the pen it xorg forgets about it. Switching to another terminal and then back to xorg refreshes xorg and the pen works. Not a really workable situation. Anyone got a clue how to get this fixed?

Offline

#14 2009-04-12 16:08:32

sfauzia
Member
Registered: 2009-01-11
Posts: 88

Re: Getting Wacom tablet working on arch testing

Oh my goodness, Ulf, you're right! (About switching to a virtual term and the pen working). That's far better than my pen not working at all! Thanks a million! Still looking, with you, for a proper solution though.

Offline

#15 2009-04-12 16:17:15

Cheesebaron
Member
From: Denmark
Registered: 2008-10-31
Posts: 65
Website

Re: Getting Wacom tablet working on arch testing

I upgraded earlier and it still works as always. Strange that you need to go to another VT and then back before it works.

Do you have anything in your xorg.conf or in a FDI file making some troubles in the neighbourhood?

Offline

#16 2009-04-12 20:36:43

lynucs
Member
Registered: 2008-05-05
Posts: 67
Website

Re: Getting Wacom tablet working on arch testing

Ulf wrote:

Lynucs, i got the same message after installing xorg-server 1.6. I deinstalled linuxwacom and installed linuxwacom-dev. That solved the issue. I also removed all the InputSections in xorg.conf concering the wacom tablet. Well works perfectly...i want to have the stylus in relative mode, going to fiddle a bit with /usr/share/hal/fdi/policy/20thirdparty/10-linuxwacom.fdi to see if i can add some settings there.

I am running kernel 2.6.28 though but it shouldn't be a kernel issue (else you would see something with dmesg or in /var/log/messages.log).

i removed all configuration regarding input devices in xorg.conf. tried with and without fdi file for wacom. still doesn't work. how could i check at all, wether my system "sees" the wacom device? it's not in lspci nor in lsusb. it's actually not a usb-device at all, it's a built-in in x41 tablet.

tried to load the wacom module manually, no change.


Pinky, are you pondering what I'm pondering?

Offline

#17 2009-04-12 21:00:10

Ulf
Member
Registered: 2007-08-26
Posts: 43

Re: Getting Wacom tablet working on arch testing

I did some test and well, nothing seems to get it working. I included my Xorg.0.log just in case (and edited a few things out since it is almost 500kb). It doesn't make sense to me but maybe someone else knows what is going on. I think that the hotplugging is still not working as it should. When changing settings in fdi files concerning the wacom (when i am out of X), then removing the wacom from the usb and reinsert it, then starting X again, just results in a frozen pen.

When using the trick to switch to another terminal and back i get the output in the included output (sorry, around 30k file)

#
#BORING DEFAULT STUFF, WACOM MODULE ENABLED, REST DISABLED OR DEFAULT
#EXCEPT FOR THE NVIDIA AND SCREEN PARTS
#
#
#
#
#
X.Org X Server 1.6.0
Release Date: 2009-2-25
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.29-ARCH x86_64 
Current Operating System: Linux opteron 2.6.28-ARCH #1 SMP PREEMPT Tue Mar 17 07:22:53 CET 2009 x86_64
Build Date: 10 April 2009  01:30:50PM
 
    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: Sun Apr 12 22:29:44 2009
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) |   |-->Monitor "Generic Monitor"
(**) |   |-->Device "nVidia Corporation NV36GL [Quadro FX 1100]"
(**) Option "DontZap" "false"
(==) Automatically adding devices
(==) Automatically enabling devices
(**) FontPath set to:
    /usr/share/fonts/misc,
    /usr/share/fonts/100dpi/:unscaled,
    /usr/share/fonts/75dpi/:unscaled,
    /usr/share/fonts/Type1,
    /usr/share/fonts/100dpi,
    /usr/share/fonts/75dpi,
    /usr/share/fonts/misc,
    /usr/share/fonts/100dpi:unscaled,
    /usr/share/fonts/75dpi:unscaled,
    /usr/share/fonts/TTF,
    /usr/share/fonts/Type1,
    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: 0x1540
(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 4

(--) PCI:*(0@1:0:0) nVidia Corporation NV36GL [Quadro FX 1100] rev 161, Mem @ 0xfd000000/16777216, 0xd0000000/268435456, BIOS @ 0x????????/131072
(II) Open ACPI successful (/var/run/acpid.socket)
(II) System resource ranges:
(II) "extmod" will be loaded by default.
(II) "dbe" will be loaded by default.
(II) "glx" will be loaded by default.
(II) "record" will be loaded by default.
(II) "dri" will be loaded by default.
(II) "dri2" will be loaded by default.
(II) LoadModule: "wacom"
(II) Loading /usr/lib/xorg/modules/input//wacom_drv.so
(II) Module wacom: vendor="X.Org Foundation"
    compiled for 1.6.0, 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.3-2 $
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
    compiled for 1.6.0, 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.0, 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: "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  173.14.18  Mon Mar  2 15:55:02 PST 2009
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
    compiled for 1.6.0, 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.0, module version = 1.0.0
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions//libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
    compiled for 1.6.0, module version = 1.0.0
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(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  173.14.18  Mon Mar  2 15:38:04 PST 2009
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 01@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.0, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "wfb"
(II) LoadModule: "wfb"
(II) Loading /usr/lib/xorg/modules//libwfb.so
(II) Module wfb: vendor="X.Org Foundation"
    compiled for 1.6.0, 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:
(**) 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 "NoLogo" "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 Quadro FX 1100 (NV36GL) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 131072 kBytes
(--) NVIDIA(0): VideoBIOS: 04.36.20.22.15
(II) NVIDIA(0): Detected AGP rate: 8X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on Quadro FX 1100 at PCI:1:0:0:
(--) NVIDIA(0):     Samsung SyncMaster (DFP-1)
(--) NVIDIA(0): Samsung SyncMaster (DFP-1): 165.0 MHz maximum pixel clock
(--) NVIDIA(0): Samsung SyncMaster (DFP-1): External Single Link TMDS
(II) NVIDIA(0): Assigned Display Device: DFP-1
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0):     "1920x1200"
(II) NVIDIA(0):     "1600x1200"
(II) NVIDIA(0):     "1280x1024"
(II) NVIDIA(0):     "1024x768"
(II) NVIDIA(0): Virtual screen size determined to be 1920 x 1200
(--) NVIDIA(0): DPI set to (93, 95); computed from "UseEdidDpi" X config
(--) NVIDIA(0):     option
(WW) NVIDIA(0): UBB is incompatible with the Composite extension.  Disabling
(WW) NVIDIA(0):     UBB.
(==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC?  No, I don't.
(II) resource ranges after preInit:
(II) NVIDIA(0): Initialized AGP GART.
(II) NVIDIA(0): Setting mode "1920x1200"
(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
(**) Option "dpms" "True"
(**) 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 Macintosh mouse button emulation
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
    compiled for 1.6.0, module version = 2.2.1
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 4.0
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event0"
(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) config/hal: Adding input device ImExPS/2 Logitech Explorer Mouse
(**) ImExPS/2 Logitech Explorer Mouse: always reports core events
(**) ImExPS/2 Logitech Explorer Mouse: Device: "/dev/input/event4"
(II) ImExPS/2 Logitech Explorer Mouse: Found 5 mouse buttons
(II) ImExPS/2 Logitech Explorer Mouse: Found x and y relative axes
(II) ImExPS/2 Logitech Explorer Mouse: Found scroll wheel(s)
(II) ImExPS/2 Logitech Explorer Mouse: Configuring as mouse
(**) ImExPS/2 Logitech Explorer Mouse: YAxisMapping: buttons 4 and 5
(**) ImExPS/2 Logitech Explorer Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "ImExPS/2 Logitech Explorer Mouse" (type: MOUSE)
(**) ImExPS/2 Logitech Explorer Mouse: (accel) keeping acceleration scheme 1
(**) ImExPS/2 Logitech Explorer Mouse: (accel) filter chain progression: 2.00
(**) ImExPS/2 Logitech Explorer Mouse: (accel) filter stage 0: 20.00 ms
(**) ImExPS/2 Logitech Explorer Mouse: (accel) set acceleration profile 0
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT Translated Set 2 keyboard: Device: "/dev/input/event1"
(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" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Wacom Intuos2 9x12
(**) Wacom Intuos2 9x12: always reports core events
(**) Wacom Intuos2 9x12 device is /dev/input/event5
(**) Option "DebugLevel" "12"
(**) WACOM: Wacom Intuos2 9x12 debug level set to 12
(**) Option "CommonDBG" "12"
(**) WACOM: Wacom Intuos2 9x12 tablet common debug level set to 12
(**) Wacom Intuos2 9x12 is in relative mode
(**) WACOM: Rotation is set to NONE
(**) WACOM: suppress value is 2
(**) Option "KeepShape" "OFF"
(**) Option "BaudRate" "9600"
(**) Wacom Intuos2 9x12: serial speed 9600
(II) XINPUT: Adding extended input device "Wacom Intuos2 9x12" (type: Wacom Stylus)
BEGIN xf86WcmProc dev=0x1cab800 priv=0x1c9fc60 type=stylus(Wacom Intuos2 9x12) flags=16385 fd=-1 what=INIT
xf86WcmDevOpen
opening /dev/input/event5
(**) Option "Device" "/dev/input/event5"
usbDetect
Wacom Intuos2 9x12 Wacom X driver grabbed event device
initializing USB tablet
(==) Wacom using pressure threshold of 61 for button 1
Tablet does not support setting link speed, or not yet implemented
(==) Wacom USB Intuos2 tablet speed=9600 (38400) maxX=30480 maxY=24060 maxZ=1023 resX=2540 resY=2540  tilt=enabled
#
#
#DEBUG OUTPUT OF THE WACOM TABLET
#
#
#
#
#
usbDetectConfig 
xf86WcmRegisterX11Devices (stylus) 7 buttons, 7 keys, 6 axes
xf86WcmInitArea
xf86WcmInitialScreens for "Wacom Intuos2 9x12" number of screen=1 
xf86WcmInitialScreens for "Wacom Intuos2 9x12" topX[0]=0 topY[0]=0 bottomX[0]=1920 bottomY[0]=1200 
(==) Wacom device "Wacom Intuos2 9x12" top X=0 top Y=0 bottom X=30480 bottom Y=24060 resol X=2540 resol Y=2540
xf86WcmRotateTablet for "Wacom Intuos2 9x12" 
rotateOneTool for "Wacom Intuos2 9x12" 
xf86WcmMappingFactor 
xf86WcmMappingFactor Active tablet area x=30480 y=24060 (virtual tablet area x=30480 y=24060) map to maxWidth =1920 maxHeight =1200
X factor = 0.063, Y factor = 0.0499
xf86WcmMappingFactor 
xf86WcmMappingFactor Active tablet area x=30480 y=24060 (virtual tablet area x=30480 y=24060) map to maxWidth =1920 maxHeight =1200
X factor = 0.063, Y factor = 0.0499
xf86WcmMappingFactor 
xf86WcmMappingFactor Active tablet area x=30480 y=24060 (virtual tablet area x=30480 y=24060) map to maxWidth =1920 maxHeight =1200
X factor = 0.063, Y factor = 0.0499
END xf86WcmProc Success 
BEGIN xf86WcmProc dev=0x1cab800 priv=0x1c9fc60 type=stylus(Wacom Intuos2 9x12) flags=16385 fd=25 what=ON
xf86WcmDevOpen
END xf86WcmProc Success 
xf86WcmReady for Wacom Intuos2 9x12 with 1 numbers of data
xf86WcmReadPacket: device=/dev/input/event5 fd=25 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 216 bytes
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseChannel 9 events received
usbParseChannel event[0]->type=3 code=0 value=23944
usbParseChannel event[1]->type=3 code=1 value=12469
usbParseChannel event[2]->type=3 code=25 value=24
usbParseChannel event[3]->type=3 code=26 value=64
usbParseChannel event[4]->type=3 code=27 value=64
usbParseChannel event[5]->type=3 code=40 value=2130
usbParseChannel event[6]->type=1 code=320 value=1
USB stylus detected 140
usbParseChannel event[7]->type=4 code=0 value=68170805
usbParseChannel event[8]->type=0 code=0 value=0
xf86WcmEvent at channel = 0
xf86WcmEvent: c=0 i=2 t=1 s=68170805 x=23944 y=12469 b=0 p=0 rz=0 tx=0 ty=0 aw=0 rw=0 t=0 df=0 px=1 st=74689 cs=0 
discarded 0th USB data.
xf86WcmReady for Wacom Intuos2 9x12 with 0 numbers of data
xf86WcmDevReadInput: Read (1)
xf86WcmReady for Wacom Intuos2 9x12 with 1 numbers of data
xf86WcmReadPacket: device=/dev/input/event5 fd=25 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 144 bytes
xf86WcmReady for Wacom Intuos2 9x12 with 0 numbers of data
xf86WcmDevReadInput: Read (1)
xf86WcmReady for Wacom Intuos2 9x12 with 1 numbers of data
xf86WcmReadPacket: device=/dev/input/event5 fd=25 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 144 bytes
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseChannel 5 events received
usbParseChannel event[0]->type=3 code=0 value=4225
usbParseChannel event[1]->type=3 code=1 value=3447
usbParseChannel event[2]->type=3 code=25 value=22
usbParseChannel event[3]->type=4 code=0 value=68170805
usbParseChannel event[4]->type=0 code=0 value=0
xf86WcmEvent at channel = 0
xf86WcmEvent: c=0 i=2 t=1 s=68170805 x=4225 y=3447 b=0 p=0 rz=0 tx=10 ty=31 aw=0 rw=0 t=0 df=0 px=1 st=80652 cs=4 
xf86WcmSuppress at level = 2 return value = 2
commonDispatchDevice device type = 1
tool id=1 for Wacom Intuos2 9x12
Distance over the tablet: 22, ProxoutDist: 10 current min/max 0 hard prox: 1
xf86WcmReady for Wacom Intuos2 9x12 with 0 numbers of data
xf86WcmDevReadInput: Read (1)
xf86WcmReady for Wacom Intuos2 9x12 with 1 numbers of data
xf86WcmReadPacket: device=/dev/input/event5 fd=25 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 120 bytes
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseChannel 5 events received
usbParseChannel event[0]->type=3 code=0 value=3372
usbParseChannel event[1]->type=3 code=1 value=2184
usbParseChannel event[2]->type=3 code=25 value=23
usbParseChannel event[3]->type=4 code=0 value=68170805
usbParseChannel event[4]->type=0 code=0 value=0
xf86WcmEvent at channel = 0
xf86WcmEvent: c=0 i=2 t=1 s=68170805 x=3372 y=2184 b=0 p=0 rz=0 tx=10 ty=31 aw=0 rw=0 t=0 df=0 px=1 st=80664 cs=4 
xf86WcmSuppress at level = 2 return value = 2
commonDispatchDevice device type = 1
tool id=1 for Wacom Intuos2 9x12
Distance over the tablet: 23, ProxoutDist: 10 current min/max 0 hard prox: 1
xf86WcmReady for Wacom Intuos2 9x12 with 0 numbers of data
xf86WcmDevReadInput: Read (1)
xf86WcmReady for Wacom Intuos2 9x12 with 1 numbers of data
xf86WcmReadPacket: device=/dev/input/event5 fd=25 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 72 bytes
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseChannel 3 events received
usbParseChannel event[0]->type=3 code=25 value=24
usbParseChannel event[1]->type=4 code=0 value=68170805
usbParseChannel event[2]->type=0 code=0 value=0
xf86WcmEvent at channel = 0
xf86WcmEvent: c=0 i=2 t=1 s=68170805 x=3372 y=2184 b=0 p=0 rz=0 tx=10 ty=31 aw=0 rw=0 t=0 df=0 px=1 st=80672 cs=4 
xf86WcmSuppress at level = 2 return value = 2
commonDispatchDevice device type = 1
tool id=1 for Wacom Intuos2 9x12
Distance over the tablet: 24, ProxoutDist: 10 current min/max 0 hard prox: 1
xf86WcmReady for Wacom Intuos2 9x12 with 0 numbers of data
xf86WcmDevReadInput: Read (1)
xf86WcmReady for Wacom Intuos2 9x12 with 1 numbers of data
xf86WcmReadPacket: device=/dev/input/event5 fd=25 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 216 bytes
#
#
#LIFT ACTION I GUESS OR LAST ACTION BEFORE THE PEN FREEZES
#
#
#
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseChannel 9 events received
usbParseChannel event[0]->type=3 code=0 value=0
usbParseChannel event[1]->type=3 code=1 value=0
usbParseChannel event[2]->type=3 code=25 value=0
usbParseChannel event[3]->type=3 code=26 value=0
usbParseChannel event[4]->type=3 code=27 value=0
usbParseChannel event[5]->type=1 code=320 value=0
USB stylus detected 140
usbParseChannel event[6]->type=3 code=40 value=0
usbParseChannel event[7]->type=4 code=0 value=68170805
usbParseChannel event[8]->type=0 code=0 value=0
xf86WcmEvent at channel = 0
xf86WcmEvent: c=0 i=2 t=1 s=68170805 x=0 y=0 b=0 p=0 rz=0 tx=-64 ty=-64 aw=0 rw=0 t=0 df=0 px=0 st=80680 cs=4 
xf86WcmSuppress at level = 2 return value = 1
commonDispatchDevice device type = 1
tool id=1 for Wacom Intuos2 9x12
Distance over the tablet: 0, ProxoutDist: 10 current min/max 0 hard prox: 0
xf86WcmReady for Wacom Intuos2 9x12 with 0 numbers of data
xf86WcmDevReadInput: Read (1)
#
#SWITCHED TO TTY2
#
#AND BACK TO XORG - TTY4
#
#
#
#
#
#
BEGIN xf86WcmProc dev=0x1cab800 priv=0x1c9fc60 type=stylus(Wacom Intuos2 9x12) flags=16385 fd=25 what=OFF
Wacom number of open devices = 1
Closing device; uninitializing.
END xf86WcmProc Success 
(II) Open ACPI successful (/var/run/acpid.socket)
(II) NVIDIA(0): Setting mode "1920x1200"
BEGIN xf86WcmProc dev=0x1cab800 priv=0x1c9fc60 type=stylus(Wacom Intuos2 9x12) flags=16385 fd=-1 what=ON
xf86WcmDevOpen
opening /dev/input/event5
usbDetect
Wacom Intuos2 9x12 Wacom X driver grabbed event device
initializing USB tablet
Tablet does not support setting link speed, or not yet implemented
(==) Wacom USB Intuos2 tablet speed=9600 (38400) maxX=30480 maxY=24060 maxZ=1023 resX=2540 resY=2540  tilt=enabled
usbDetectConfig 
xf86WcmRegisterX11Devices (stylus) 7 buttons, 7 keys, 6 axes
xf86WcmInitArea
xf86WcmInitialScreens for "Wacom Intuos2 9x12" number of screen=1 
xf86WcmInitialScreens for "Wacom Intuos2 9x12" topX[0]=0 topY[0]=0 bottomX[0]=1920 bottomY[0]=1200 
(==) Wacom device "Wacom Intuos2 9x12" top X=0 top Y=0 bottom X=30480 bottom Y=24060 resol X=2540 resol Y=2540
xf86WcmRotateTablet for "Wacom Intuos2 9x12" 
rotateOneTool for "Wacom Intuos2 9x12" 
xf86WcmMappingFactor 
xf86WcmMappingFactor Active tablet area x=30480 y=24060 (virtual tablet area x=30480 y=24060) map to maxWidth =1920 maxHeight =1200
X factor = 0.063, Y factor = 0.0499
xf86WcmMappingFactor 
xf86WcmMappingFactor Active tablet area x=30480 y=24060 (virtual tablet area x=30480 y=24060) map to maxWidth =1920 maxHeight =1200
X factor = 0.063, Y factor = 0.0499
xf86WcmMappingFactor 
xf86WcmMappingFactor Active tablet area x=30480 y=24060 (virtual tablet area x=30480 y=24060) map to maxWidth =1920 maxHeight =1200
X factor = 0.063, Y factor = 0.0499
END xf86WcmProc Success 
(II) Macintosh mouse button emulation: Device reopened after 1 attempts.
(II) ImExPS/2 Logitech Explorer Mouse: Device reopened after 1 attempts.
(II) AT Translated Set 2 keyboard: Device reopened after 1 attempts.
xf86WcmReady for Wacom Intuos2 9x12 with 1 numbers of data
xf86WcmReadPacket: device=/dev/input/event5 fd=22

Offline

#18 2009-04-12 21:41:18

sfauzia
Member
Registered: 2009-01-11
Posts: 88

Re: Getting Wacom tablet working on arch testing

Cheesebaron wrote:

I upgraded earlier and it still works as always. Strange that you need to go to another VT and then back before it works.

Do you have anything in your xorg.conf or in a FDI file making some troubles in the neighbourhood?

Here's my xorg.conf:

Section "InputDevice"
  Driver        "wacom"
  Identifier    "stylus"
  Option        "Device"        "/dev/ttyS0"          # SERIAL ONLY
  Option        "Type"          "stylus"
  Option        "ForceDevice"   "ISDV4"               # Tablet PC ONLY
  # http://wiki.informatik.hu-berlin.de/nomads/index.php     
  Option          "Button2" "3"
EndSection

Section "InputDevice"
  Driver        "wacom"
  Identifier    "eraser"
  Option        "Device"        "/dev/ttyS0"          # SERIAL ONLY
  Option        "Type"          "eraser"
  Option        "ForceDevice"   "ISDV4"               # Tablet PC ONLY
  # http://wiki.informatik.hu-berlin.de/nomads/index.php     
  Option          "Button1" "2"
EndSection 

Section "InputDevice"
  Driver        "wacom"
  Identifier    "cursor"
  Option        "Device"        "/dev/ttyS0"          # SERIAL ONLY
  Option        "Type"          "cursor"
  Option        "ForceDevice"   "ISDV4"               # Tablet PC ONLY
EndSection 

# This section is for the TabletPC that supports touch
Section "InputDevice"
  Driver        "wacom"
  Identifier    "touch"
  Option        "Device"        "/dev/ttyS0"          # SERIAL ONLY
  Option        "Type"          "touch"
  Option        "ForceDevice"   "ISDV4"               # Tablet PC ONLY
  Option "BottomY" "953"
  Option "BottomX" "931"
  Option "TopY" "80"
  Option "TopX" "50"
EndSection

Section "Device"
    Identifier    "Configured Video Device"
EndSection

Section "Monitor"
    Identifier    "Configured Monitor"
EndSection

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

Section "Files"
    FontPath    "/usr/share/fonts/local"    # for terminus and other local fonts
    FontPath    "/home/sara/.fonts"        # for local fonts
EndSection

Section "ServerLayout" 
  Identifier    "Default Layout"
  Screen    "Default Screen"
  # http://linuxwacom.sourceforge.net/index.php/howto/srvlayout
  InputDevice    "stylus"    "SendCoreEvents"
  InputDevice    "eraser"    "SendCoreEvents"
  InputDevice    "touch"     "SendCoreEvents"
EndSection

Are you also using a tablet PC, or a USB-attached tablet?

[edit] Nevermind, I see you're using the x60t. Strange, that I'm having a problem with the x61t! [/edit]

Last edited by sfauzia (2009-04-12 21:49:08)

Offline

#19 2009-04-30 15:27:19

NWhisper
Member
Registered: 2009-04-24
Posts: 8

Re: Getting Wacom tablet working on arch testing

Arjann wrote:

1. Eraser isn't working after connecting my tablet using hot-swappable fdi file. Is a hal issue because it can't add multiple devices although there is a xorg1.6 hack-patch which isn't in 0.8.3-2.

linuxwacom-0.8.3-3 from AUR works fine (stylus, eraser, cursor, pad, touch) after "ln -s /usr/libexec/hal-setup-wacom /usr/bin/hal-setup-wacom". HAL can't find hal-setup-wacom in /usr/libexec/.

Offline

#20 2009-05-03 20:03:48

Arjann
Member
From: The Netherlands
Registered: 2008-09-26
Posts: 21

Re: Getting Wacom tablet working on arch testing

@NWhisper: Thanx!!! big_smile

Offline

#21 2009-05-06 14:45:01

sfauzia
Member
Registered: 2009-01-11
Posts: 88

Re: Getting Wacom tablet working on arch testing

What is the equivalent to libexec in Ubuntu? I wanted to see if NWhisper's fix works in Ubuntu as well smile

Offline

#22 2009-05-18 16:04:45

Lux Perpetua
Member
From: The Local Group
Registered: 2009-02-22
Posts: 64

Re: Getting Wacom tablet working on arch testing

NWhisper wrote:
Arjann wrote:

1. Eraser isn't working after connecting my tablet using hot-swappable fdi file. Is a hal issue because it can't add multiple devices although there is a xorg1.6 hack-patch which isn't in 0.8.3-2.

linuxwacom-0.8.3-3 from AUR works fine (stylus, eraser, cursor, pad, touch) after "ln -s /usr/libexec/hal-setup-wacom /usr/bin/hal-setup-wacom". HAL can't find hal-setup-wacom in /usr/libexec/.

Thanks. I was recently having trouble with mine, and that fixed it nicely. Does anybody want to add that to the wiki? I would, but I don't really understand the problem well.

Offline

#23 2009-05-31 10:30:13

Ulf
Member
Registered: 2007-08-26
Posts: 43

Re: Getting Wacom tablet working on arch testing

NWhisper i followed your advice but the wacom is still terribly broken. Non of the debugging tools with the wacom work (xidump xsetwacom etc). Also doing an xxd /dev/input/wacom shows no output at all. When in Gimp i get a really weird behaviour that when using the pen it doesn't update the airbrush tool when you use it untill after a second or something, then there is a weird line coming from the left. I changed my xorg.conf to enable automatically add devices but that made things worse for gimp, it didn't recognize any wacom devices. It seems that the wacom tablet is just another mouse to the system...

Could anyone who has a tablet properly working with pressure and in relative mode explain how he got it working? Do you have to make changes to xorg.conf? To 10-wacom.rules or to the hal-setup policy files? I changed so much by now that my system is probably one big mess (and i am definitely completely clueless):(

Thanks for any help

Offline

Board footer

Powered by FluxBB