From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Fwd: hcitool scan problem
Date: Sat, 18 Aug 2007 14:50:12 +0200 [thread overview]
Message-ID: <1187441413.11068.15.camel@violet> (raw)
In-Reply-To: <79be12f70708171422h6321e538hd92ea920068ea237@mail.gmail.com>
Hi John,
> I am having a problem with the hcitool scan command (v3.13) using the
> 2.6.21 kernel, as well as 2.6.23. Here is my output:
>
> Scanning ...
> 3A:5E:11:6B:00:00 n/a
> 38:C1:5E:35:3F:D9 n/a
> C5:2B:F4:F7:3C:6A n/a
> 3A:75:F9:65:1A:02 n/a.
> 38:C1:60:35:1A:F6 n/a
>
> All of the addresses are partially junk for some reason - for example
> 38:C1:60:35:1A:F6 should be 00:16:38:C1:60:35, and no name are
> returned. This seems to effect other tools as well, for example if I
> do try to do a hidd search I can't detect anything even if there are
> discoverable hid devices around - I'm guessing because it doesn't have
> valid addresses. Previously I had been using the 2.6.10 kernel and
> everything worked fine.
run "hcidump -X -V" and compare the output.
Regards
Marcel
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-08-18 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <79be12f70708171418i44648442g45dbff593b84063@mail.gmail.com>
2007-08-17 21:22 ` [Bluez-users] Fwd: hcitool scan problem John Sample
2007-08-18 12:50 ` Marcel Holtmann [this message]
2007-08-20 15:24 John Sample
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=1187441413.11068.15.camel@violet \
--to=marcel@holtmann.org \
--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