Need help with M$ touchmouse
Gene Heskett
gheskett at wdtv.com
Fri Dec 5 07:56:14 PST 2014
On Thursday 04 December 2014 23:03:38 Peter Hutterer did opine
And Gene did reply:
> On Thu, Dec 04, 2014 at 09:43:44PM -0500, Gene Heskett wrote:
> > On Thursday 04 December 2014 16:18:16 Peter Hutterer did opine
> >
> > And Gene did reply:
> > > On Thu, Dec 04, 2014 at 01:23:49PM -0500, Gene Heskett wrote:
> > > > Greetings all;
> > > >
> > > > I have a wireless M$ Explorer Touchmouse, and the touch pad is
> > > > buggier than a 10 day old carcass.
> > > >
> > > > Specifically, the side scrolling is driving me crazy, and its not
> > > > a long trip. ;)
> > > >
> > > > When it works, its 20x more sensitive sideways than vertically,
> > > > and I can't get my fingers far enough away from the pad to stop
> > > > its crazy behavior, and still rest them in a comfy location for
> > > > button pushing.
> > > >
> > > > Is there anything I can put in an /etc/X11 file that will shut
> > > > the side scroll function off, but leave the vertical finger
> > > > drags working?
> > >
> > > attach an evemu recording and your xorg.log to a bug please. I
> > > don't have a recording for this one yet so it's hard to tell.
> > >
> > > Cheers,
> > >
> > > Peter
> >
> > First off Peter, evemu is not 'locate'able. And I'm not sure you
> > want the current Xorg.0.log in your mailbox as its north of 179
> > megabytes.
>
> you could have restarted X, or started another session for a fresh log
> file. or cut down the thousands of lines of errors which is likely
> what 99% of the log file are if it grows to that size in a week.
>
> > I even sicc'd synaptic to find it in the ubuntu repo, and came up dry
> > there too.
>
> evemu shows up as second link on google for me:
> http://www.freedesktop.org/wiki/Evemu/
>
> but tbh, if you're on a 4 year old box you're pretty much on your own,
> sorry. there may have been kernel fixes since, there may have been
> evdev fixes since, etc.
I do occsionally build a fresher kernel because the default kernel for
this particular install, an rtai kit on top of 2.6.32-123, has no PAE and
there's 8Gb in this box. Running the OEM kernel only sees 3Gb of that,
and I'm a gigabyte into swap in 24hrs.
So the presently running kernel is a 3.16.0. 32 bit with PAE. Hasn't
touched swap in months.
Nest, that link 3rd line is bogus, needs an ".sh" tagged onto the
./autogen script cli invocation.
The autogen output this to the screen:
gene at coyote:/usr/src/evemu$ ./autogen.sh --prefix=/usr
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal
autoreconf: configure.ac: tracing
autoreconf: configure.ac: creating directory config-aux
autoreconf: running: libtoolize --install --copy
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `config-aux'.
libtoolize: copying file `config-aux/config.guess'
libtoolize: copying file `config-aux/config.sub'
libtoolize: copying file `config-aux/install-sh'
libtoolize: copying file `config-aux/ltmain.sh'
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac
and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-
tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
autoreconf: running: /usr/bin/autoconf
autoreconf: running: /usr/bin/autoheader
autoreconf: running: automake --add-missing --copy --no-force
configure.ac:12: installing `config-aux/missing'
python/Makefile.am:20: installing `config-aux/py-compile'
src/Makefile.am: installing `config-aux/depcomp'
autoreconf: Leaving directory `.'
But make cannot find the makefile, and indeed there was not one created.
The INSTALL inserts a ./configure step in the sequence, and that bails out
for lack of:
checking pkg-config is at least version 0.9.0... yes
checking for LIBEVDEV... configure: error: Package requirements (libevdev
>= 1.2.99.902) were not met:
No package 'libevdev' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables LIBEVDEV_CFLAGS
and LIBEVDEV_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
Apparently I'll need a git URL to get it and install it? Amazingly that
gets zero hits on google. You have found the ultimate google non-entity!
That has NEVER happened before.
So you see what I need to do above and I am waiting, with "baited" breath
for further instruction. ;-)
Thanks Peter.
> Cheers,
> Peter
>
> > This is a 10.04.4 LTS server install with enough kde pulled in to get
> > kmail & friends.
> >
> > I can copy/paste the relevant module loading bits. Here if it would
> > help.
> >
> > THere is about 160 megabytes of this in the log:
> > (II) LoadModule: "fb"
> >
> > (II) Loading /usr/lib/xorg/modules/libfb.so
> > (II) Module fb: vendor="X.Org Foundation"
> >
> > compiled for 1.7.6, module version = 1.0.0
> > ABI class: X.Org ANSI C Emulation, version 0.4
> >
> > (**) FBDEV(0): using shadow framebuffer
> > (II) Loading sub module "shadow"
> > (II) LoadModule: "shadow"
> > (II) Loading /usr/lib/xorg/modules/libshadow.so
> > (II) Module shadow: vendor="X.Org Foundation"
> >
> > compiled for 1.7.6, module version = 1.1.0
> > ABI class: X.Org ANSI C Emulation, version 0.4
> >
> > (II) UnloadModule: "nv"
> > (II) Unloading /usr/lib/xorg/modules/drivers/nv_drv.so
> > (==) Depth 24 pixmap format is 32 bpp
> > (==) FBDEV(0): Backing store disabled
> > (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
> > (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
> > (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
> > (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
> > (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
> > (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
> > (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
> > (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
> >
> >
> > Which is repeated at least 1000 times, then later after it has found
> > my pcHDTV-3000 card:
> >
> > (II) MCE IR Keyboard/Mouse (cx88xx): initialized for relative axes.
> > (II) config/udev: Adding input device MCE IR Keyboard/Mouse (cx88xx)
> > (/dev/input/mouse0)
> > (II) No input driver/identifier specified (ignoring)
> > (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
> > (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
> > (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
> > (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
> > (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
> > (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
> > (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
> > (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
> > (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
> > (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
> > (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
> >
> > I'd guess another 165 megabytes of that to the end of the log.
> > Uptime is a week & small change.
> >
> > I didn't even know the tv card had a mouse port? But I'll be dipped,
> > it actually has a ps2 socket on the back of it! But I'm not sure I
> > still have one of those critters.
> >
> > > > Even that goes away quite frequently, and I have to turn the
> > > > mouse over, shut it off for a second or two & turn it back on,
> > > > at which point it works fairly well but will eventually become
> > > > intermittent in its response for an hour or so before completely
> > > > dying, the the screen cursor still follows it well, and the two
> > > > buttons work well. But I've blamed that on a buggy mouse.
> > > >
> > > > This is extremely distracting when I am writing code in geany
> > > > (gedit does not have a sideways scroll, but it has trashed
> > > > important source code file entirly too often, geany never has)
> > > > because I have to drag the bar on the bottom back the the left
> > > > stop in order to see what I am writing. I need help since the
> > > > mouse makers figured out how to sell the high priced versions by
> > > > putting the optical eye way back under the palm of our hands
> > > > instead of up under your fingers in the #<$50 models. So the
> > > > <$50 mice aren't at all intuitive to use because you are forced
> > > > to move the whole arm when using them.
> >
> > Thanks Peter.
> >
> > Cheers, Gene Heskett
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS
More information about the xorg
mailing list