Logitech diNovo hub not recognized

Hello,

I am having trouble getting the hub from my Logitech diNovo Cordless Desktop Keyboard & Mouse recognized by the Bluetooth system. (The system is able to communicate flawlessly with a Palm Tungsten E2, over a D-Link DBT-120 USB Bluetooth dongle.) I have looked at earlier posts on this list dealing with this device, but all previous posters were able to get this hub recognized as a Bluetooth device, as far as I have been able to tell. The keyboard and mouse work fine in HID mode.

I am running a Fedora-modified 2.6.13 kernel. My understanding is that recent kernels should have sufficient Bluetooth support, so that a Bluez patch is not necessary. (Anyway, I tried patch-2.6.13-mh1, and the resulting kernel didn't work any better.) I am using the current Fedora Core 4 version of bluez-utils, bluez-utils-2.15-7.

Here is what the system log shows when the device is insterted:

Oct 11 21:20:03 georg kernel: usb 2-4.2: new low speed USB device using ohci_hcd and address 39
Oct 11 21:20:03 georg kernel: input: USB HID v1.10 Keyboard [Logitech USB Receiver] on usb-0000:00:02.0-4.2
Oct 11 21:20:03 georg hal.hotplug[32675]: DEVPATH is not set (subsystem input)
Oct 11 21:20:03 georg kernel: input,hiddev96: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:02.0-4.2
Oct 11 21:20:04 georg hal.hotplug[32706]: DEVPATH is not set (subsystem input)

(From what I was able to find from Google searches, the DEVPATH issue shouldn't be significant.)

Here are what some commands return:

  # /usr/sbin/hid2hci
  No devices in HCI mode found
  # /usr/sbin/hid2hci -1
  No devices in HID mode found
  # /usr/sbin/hciconfig -a
  [blank]
  #

Inserting the D-Link DBT-120, while keeping the Logitech device plugged in, produces:

Oct 11 21:34:58 georg kernel: usb 2-6: new full speed USB device using ohci_hcd and address 40
Oct 11 21:34:58 georg hcid[11501]: HCI dev 0 registered
Oct 11 21:34:58 georg hcid[11501]: HCI dev 0 up
Oct 11 21:34:58 georg hcid[11501]: Starting security manager 0

# /usr/sbin/hciconfig -a
hci0:   Type: USB
        BD Address: 00:13:46:4D:6F:14 ACL MTU: 192:8 SCO MTU: 64:8
        UP RUNNING PSCAN ISCAN AUTH ENCRYPT
        RX bytes:101 acl:0 sco:0 events:13 errors:0
        TX bytes:296 acl:0 sco:0 commands:12 errors:0
        Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'georg-0'
        Class: 0x000100
        Service Classes: Unspecified
        Device Class: Computer, Uncategorized
        HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP 
Subver: 0x20d
        Manufacturer: Cambridge Silicon Radio (10)

#

I am at a loss as to what could be wrong, especially since I read a post for I believe the same device saying that it is supported by bluez.

Many thanks in advance for any help,

Alex

-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Hi Alex,

the latest version is bluez-utils-2.21 and you might wanna try it.

What does /proc/bus/usb/devices shows you?

Regards

Marcel

-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Hi Marcel,

Thanks much for your response. I compiled and installed bluez-libs-2.21 and bluez-utils-2.21, removing the corresponding Fedora binary packages. Unfortunately, hid2hci and hciconfig -a produced exactly the same results.

Here is the output of /proc/bus/usb/devices, with only the Logitech receiver inserted:

T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12  MxCh=10
B:  Alloc= 42/900 us ( 5%), #Int=  4, #Iso=  0
D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0000 ProdID=0000 Rev= 2.06
S:  Manufacturer=Linux 2.6.13-1.1526_av0 ohci_hcd
S:  Product=OHCI Host Controller
S:  SerialNumber=0000:00:02.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

T:  Bus=02 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#=  2 Spd=12  MxCh= 2
D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0451 ProdID=2036 Rev= 1.01
S:  Product=General Purpose USB Hub
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=255ms

T:  Bus=02 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#=  4 Spd=1.5 MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=046d ProdID=abd0 Rev=41.02
S:  Manufacturer=Logitech
S:  Product=Desktop USB stand
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 98mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid
E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=10ms

T:  Bus=02 Lev=02 Prnt=02 Port=01 Cnt=02 Dev#=  3 Spd=1.5 MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=046d ProdID=c50c Rev=22.40
S:  Manufacturer=Logitech
S:  Product=USB Receiver
C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr= 98mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=usbhid
E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=10ms
I:  If#= 1 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid
E:  Ad=82(I) Atr=03(Int.) MxPS=   8 Ivl=10ms

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh=10
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS= 8 #Cfgs=  1
P:  Vendor=0000 ProdID=0000 Rev= 2.06
S:  Manufacturer=Linux 2.6.13-1.1526_av0 ehci_hcd
S:  Product=EHCI Host Controller
S:  SerialNumber=0000:00:02.1
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=256ms

(When I saw "Desktop USB stand" in the list above, I removed it and inserted the receiver directly into a USB port, but that didn't change anything.)

I am mystified.

Thanks and regards,

Alex

-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Hi Alex,

try the attached patch. Hopefully they haven't changed the protocol.

Regards

Marcel

Index: hid2hci.c
===================================================================
RCS file: /cvsroot/bluez/utils/tools/hid2hci.c,v
retrieving revision 1.6

diff -u -r1.6 hid2hci.c
@@ -226,6 +226,7 @@
 	{ HCI, 0x046d, 0xc703, switch_logitech },
 	{ HCI, 0x046d, 0xc704, switch_logitech },
 	{ HCI, 0x046d, 0xc705, switch_logitech },
+	{ HCI, 0x046d, 0xc50c, switch_logitech },
 	{ -1 }
 };
 

Hi Marcel,

Thanks for the patch. Now hid2hci produces

Switching device 046d:c50c to HCI mode was successful

Unfortunately however, "hciconfig -a" still produces a blank line. Also, I can type "hid2hci" any number of times, and it always produces the same response, which makes me think it isn't doing much of anything. Furthermore, if I give the command "hid2hci" when hcid and sdpd are stopped, I can continue to use the diNovo keyboard and mouse undisturbed, which suggests that the receiver never really leaves hid mode.

I don't know if they've changed the protocol, or if it's simply that other patches along the lines of this one are required.

Regards,

Alex

-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Hi Alex,

is this the new version of the diNovo? So maybe they changed something and the protocol is different. Someone has to reverse engineer it or send me the diNovo desktop.

Regards

Marcel

-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Hi Marcel,

I guess this is the new version. A description of it at the place I bought it is here:

http://www.buy.com/retail/product.asp?sku=10389803&loc=101&sp=1

The manufacturer's part number however is 867431-0100, which doesn't match the one given in the above page.

The good news I suppose, for any potential contributors, is that it lists for only $129.99, whereas my impression is that the "old" diNovo desktop listed for about twice that, which is a bit exorbitant, I think.

Regards,

Alex

-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Hi Alex,

this is not the Bluetooth version of the diNovo.

Regards

Marcel

-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Hi Marcel,

Thank you for clearing up my misapprehension. I had been assuming that any mouse or keyboard that uses radio would be using Bluetooth. (This led me to be mystified over why the cordless Logitech keyboard & mouse I bought was so much cheaper than the other models.) What I had not been taking into account is that Logitech is a business: excluding Bluetooth, while it does not lead to significantly lower production costs, does allow Logitech to establish a lower "price point". I should have expected this kind of behavior from them, given their refusal to release their "proprietary" information to Linux developers.

I'm sorry to have wasted your time. Now I'll reinsert my D-Link DBT-120 (which, together with my wireless keyboard/mouse, is still substantially cheaper than the Bluetooth version). :)

Best regards,

Alex

-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users