* [Bluez-users] HCI Daemon Unable to get on D-Bus
@ 2007-08-20 16:08 John Sample
2007-08-20 16:11 ` umamahesh yelchuru venkata
2007-08-20 17:25 ` John Sample
0 siblings, 2 replies; 3+ messages in thread
From: John Sample @ 2007-08-20 16:08 UTC (permalink / raw)
To: bluez-users
[-- Attachment #1.1: Type: text/plain, Size: 964 bytes --]
I've been working on getting Bluez up an running on an embedded platform and
am having some problems getting hcid to run. I'm using the 2.6.23 kernel,
but I've also tested on an old 2.6.10 kernel and run into the same problem.
I start D-Bus using dbus-daemon-1 --system, and it starts ok without any
error messages. I then start hcid, but it immediately exits and I get the
following in my syslog:
hcid[1021]: Bluetooth HCI daemon
hcid[1021]: Can't connect to system message bus: Did not receive a reply.
Possible causes include: the remote application did not send a reply, the
message bus security policy blocked the reply, the reply timeout expired, or
the network connection was broken.
hcid[1021]: Unable to get on D-Bus
Do I need to modify bluetooth.conf or system.conf in any way to get the
security policy to allow the connection? I saw a similar post a while ago
on this same topic but I couldn't find a resolution anywhere.
Thanks,
--
John Sample
[-- Attachment #1.2: Type: text/html, Size: 1132 bytes --]
[-- Attachment #2: Type: text/plain, Size: 315 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Bluez-users] HCI Daemon Unable to get on D-Bus
2007-08-20 16:08 [Bluez-users] HCI Daemon Unable to get on D-Bus John Sample
@ 2007-08-20 16:11 ` umamahesh yelchuru venkata
2007-08-20 17:25 ` John Sample
1 sibling, 0 replies; 3+ messages in thread
From: umamahesh yelchuru venkata @ 2007-08-20 16:11 UTC (permalink / raw)
To: BlueZ users
[-- Attachment #1.1: Type: text/plain, Size: 1653 bytes --]
Hi Mr.John, Can i get the compilation procedure for bluez libs and utils
Regards
Umesh
On 8/20/07, John Sample <john.m.sample@gmail.com> wrote:
>
> I've been working on getting Bluez up an running on an embedded platform
> and am having some problems getting hcid to run. I'm using the 2.6.23kernel, but I've also tested on an old
> 2.6.10 kernel and run into the same problem. I start D-Bus using
> dbus-daemon-1 --system, and it starts ok without any error messages. I then
> start hcid, but it immediately exits and I get the following in my syslog:
>
> hcid[1021]: Bluetooth HCI daemon
> hcid[1021]: Can't connect to system message bus: Did not receive a reply.
> Possible causes include: the remote application did not send a reply, the
> message bus security policy blocked the reply, the reply timeout expired, or
> the network connection was broken.
> hcid[1021]: Unable to get on D-Bus
> Do I need to modify bluetooth.conf or system.conf in any way to get the
> security policy to allow the connection? I saw a similar post a while ago
> on this same topic but I couldn't find a resolution anywhere.
>
> Thanks,
>
> --
> John Sample
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
>
[-- Attachment #1.2: Type: text/html, Size: 2497 bytes --]
[-- Attachment #2: Type: text/plain, Size: 315 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bluez-users] HCI Daemon Unable to get on D-Bus
2007-08-20 16:08 [Bluez-users] HCI Daemon Unable to get on D-Bus John Sample
2007-08-20 16:11 ` umamahesh yelchuru venkata
@ 2007-08-20 17:25 ` John Sample
1 sibling, 0 replies; 3+ messages in thread
From: John Sample @ 2007-08-20 17:25 UTC (permalink / raw)
To: bluez-users
[-- Attachment #1.1: Type: text/plain, Size: 1319 bytes --]
Umesh,
I did a ./configure --prefix=/usr followed by make and make install for both
libs and utils.
John
> Hi Mr.John, Can i get the compilation procedure for bluez libs and utils
>
> Regards
> Umesh
>
>
> On 8/20/07, John Sample <john.m.sample@gm...> wrote:
> >
> > I've been working on getting Bluez up an running on an embedded platform
> > and am having some problems getting hcid to run. I'm using the
> 2.6.23kernel, but I've also tested on an old
> > 2.6.10 kernel and run into the same problem. I start D-Bus using
> > dbus-daemon-1 --system, and it starts ok without any error messages. I
> then
> > start hcid, but it immediately exits and I get the following in my
> syslog:
> >
> > hcid[1021]: Bluetooth HCI daemon
> > hcid[1021]: Can't connect to system message bus: Did not receive a
> reply.
> > Possible causes include: the remote application did not send a reply,
> the
> > message bus security policy blocked the reply, the reply timeout
> expired, or
> > the network connection was broken.
> > hcid[1021]: Unable to get on D-Bus
> > Do I need to modify bluetooth.conf or system.conf in any way to get the
> > security policy to allow the connection? I saw a similar post a while
> ago
> > on this same topic but I couldn't find a resolution anywhere.
> >
> > Thanks,
> >
> > --
> > John Sample
>
[-- Attachment #1.2: Type: text/html, Size: 1659 bytes --]
[-- Attachment #2: Type: text/plain, Size: 315 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-08-20 17:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-08-20 16:08 [Bluez-users] HCI Daemon Unable to get on D-Bus John Sample
2007-08-20 16:11 ` umamahesh yelchuru venkata
2007-08-20 17:25 ` John Sample
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox