View previous topic :: View next topic |
Author |
Message |
Nitro_146 Apprentice
Joined: 02 Mar 2005 Posts: 221 Location: Digne les bains, France
|
Posted: Fri Apr 10, 2009 4:51 pm Post subject: [SOLVED] Wacom tablet setup messed up after xorg upgrade |
|
|
Hi all,
Most of the updade to xorg 1.5.3 worked well for me.
However, my Wacom Volito2 tablet does not work as exepected. (It worked well before the upgrade)
I have a dual screen setup and I would like the tablet to be contained only in screen 0, and to be in absolute mode
Instead of that, the pointer behaves like my mouse (relative mode, and goes in both screens)
Here is my Xorg.conf section that used to work :
Code: |
Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/input/tablet-volito2-4x5"
Option "Type" "stylus"
Option "USB" "on"
Option "TVResolution" "1280x960"
Option "ScreenNo" "0"
Option "PressCurve" "0,0,100,100" #linéaire
EndSection
|
Anyone having an idea where to look at ?
Thanks _________________ Linux, cause booting is for adding new hardware
Last edited by Nitro_146 on Fri Apr 10, 2009 9:16 pm; edited 1 time in total |
|
Back to top |
|
|
Nitro_146 Apprentice
Joined: 02 Mar 2005 Posts: 221 Location: Digne les bains, France
|
Posted: Fri Apr 10, 2009 9:15 pm Post subject: |
|
|
After some intensive googling I found a fdi file that I customized.
It seems to work right now.
Here it is, hope this might help someone
/etc/hal/fdi/policy/10-wacom.fdi
Code: | <?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- -->
<deviceinfo version="0.2">
<device>
<match key="info.capabilities" contains="input">
<match key="info.product" contains="Wacom">
<merge key="input.x11_driver" type="string">wacom</merge>
<merge key="input.x11_options.Type" type="string">stylus</merge>
<merge key="input.x11_options.TVResolution" type="string">1280x960</merge>
<merge key="input.x11_options.ScreenNo" type="string">0</merge>
<merge key="input.x11_options.PressCurve" type="string">0,0,100,100</merge>
</match>
</match>
</device>
</deviceinfo> |
_________________ Linux, cause booting is for adding new hardware |
|
Back to top |
|
|
VoidMage Watchman
Joined: 14 Oct 2006 Posts: 6196
|
Posted: Fri Apr 10, 2009 10:00 pm Post subject: |
|
|
You can probably do better than 'input', it should have a more
distinctive capability (mouses have input.mouse, touchpads have
input.mouse and input.touchpad, so tablets may have something too).
I'm not saing "it won't work", just "it looks ugly, probably without a reason". |
|
Back to top |
|
|
Nitro_146 Apprentice
Joined: 02 Mar 2005 Posts: 221 Location: Digne les bains, France
|
Posted: Fri Apr 10, 2009 10:09 pm Post subject: |
|
|
here is what I have found in lshal
Quote: | info.capabilities = {'input', 'input.touchpad'} (string list) |
would it be better to put input.touchpad instead of input _________________ Linux, cause booting is for adding new hardware |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|