Linux Wacom Tablet Project

Did you try to install linuxwacom-0.7.0 from this site? What kind of tablet
are you using?
 Ping
 On 10/26/05, Raeth <raeth.phox@...> wrote:
>
> Greets,
>
> I got my tablet working perfectly on Ubuntu 5.10 via the tutorial at
> http://www.ubuntuforums.org/showthread.php?t=3D25151&highlight=3Dwacom
>
> Now there is one place it doesn't work perfectly, and that is
> (ironically) The GIMP.
>
> In the GIMP I can put the stylus down and start painting with
> pressure, however it ignores the stylus going up, and continues to
> think I am still touching the tablet. This is a problem because I have
> to double click with the tablet on a random dialog box to stop it.
>
> How can I get the GIMP to detect my tablet's up signal?
>
> Thanks,
> RaethDragon
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.
> Get Certified Today * Register for a JBoss Training Course
> Free Certification Exam for All Training Attendees Through End of 2005
> Visit http://www.jboss.com/services/certification for more information
> _______________________________________________
> Linuxwacom-discuss mailing list
> Linuxwacom-discuss@...
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>

Hi Raeth,

> In the GIMP I can put the stylus down and start painting with
> pressure, however it ignores the stylus going up, and continues to
> think I am still touching the tablet. This is a problem because I have
> to double click with the tablet on a random dialog box to stop it.
This sounds just like the problem I'm having!
 (see my msg from 12th of October)
Unfortunately I haven't found a solution yet. :-(

What tablet do you have?  Mine is a Graphire 3 6x8 on USB.
What kernel version are you running?

Hopefully we can tackle this problem together!

Bye,
 Andy.

-- 
 Fotos: francisco.spiegl.de            o      _     _         _              
 Infos: peru.spiegl.de       __o      /\_   _ \\o  (_)\__/o  (_)         -o) 
 Andy, Heidi, Francisco    _`\<,_    _>(_) (_)/<_    \_| \   _|/' \/      /\\
 heidi.und.andy@... (_)/ (_)  (_)        (_)   (_)    (_)'  _\o_   _\_v
 ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
 On a clear day, U.C.L.A.
                 -- Graffiti in San Francisco

Right, I'm on the 2.6.11 kernel, Ubuntu 5.10. I'm using a Volito on USB.

I shall try Jose Hevia's solution for now.

Raeth

On 10/27/05, Andy Spiegl <linuxwacom.andy@...> wrote:
> Hi Raeth,
>
> > In the GIMP I can put the stylus down and start painting with
> > pressure, however it ignores the stylus going up, and continues to
> > think I am still touching the tablet. This is a problem because I have
> > to double click with the tablet on a random dialog box to stop it.
> This sounds just like the problem I'm having!
>  (see my msg from 12th of October)
> Unfortunately I haven't found a solution yet. :-(
>
> What tablet do you have?  Mine is a Graphire 3 6x8 on USB.
> What kernel version are you running?
>
> Hopefully we can tackle this problem together!

Le 26.10.2005 22:37:42, Ping@... a =E9crit=A0:
> Did you try to install linuxwacom-0.7.0 from this site? What kind of
> tablet
> are you using?
>  Ping
>  On 10/26/05, Raeth <raeth.phox@...> wrote:
> >
> > Greets,

I've the same problem with Graphire 2 USB on amd64 architecture with =20
both linuxwacom 0.6.9 and 0.7.0 and linux 2.6.1[123]

The pen up event detection is random. If you try several times and tap =20
the pen tip several times on the tablet sometimes it works...

Otherwise, even the corepointer doesnt work.

Jean-Luc

> >
> > I got my tablet working perfectly on Ubuntu 5.10 via the tutorial at
> > http://www.ubuntuforums.org/showthread.php?t=3D25151&highlight=3Dwacom
> >
> > Now there is one place it doesn't work perfectly, and that is
> > (ironically) The GIMP.
> >
> > In the GIMP I can put the stylus down and start painting with
> > pressure, however it ignores the stylus going up, and continues to
> > think I am still touching the tablet. This is a problem because I
> have
> > to double click with the tablet on a random dialog box to stop it.
> >
> > How can I get the GIMP to detect my tablet's up signal?
> >
> > Thanks,
> > RaethDragon

Le 27.10.2005 17:12:33, Omar a =E9crit=A0:
Jean-Luc Coulon (f5ibh) a =E9crit :

[ ... ]

>=20
> I've the same problem with Graphire 2 USB on amd64 architecture with  =20
> both linuxwacom 0.6.9 and 0.7.0 and linux 2.6.1[123]
>=20
> The pen up event detection is random. If you try several times and =20
> tap  the pen tip several times on the tablet sometimes it works...
>=20
> Otherwise, even the corepointer doesnt work.
>=20
> Jean-Luc

[ ... ]


A thing messing up with tablet signal, specially in the gimp, is the =20
/dev/psaux for your Core Pointer.
Try to change your mouse core device to other like: /dev/mouseX (where =20
X is a number)
**It's true if your mouse works on USB, if not, the problem is anything =20
else...

Yes, it is an USB moouse.
I was using /dev/input/mice
I've changed to /dev/input/mouse0

(I can find also the mouse on /dev/input/event1, the keyboard on =20
/dev/input/event0)

To detect the good device type this:
**BE AWARE, you have to be root or having root_permissions to do this

cat /dev/input/mouseX
**move your mouse and look if you get weird feedbacks, if you get, this =20
is your device*

then edit your /etc/X11/xorg.conf  and change value of your Core Pointer

[ ... ]

With /dev/input/mouse0, it is *much* better but time to time, I've the =20
same behaviour. Thnaks for the tip

In these case, I can see the following in the terminal from which I've =20
launched The Gimp:

(gimp-2.3:24483): Gdk-WARNING **: Invalid device key code received

(gimp-2.3:24483): Gdk-WARNING **: Invalid device key code received

(gimp-2.3:24483): Gdk-WARNING **: Invalid device key code received

(gimp-2.3:24483): Gdk-WARNING **: Invalid device key code received


Best
-Omar


Regards

Jean-Luc

Raeth wrote:
> Right, I'm on the 2.6.11 kernel, Ubuntu 5.10. I'm using a Volito on USB.
> 
> I shall try Jose Hevia's solution for now.
> 
> Raeth
> 
> On 10/27/05, Andy Spiegl <linuxwacom.andy@...> wrote:
>>Hi Raeth,
>>
>>>In the GIMP I can put the stylus down and start painting with
>>>pressure, however it ignores the stylus going up, and continues to
>>>think I am still touching the tablet. This is a problem because I have
>>>to double click with the tablet on a random dialog box to stop it.
>>This sounds just like the problem I'm having!
>> (see my msg from 12th of October)
>>Unfortunately I haven't found a solution yet. :-(
>>
>>What tablet do you have?  Mine is a Graphire 3 6x8 on USB.
>>What kernel version are you running?
>>
>>Hopefully we can tackle this problem together!
> 

Hi,
	I'm having the same problem (Intuos3 6x8, linuxwacom-0.7.0, SuSE 
9.3 with kernel 2.6.11) since I got my tablet a couple of weeks 
ago.  I am using it primarily in the GIMP, but just to see what 
would happen, I've tried it, without the problem, in scribus, 
skencil and in qcad.  I've found the easiest way to "undo" the 
"sticky" stylus is to flip the pen over and activate (even use) 
the eraser.

Best regards,

Trase

I forgot to mention one very important step, I cp'd the
linuxwacom-dev/src/2.6.13/*ko files to their correct resting
places in /lib/modules/2.6.13.4/

/lib/modules/2.6.13.4/kernel/drivers/input/evdev.ko
/lib/modules/2.6.13.4/kernel/drivers/input/mousedev.ko
/lib/modules/2.6.13.4/kernel/drivers/usb/input/usbmouse.ko
/lib/modules/2.6.13.4/kernel/drivers/usb/input/wacom.ko

Thanks again.


On 10/26/05, Richard Hubbell <richard.hubbell@...> wrote:
>
> A quick summary of what I did to get this working. The intended audience
> is anyone trying to do same
> and those that helped me get this far.
>
> A got the latest CVS (as I said earlier) (Note: to new CVS users, follow
> CVS instructions on linuxwacom)
>
> ./configure --enable-wacom --enable-wacdump --enable-xidump
> --enable-libwacomcfg --enable-xsetwacom --enable-libwacomxi
> --enable-usbmouse --enable-evdev --enable-mousedev --enable-input
> --enable-tabletdev --enable-wacomdrv --enable-modver
> --with-kernel=3D/kernels/linux-2.6.13.4 <http://2.6.13.4>
>
> I could have (as Jens Georg pointed out) added -enable-hid to line
> above...but I didn't have that advice yet.
> I copied the hid-core.c /kernels/linux-
> 2.6.13.4/drivers/usb/input/hid-core.c<http://2.6.13.4/drivers/usb/input/h=
id-core.c>
> rebuilt my kernel
>
> After diff'ing the linuxwacom-dev/src/2.6.13 files with those in the
> kernel I suspect that it might work
> to just copy them all into the correct places in the kernel tree and
> rebuild the kernel.
>
> I used the prebuilt wacom_drv.o and rebooted twice (for some reason the
> first reboot didn't make things better???
> very puzzling, maybe something to do with the usb cards I use??)
>
> The tablet works so thanks to all of the people that worked on all the
> bits to make this
> run on linux and advice I got here.
>
> I do have one error that I'm seeing on boot. It seems to not cause any
> problems as far as I can tell.
> But I also don't think it's meaningless/harmless, it's more that I just
> don't see any symptoms., yet.
>
> usb-storage: device scan complete
> ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI=
)
> kobject_register failed for ohci_hcd (-17)
> [<c01d799d>] kobject_register+0x35/0x49
> [<c0231411>] bus_add_driver+0x3e/0x96
> [<c0231bc1>] driver_register+0x30/0x33
> [<c01df38d>] pci_register_driver+0x6e/0x7c
> [<d08bc029>] ohci_hcd_pci_init+0x29/0x2f [ohci_hcd]
> [<c012da97>] sys_init_module+0xc6/0x1a9
> [<c01026e3>] sysenter_past_esp+0x54/0x75
>
>
>

On Tue, Oct 25, 2005 at 02:43:36PM +0200, Roland Kwee wrote:
> For your information I experienced a problem with the Wacom Graphire3 
> that went away on a reboot.

Not sure if I'm on the right track, but take a look at the kernel log
when it happens. For me sometimes it behaves as if I did unplut and
replug my tablet manually.

Then X11 looses the device and does not reopen the new file when it
appears. If that's the case, the evdev.c version from linuxwacom should
help.

bye,
Martin

Hi,

	I got the second monitor after I upgraded to FC4 so I did not have that
part working under FC3. I have played around a bit more. After I use the
command:

xsetwacom set stylus mmonitor off

I can use the tablet with the stylus on one monitor at a time except
that with the second monitor if I drag a scroll bar the cursor
jumps to the first monitor. When using the stylus on the first monitor
it does not jump to the second monitor. (I still have the scroll wheel
problem and the pen not releasing after a quick stroke problem.)

	Oh, I am now using cvs from yesterday for wacom.ko.

	My xorg.conf file follows. The "mmonitor" "off" in the file didn't seem
to have any effect... I had to use the xsetwacom command.

	One additional problem I see is that with the mouse ("cursor") the
pointer slowly drifts in the +x-direction. The y-direction is reasonably
stable.

	Thanks for looking at these things,

					Tav


# Xorg configuration created by system-config-display

Section "ServerLayout"
        Identifier     "Multihead layout"
        Screen      0  "Screen0" RightOf "Screen1"
        Screen      1  "Screen1" 0 0
        InputDevice    "Mouse0" "CorePointer"
        InputDevice    "Keyboard0" "CoreKeyboard"
        InputDevice    "Synaptics" "AlwaysCore"
        InputDevice    "cursor"      "SendCoreEvents"
        InputDevice    "stylus"      "SendCoreEvents"
        InputDevice    "eraser"      "SendCoreEvents"
        InputDevice    "pad"        # Don't send core event!
        Option      "Xinerama" "off"
        Option      "Clone" "on"
EndSection

Section "Files"

# RgbPath is the location of the RGB database.  Note, this is the name
of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.
# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.
        RgbPath      "/usr/X11R6/lib/X11/rgb"
        FontPath     "unix/:7100"
EndSection

Section "Module"
        Load  "dbe"
        Load  "extmod"
        Load  "fbdevhw"
        Load  "glx"
        Load  "record"
        Load  "freetype"
        Load  "type1"
        Load  "synaptics"
        Load  "dri"
EndSection

Section "InputDevice"
        Identifier  "Keyboard0"
        Driver      "kbd"
        Option      "XkbModel" "pc105"
        Option      "XkbLayout" "us"
EndSection

Section "InputDevice"
        Identifier  "Mouse0"
        Driver      "mouse"
        Option      "Protocol" "IMPS/2"
        Option      "Device" "/dev/input/mice"
        Option      "ZAxisMapping" "4 5"
        Option      "Emulate3Buttons" "yes"
EndSection

Section "InputDevice"
        Identifier  "Synaptics"
        Driver      "synaptics"
        Option      "Device" "/dev/input/mice"
        Option      "Protocol" "auto-dev"
        Option      "Emulate3Buttons" "yes"
        Option      "LeftEdge" "120"
        Option      "RightEdge" "830"
        Option      "TopEdge" "120"
        Option      "BottomEdge" "650"
        Option      "FingerLow" "14"
        Option      "FingerHigh" "15"
        Option      "MaxTapMove" "110"
        Option      "VertScrollDelta" "20"
        Option      "HorizScrollDelta" "20"
        Option      "MinSpeed" "0.3"
        Option      "MaxSpeed" "0.75"
        Option      "AccelFactor" "0.02"
        Option      "EdgeMotionMinSpeed" "15"
        Option      "EdgeMotionMaxSpeed" "30"
        Option      "UpDownScrolling" "1"
        Option      "CircularScrolling" "1"
        Option      "CircScrollDelta" "0.1"
        Option      "CircScrollTrigger" "2"
        Option      "TapButton1" "1"
        Option      "TapButton2" "2"
        Option      "TapButton3" "3"
EndSection

Section "InputDevice"
        Identifier  "cursor"
        Driver      "wacom"
        Option      "Device" "/dev/input/wacom"
        Option      "Type" "cursor"
        Option      "USB" "on"
        Option      "DebugLevel" "2"
        Option      "Suppress" "4"
EndSection

Section "InputDevice"
        Identifier  "stylus"
        Driver      "wacom"
        Option      "Device" "/dev/input/wacom"
        Option      "Type" "stylus"
        Option      "Tilt" "on"
        Option      "USB" "on"
        Option      "DebugLevel" "1"
        Option      "Mode" "absolute"
# Cursor works only on one monitor at a time... but it works!
        Option      "mmonitor" "off"
# Hmmm see http://xxlwallpapers.com/about.html
#       Option      "ScreenNo" "0"
EndSection

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

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

Section "Monitor"
        Identifier   "Monitor0"
        VendorName   "Monitor Vendor"
        ModelName    "LCD Panel 1920x1200"
        HorizSync    31.5 - 90.0
        VertRefresh  60.0 - 60.0
        Option      "dpms"
EndSection

Section "Monitor"
        Identifier   "Monitor1"
        VendorName   "Monitor Vendor"
        ModelName    "Samsung SyncMaster 730B (Analog)"
        HorizSync    30.0 - 81.0
        VertRefresh  56.0 - 75.0
        Option      "dpms"
EndSection

Section "Device"
        Identifier  "Videocard0"
        Driver      "fglrx"
        VendorName  "Videocard vendor"
        BoardName   "ATI Radeon Mobility 9600 M10"
        Option      "VideoOverlay" "on"
EndSection

Section "Device"
        Identifier  "Videocard1"
        Driver      "fglrx"
        VendorName  "Videocard Vendor"
        BoardName   "ATI Radeon Mobility 9600 M10"
        Option      "VideoOverlay" "on"
        BusID       "PCI:1:0:0"
        Screen      1
EndSection

Section "Screen"
        Identifier "Screen0"
        Device     "Videocard0"
        Monitor    "Monitor0"
        DefaultDepth     24
        SubSection "Display"
                Viewport   0 0
                Depth     24
                Modes    "1920x1200"
        EndSubSection
EndSection

Section "Screen"
        Identifier "Screen1"
        Device     "Videocard1"
        Monitor    "Monitor1"
        DefaultDepth     24
        SubSection "Display"
                Viewport   0 0
                Depth     24
                Modes    "1280x1024"
        EndSubSection
EndSection

Section "DRI"
        Group        0
        Mode         0666
EndSection


	


On Mon, 2005-10-24 at 10:42 -0700, Ping@... wrote:
> Did dual monitor work under FC3? Please email me you xorg.conf.
> 
> REL_WHEEL can be larger/smaller than +/-1 depending on the speed you
> scroll the wheel.
> 
> Ping
> 
> On 10/15/05, Tavmjong Bah <tavmjong@...> wrote:
> >
> > Hi again,
> >
> > 	Sorry, I inadvertently sent the prior email before finishing it... I am
> > still a bit clumsy with the Wacom tablet and not everything is working
> > correctly. Let me repeat what I started:
> >
> >
> > Hi,
> >
> > I have an Intuos 3 4x5 that I am using with Fedora Core 4 on a laptop. I
> > had the tablet working with Fedora Core 3 but can't seem to get it to
> > work completely with FC4. Has anybody gotten it to work?
> >
> > The problems I have are:
> >
> > 1. I can't get the mouse (cursor) scroll wheel to work. wacdump
> >    shows the "RELWHEEL" changing values. As I understand it,
> >    the values in parenthesis are suppose to be the limits so the
> >    values should be between -00001 and +00001. The values I see
> >    exceed these limits.
> >
> > 2. I have a second monitor. If in the xorg.conf file I specify the
> >    "Mode" to be "absolute" the pad area corresponds to half of each
> >    monitor. If I try "relative" then I can get the stylus to cover
> >    both monitors fully but when ever I touch the stylus to the pad,
> >    the pointer jumps.
> >
> > 3. Using Inkscape and Gimp, the stylus continues to draw sometimes after
> >    lifting it off the pad. This happens when the drawing stroke
> >    is made quickly.
> >
> > I am currently using a 2.6.13 kernel but also observed the same problems
> > with a 2.6.12 kernel. And also both using the Fedora distribution
> > wacom_drv.o and the one from 0.7.0-1.tar.bz2.
> >
> > One potential problem is that I still have references to /dev/input/mice
> > in the xorg.conf file. It occurs twice, once for the USB mouse and once
> > for the built in Alps touchpad. I thought I read somewhere that with the
> > more recent drivers this is not a problem. Just in case it is I was
> > going to replace the /dev/input/mice with the actual /dev/input/mouseX
> > entries but it doesn't appear that Alps touchpad is using any of
> > the /dev/input/mouseX devices. (At least xxd doesn't show any data.)
> >
> > Any help would be greatly appreciated.
> >
> > 						Tav
> >
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.
> Get Certified Today * Register for a JBoss Training Course
> Free Certification Exam for All Training Attendees Through End of 2005
> Visit http://www.jboss.com/services/certification for more information
> _______________________________________________
> Linuxwacom-discuss mailing list
> Linuxwacom-discuss@...
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>

Please change mice to mouse# for Mouse0 and Synaptics in:
  Option "Device" "/dev/input/mice"
 Refer to http://linuxwacom.sourceforge.net/index.php/howto/mouse1 for
details.
 We'll try something else if this doesn't help.
 Ping
 P.S., "mmonitor" option isn't supported in xorg.conf. It can only be used
by xsetwacom command.

 On 10/24/05, Tavmjong Bah <tavmjong@...> wrote:
>
>
> Hi,
>
> I got the second monitor after I upgraded to FC4 so I did not have that
> part working under FC3. I have played around a bit more. After I use the
> command:
>
> xsetwacom set stylus mmonitor off
>
> I can use the tablet with the stylus on one monitor at a time except
> that with the second monitor if I drag a scroll bar the cursor
> jumps to the first monitor. When using the stylus on the first monitor
> it does not jump to the second monitor. (I still have the scroll wheel
> problem and the pen not releasing after a quick stroke problem.)
>
> Oh, I am now using cvs from yesterday for wacom.ko.
>
> My xorg.conf file follows. The "mmonitor" "off" in the file didn't seem
> to have any effect... I had to use the xsetwacom command.
>
> One additional problem I see is that with the mouse ("cursor") the
> pointer slowly drifts in the +x-direction. The y-direction is reasonably
> stable.
>
> Thanks for looking at these things,
>
> Tav
>

Hi Ping,

	I have made the change from mice to mouse#. I hadn't tried this before
as I could not determine which mouse# the Synaptics (Alps) uses. It
appears that the Synaptics driver doesn't use any and ignores the
setting (I arbitrarily picked /dev/input/mouse0 and it works). The
change has fixed:

1. The scrolling problem with the "cursor" wheel.

2. The problem dragging scroll bars with the stylus on the second
monitor. I still see one strange behavior. If I move the stylus to the
far right of the pad while using the second monitor, the stylus jumps to
the first monitor. I can not get it back to the second monitor unless I
use the "cursor" or touchpad.

3. The stylus no longer seems to continuing to draw after lifting off
the tablet. I thought I saw it do this a couple of time after the change
in xorg.conf but I can't make it happen now. In the Inkscape release
notes for 0.43 it says this is a known problem with X.org not releasing
events.

	The problems I still have are:

1. The "cursor" drifting in the x-direction. Is this a hardware problem?

2. Not being able to use the stylus easily on both monitors.

	In any case, life is much better.

				Thanks for your help! 

						Tav


On Mon, 2005-10-24 at 17:14 -0700, Ping@... wrote:
> Please change mice to mouse#  for Mouse0 and Synaptics in:
>  
>        Option      "Device" "/dev/input/mice"
>  
> 
> Refer to http://linuxwacom.sourceforge.net/index.php/howto/mouse1 for
> details. 
>  
> We'll try something else if this doesn't help.
>  
> Ping
>  
> P.S., "mmonitor" option isn't supported in xorg.conf. It can only be
> used by xsetwacom command.
> 
>  
> On 10/24/05, Tavmjong Bah <tavmjong@...> wrote: 
>         
>         Hi,
>         
>                I got the second monitor after I upgraded to FC4 so I
>         did not have that
>         part working under FC3. I have played around a bit more. After
>         I use the 
>         command:
>         
>         xsetwacom set stylus mmonitor off
>         
>         I can use the tablet with the stylus on one monitor at a time
>         except
>         that with the second monitor if I drag a scroll bar the cursor
>         jumps to the first monitor. When using the stylus on the first
>         monitor 
>         it does not jump to the second monitor. (I still have the
>         scroll wheel
>         problem and the pen not releasing after a quick stroke
>         problem.)
>         
>                Oh, I am now using cvs from yesterday for wacom.ko.
>         
>                My xorg.conf file follows. The "mmonitor" "off" in the
>         file didn't seem
>         to have any effect... I had to use the xsetwacom command.
>         
>                One additional problem I see is that with the mouse
>         ("cursor") the 
>         pointer slowly drifts in the +x-direction. The y-direction is
>         reasonably
>         stable.
>         
>                Thanks for looking at these things,
>         
>                                                Tav

Let me make sure that I fully understood your message:
 1.

 On 10/25/05, Tavmjong Bah <tavmjong@...> wrote:
>
> Hi Ping,
>
> I have made the change from mice to mouse#. I hadn't tried this before
> as I could not determine which mouse# the Synaptics (Alps) uses. It
> appears that the Synaptics driver doesn't use any and ignores the
> setting (I arbitrarily picked /dev/input/mouse0 and it works). The
> change has fixed:
>
> 1. The scrolling problem with the "cursor" wheel.
>
> 2. The problem dragging scroll bars with the stylus on the second
> monitor. I still see one strange behavior. If I move the stylus to the
> far right of the pad while using the second monitor, the stylus jumps to
> the first monitor. I can not get it back to the second monitor unless I
> use the "cursor" or touchpad.
>
> 3. The stylus no longer seems to continuing to draw after lifting off
> the tablet. I thought I saw it do this a couple of time after the change
> in xorg.conf but I can't make it happen now. In the Inkscape release
> notes for 0.43 it says this is a known problem with X.org <http://X.org>n=
ot releasing
> events.
>
> The problems I still have are:
>
> 1. The "cursor" drifting in the x-direction. Is this a hardware problem?
>
> 2. Not being able to use the stylus easily on both monitors.
>
> In any case, life is much better.
>
> Thanks for your help!
>
> Tav
>

Sorry, somehow hit "Send" while typing.
 So, you have changed both /dev/input/mice settings.
 Let's see what we can do to resolve your remaining issues:
 1. The "cursor" drifting in the x-direction. Is this a hardware problem?
 No, I don't think so since I have one running and I don't see this problem=
.
I'll setup my system with your xorg.conf to see if it is related to the
configuration or not (give me some time for this).

2. Not being able to use the stylus easily on both monitors.

If you have issued "xsetwacom set stylus mmonitor off", you can not move th=
e
cursor from one screen to the other since it supposes to stay in one screen
unless you manually move it the other screen. If this is not what you were
talking about, you'll need to wait for me to set up a system like yours to
see the issue.
 Ping
 On 10/25/05, Ping@... <pinglinux@...> wrote:
>
> Let me make sure that I fully understood your message:
>  1.
>
>  On 10/25/05, Tavmjong Bah <tavmjong@...> wrote:
> >
> > Hi Ping,
> >
> > I have made the change from mice to mouse#. I hadn't tried this before
> > as I could not determine which mouse# the Synaptics (Alps) uses. It
> > appears that the Synaptics driver doesn't use any and ignores the
> > setting (I arbitrarily picked /dev/input/mouse0 and it works). The
> > change has fixed:
> >
> > 1. The scrolling problem with the "cursor" wheel.
> >
> > 2. The problem dragging scroll bars with the stylus on the second
> > monitor. I still see one strange behavior. If I move the stylus to the
> > far right of the pad while using the second monitor, the stylus jumps t=
o
> >
> > the first monitor. I can not get it back to the second monitor unless I
> > use the "cursor" or touchpad.
> >
> > 3. The stylus no longer seems to continuing to draw after lifting off
> > the tablet. I thought I saw it do this a couple of time after the chang=
e
> >
> > in xorg.conf but I can't make it happen now. In the Inkscape release
> > notes for 0.43 it says this is a known problem with X.org<http://x.org/=
>not releasing
> > events.
> >
> > The problems I still have are:
> >
> > 1. The "cursor" drifting in the x-direction. Is this a hardware problem=
?
> >
> > 2. Not being able to use the stylus easily on both monitors.
> >
> > In any case, life is much better.
> >
> > Thanks for your help!
> >
> > Tav
> >
>