[Bluez-users] Fwd: hcitool scan problem

[Bluez-users] Fwd: hcitool scan problem

[John Sample]

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

Hello,

I am having a problem with the hcitool scan command (v3.13) using the
2.6.21kernel, 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.

-- 
John Sample

[-- Attachment #1.2: Type: text/html, Size: 1270 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

Re: [Bluez-users] Fwd: hcitool scan problem

[Marcel Holtmann]

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

Re: [Bluez-users] Fwd: hcitool scan problem

[John Sample]

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

Hi Marcel,

Thanks for the reply.  I ran the hcidump with hcitool scan and it appears
that the inquiry retrieves all of the correct addresses, but when it does a
remote name request the addresses are all scrambled.  There is also an
occassional "Error: Invalid HCI Command Parameters" following the name
request.  Any idea what is causing this to happen?

Thanks.

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

-- 
John Sample

[-- Attachment #1.2: Type: text/html, Size: 1723 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