From: "James E. Jennison" <james.jennison@digital-creationsonline.com>
To: "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: ImExPS/2 status
Date: Tue, 18 Oct 2005 21:48:37 -0700 [thread overview]
Message-ID: <200510182148.37822.james.jennison@digital-creationsonline.com> (raw)
In-Reply-To: <4355C2F7.1080007@shaw.ca>
Robert:
Yes, it does. I have also tried manually specifying the mouse protocol to
use, and that does not seem to help either. Let me know if I can give you
any other information.
-James
On Tuesday 18 October 2005 20:52, you wrote:
> James E. Jennison wrote:
> > Hey everyone...this is my first posting here, and I may not be going
> > about this the right way so please forgive me if I am not. I had a
> > question regarding the status of the code for the ImExPS/2 style mice.
> >
> > I currently have a Nexxtech NXX200 PS/2 Optical Wheel Mouse, running
> > kernel 2.6.13.4. I noticed that prior to the 2.6.x.x series (whilst in
> > the 2.4.x.x series (I was stubborn)), that my mouse was working fine.
> >
> > Now, however,if I plug my mouse in, the optical light comes on for
> > perhaps half a second, and the mouse goes dark. The second thing that
> > happens is if you click either button, or move/click the scrollwheel, the
> > cursor will go to the upper right hand corner of the screen to where you
> > only see a small fraction of it. This happens in both console mode and
> > in graphical.
>
> Does this also happen if the mouse is plugged in when powering up the
> machine? PS/2 devices are not really designed to be hot-plugged.
next prev parent reply other threads:[~2005-10-19 4:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4Z9Qz-7an-5@gated-at.bofh.it>
2005-10-19 3:52 ` Robert Hancock
2005-10-19 4:48 ` James E. Jennison [this message]
2005-10-19 0:11 James E. Jennison
2005-10-19 5:30 ` Dmitry Torokhov
2005-10-19 13:45 ` James E. Jennison
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=200510182148.37822.james.jennison@digital-creationsonline.com \
--to=james.jennison@digital-creationsonline.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
all inboxes | Powered by JetHome®