On Tue, 15 May 2007, Juan RP wrote:

> Hey, I'm having problems with bluetooth on amd64 that I did not
> have when I was using i386.
>
> I have the ubt0 device configured as:
>
> $ btconfig -vvvv ubt0
> ubt0: bdaddr 00:0a:94:13:22:93 flags 0x3<UP,RUNNING>
>         num_cmd = 1
>         num_acl = 20, acl_mtu = 120
>         num_sco = 0, sco_mtu = 0
>         class: [0x02010c] Laptop Computer <Networking>
>         name: "ubt0"
>         voice: [0x0060]
>                 Input Coding: Linear PCM [16-bit, pos 0], 2's complement
>                 Air Coding: CVSD
>         pin: variable
>         options: -iscan pscan auth encrypt switch -hold -sniff -park
>         ptype: [0xff1e] DM1 DH1 DM3 DH3 DM5 DH5
>         page timeout: 5120 ms
>         features: <3 slot> <5 slot> <encryption> <slot offset> <timing
> accuracy> <role switch> <hold mode> <sniff mode> <park mode> <RSSI>
> accuracy> <channel quality>
> <SCO link> <HV2> <HV3> <u-Law log> <A-Law log> <CVSD data> <power control>
> $
>
> btconfig inquiry shows my other bluetooth device:
>
> $ btconfig -v ubt0 inquiry
> ubt0: bdaddr 00:0a:94:13:22:93 flags 0x3<UP,RUNNING>
> Device Discovery from device: ubt0 .... 1 response
>   1: bdaddr 00:16:b8:f7:ae:1a (xtraeme)
>    : name "xtraeme"
>    : class: [0x5a0204] Cellular Phone <Networking> <Capturing> <Object
> Transfer> <Telephony>
>    : page scan rep mode 0x01
>    : page scan period mode 0x02
>    : page scan mode 0x00
>    : clock offset 12014
>
> $
>
> But when I try to use another program that uses connect() with the bdaddr
> it returns ETIMEDOUT.
>
> ktruss output from "sdpquery -a xtraeme Browse" (note that sdpd is already
> running):
>
>   2379      1 sdpquery setsockopt(0x4, 0xffff, 0x80, 0x7f7fffffe6e0, 0x8) =
> 0 2379      1 sdpquery bind(0x4, 0x7f7fffffe6d0, 0x10) = 0
> sdpquery: sdp_open: Connection timed out
>   2379      1 sdpquery connect(0x4, 0x7f7fffffe6d0, 0x10) Err#60 ETIMEDOUT
>
> So I can't use any program that uses connect().
>
> Do you have any idea what's wrong, Iain?

I guess its time out as in paused for some seconds, then timed out..?

Could be related to auth being enabled, is bthcid running?

what does 'hcidump -V' (as root) show?

iain