From: Simon Williams <systemparadox@googlemail.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Can't init device hci0: Connection timed out (110)
Date: Thu, 23 Nov 2006 12:56:11 +0000 [thread overview]
Message-ID: <45659A6B.5050206@gmail.com> (raw)
In-Reply-To: <20061122232153.00cfe612@localhost.localdomain>
Andres Vargas - zodman wrote:
> get more errors
>
> first kill hcid process
>
> run:
>
> $ hcid -n -f /dirof/hcid.conf
>
> and 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)
> On Wed, 22 Nov 2006 17:24:21 +0000
> Simon Williams <systemparadox@googlemail.com> wrote:
>
>> 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:0
>>
>> Is 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
>> Bluez-users@lists.sourceforge.net
>> 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
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2006-11-23 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 17:24 [Bluez-users] Can't init device hci0: Connection timed out (110) Simon Williams
2006-11-23 7:21 ` Andres Vargas - zodman
2006-11-23 12:56 ` Simon Williams [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45659A6B.5050206@gmail.com \
--to=systemparadox@googlemail.com \
--cc=bluez-users@lists.sourceforge.net \
--cc=systemparadox@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox