From: Vojtech Pavlik <vojtech@suse.cz>
To: Jon Grimm <jgrimm2@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.44: Still has KVM + Mouse issues
Date: Sun, 26 Jan 2003 14:13:37 +0100 [thread overview]
Message-ID: <20030126141337.J31427@ucw.cz> (raw)
In-Reply-To: <3DB9DA64.E48C8C5B@us.ibm.com>; from jgrimm2@us.ibm.com on Fri, Oct 25, 2002 at 06:57:24PM -0500
On Fri, Oct 25, 2002 at 06:57:24PM -0500, Jon Grimm wrote:
> Hello,
> I see that Thomas Molina 2.5 problem list no longer carries a KVM and
> mouse
> issue where it previously had.
>
> If a fix is available I'd love to test it out as I still see strange
> behavior
> with an Intellimouse and my MasterView CS-104 KVM switch (yep its
> old).
>
> With a few trusty printks, it looks like after I switch away & back
> into 2.5.44, the mouse is now sending 3 byte packets instead of the 4 it
> previously was.
>
> As you can imagine this causes all sorts of havok as the packets are
> interpretted completely wrong from there on out. If there is enough
> delay between
> events, the synchonization logic kicks in and throws the packet out,
> since
> it thinks the 4th byte is old (where it is really the first byte of the
> next
> 3-byte packet). This generates those pesky "psmouse.c: Lost
> synchronization "..
> However, much of the time an incorrect 4-byte frame gets interpretted
> and
> the X going totally haywire.
>
> BTW, serio_rescan() gets the mouse back into a happy 4-byte generating
> state.
Use the psmouse_noext option.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2003-01-26 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 23:57 Jon Grimm
2002-10-28 17:34 ` Vojtech Pavlik
2003-01-26 13:13 ` Vojtech Pavlik [this message]
[not found] <3DB9DA64.E48C8C5B@us.ibm.com.suse.lists.linux.kernel>
2002-10-26 6:43 ` Andi Kleen
2002-10-26 16:44 ` Jon Grimm
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=20030126141337.J31427@ucw.cz \
--to=vojtech@suse.cz \
--cc=jgrimm2@us.ibm.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome