From: Keith Owens <kaos@ocs.com.au>
To: Stephen Satchell <satch@fluent-access.com>
Cc: linas@linas.org, linux-kernel@vger.kernel.org
Subject: Re: mouse problems in 2.4.2
Date: Mon, 26 Mar 2001 10:47:02 +1000 [thread overview]
Message-ID: <12849.985567622@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Sun, 25 Mar 2001 16:27:37 PST." <4.3.2.7.2.20010325162459.00b54620@mail.fluent-access.com>
On Sun, 25 Mar 2001 16:27:37 -0800,
Stephen Satchell <satch@fluent-access.com> wrote:
>I'm experiencing the same thing with an ASUS P5A-B running a K6-2/266 with
>Linux 2.2.17, and Windows 98. Central problem appears to be the KVM
>switch I'm using. Save yourself the problem.
>
>I had to reboot all the systems to get regular mouse operation back with
>the Logitech.
I sometimes have keyboard and mouse problems after changing machines
using a mechanical KVM, on a Logitech mouse. This script fixes it for
me.
/usr/local/bin/switched
#!/bin/sh
/etc/rc.d/init.d/gpm restart
/sbin/kbdrate -r 30
I run gpm in redirect -R mode as
daemon gpm -t $MOUSETYPE -R -m /dev/ttyS0
and tell X11 to read from /dev/gpmdata as
Protocol "MouseSystems"
Device "/dev/gpmdata"
not directly from the mouse; the redirect protocol is always
MouseSystems, no matter what the underlying mouse type is. Restarting
gpm after KVM switch then fixes everything else.
next prev parent reply other threads:[~2001-03-26 0:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-25 22:33 mouse problems in 2.4.2 linas
2001-03-26 0:27 ` Stephen Satchell
2001-03-26 0:47 ` Keith Owens [this message]
2001-03-26 3:22 ` linas
2001-03-27 20:15 ` mouse problems in 2.4.2 -> lost byte Gunther Mayer
2001-03-27 20:45 ` linas
2001-03-28 18:31 ` Gunther Mayer
2001-03-28 21:59 ` Vojtech Pavlik
2001-03-28 23:19 ` linas
2001-03-29 5:45 ` Vojtech Pavlik
2001-04-08 20:23 ` mouse problems in 2.4.2 -> lost byte -> Patch(2.4.3)! Gunther Mayer
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=12849.985567622@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linas@linas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=satch@fluent-access.com \
/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