Can't init device hci0: Connection timed out (110)
Hello again. I've finally managed to get the device (my 3Com 3CRWB6096 Version 2.0 PCMCIA Card) to show up in hciconfig (I had the wrong firmware).
Dbus is running, all the bluetooth services are running. But I get the following...
# hciconfig
hci0: Type: PCCARD
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN INIT RUNNING
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:4 acl:0 sco:0 commands:1 errors:0# hciconfig hci0 up
Can't init device hci0: Connection timed out (110)
# hciconfig
hci0: Type: PCCARD
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:4 acl:0 sco:0 commands:2 errors:0Is there some way I can manually probe the card for it's address to find out if it's bluez or the driver?
Shouldn't it have an address even when it's down?
Please, any other suggestions very much appreciated. Thanks in advance
Simon
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
get more errors
first kill hcid process
run:
$ hcid -n -f /dirof/hcid.conf
and it get more errors
Quoted 39 lines · On Wed, 22 Nov 2006 17:24:21 +0000 Simon Williams…
Hello again. I've finally managed to get the device (my 3Com 3CRWB6096 Version 2.0 PCMCIA Card) to show up in hciconfig (I had the wrong firmware).
Dbus is running, all the bluetooth services are running. But I get the following...
# hciconfig hci0: Type: PCCARD BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN INIT RUNNING RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:4 acl:0 sco:0 commands:1 errors:0# hciconfig hci0 up Can't init device hci0: Connection timed out (110) # hciconfig hci0: Type: PCCARD BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:4 acl:0 sco:0 commands:2 errors:0Is there some way I can manually probe the card for it's address to find out if it's bluez or the driver?
Shouldn't it have an address even when it's down?Please, any other suggestions very much appreciated. Thanks in advance
Simon-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Signature · 9 lines
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bluez-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bluez-users
Quoted 9 lines · Andres Vargas - zodman
get more errors
first kill hcid process
run:
$ hcid -n -f /dirof/hcid.confand it get more errors
Not really. The error appears to be with the driver, and not hcid. All that I get from the above is this, which I already had in my syslogs.
hcid[20521]: Bluetooth HCI daemon
hcid[20521]: Register path:/org/bluez fallback:1 hcid[20521]: HCI dev 0 registered
hcid[20521]: Register path:/org/bluez/hci0 fallback:0 hcid[20522]: Can't init device hci0: Connection timed out (110)
Quoted 33 lines
Quoted 30 lines · On Wed, 22 Nov 2006 17:24:21 +0000 Simon Williams…
Hello again. I've finally managed to get the device (my 3Com 3CRWB6096 Version 2.0 PCMCIA Card) to show up in hciconfig (I had the wrong firmware).
Dbus is running, all the bluetooth services are running. But I get the following...
# hciconfig hci0: Type: PCCARD BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN INIT RUNNING RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:4 acl:0 sco:0 commands:1 errors:0# hciconfig hci0 up Can't init device hci0: Connection timed out (110) # hciconfig hci0: Type: PCCARD BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:4 acl:0 sco:0 commands:2 errors:0Is there some way I can manually probe the card for it's address to find out if it's bluez or the driver?
Shouldn't it have an address even when it's down?Please, any other suggestions very much appreciated. Thanks in advance
Simon
Quoted 11 lines
Quoted 9 lines
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users