public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Satchell <satch@fluent-access.com>
To: linux-kernel@vger.kernel.org
Subject: FYI  PS/2 Mouse problems -- userland issue
Date: Tue, 21 Aug 2001 11:07:54 -0700	[thread overview]
Message-ID: <4.3.2.7.2.20010821084512.00bdf800@mail.fluent-access.com> (raw)

Last week I had asked about mouse problems.  I have discovered the root 
cause.  This affects you if (1) you are using a KVM switch and (2) you have 
a "wheel" mouse.

The problem is that sometime during system initialization the mouse is 
being configured as a generic PS/2 mouse (no wheel).  This works 
fine...until you switch the mouse away from the system.  Depending on the 
KVM switch you are using, the mouse MAY reset itself into its native 
mode.  In the case of the Logitech wheel mice, this means that each mouse 
event sends four codes instead of three.  The X mouse support doesn't like 
that very much.  :)

This MAY be a kernel issue depending on where I locate the mouse 
initialization code.  If it is in the kernel, then there will need to be a 
patch to allow the mouse to be re-initialized into the mode everyone expects.

Satch


             reply	other threads:[~2001-08-21 18:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-21 18:07 Stephen Satchell [this message]
2001-08-21 18:17 ` FYI PS/2 Mouse problems -- userland issue Ben LaHaise
2001-08-21 18:28   ` James Simmons
2001-08-21 18:35     ` Ben LaHaise
2001-08-21 20:30       ` James Simmons
2001-08-21 20:29 ` Kurt Garloff
     [not found] <mailman.998417940.18388.linux-kernel2news@redhat.com>
2001-08-21 18:59 ` Pete Zaitcev
  -- strict thread matches above, loose matches on Subject: below --
2001-08-21 19:40 Andries.Brouwer
2001-08-21 20:22 ` Ben LaHaise
2001-08-21 22:35 Andries.Brouwer
2001-08-21 22:41 ` Ben LaHaise
2001-08-22 18:09 ` 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=4.3.2.7.2.20010821084512.00bdf800@mail.fluent-access.com \
    --to=satch@fluent-access.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