All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Sorenson <frank@tuxrocks.com>
To: Marc Koschewski <marc@osknowledge.org>
Cc: Joe Feise <jfeise@feise.com>,
	linux-kernel@vger.kernel.org,
	Dmitry Torokhov <dtor_core@ameritech.net>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: mouse issues in 2.6.15-rc5-mm series
Date: Sat, 24 Dec 2005 03:57:42 -0700	[thread overview]
Message-ID: <43AD29A6.10407@tuxrocks.com> (raw)
In-Reply-To: <20051224104224.GA5789@stiffy.osknowledge.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marc Koschewski wrote:
> * Joe Feise <jfeise@feise.com> [2005-12-23 22:43:32 -0800]:
> 
> 
>>[Note: please cc me on answers since I'm not subscribed to the kernel list]
>>
>>I am experiencing problems with mouse resyncing in the -mm series.
>>This is a Logitech wheel mouse connected through a KVM.
>>Symptom: whenever the mouse isn't moved for some seconds, it doesn't
>>react to movement for a second, and then resyncs. Sometimes, the
>>resyncing results in the mouse pointer jumping, which as far as I
>>know is a protocol mismatch.
>>While searching for reports of similar problems, I came across
>>Frank Sorenson's post from Nov. 23 (http://lkml.org/lkml/2005/11/23/533).
>>Like in his case, reverting
>>input-attempt-to-re-synchronize-mouse-every-5-seconds.patch
>>resulted in a kernel without this problem.
>>
>>-Joe

Joe,

I continue to see the same issues with the resync patch in -mm.  For me,
tapping stops working, and I'm now seeing both the mouse pointer jumping
 as well (a lesser issue for me, so it was probably present earlier as
well).

I switched to using the synaptics X driver as recommended by Dmitry
Torokhov (http://lkml.org/lkml/2005/11/25/130), and that has worked
splendidly for me.  However, that's really just a band-aid, and I'd be
happier with a working resync patch.

> Hi Joe,
> 
> read these ones:
> 
> http://lkml.org/lkml/2005/11/18/152
> http://www.uwsg.iu.edu/hypermail/linux/kernel/0511.3/0019.html
> 
> Maybe they help you out.
> 
> I didn't get it working in the rc5 -mm tree so far. But non -mm work as good as
> they always did.

Same issue for me as well.

Frank
- --
Frank Sorenson - KD7TZK
Systems Manager, Computer Science Department
Brigham Young University
frank@tuxrocks.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFDrSmmaI0dwg4A47wRAidbAJ9rR7ZtgavKNw1aEamcdZ8Br/27GwCdEQcc
JHP9CL6TTlbhYm8kyzeXH+w=
=w3cG
-----END PGP SIGNATURE-----

  reply	other threads:[~2005-12-24 10:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-24  6:43 mouse issues in 2.6.15-rc5-mm series Joe Feise
2005-12-24 10:42 ` Marc Koschewski
2005-12-24 10:57   ` Frank Sorenson [this message]
2005-12-26  4:09     ` Dmitry Torokhov
2005-12-26  4:40       ` Frank Sorenson
2005-12-26  4:55         ` Dmitry Torokhov
2006-01-05  3:24         ` Dmitry Torokhov
2006-01-06  8:28           ` Frank Sorenson
2006-01-06 16:26             ` Dmitry Torokhov
2006-01-06 16:44               ` Frank Sorenson
2006-01-06 22:30             ` Frank Sorenson
2005-12-24 17:56 ` Dmitry Torokhov
2005-12-24 18:49   ` Joe Feise

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43AD29A6.10407@tuxrocks.com \
    --to=frank@tuxrocks.com \
    --cc=akpm@osdl.org \
    --cc=dtor_core@ameritech.net \
    --cc=jfeise@feise.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc@osknowledge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.