public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org, orders@nodivisions.com
Subject: Re: KVM -> jumping mouse... still no solution?
Date: Wed, 6 Oct 2004 11:22:44 -0500	[thread overview]
Message-ID: <200410061122.45191.dtor_core@ameritech.net> (raw)
In-Reply-To: <4163C46A.2050004@nodivisions.com>

On Wednesday 06 October 2004 05:09 am, Anthony DiSante wrote:
>  > One quick solution I know of is to restart the gpm daemon,
>  > (/etc/init.d/gpm  restart) that resets the mouse settings.
>  > But this is not the correct way, there should be some way
>  > where the driver automatically detects and resets the mouse.
>  >
> 
> That doesn't work for me either.  Hmm... maybe it's because I'm using a 
> Microsoft mouse... only plays nice with Windows systems?
> 

In 2.6 GPM does not have access to the hardware and therefore cannot reset
it. A temporary fix can be downloaded from here:

	http://bugme.osdl.org/attachment.cgi?id=3244&action=view

It will for only on pre 2.6.9-rc2 kernels. When using kernels 2.6.9-rc3+
there is no automatic re-synchronization [yet] but one can restore a mouse
by issuing the following command:

	echo -n "reconnect" > /sys/bus/serio/devices/serioX/driver

To find out which 'serioX' your mouse connected to just look into their
respective "driver" attributes - the one with "psmouse" is the one you
need.

-- 
Dmitry

  reply	other threads:[~2004-10-06 16:26 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
2004-10-06  7:23 ` Rajendra P Mishra
2004-10-06 10:09   ` Anthony DiSante
2004-10-06 16:22     ` Dmitry Torokhov [this message]
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=200410061122.45191.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=orders@nodivisions.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