From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hcid returning "Device or resource busy"?
Date: Wed, 28 Mar 2007 12:18:04 +0200 [thread overview]
Message-ID: <1175077084.5815.123.camel@violet> (raw)
In-Reply-To: <007801c77120$bb936640$9d0cc70a@dlh.st.com>
Hi Mayank,
> > > > I've been wondering why my devices weren't showing up in
> > > > nautilus-sendto, and it looks like DiscoverDevices
> > doesn't work. Here's
> > > > the snippet of code:
> > > >
> > > > dbus_g_proxy_call (object, "DiscoverDevices", &e,
> > > > G_TYPE_INVALID, G_TYPE_INVALID);
> > > > if (e != NULL) {
> > > > g_warning ("Couldn't start discovery: %s: %s",
> > > > dbus_g_error_get_name (e), e->message);
> > > > g_error_free (e);
> > > > }
> > > >
> > > > I do a list ListBondings before that on the same object,
> > so I know that
> > > > it works. But I still get that error:
> > > > Couldn't start discovery: org.bluez.Error.Failed: Device
> > or resource busy
> > >
> > > please run "hcidump -X -V" to see what happens on the HCI
> > layer. Do you
> > > have running anything else at the same time.
> >
> > Nope, not doing anything else, apart from having the applet
> > running, let
> > me attach the hcidump output.
>
> [...]
>
> > HCI Event: Command Status (0x0f) plen 4
> > Remote Name Request Cancel (0x01|0x001a) status 0x01 ncmd 1
> > Error: Unknown HCI Command
>
> Looks like a BT1.1 dongle to me since Remote Name Request Cancel was
> introduced after that.
> And since the device is not yet finished paging during the remote name
> request, it disallows the Inquiry Command.
>
> Solution: Get yourself a dongle > BT1.1 !
actually it was the Create Connection Cancel that was introduced with
Bluetooth 1.2. The Remote Name Request Cancel was always present, but it
seems we have a chip that doesn't support it.
Bastien, what does "hciconfig hci0 version" tells you?
Regards
Marcel
-------------------------------------------------------------------------
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-03-28 10:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 9:16 [Bluez-devel] hcid returning "Device or resource busy"? Bastien Nocera
2007-03-28 9:28 ` Marcel Holtmann
2007-03-28 9:56 ` Bastien Nocera
2007-03-28 10:06 ` Mayank BATRA
2007-03-28 10:18 ` Marcel Holtmann [this message]
2007-03-28 10:29 ` Mayank BATRA
2007-03-28 10:42 ` Marcel Holtmann
2007-03-28 12:34 ` Bastien Nocera
2007-03-28 12:47 ` Marcel Holtmann
2007-03-28 13:07 ` Bastien Nocera
2007-03-28 13:20 ` Marcel Holtmann
2007-03-28 15:05 ` [Bluez-devel] L2CAP: ECONNRESET is set for every l2cap disconnect Aarti Kumar
2007-03-29 12:18 ` [Bluez-devel] hcid returning "Device or resource busy"? Bastien Nocera
2007-03-29 12:20 ` Marcel Holtmann
2007-03-29 13:24 ` Bastien Nocera
2007-03-29 16:16 ` Marcel Holtmann
2007-03-29 5:58 ` Mayank BATRA
2007-03-31 13:56 ` Marcel Holtmann
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=1175077084.5815.123.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-devel@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