public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael Ellis" <michael.f.ellis@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] dbus-1.pc not found
Date: Mon, 7 Aug 2006 21:18:01 -0400	[thread overview]
Message-ID: <7b9ca310608071818v5871bb19y2593b7a693ca4ab6@mail.gmail.com> (raw)
In-Reply-To: <1154999049.3905.108.camel@aeonflux.holtmann.net>


[-- Attachment #1.1: Type: text/plain, Size: 3712 bytes --]

Hi Marcel,

Thanks! That did the trick and it installed without error.

So, if I may be so bold as to ask a little more help :-),  I now have a
configuration that almost works.  I can plug a DBT-120 dongle into the linux
laptop and it seems to find and initialize it appropriately.  Similarly,  I
can use hcitool -inq and detect the embedded bluetooth device.  When I try
to connect with hcitool cc, I get an input/output error.  FWIW, I'm able to
connect the devices and exchange data if I plug the same dongle into a
Windows box.

Here are the outputs from the hci commands.

bash-3.00$ sudo /usr/sbin/hciconfig -a
hci0:   Type: USB
        BD Address: 00:11:95:50:30:6A ACL MTU: 192:8 SCO MTU: 64:8
        UP RUNNING
        RX bytes:767 acl:0 sco:0 events:57 errors:0
        TX bytes:513 acl:0 sco:0 commands:35 errors:0
        Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'BlueZ (0)'
        Class: 0x3e0100
        Service Classes: Networking, Rendering, Capturing
        Device Class: Computer, Uncategorized
        HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP Subver:
0x20d
        Manufacturer: Cambridge Silicon Radio (10)


bash-3.00$ hcitool inq
Inquiring ...
        00:0C:84:00:16:51       clock offset: 0x670f    class: 0x000000

bash-3.00$ sudo hcitool cc 00:0C:84:00:16:51
Can't create connection: Input/output error

Any recommendations for troubleshooting?

Thanks for your help.
Mike

On 8/7/06, Marcel Holtmann <marcel@holtmann.org> wrote:
>
> Hi Mike,
>
> > Apologies if this has already been discussed, but I've searched on
> > Google and Gmane and haven't found anything that seems to fit exactly.
> >
> > Trying to configure bluez-utils-3.2 on slackware 10.1 with a 2.6.11
> > kernel,  I get
> >
> > checking for DBUS... Package dbus-1 was not found in the pkg-config
> > search path.
> > Perhaps you should add the directory containing `dbus-1.pc'
> > to the PKG_CONFIG_PATH environment variable
> > No package 'dbus-1' found
> > configure: error: dbus > 0.35 is required
> >
> > Installing dbus-0.91, apparently successfully, does not cure the
> > error.  Is there something I needed to do other than the
> > usual ./configure;  make;  sudo make install?  My dbus executables
> > were installed in /usr/local/bin.
> >
> > I also tried building bluez-utils-3.2 with  ./configure
> > --disable-dbus.  No effect, same error.  FWIW, I'm using the FCE4
> > desktop rather than Gnome or KDE. I mention this because I get the
> > impression the need for dbus is typically associated with Desktop
> > support.
> >
> >  I very much need to get bluez-utils working for simple serial comm to
> > an embedded device and could care less about GUIs.  What's the most
> > straightforward way get past this hurdle?
>
> run "find /usr -name 'dbus*.pc'" to find the actual pkg-config file from
> your D-Bus installation.
>
> Regards
>
> Marcel
>
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>



-- 
Michael F. Ellis
Managing Partner
Ellis & Grant, Inc.
Make Better Decisions with PeerTool!
http://www.peertools.com

[-- Attachment #1.2: Type: text/html, Size: 5444 bytes --]

[-- Attachment #2: Type: text/plain, Size: 373 bytes --]

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

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

  reply	other threads:[~2006-08-08  1:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-07 21:27 [Bluez-users] dbus-1.pc not found Michael Ellis
2006-08-07 23:13 ` bees
2006-08-08  1:04 ` Marcel Holtmann
2006-08-08  1:18   ` Michael Ellis [this message]
2006-08-08 13:58     ` Michael Ellis
2006-08-08 14:31       ` Michael Ellis

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=7b9ca310608071818v5871bb19y2593b7a693ca4ab6@mail.gmail.com \
    --to=michael.f.ellis@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