[Bluez-users] problem pairing device

[Bluez-users] problem pairing device

[Michele Puccio]

hi all
I cannot pair any device using hcitool scan or hcitool inq: both exit
without any result or error. this is the output of hcidump during a
scan:
HCI sniffer - Bluetooth packet analyzer ver 1.33
device: hci0 snap_len: 1028 filter: 0xffffffff
HCI Command: Inquiry (0x01|0x0001) plen 5
        lap 0x9e8b33 len 8 num 0
HCI Event: Command Status (0x0f) plen 4
        Inquiry (0x01|0x0001) status 0x00 ncmd 1
HCI Event: Vendor (0xff) plen 7
        0000: cd 03 00 04 00 0000                              .......
HCI Event: Vendor (0xff) plen 7
        0000: cd 03 00 04 00 0000                              .......
HCI Event: Vendor (0xff) plen 7
        0000: cd 03 00 04 00 0000                              .......
HCI Event: Vendor (0xff) plen 7
        0000: cd 03 00 04 00 0000                              .......
HCI Event: Vendor (0xff) plen 7
        0000: cd 03 00 04 00 0000                              .......
HCI Event: Vendor (0xff) plen 7
        0000: cd 03 00 04 00 0000                              .......
HCI Event: Vendor (0xff) plen 7
        0000: cd 03 00 04 00 0000                              .......
HCI Event: Vendor (0xff) plen 7
        0000: cd 03 00 04 00 0000                              .......
HCI Event: Vendor (0xff) plen 7
        0000: cd 03 00 04 00 0000                              .......
HCI Event: Vendor (0xff) plen 7
        0000: cd 03 00 04 00 0000                              .......
HCI Event: Inquiry Complete (0x01) plen 1
        
status 0x00 and this is the output of hciconfig -a
hci0:   Type: USB
        BD Address: 00:16:41:1B:97:A3 ACL MTU: 384:8 SCO MTU: 64:8
        UP RUNNING PSCAN 
        RX bytes:807 acl:0 sco:0 events:63 errors:0
        TX bytes:331 acl:0 sco:0 commands:20 errors:0
        Features: 0xff 0xff 0x9f 0xfe 0x9b 0xf9 0x00 0x80
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: RSWITCH HOLD SNIFF PARK 
        Link mode: SLAVE ACCEPT 
        Name: 'D610'
        Class: 0x000100
        Service Classes: Unspecified
        Device Class: Computer, Uncategorized
        HCI Ver: 1.2 (0x2) HCI Rev: 0x679 LMP Ver: 1.2 (0x2) LMP Subver:
0x679
        Manufacturer: Cambridge Silicon Radio (10)

I'm using ubuntu feisty. any suggestions?
thanks
michele


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] problem pairing device

[Fulvio]

On luned=EC 24 settembre 2007, Michele Puccio wrote:
> =A0 =A0 =A0 =A0 Class: 0x000100
> =A0 =A0 =A0 =A0 Service Classes: Unspecified
> =A0 =A0 =A0 =A0 Device Class: Computer, Uncategorized

Try to specify a better class like:

hciconfig hci0 (or which rely on) class 0x03e100

I can't assure this is the fix, but there'll be other things to try like

dbus-send --system --type=3Dmethod_call --print-reply --dest=3Dorg.bluez /o=
rg/bluez/hci0 =

org.bluez.Adapter.GetMode

To know if it's in discorable mode

dbus-send --system --type=3Dmethod_call --print-reply --dest=3Dorg.bluez /o=
rg/bluez/hci0 =

org.bluez.Adapter.GetDiscoverableTimeout

To know how long it'll remain on disoverable mode

F

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] problem pairing device

[Michele Puccio]

ZnVsdmlvLAp0aGFua3MgZm9yIHlvdXIgYW5zd2VyLgpJIGZpeGVkIHRoZSBjbGFzcyBidXQgbm90
aGluZyBjaGFuZ2UhCnRoZSBtb2RlIHdhcyBzZXQgdG8gY29ubmVjdGFibGUsIEkgY2hhbmdlZCB0
byBkaXNjb3ZlcmFibGUgKHRpbWVvdXQKbmV2ZXIpIHRocm91Z2ggdGhlIGdub21lLWJsdWV0b290
aCBhcHBsZXQgYnV0IHdpdGhvdXQgc3VjY2Vzcy4Kc29tZSBtb3JlIHN1Z2dlc3Rpb25zPwp0aGFu
a3MgYWdhaW4KCm1pY2hlbGUKT24gTW9uLCAyMDA3LTA5LTI0IGF0IDE5OjA5ICswMjAwLCBGdWx2
aW8gd3JvdGU6Cj4gT24gbHVuZWTDrCAyNCBzZXR0ZW1icmUgMjAwNywgTWljaGVsZSBQdWNjaW8g
d3JvdGU6Cj4gPiAgICAgICAgIENsYXNzOiAweDAwMDEwMAo+ID4gICAgICAgICBTZXJ2aWNlIENs
YXNzZXM6IFVuc3BlY2lmaWVkCj4gPiAgICAgICAgIERldmljZSBDbGFzczogQ29tcHV0ZXIsIFVu
Y2F0ZWdvcml6ZWQKPiAKPiBUcnkgdG8gc3BlY2lmeSBhIGJldHRlciBjbGFzcyBsaWtlOgo+IAo+
IGhjaWNvbmZpZyBoY2kwIChvciB3aGljaCByZWx5IG9uKSBjbGFzcyAweDAzZTEwMAo+IAo+IEkg
Y2FuJ3QgYXNzdXJlIHRoaXMgaXMgdGhlIGZpeCwgYnV0IHRoZXJlJ2xsIGJlIG90aGVyIHRoaW5n
cyB0byB0cnkgbGlrZQo+IAo+IGRidXMtc2VuZCAtLXN5c3RlbSAtLXR5cGU9bWV0aG9kX2NhbGwg
LS1wcmludC1yZXBseSAtLWRlc3Q9b3JnLmJsdWV6IC9vcmcvYmx1ZXovaGNpMCAKPiBvcmcuYmx1
ZXouQWRhcHRlci5HZXRNb2RlCj4gCj4gVG8ga25vdyBpZiBpdCdzIGluIGRpc2NvcmFibGUgbW9k
ZQo+IAo+IGRidXMtc2VuZCAtLXN5c3RlbSAtLXR5cGU9bWV0aG9kX2NhbGwgLS1wcmludC1yZXBs
eSAtLWRlc3Q9b3JnLmJsdWV6IC9vcmcvYmx1ZXovaGNpMCAKPiBvcmcuYmx1ZXouQWRhcHRlci5H
ZXREaXNjb3ZlcmFibGVUaW1lb3V0Cj4gCj4gVG8ga25vdyBob3cgbG9uZyBpdCdsbCByZW1haW4g
b24gZGlzb3ZlcmFibGUgbW9kZQo+IAo+IEYKPiAKPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCj4gVGhpcyBT
Ri5uZXQgZW1haWwgaXMgc3BvbnNvcmVkIGJ5OiBNaWNyb3NvZnQKPiBEZWZ5IGFsbCBjaGFsbGVu
Z2VzLiBNaWNyb3NvZnQoUikgVmlzdWFsIFN0dWRpbyAyMDA1Lgo+IGh0dHA6Ly9jbGsuYXRkbXQu
Y29tL01SVC9nby92c2UwMTIwMDAwMDcwbXJ0L2RpcmVjdC8wMS8KPiBfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+IEJsdWV6LXVzZXJzIG1haWxpbmcgbGlz
dAo+IEJsdWV6LXVzZXJzQGxpc3RzLnNvdXJjZWZvcmdlLm5ldAo+IGh0dHBzOi8vbGlzdHMuc291
cmNlZm9yZ2UubmV0L2xpc3RzL2xpc3RpbmZvL2JsdWV6LXVzZXJzCj4gCgoKLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLQpUaGlzIFNGLm5ldCBlbWFpbCBpcyBzcG9uc29yZWQgYnk6IE1pY3Jvc29mdApEZWZ5IGFs
bCBjaGFsbGVuZ2VzLiBNaWNyb3NvZnQoUikgVmlzdWFsIFN0dWRpbyAyMDA1LgpodHRwOi8vY2xr
LmF0ZG10LmNvbS9NUlQvZ28vdnNlMDEyMDAwMDA3MG1ydC9kaXJlY3QvMDEvCl9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCkJsdWV6LXVzZXJzIG1haWxpbmcg
bGlzdApCbHVlei11c2Vyc0BsaXN0cy5zb3VyY2Vmb3JnZS5uZXQKaHR0cHM6Ly9saXN0cy5zb3Vy
Y2Vmb3JnZS5uZXQvbGlzdHMvbGlzdGluZm8vYmx1ZXotdXNlcnMK

Re: [Bluez-users] problem pairing device

[Marcel Holtmann]

Hi Michele,

> I cannot pair any device using hcitool scan or hcitool inq: both exit
> without any result or error. this is the output of hcidump during a
> scan:
> HCI sniffer - Bluetooth packet analyzer ver 1.33
> device: hci0 snap_len: 1028 filter: 0xffffffff
> HCI Command: Inquiry (0x01|0x0001) plen 5
>         lap 0x9e8b33 len 8 num 0
> HCI Event: Command Status (0x0f) plen 4
>         Inquiry (0x01|0x0001) status 0x00 ncmd 1
> HCI Event: Vendor (0xff) plen 7
>         0000: cd 03 00 04 00 0000                              .......
> HCI Event: Vendor (0xff) plen 7
>         0000: cd 03 00 04 00 0000                              .......
> HCI Event: Vendor (0xff) plen 7
>         0000: cd 03 00 04 00 0000                              .......
> HCI Event: Vendor (0xff) plen 7
>         0000: cd 03 00 04 00 0000                              .......
> HCI Event: Vendor (0xff) plen 7
>         0000: cd 03 00 04 00 0000                              .......
> HCI Event: Vendor (0xff) plen 7
>         0000: cd 03 00 04 00 0000                              .......
> HCI Event: Vendor (0xff) plen 7
>         0000: cd 03 00 04 00 0000                              .......
> HCI Event: Vendor (0xff) plen 7
>         0000: cd 03 00 04 00 0000                              .......
> HCI Event: Vendor (0xff) plen 7
>         0000: cd 03 00 04 00 0000                              .......
> HCI Event: Vendor (0xff) plen 7
>         0000: cd 03 00 04 00 0000                              .......
> HCI Event: Inquiry Complete (0x01) plen 1
>         
> status 0x00 and this is the output of hciconfig -a
> hci0:   Type: USB
>         BD Address: 00:16:41:1B:97:A3 ACL MTU: 384:8 SCO MTU: 64:8
>         UP RUNNING PSCAN 
>         RX bytes:807 acl:0 sco:0 events:63 errors:0
>         TX bytes:331 acl:0 sco:0 commands:20 errors:0
>         Features: 0xff 0xff 0x9f 0xfe 0x9b 0xf9 0x00 0x80
>         Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
>         Link policy: RSWITCH HOLD SNIFF PARK 
>         Link mode: SLAVE ACCEPT 
>         Name: 'D610'
>         Class: 0x000100
>         Service Classes: Unspecified
>         Device Class: Computer, Uncategorized
>         HCI Ver: 1.2 (0x2) HCI Rev: 0x679 LMP Ver: 1.2 (0x2) LMP Subver:
> 0x679
>         Manufacturer: Cambridge Silicon Radio (10)

this is one of the funny Dell adapters with the vendor messages. No idea
what this is actually doing. However maybe loading hci_usb with reset=1
might help.

Also you can check "sudo bccmd buildname" if this is a special firmware.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] problem pairing device

[Michele Puccio]

hi marcel,
thanks for answering...but how can I "loading hci_usb with reset=1"?
my system don't the recognize bccmd as a valid command; may be I need
some extra package to install...
can you please help me? the bluetooth is the only stuff that doesn't
work in my linuxbox (dell latitude d610 + ubuntu feisty)

regards
michele


On Tue, 2007-09-25 at 00:17 +0200, Marcel Holtmann wrote:
> Hi Michele,
> 
> > I cannot pair any device using hcitool scan or hcitool inq: both exit
> > without any result or error. this is the output of hcidump during a
> > scan:
> > HCI sniffer - Bluetooth packet analyzer ver 1.33
> > device: hci0 snap_len: 1028 filter: 0xffffffff
> > HCI Command: Inquiry (0x01|0x0001) plen 5
> >         lap 0x9e8b33 len 8 num 0
> > HCI Event: Command Status (0x0f) plen 4
> >         Inquiry (0x01|0x0001) status 0x00 ncmd 1
> > HCI Event: Vendor (0xff) plen 7
> >         0000: cd 03 00 04 00 0000                              .......
> > HCI Event: Vendor (0xff) plen 7
> >         0000: cd 03 00 04 00 0000                              .......
> > HCI Event: Vendor (0xff) plen 7
> >         0000: cd 03 00 04 00 0000                              .......
> > HCI Event: Vendor (0xff) plen 7
> >         0000: cd 03 00 04 00 0000                              .......
> > HCI Event: Vendor (0xff) plen 7
> >         0000: cd 03 00 04 00 0000                              .......
> > HCI Event: Vendor (0xff) plen 7
> >         0000: cd 03 00 04 00 0000                              .......
> > HCI Event: Vendor (0xff) plen 7
> >         0000: cd 03 00 04 00 0000                              .......
> > HCI Event: Vendor (0xff) plen 7
> >         0000: cd 03 00 04 00 0000                              .......
> > HCI Event: Vendor (0xff) plen 7
> >         0000: cd 03 00 04 00 0000                              .......
> > HCI Event: Vendor (0xff) plen 7
> >         0000: cd 03 00 04 00 0000                              .......
> > HCI Event: Inquiry Complete (0x01) plen 1
> >         
> > status 0x00 and this is the output of hciconfig -a
> > hci0:   Type: USB
> >         BD Address: 00:16:41:1B:97:A3 ACL MTU: 384:8 SCO MTU: 64:8
> >         UP RUNNING PSCAN 
> >         RX bytes:807 acl:0 sco:0 events:63 errors:0
> >         TX bytes:331 acl:0 sco:0 commands:20 errors:0
> >         Features: 0xff 0xff 0x9f 0xfe 0x9b 0xf9 0x00 0x80
> >         Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
> >         Link policy: RSWITCH HOLD SNIFF PARK 
> >         Link mode: SLAVE ACCEPT 
> >         Name: 'D610'
> >         Class: 0x000100
> >         Service Classes: Unspecified
> >         Device Class: Computer, Uncategorized
> >         HCI Ver: 1.2 (0x2) HCI Rev: 0x679 LMP Ver: 1.2 (0x2) LMP Subver:
> > 0x679
> >         Manufacturer: Cambridge Silicon Radio (10)
> 
> this is one of the funny Dell adapters with the vendor messages. No idea
> what this is actually doing. However maybe loading hci_usb with reset=1
> might help.
> 
> Also you can check "sudo bccmd buildname" if this is a special firmware.
> 
> Regards
> 
> Marcel
> 
> 
> 


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] problem pairing device

[Marcel Holtmann]

Hi Michele,

> thanks for answering...but how can I "loading hci_usb with reset=1"?

there are millions of howtos that deal with kernel modules/drivers and
how to load them with special options. Also /sys/module/hci_usb can be
used to changed them at runtime. Then however the device needs to be
unplugged and replugged.

> my system don't the recognize bccmd as a valid command; may be I need
> some extra package to install...

Ask your distro. It is part of bluez-utils. Compile it from the sources.

> can you please help me? the bluetooth is the only stuff that doesn't
> work in my linuxbox (dell latitude d610 + ubuntu feisty)

If someone donates a D610 to me, then I can make this easily work, but
until then, you have to play with it.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] problem pairing device

[Michele Puccio]

Marcel
thanks again!
mmmhhhhh not so easy....I have to study some fundamental stuff and spend
time on it...anyway...
if someone donates you a D610 please let me know ;-)

Best regards

michele

On Tue, 2007-09-25 at 09:57 +0200, Marcel Holtmann wrote:
> Hi Michele,
> 
> > thanks for answering...but how can I "loading hci_usb with reset=1"?
> 
> there are millions of howtos that deal with kernel modules/drivers and
> how to load them with special options. Also /sys/module/hci_usb can be
> used to changed them at runtime. Then however the device needs to be
> unplugged and replugged.
> 
> > my system don't the recognize bccmd as a valid command; may be I need
> > some extra package to install...
> 
> Ask your distro. It is part of bluez-utils. Compile it from the sources.
> 
> > can you please help me? the bluetooth is the only stuff that doesn't
> > work in my linuxbox (dell latitude d610 + ubuntu feisty)
> 
> If someone donates a D610 to me, then I can make this easily work, but
> until then, you have to play with it.
> 
> Regards
> 
> Marcel
> 
> 
> 


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

[Bluez-users] problem pairing, hcid die

[Fulvio]

Hello there,

I still have a long way to go to understand what's going on with bluez 3.20, 
Arch Linux and KDE desktop manager.
As far as I could see the deamon die after a trial to set a link with the 
device which I want to connect.
Here's the syslog:

Nov 18 20:28:20 laptop hcid[11827]: link_key_request (sba=00:A0:96:xx:CE:34, 
dba=00:1A:xx:08:A5:F9)
Nov 18 20:28:28 laptop hcid[11827]: pin_code_request (sba=00:A0:96:xx:CE:34, 
dba=00:1A:xx:08:A5:F9)
Nov 18 20:28:31 laptop sdpd[11831]: Stopping SDP server
Nov 18 20:28:31 laptop sdpd[11831]: Exit
Nov 18 20:28:31 laptop hcid[11827]: Unregister path: /org/bluez/hci0
Nov 18 20:28:31 laptop hcid[11827]: Unregister path: /org/bluez
Nov 18 20:28:31 laptop hcid[11827]: Shutting down local server
Nov 18 20:28:31 laptop hcid[11827]: Exit

Therefore, is there a practical way to make the link/pairing, some simple 
script that will answer to the pin request?
What should I check if something goes wrong and it will kill the hcid?


F

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users