Logitech diNovo hub not recognized?
Hi,
I've bought a Logitech diNovo set some time ago which I have used in non-bluetooth mode so far (because I do not have any other bluetooth devices anyway, and the procedure to switch into bluetooth mode seemed to complicated to me to be worth the time). But now that I've read that with the latest tools and kernel patches and the use of the HIDP protocol the process should have become quite the easy task, I decided to give it a try. Well, so I downloaded the 2.6.7 kernel, applied the mh1 patch (and additionally the ck5 patch, if that matters) and configured it along with the bluetooth options. Then I rebooted with the new kernel and executed the bluetooth start script, which should have been about all to do, at least so far that I've read in this mailing list here. But, well, nothing at all happens... The hub does not switch to Bluetooth mode, and any attempt to use hcitool to search for bluetooth devices just reports me a "device not found" error. I've since tried to compile the bluetooth parts both as modules and as built-in and compiled virtually everything in there, but so far no success. I can still use this 'hid2hci' tool, which obviously switches the hub to HCI mode, but that results in my keyboard and mouse not working anymore, and I didn't succeed in reconnecting them.
So my question is, am I missing something or am I doing it completely wrong? Thanks for any help you can offer.
Best regards
Holger Frydrych
P.S.: I did not attach any output or configuration file to this mail since I am not really sure what might be helpful. If you need anything, just tell me, I'll provide any such feedback that I can.
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Marcel Holtmann
maintainerHi Holger,
Quoted 7 lines
I've bought a Logitech diNovo set some time ago which I have used in non-bluetooth mode so far (because I do not have any other bluetooth devices anyway, and the procedure to switch into bluetooth mode seemed to complicated to me to be worth the time). But now that I've read that with the latest tools and kernel patches and the use of the HIDP protocol the process should have become quite the easy task, I decided to give it a try.
Quoted 8 lines
Well, so I downloaded the 2.6.7 kernel, applied the mh1 patch (and additionally the ck5 patch, if that matters) and configured it along with the bluetooth options. Then I rebooted with the new kernel and executed the bluetooth start script, which should have been about all to do, at least so far that I've read in this mailing list here. But, well, nothing at all happens... The hub does not switch to Bluetooth mode, and any attempt to use hcitool to search for bluetooth devices just reports me a "device not found" error.
use 2.6.7-mh2 and bluez-libs-2.8 and bluez-utils-2.8 to get this really working. To use hid2hci you must enable CONFIG_USB_HIDDEV in your kernel config and it is a good idea to use udev for creation of the hiddev device nodes.
Quoted 5 lines
I've since tried to compile the bluetooth parts both as modules and as built-in and compiled virtually everything in there, but so far no success. I can still use this 'hid2hci' tool, which obviously switches the hub to HCI mode, but that results in my keyboard and mouse not working anymore, and I didn't succeed in reconnecting them.
Show us the content of /proc/bus/usb/devices.
Regards
Marcel
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-users mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
A message that is not in the archive (sent off-list or not yet received): [email protected]
Marcel Holtmann
maintainerHi Holger,
Quoted 11 lines
Quoted 4 lines
use 2.6.7-mh2 and bluez-libs-2.8 and bluez-utils-2.8 to get this really working. To use hid2hci you must enable
CONFIG_USB_HIDDEVin your kernel config and it is a good idea to use udev for creation of the hiddev device nodes.well, I had 2.8 libs and tools already installed and HIDDEV enabled. So I just tried the mh2 patch, but nothing's changed so far. Maybe the hub even is in bluetooth mode because the MediaPad automatically connected during boot (which it has never done before), but apart from that, hcitool still complains about non-existing devices, so this can't be right, I guess.
did hid2hci showed any error messages. Is there anything in the logfiles or visible through dmesg. What kind of machine do you use? Do you have the hiddevX devices nodes?
Quoted 11 lines
T: Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 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=c704 Rev=24.04 S: Manufacturer=Logitech S: Product=USB Receiver S: SerialNumber=0DC4DF 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
This is fine. We actually support this hub.
Regards
Marcel
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-users mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi,
Quoted 3 lines · Marcel Holtmann
did hid2hci showed any error messages. Is there anything in the logfiles or visible through dmesg. What kind of machine do you use? Do you have the hiddevX devices nodes?
hid2hci tells this:
Switching device 046d:c704 to HCI mode was successful.
But this immediately results in my keyboard, mouse and MediaPad not working anymore, or rather they get disconnected, I suppose. So I press the connect button on the keyboard and then the one on the hub, just the hub does not react (does not start blinking) and so nothing happens. Ok, so I've got my old PS/2 keyboard and attached this one additionally so I can keep typing. I then tried 'hcitool dev' which now (after hid2hci) shows me the logitech hub as hci0. I then typed 'hcitool scan', it does not complain about missing devices, the hub starts blinking and it finally lists all my diNovo devices. So far, so good. Then I try to manually connect one of my devices (doesn't matter, which) via 'hcitool cc [address]', and the hub again starts blinking, but all I get in result is: 'Can't create connection: Input/Output error'. 'hidd --search' returns a similar error: 'Can't create HID control channel: Invalid exchange'...
hiddev device nodes are available at /dev/usb/hid, this is where the devfs filesystem put them into. The log files do not contain anything of interest (unless I missed it), they just state that hcid and hidd have started. dmesg does not state any error with Bluetooth, but I'll attach anything specific to bluetooth and USb anyway, maybe you can read something out of it.
------------------------------ dmesg ---------------------------------
------USB Universal Host Controller Interface driver v2.2uhci_hcd 0000:00:11.2: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller uhci_hcd 0000:00:11.2: irq 4, io base 0000e000uhci_hcd 0000:00:11.2: new USB bus registered, assigned bus number 1 hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detecteduhci_hcd 0000:00:11.3: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#2) uhci_hcd 0000:00:11.3: irq 4, io base 0000e400uhci_hcd 0000:00:11.3: new USB bus registered, assigned bus number 2 hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detecteduhci_hcd 0000:00:11.4: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#3) uhci_hcd 0000:00:11.4: irq 4, io base 0000e800uhci_hcd 0000:00:11.4: new USB bus registered, assigned bus number 3 hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
usbcore: registered new driver usblpdrivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
usbcore: registered new driver hiddev
usbcore: registered new driver usbhiddrivers/usb/input/hid-core.c: v2.0:USB HID core driver
[...]
Bluetooth: HCI USB driver ver 2.6
usbcore: registered new driver hci_usb
Bluetooth: VHCI driver ver 1.1
Bluetooth: Broadcom Blutonium firmware driver ver 1.0
usbcore: registered new driver bcm203x
[...]
Bluetooth: L2CAP ver 2.2
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.3
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM ver 1.3
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: BNEP (Ethernet Emulation) ver 1.0
Bluetooth: HIDP (Human Interface Emulation) ver 1.0-mh1
usb 1-1: new full speed USB device using address 2
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 2 ports detected
[...]
usb 1-1.1: new low speed USB device using address 3
input: USB HID v1.10 Keyboard [Logitech USB Receiver] on usb-0000:00:11.2-1.1 input,hiddev96: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:11.2-1.1 [...]
usb 1-1.2: new full speed USB device using address 4
usb 1-2: new low speed USB device using address 5
input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:11.2-2 ---------------------- dmesg ----------------------------------
Interestingly, the HIDP protocol still identifies as mh1, though I meanwhile did supply the mh2 patch. So is this correct, or should I investigate more here?
Quoted 1 line
This is fine. We actually support this hub.
Good. That leaves some hope, at least :)
Best regards
Holger
Marcel Holtmann
maintainerHi Holger,
Quoted 5 lines
Quoted 3 lines
did hid2hci showed any error messages. Is there anything in the logfiles or visible through dmesg. What kind of machine do you use? Do you have the hiddevX devices nodes?
hid2hci tells this:
Switching device 046d:c704 to HCI mode was successful.
this sound good.
Quoted 6 lines
But this immediately results in my keyboard, mouse and MediaPad not working anymore, or rather they get disconnected, I suppose. So I press the connect button on the keyboard and then the one on the hub, just the hub does not react (does not start blinking) and so nothing happens. Ok, so I've got my old PS/2 keyboard and attached this one additionally so I can keep typing. I then tried 'hcitool dev' which now (after hid2hci)
Quoted 8 lines
shows me the logitech hub as hci0. I then typed 'hcitool scan', it does not complain about missing devices, the hub starts blinking and it finally lists all my diNovo devices. So far, so good. Then I try to manually connect one of my devices (doesn't matter, which) via 'hcitool cc [address]', and the hub again starts blinking, but all I get in result is: 'Can't create connection: Input/Output error'. 'hidd --search' returns a similar error: 'Can't create HID control channel:
Invalid exchange'...
Don't use "hcitool cc ...", because this is only for development. What does "hciconfig -a" show?
Run "hcidump -x" as root while connecting with hidd.
Quoted 3 lines
Interestingly, the HIDP protocol still identifies as mh1, though I meanwhile did supply the mh2 patch. So is this correct, or should I investigate more here?
These are two different version numbers. What "modinfo hidp" shows means that you use the HIDP version 1.0 with an additional patch for the report protocol mode. I only put -mh1 after it to identify it, because the HIDP with boot protocol mode is submitted for kernel inclusion.
Regards
Marcel
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-users mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi,
Quoted 2 lines · Marcel Holtmann
Don't use "hcitool cc ...", because this is only for development. What does "hciconfig -a" show?
This is the output:
hci0: Type: USB
BD Address: 00:07:61:0D:C4:DF ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN AUTH ENCRYPT
RX bytes:19699 acl:854 sco:0 events:334 errors:0
TX bytes:3722 acl:122 sco:0 commands:64 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: 'BlueZ (0)'
Class: 0x000100
Service Classes: Unspecified
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x34e LMP Ver: 1.1 (0x1) LMP Subver: 0x34e
Manufacturer: Cambridge Silicon Radio (10)
Well, this reminded me of the fact that I had auth and encrypt options in the hcid config file enabled because I considered that to be good things. Well, but I disabled them, and guess what? My diNovo hardware can now connect to the hub. So far, so good, I guess, though I still thought that hid2hci was not necessary anymore? Well ok, it does work so far, but only without auth and encrypt. Is there anything special I must do to get it working with both?
Anyway, thanks for your help so far!
Best regards
Holger
Marcel Holtmann
maintainerHi Holger,
Quoted 22 lines
Quoted 2 lines
Don't use "hcitool cc ...", because this is only for development. What does "hciconfig -a" show?
This is the output:
hci0: Type: USB
BD Address: 00:07:61:0D:C4:DF ACL MTU: 192:8 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN AUTH ENCRYPT RX bytes:19699 acl:854 sco:0 events:334 errors:0 TX bytes:3722 acl:122 sco:0 commands:64 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: 'BlueZ (0)' Class: 0x000100 Service Classes: Unspecified Device Class: Computer, Uncategorized HCI Ver: 1.1 (0x1) HCI Rev: 0x34e LMP Ver: 1.1 (0x1) LMPSubver:
0x34e
Manufacturer: Cambridge Silicon Radio (10)
Quoted 7 lines
Well, this reminded me of the fact that I had auth and encrypt options in the hcid config file enabled because I considered that to be good things. Well, but I disabled them, and guess what? My diNovo hardware can now connect to the hub. So far, so good, I guess, though I still thought that hid2hci was not necessary anymore?
Well ok, it does work so far, but only without auth and encrypt. Is there anything special I must do to get it working with both?
actually I thought that you enabled auth and encrypt ;)
Setting auth and encrypt in hcid.conf or with hciconfig sets your device into security mode 3 and this is not what you want. The basic security mode should be 2 which means service level security. I explained this some times, so check the mailing list archive or the Bluetooth spec. for more details.
Regards
Marcel
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-users mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi,
Quoted 7 lines
actually I thought that you enabled auth and encrypt ;)
Setting auth and encrypt in hcid.conf or with hciconfig sets your device into security mode 3 and this is not what you want. The basic security mode should be 2 which means service level security. I explained this some times, so check the mailing list archive or the Bluetooth spec. for more details.
So it really was my fault then, eh? Well, thanks for your time then, and I'll go read the archives :)
Just two last questions for clarification:
1. What's the status on hid2hci now? Is it still needed or should it be obsolete by now? Because I've read in this mailing list that others do not need it anymore, but I can't get it to work without, as described.
2. The usual procedure (as I understand, I'm not much into that bluetooth stuff, as may be obvious ;) ) to connect a new bluetooth device would be to press its connect button and then the one on the hub, right? Well, this does not work, simply because the hub (after hid2hci) does no longer react to a press on 'Connect', so I have to manually search for new devices via hidd. The diNovo devices seem to automatically reconnect when I use them, though, so if that's the way it's meant to be currently, then this is ok, I only rarely connect an additional device (a cell phone). Just wanted to know.
Ok, so far from my end, I hope I did not pose questions that you already had answered more or less recently :)
Best regards
Holger
Marcel Holtmann
maintainerHi Holger,
Quoted 3 lines
1. What's the status on hid2hci now? Is it still needed or should it be obsolete by now? Because I've read in this mailing list that others do not need it anymore, but I can't get it to work without, as described.
no. You will always need hid2hci to switch from HID mode into HCI mode, because after reboot the HID mode is default.
Quoted 9 lines
2. The usual procedure (as I understand, I'm not much into that bluetooth stuff, as may be obvious ;) ) to connect a new bluetooth device would be to press its connect button and then the one on the hub, right? Well, this does not work, simply because the hub (after hid2hci) does no longer react to a press on 'Connect', so I have to manually search for new devices via hidd. The diNovo devices seem to automatically reconnect when I use them, though, so if that's the way it's meant to be currently, then this is ok, I only rarely connect an additional device (a cell phone). Just wanted to know.
For your HID devices you only have to connect them once using "hidd -c". After that they will reconnect if you use them. To make this work without any trouble you must run "hidd --server" at boot time and before you switch into HCI mode with hid2hci.
Regards
Marcel
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-users mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users