* [Bluez-users] problem switching via hid2hci
@ 2004-12-28 8:08 Michal Semler
2004-12-29 10:23 ` Marcel Holtmann
0 siblings, 1 reply; 2+ messages in thread
From: Michal Semler @ 2004-12-28 8:08 UTC (permalink / raw)
To: bluez-users
Hi Marcel,
when I call hid2hci I get:
# hid2hci
Switching device 0a12:1000 to HCI mode failed (Protocol error)
notas:/home/cijoml# hciconfig
hci0: Type: USB
BD Address: 00:0D:88:8E:AB:2F ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:107 acl:0 sco:0 events:14 errors:0
TX bytes:300 acl:0 sco:0 commands:13 errors:0
notas:/home/cijoml# hciconfig hci0 revision
hci0: Type: USB
BD Address: 00:0D:88:8E:AB:2F ACL MTU: 192:8 SCO MTU: 64:8
HCI 18.2
Chip version: BlueCore02-External
Max key size: 128 bit
SCO mapping: HCI
And in dmesg is:
usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd hid2hci rqt 64 rq 0 len 0 ret -71
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: input irq status -84 received
usb 3-1: USB disconnect, address 3
drivers/usb/input/hid-core.c: input irq status -84 received
drivers/usb/input/hid-core.c: can't resubmit intr, 0000:00:1d.2-1/input1,
status -19
usb 3-1: new full speed USB device using uhci_hcd and address 4
Bluetooth: HCI USB driver ver 2.7
usbcore: registered new driver hci_usb
Thanks for fixing these stupid messages :)
kernel 2.6.10 without -mh patch
Michal
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Bluez-users] problem switching via hid2hci
2004-12-28 8:08 [Bluez-users] problem switching via hid2hci Michal Semler
@ 2004-12-29 10:23 ` Marcel Holtmann
0 siblings, 0 replies; 2+ messages in thread
From: Marcel Holtmann @ 2004-12-29 10:23 UTC (permalink / raw)
To: bluez-users
Hi Michal,
> when I call hid2hci I get:
> # hid2hci
> Switching device 0a12:1000 to HCI mode failed (Protocol error)
this error happens, but you can ignore it. It is a problem somewhere in
the USB subsystem when you reset the dongle.
> notas:/home/cijoml# hciconfig
> hci0: Type: USB
> BD Address: 00:0D:88:8E:AB:2F ACL MTU: 192:8 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN
> RX bytes:107 acl:0 sco:0 events:14 errors:0
> TX bytes:300 acl:0 sco:0 commands:13 errors:0
>
> notas:/home/cijoml# hciconfig hci0 revision
> hci0: Type: USB
> BD Address: 00:0D:88:8E:AB:2F ACL MTU: 192:8 SCO MTU: 64:8
> HCI 18.2
> Chip version: BlueCore02-External
> Max key size: 128 bit
> SCO mapping: HCI
>
> And in dmesg is:
> usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd hid2hci rqt 64 rq 0 len 0 ret -71
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: input irq status -84 received
> usb 3-1: USB disconnect, address 3
> drivers/usb/input/hid-core.c: input irq status -84 received
> drivers/usb/input/hid-core.c: can't resubmit intr, 0000:00:1d.2-1/input1,
> status -19
> usb 3-1: new full speed USB device using uhci_hcd and address 4
> Bluetooth: HCI USB driver ver 2.7
> usbcore: registered new driver hci_usb
>
> Thanks for fixing these stupid messages :)
This is the wrong mailing list for these error message. Ask the USB
guys.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-12-29 10:23 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-12-28 8:08 [Bluez-users] problem switching via hid2hci Michal Semler
2004-12-29 10:23 ` Marcel Holtmann
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox