Ubuntu
bluez package

bluez-utils does not put logitech mx 5500 bluetooth into hci mode

Bug #272352 reported by Tom Rothamel on 2008-09-20

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	bluez (Ubuntu)	Fix Released	Low	Mario Limonciello
Nominated for Karmic by Kzin

Bug Description

Binary package hint: bluez-utils

hid2hci doesn't know about the reciever that comes with the Logitech MX 5500 keyboard/mouse combo. This is because the usb id is not in the whitelist. The attached patch fixes it.

Revision history for this message

Tom Rothamel (tom-ubuntu-onegeek) wrote on 2008-09-20:

5500.patch Edit (625 bytes, text/plain)

Revision history for this message

Qiuli (ivyharry) wrote on 2008-09-21:

I too have MX 5500 with MX Revolution mouse
I think the problem is more lie the USB id is not in the usd.ids files even after I have upgraded it by using update-usbids

lsusb shows:

Bus 002 Device 011: ID 046d:c71c Logitech, Inc.
Bus 002 Device 010: ID 046d:c71b Logitech, Inc.
Bus 002 Device 009: ID 046d:0b06 Logitech, Inc.

I believe these are for usb dongle comes from the combo box.

However, inside the updated usb.ids file, the section just missed c71c, c71b and 0b06:

        0a04 V20 portable speakers (USB powered)
        0b02 BT Mini-Receiver (HID proxy mode)
        8801 Video Camera
        b305 BT Mini-Receiver
        bfe4 Premium Optical Wheel Mouse

        c715 Bluetooth wireless hub
        c71a Bluetooth wireless hub
        c71d Bluetooth wireless hub
        c720 Bluetooth wireless hub

so, would those ids be added in the next release?

or we have to compile our own list into the module?

thanks

Mario Limonciello (superm1) on 2008-10-10

Changed in bluez:
importance:	Undecided → Low
status:	New → Confirmed

Revision history for this message

Mario Limonciello (superm1) wrote on 2008-10-22:

I've committed a fix to the bluez bzr tree and submitted this upstream. Thanks.

Changed in bluez:
assignee:	nobody → superm1
status:	Confirmed → Fix Committed

Revision history for this message

Launchpad Janitor (janitor) wrote on 2008-10-24:

This bug was fixed in the package bluez - 4.12-0ubuntu4

---------------
bluez (4.12-0ubuntu4) intrepid; urgency=low

  * Add hid2hci.patch to enable hid2hci to be ran after
    suspending a machine. (LP: #268877)
  * debian/rules:
    - Install new script from above patch.
  * Add logitech_5500_ids.patch for enabling hid2hci on
    more logitech devices. (LP: #272352)

-- Mario Limonciello <email address hidden> Wed, 22 Oct 2008 16:01:59 -0500

Changed in bluez:
status:	Fix Committed → Fix Released

Revision history for this message

Andras Kovacs (andras-csevego) wrote on 2009-10-05:

it doen't work on karmic beta. The donlge is still in hid mode, it worked on jaunty.

Revision history for this message

Kzin (wmkzin) wrote on 2009-10-09:

Confirmed #5 by Andras Kovacs
I believe this may have a duplicate of 318465 .
However will add to both for now as this one has an assignee...

$ lsusb
Bus 002 Device 009: ID 046d:c70a Logitech, Inc. MX5000 Cordless Desktop
Bus 002 Device 008: ID 046d:c70e Logitech, Inc. MX1000 Bluetooth Laser Mouse
Bus 002 Device 007: ID 046d:0b02 Logitech, Inc. BT Mini-Receiver (HID proxy mode)
Bus 002 Device 002: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Let me know what logs you will need.

Revision history for this message

Kzin (wmkzin) wrote on 2009-10-09:

Ok installed latest kernel and now it works according to workaround #5 in 318465!
kzin@IT-001:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 007: ID 046d:c709 Logitech, Inc. BT Mini-Receiver (HCI mode)
Bus 002 Device 006: ID 046d:0b02 Logitech, Inc. BT Mini-Receiver (HID proxy mode)
Bus 002 Device 002: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Sorry for the spamposting