From: Greg KH <greg@kroah.com>
To: Ivan Gyurdiev <ivg2@cornell.edu>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Novatek USB Keyboard/Mouse Bug
Date: Thu, 28 Aug 2003 14:59:13 -0700 [thread overview]
Message-ID: <20030828215913.GA13284@kroah.com> (raw)
In-Reply-To: <3F4E796E.5090203@cornell.edu>
On Thu, Aug 28, 2003 at 05:51:42PM -0400, Ivan Gyurdiev wrote:
> Hi, I finally figured out why my wireless mouse turns off and on
> randomly every once in a while and works depending on the usb hub it is
> in - it's the keyboard's fault.
>
> My mouse is:
> PM: Adding info for usb:2-2
> input: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:10.0-2
>
> My keyboard is:
> PM: Adding info for usb:2-1
> input: USB HID v1.00 Keyboard [NOVATEK Keyboard NT6881] on
> usb-0000:00:10.0-1
> PM: Adding info for usb:2-1:0
> input: USB HID v1.00 Mouse [NOVATEK Keyboard NT6881] on
> usb-0000:00:10.0-1
> PM: Adding info for usb:2-1:1
>
>
> As you can see the kernel thinks it's also a mouse, which it definitely
> is not. I've previously posted this to LKML somewhere, and my
> impressions were that people don't think it's a bug, since some other
> model of that keyboard worked together with a mouse somehow. Perhaps
> that's true, but I do not have a second mouse. The kernel thinks I do,
> and switching the keyboard and the mouse usb hubs results in mouse
> devices reordering and X not working with the proper mouse (attempting
> to use the keyboard as mouse, which apparently does not work).
Why not just use /dev/mice and then you don't have to worry about the
mice ording issue?
Also lots of USB keyboards have a fake "mouse" within them to handle
some of the extended keys. It's quite common.
thanks,
greg k-h
next prev parent reply other threads:[~2003-08-28 21:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 21:51 Novatek USB Keyboard/Mouse Bug Ivan Gyurdiev
2003-08-28 21:59 ` Greg KH [this message]
2003-08-28 23:35 ` Ivan Gyurdiev
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=20030828215913.GA13284@kroah.com \
--to=greg@kroah.com \
--cc=ivg2@cornell.edu \
--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