All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony DiSante <orders@nodivisions.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: KVM -> jumping mouse... still no solution?
Date: Wed, 06 Oct 2004 02:15:03 -0400	[thread overview]
Message-ID: <41638D67.2020307@nodivisions.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0410060753590.2993@dragon.hygekrogen.localhost>

Jesper Juhl wrote:
>>you don't move it, but if you move it N/E/NE it's really slow and jerky, and
>>if you move it S/W/SW even a hair, it slams down to the SW corner of the
>>screen and acts like you hit all the mouse's buttons 50 times simultaneously.
>>
> 
> I've had similar problems with my mouse and KVM switch.
> 
> 
>>The other day I came across this (kerneltrap.org/node/view/2199): "Use
>>psmouse.proto=bare on the kernel command line, or proto=bare on the
>>psmouse module command line."  But that makes the mouse's scroll-wheel not
>>work.  (And this problem doesn't exist with some of the mouse drivers, but it
>>does with IMPS/2, which is the only one I've ever been able to get the scroll
>>wheel working with.)
>>
> 
> psmouse.proto=imps solves the problem for me (wheel works as well).
> The funny thing is that I don't need to do anything like this when I boot 
> a 2.4 kernel, only 2.6 kernels show this behaviour on my system.???

That doesn't make any difference on my system.  Mouse freakout is just the same.

-Anthony DiSante
http://nodivisions.com/

  reply	other threads:[~2004-10-06  6:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-06  5:36 KVM -> jumping mouse... still no solution? Anthony DiSante
2004-10-06  5:57 ` Jesper Juhl
2004-10-06  6:15   ` Anthony DiSante [this message]
2004-10-06  7:23 ` Rajendra P Mishra
2004-10-06 10:09   ` Anthony DiSante
2004-10-06 16:22     ` Dmitry Torokhov
2004-10-06 22:07     ` Peter Williams

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=41638D67.2020307@nodivisions.com \
    --to=orders@nodivisions.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 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.