public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "John Sample" <john.m.sample@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] HCI Daemon Unable to get on D-Bus
Date: Mon, 20 Aug 2007 11:25:01 -0600	[thread overview]
Message-ID: <79be12f70708201025o57287cfeu43a86231220571fe@mail.gmail.com> (raw)
In-Reply-To: <79be12f70708200908k48717fd4w2baa95824304733c@mail.gmail.com>


[-- 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

      parent reply	other threads:[~2007-08-20 17:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 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=79be12f70708201025o57287cfeu43a86231220571fe@mail.gmail.com \
    --to=john.m.sample@gmail.com \
    --cc=bluez-users@lists.sourceforge.net \
    /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