public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Raul Miller <moth@magenta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: problem with usb duo mouse and keyboard
Date: Sun, 21 Dec 2003 22:39:50 +0100	[thread overview]
Message-ID: <20031221213950.GA14664@ucw.cz> (raw)
In-Reply-To: <20031221154331.Z28449@links.magenta.com>

On Sun, Dec 21, 2003 at 03:43:31PM -0500, Raul Miller wrote:
> Linux 2.6.0 (and 2.6.0-test11) appears to have a significant problem
> with the mouse of the logitech 700mx duo when it's plugged in using usb.
> 
> The mouse works fine* when plugged in using the ps/2 mouse connector,
> and the keyboard works ok even when plugged in using usb.  However,
> when using usb:
> 
> o   horizontal mouse movement is interpreted as vertical movement 
> o   vertical mouse movement is ignored 
> o   strange things happen with mouse button presses (I didn't bother
>     working with this configuration long enough to figure out the
>     details).
> 
> This occurs under both x and gpm, which is mild evidence that it's
> not a user space problem.
> 
> It might also be worth noting that some of the extra keys on the keyboard
> do odd mouse-like things (like move the mouse's pointer horizontally
> a short distance) when it's a usb keyboard.  However, these keys work
> reasonably normally (or, in two cases**, generate entries in syslog)
> when it's plugged in as a ps/2 keyboard.
> 
> My guess is that the respective usb drivers haven't taken into account
> that both a keyboard and a mouse might appear on the same physical
> connection.  [But I'm still coming up to speed, and haven't yet figured
> out how to confirm/disprove that guess.]

They do take that into account. It's just that the descriptors are maybe
too complex. Could you possibly enable DEBUG in hid-core.c and send me
the output?

> -- 
> Raul Miller
> moth@magenta.com
> 
> 
> * one mouse button is ignored, however it is so awkwardly placed that I
> doubt anyone would want to use it.
> 
> 
> ** the syslog entries from the unsupported keys:
> 
> Dec 21 15:28:07 localhost kernel: atkbd.c: Unknown key pressed (translated set 2, code 0x11d, data 0x11, on isa0060/serio0).
> Dec 21 15:28:07 localhost kernel: atkbd.c: Unknown key released (translated set
> 2, code 0x11d, data 0x91, on isa0060/serio0).
> Dec 21 15:28:10 localhost kernel: atkbd.c: Unknown key pressed (translated set 2, code 0x12c, data 0x14, on isa0060/serio0).
> Dec 21 15:28:10 localhost kernel: atkbd.c: Unknown key released (translated set
> 2, code 0x12c, data 0x94, on isa0060/serio0).
> 
> Perhaps it's also worth noting that most of the other extra keys send two
> byte sequences when pressed (as reported by showkey -s), and showkey -k
> seems to be reporting the extra information as extra key releases, I think
> I've seen something similar on other keyboards, but I don't have one of
> those handy to test on).  If anyone cares, I can document this for them.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2003-12-21 21:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-21 20:43 problem with usb duo mouse and keyboard Raul Miller
2003-12-21 21:39 ` Vojtech Pavlik [this message]
2003-12-21 22:03   ` Raul Miller
     [not found]     ` <20031221223443.GA15744@ucw.cz>
     [not found]       ` <20031221175121.E28449@links.magenta.com>
     [not found]         ` <20031221230042.GA15960@ucw.cz>
2003-12-21 23:27           ` user " Raul Miller
2003-12-22  0:10             ` Vojtech Pavlik

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=20031221213950.GA14664@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=moth@magenta.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