Re: xsetwacom parameter question

2006-10-30 Thread Thomas H. George
On Mon, Oct 30, 2006 at 07:57:08AM -0500, Thomas H. George wrote: > On Mon, Oct 30, 2006 at 09:35:40PM +1300, Chris Bannister wrote: > > On Sat, Oct 28, 2006 at 09:13:36AM -0400, Thomas H. George wrote: > > > Now my Wacom Graphire 4 mouse moves in fits and starts. It worked > > > smoothly before t

Re: xsetwacom parameter question

2006-10-30 Thread Thomas H. George
On Mon, Oct 30, 2006 at 09:35:40PM +1300, Chris Bannister wrote: > On Sat, Oct 28, 2006 at 09:13:36AM -0400, Thomas H. George wrote: > > Now my Wacom Graphire 4 mouse moves in fits and starts. It worked > > smoothly before the upgrade. The upgrade was from Debian Sarge with a > > 2.6.11 kernel t

Re: xsetwacom parameter question

2006-10-30 Thread Chris Bannister
On Sat, Oct 28, 2006 at 09:13:36AM -0400, Thomas H. George wrote: > Now my Wacom Graphire 4 mouse moves in fits and starts. It worked > smoothly before the upgrade. The upgrade was from Debian Sarge with a > 2.6.11 kernel to Debian testing with a 2.6.17 kernel built from > linux-source-2.6.17 w

Re: xsetwacom parameter question

2006-10-28 Thread Michael Waters
On Sat, 28 Oct 2006 09:13 -0400, Thomas H. George wrote: > I have tried changing the Motion_Buffer from 256 to 0 with xsetwacom set > cursor Motion_Buffer 0. Result: Motion_Buffer is an unknown parameter. > > My object is to correct the following problem resulting from the move > from Sarge to

xsetwacom parameter question

2006-10-28 Thread Thomas H. George
I have tried changing the Motion_Buffer from 256 to 0 with xsetwacom set cursor Motion_Buffer 0. Result: Motion_Buffer is an unknown parameter. My object is to correct the following problem resulting from the move from Sarge to testing: Now my Wacom Graphire 4 mouse moves in fits and starts