Greetings,
If you have a mouse that exhibits some of the following symptoms, could
you test the patch found within
http://www.freebsd.org/cgi/query-pr.cgi?pr=106565 and provide feedback?
* The mouse wheel does not work.
* In some cases, when you move the mouse cursor and/or presses a
button, the mouse behaves as if its wheel were turned (and
consequently moves the scrollbar of the current window, for example).
* Rarely, the mouse is recognized but does not work at all, except
when you press a certain combination of buttons (usually the left
button only) and the cursor moves erratically and spurious button
events are generated (i.e. the mouse behaves as if some other
buttons are pressed).
* You cannot bring a window to the top by clicking in it; you have
to click its window decoration (such as the title bar or a
border). At least this happened to me when using metacity, the
default window manager of GNOME.
In a nutshell, the problem is that the mouse erroneously defaults not to
the standard report protocol, but to the boot protocol (used by
motherboards and embedded systems for legacy emulation) when it is
attached and configured. This presumably happened because developers of
the problematic model of mouse had a broken motherboard that did not
specifically configure the mouse into the boot protocol, which they had
to work around.
The patch solves the problem by forcing ums(4) to reset the mouse back
into the report protocol so that it reports its full status that
includes mouse wheels and more than three buttons. This aligns to the
USB 2.0 specification, which recommends resetting the protocol although
the mouse should already default to the report protocol.
Cheers,
Eugene
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to [EMAIL PROTECTED]
