> Date: Mon, 24 Jul 2006 23:35:43 +0100 > From: Andrew Bowden <[EMAIL PROTECTED]> > Subject: Re: [Linuxwacom-discuss] Volito 2 on Ubuntu Dapper > To: linuxwacom-discuss@lists.sourceforge.net > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain
> Okay, so I've now got > > Section "InputDevice" > Driver "wacom" > Identifier "stylus" > Option "Device" "/dev/input/wacom" # Change to > # /dev/input/event > # for USB > Option "Type" "stylus" > Option "USB" "on" > # Option "ForceDevice" "ISDV4" # Tablet PC ONLY > EndSection > > > I now have another problem. If I try to use the tablet, the cursor > doesn't appear. Clicking on the tablet just seems to click on the item > in the top right corner (the GNOME calendar widget) :( > > (Incidentally I did try putting the Option "USB" "on" for the cursor and > eraser, but it didn't make any difference) > > wacdump on /dev/input/event3 gives no output at all (for the record, > event0 doesn't seem to be anything, event1 is the mouse, event2 is the > keyboard - event3 is where /dev/input/wacom is now being mapped. > > > On the plus side(!), The GIMP for the first time recognises that there > is a tablet attached when you click on "Configure Extended Input > Devices". It refused to do so previously. Of course it doesn't work, > so is of now use! > > Xorg.0.log seems to show things are loading that didn't appear > before.... > > > (**) Option "Device" "/dev/input/wacom" > stylus Wacom X driver grabbed event device > (==) Wacom using pressure threshold of 30 for button 1 > (==) Wacom USB Volito2 tablet speed=9600 maxX=5104 maxY=3712 maxZ=511 > resX=1016 resY=1016 suppress=2 tilt=disabled > (==) Wacom device "stylus" top X=0 top Y=0 bottom X=5104 bottom Y=3712 > (==) Wacom device "cursor" top X=0 top Y=0 bottom X=5104 bottom Y=3712 > (==) Wacom device "eraser" top X=0 top Y=0 bottom X=5104 bottom Y=3712 > > > However there's lots of things like this in the log file - don't know if > it's related. > > (**) Option "TopX" "-1209658536" > ProcXCloseDevice to close or not ? > (**) Option "TopY" "9" > ProcXCloseDevice to close or not ? > (**) Option "BottomX" "0" > ProcXCloseDevice to close or not ? > (**) Option "BottomY" "975793769" > ProcXCloseDevice to close or not ? > > > Does look rather odd. > > I did try loading the 0.7.4-3 driver that I'd built (but not installed) > and when I did that, the wacom tablet did work again, but with the same > intermittent boundary problems as before. Xorg.0.log has a new message. > > Error reading wacom device : Invalid argument > > A new copy of which appears everytime I use the pen. As an aside, if I try using the 0.7.3-1 driver, I get absolutely no response from the cursor at all. It seems to be loading, and wacdump recognises that there is a Volito2 there, but doesn't register anything at all when the cursor moves. In this case, "Error reading wacom device" only appears when I move the mouse. Has anyone any ideas at all? Or should I just give this up as a bad lot? ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Linuxwacom-discuss mailing list Linuxwacom-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
