Bug 62323 - [kbd] Logitech Cordless MX Duo Keyboard/Mouse combination does not work correctly
Summary: [kbd] Logitech Cordless MX Duo Keyboard/Mouse combination does not work corre...
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-04 00:00 UTC by Will Saxon
Modified: 2008-02-11 21:12 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Will Saxon 2004-02-04 00:00:36 UTC
Logitech makes a cordless keyboard/mouse combination called the Cordless
MX Duo. This consists of a wireless keyboard and their MX700 cordless
mouse. It uses 1 USB connection or can be used as 2 PS/2 devices using
an included adapter and pigtail.

When connected as a USB device, the keyboard and mouse are detected
properly however the mouse will not respond with moused and cat
/dev/ums0 does not show any output. Configuring XFree86 to use the
mouse directly also does not work. The keyboard will work but will
occasionally repeat previously pressed keys. 

When connected as 2 PS/2 devices, the keyboard is detected properly
and works correctly in all situations. However, the mouse is detected
as a 'Generic PS/2 device' and the wheel is not available when using
moused or directly through XFree86.

I also own a standalone MX700 cordless mouse which is detected correctly
and works correctly in USB mode using FreeBSD 4.9 and 5.2

This device does work correctly in Linux.

How-To-Repeat: Plug the device in as either USB or PS2 and attempt to configure using
moused, etc.
Comment 1 dr 2004-02-13 14:30:47 UTC
Hello,

I can confirm that I'm having exactly the same problem here. I've just wa=
nted to add,
that the mouse (attached to PS/2) and the wheel does work properly under =
OpenBSD-3.4
(the mouse is detected as a Logitech Mouse, not a Generic PS/2 Mouse). Ho=
wever, I
haven't tested USB functionality under OpenBSD yet.

With kind regards / Mit freundlichen Gr=FCssen

Aurel Bodenmann

--=20
Aurel Bodenmann, WWW: http://www.dr.sweety.li
E-Mail: mailto:dr@sweety.li
Mobile: ++41 (0)76 526 94 17 Home: ++41 (0)61 711 GEEK
Always look on the bright side of life!
Comment 2 Anish Mistry 2004-08-18 05:14:16 UTC
=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

My patch in the following PR should fix this problem.
http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/63837

=2D --=20
Anish Mistry
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFBIte5xqA5ziudZT0RAqXWAJ4zqHSr0yOscB+P8ERKsdkCjbauuACePHeP
p7Ue5cHd+YXfaICdQDc/idw=3D
=3Di2Et
=2D----END PGP SIGNATURE-----
Comment 3 Thomas Pasch 2005-02-06 20:51:01 UTC
Hi,

got exactly the same problem on FreeBSD 5.3-RELEASE / AMD64.
This time it's a logitech usb optical mouse and keyboard combination.
Has the mentioned patch been incooperated in the 5.3 release???

Cheers,

Thomas
Comment 4 Volker 2008-02-11 17:57:09 UTC
PR usb/63837 contains patches and a deeper discussion for this
problem. I suggest to close this PR in favor of usb/63837.

Will: Do you see this problem on recent releases? Agree to close this PR?

If the problem has been solved, PR usb/63837 can also be closed.
Comment 5 saxonww 2008-02-11 18:12:50 UTC
62323 should be closed. I thought it was already closed. I think  
63837 may be overtaken by events - I think the combo usb device  
enumeration has been working in 6.x for a long time. I don't have the  
hardware referenced in 62323 anymore, so I am not able to verify myself.

Thanks for following up.

-Will

On Feb 11, 2008, at 12:57 EST, Volker wrote:

> PR usb/63837 contains patches and a deeper discussion for this
> problem. I suggest to close this PR in favor of usb/63837.
>
> Will: Do you see this problem on recent releases? Agree to close  
> this PR?
>
> If the problem has been solved, PR usb/63837 can also be closed.
Comment 6 Remko Lodder freebsd_committer freebsd_triage 2008-02-11 21:12:22 UTC
State Changed
From-To: open->closed

Volker reports: the submitter can no longer reproduce this, he believes 
this had been fixed a long time ago. Close the ticket.