Skip site navigation (1)Skip section navigation (2) 
Date:      Tue, 21 Dec 2004 12:57:59 +0300
From:      Vladimir Grebenschikov <vova@fbsd.ru>
To:        Maksim Yevmenkin <maksim.yevmenkin@savvis.net>
Cc:        bluetooth@freebsd.org
Subject:   Re: Bluetooth mouse
Message-ID:  <1103623079.954.10.camel@localhost>
In-Reply-To: <41C72A9B.6090405@savvis.net>
References:  <1100552998.1098.5.camel@localhost> <419B8353.7040908@savvis.net>     <opshmg45c1lo1qsj@mail.xs4all.nl> <419B9EF8.2090401@savvis.net>     <1103269957.974.7.camel@localhost> <41C32471.2050805@savvis.net> <866530fusa.fsf@kamino.rfc1149.org> <41C35B92.7080908@savvis.net> <1103489813.1721.14.camel@localhost> <41C63A62.20304@savvis.net> <1103527349.1024.18.camel@localhost> <41C72A9B.6090405@savvis.net>
index | next in thread | previous in thread | raw e-mail 

[-- Attachment #1 --]
 , 20/12/2004  11:40 -0800, Maksim Yevmenkin :
> Vladimir,
>  
> > looks like it does not require key or pin, also winXP connects only
> > without pin.
> 
> how can you tell? the pin code may be hardwired somewhere in the windows 
> registry. did windows software prompt you for anything during install? 
> can you check all the documentation that came with the mouse to see if 
> there is a pin code?

I have not installed any drivers shipped with this mouse, only native
winxp driver. WinXP bluetooth explorer found mouse and ask me Do I want
to provide pin or do not. I select do not provide and this works.

> Arne: could you please tell us what did you do to make your mouse work?
> 
> >> 7) start bthidd(8)
> >> 
> >> if you did everything right the mouse should work.
> > 
> > Still no luck, but this time there is attempt to connect from host to
> > mouse on bthidd start:
> > 
> > # bthidd -d bthidd[1398]: Opening outbound session for
> > 00:07:61:17:9b:27 (new_device=1, reconnect_initiate=1) bthidd[1398]:
> > Could not connect to 00:07:61:17:9b:27. Socket is not connected (57)
> 
> that the way it should work.
> 
> > There hcidump output while bthidd connection attempt # hcidump -r
> > mouse.dump HCIDump - HCI packet analyzer ver 1.5
> 
> [...]
> 
> 1103525841.696334 < ACL data: handle 0x002a flags 0x02 dlen 12
>      L2CAP(s): Connect req: psm 17 scid 0x0060
> 
> here host is trying to open hid-control channel (psm 17 (0x11))
> 
> 1103525841.738294 > ACL data: handle 0x002a flags 0x02 dlen 16
>      L2CAP(s): Connect rsp: dcid 0x005c scid 0x0060 result 1 status 2
> 
> 1103525841.772308 > ACL data: handle 0x002a flags 0x02 dlen 16
>      L2CAP(s): Connect rsp: dcid 0x0000 scid 0x0060 result 2 status 0
> 
> and these are mouse responses. the first response returns with result 
> code 1 (Connection Pending) and status code 2 (Authorization Pending).
> 
> the second response is with result code 2 (PSM Not Supported) and status 
> code 0 (No Information).
> 
> note timestamps - responses are only 34 msec apart - not much time. so 
> it looks like the mouse does not like the host.
> 
> are you using different bluetooth adapters on your freebsd and winxp 
> boxes? if so, can you try and use winxp adapter on your freebsd box? 
> also did you check the manual to find out what is the correct reset 
> procedure for the mouse?

The same adapter was used, my notebooks's on-board bt

> > bthidd[1610]: Opening outbound session for 00:07:61:17:9b:27 
> > (new_device=1, reconnect_initiate=1) bthidd[1610]: Could not connect
> > to 00:07:61:17:9b:27. Socket is not connected (57)
> > 
> > hcidump while this is:
> 
>      < ACL data: handle 0x0029 flags 0x02 dlen 12
>          L2CAP(s): Connect req: psm 17 scid 0x006d
> 
> again host is trying to open hid-control channel
> 
>     > ACL data: handle 0x0029 flags 0x02 dlen 16
>          L2CAP(s): Connect rsp: dcid 0x0042 scid 0x006d result 1 status 2
> 
>      > ACL data: handle 0x0029 flags 0x02 dlen 16
>          L2CAP(s): Connect rsp: dcid 0x0042 scid 0x006d result 0 status 0
> 
> whoa! this time it has opened hid-control channel. lets see what happens 
> next...
>
>      < ACL data: handle 0x0029 flags 0x02 dlen 12
>          L2CAP(s): Config req: dcid 0x0042 flags 0x0000 clen 0
> 
>      > ACL data: handle 0x0029 flags 0x02 dlen 14
>          L2CAP(s): Config rsp: scid 0x006d flags 0x0000 result 0 clen 0
> 
> here host configures its side of the l2cap channel (hid control) and 
> mouse accepts it.
> 
>      > ACL data: handle 0x0029 flags 0x01 dlen 13
>          L2CAP(s): Config req: dcid 0x006d flags 0x0000 clen 28
>          MTU 48 Unknown (type 03, len 22)
> 
>      < ACL data: handle 0x0029 flags 0x02 dlen 14
>          L2CAP(s): Config rsp: scid 0x0042 flags 0x0000 result 0 clen 0
> 
> here mouse configures its side of the l2cap channel (hid control), sets 
> mtu and qos. (ignore Unknown - hcidump does not know how to parse qos 
> option). host accepts it.
> 
> so far everything looks fine to me. after this point hid control channel 
>   should be opened and configured. the next step is to open hid 
> interrupt channel.
> 
>      < ACL data: handle 0x0029 flags 0x02 dlen 12
>          L2CAP(s): Connect req: psm 25 scid 0x006e
> 
>      > ACL data: handle 0x0029 flags 0x02 dlen 16
>          L2CAP(s): Connect rsp: dcid 0x0000 scid 0x006e result 2 status 0
> 
> ok, this does not make any sense. psm 25 ?! why the hell it tries to 
> connect to psm 25? of course mouse tells host to get lost, because it 
> does not want to talk on psm 25.
> 
> wait, i know why. i just checked your older email and find out that you have
> 
> "interrupt_psm 0x19;"
> 
> line in your /etc/bluetooth/bthidd.conf file (mouse section). could you 
> please try to change it to
> 
> "interrupt_psm 0x13;"
> 
> then do the following:
> 
> 0) run 'hcidump -w mouse.dump' as root
> 
> 1) remove mouse bd_addr from /var/db/bthidd.hids file
> 
> 2) disconnect and reconnect batteries on your mouse
> 
> 3) press 'connect' button on your mouse
> 
> 4) restart bthidd(8)
> 
> > It happens when I disconnect/connect batteries and then press connect
> >  button.
> > 
> > Even after that mouse does not moved. if I restart bthidd - it does
> > not connects and mouse does not send any traffic.
> 
> it will not move - you do not have hid session, that is you need to open 
> both hid control and hid interrupt channels.
> 
> if the above works then there is a problem with


Yes, it works ! (dump in attachment)

> 1) bthidcontrol(8) - because it has incorrectly parsed sdp response and 
> showed wrong psm for the hid interrupt channel. that is what you put 
> into the /etc/bluetooth/bthidd.conf file (unless of course you 
> hand-edited it as well)

No, I do not edit this manually.

> or
> 
> 2) mouse itself. it advertises wrong psm for the hid interrupt channel.

Why it works with winXP in this case ?

How to find what happens ? 

> thanks,
> max
-- 
Vladimir B. Grebenchikov
vova@fbsd.ru

[-- Attachment #2 --]
CA
'aCADCA
)'aCA

)CA
) @CA
)	CA~
)
CAK 'aCA=) B@CA) B@CA) BCA84)CA
)+CA'2
) 
@ CAE
) $ @0CAqM
)
+CAM
) 
BCA'N
) ACAh
)CAp
)CA
) CACA) CACA) CCA)DA *) 
A DA`) $ A0DAh)
+DAh) 
CDA)	DAZ)KA
) AKA'
) AKAR
) AKAg
) AKA)
) AKA
) AKAD) AKAqw) AKAV) AKA ) AKA) AKA) AKA:) AKAi) AKAE) AKA) AKA,
) AKA_
) AKA
) A	KAX
) A
KAW
) AKA0
) AKA") AKAQ) A KA) A0KAv) A KA6) A`KA) A@LA0) ALA]c) ALA ) ALA) ALA) ALA) AOLA*) A?LAdY) ALAO) ALA) ALA) ALA) ALAqO) ALAc~) ALA)) ALA\) ALAr) ALAV) ALA) ALA) ALAN) ALA) ALA\) ALA) ALA) ALAs) ALAv{) ALAs) ALAE) ALA) ALAB) ALAi) ALA) ALAe) ALA5) ALA,	) ALA[	) ALA	) ALAz	) ALAD	) ALA#
) ALAQ
) ALA
) ALA
) ALAP
) ALA6) ALAG) ALAv) ALA) ALAP) AoLA) ALA:) ALAl) ALAÛ) ALA}) ALA[) ALA.0
) ALA_
) APLAƑ
) ALA
) AoLAi
) ALAR") A LAU) A@LA) ALA) ALAm) ALA>) AMA7) AMAf) ApMAt) A0MAF) ApMA) A0MA)) AMA1) A MA) AMAJ) A@MA4) APMA) APMA) A`MA}) AMA}) AMAu) AMA) AMA) AMAD) AMAƢ) AMAv) AMA]) AMA7) AMA>) AMAe) AMA) AMAh) AMAS) AMA[) AMA) A@MA) APMA^) AMA1) AMAQ) AMA) AMA) APMAx) A
`MA=) A
PMAD) AMAs) A
MAz) AMA) AMA) A
MA:) AMA/:) AMAi) AMAΛ) AMA) A_MAt) A/MAO,	) AMA_	) AMA	) AMA	) AMA	) AMAe"
) AMA;Q
) AOMA
) AMAݲ
) AOMA
) AMA) AMAMG) AMA'v) AMA) AMA) AMA
) AMAl9) AOMAAl) AMA) AMA) AMA) AMA}/
) AOMAW^
) AMA 
) AOMA
) AMA
) AOMA!) AMAP) AoMAPX) AMA) AMA) AMA) AMA) ANA[) ANAe) ANA۔) A	NA) ANAg)PNAq) A	@NAC) A NA7)) ANA[) ANA) ANA) ANA) ANA)N) ANAU) ANA) ANAɯ) ANAz) ANA@) A
NA9D) ANAs) ANA) ANA) ANAd) A/NA-i) A/NA) AONA) A?NA) A?NAh,) ANAA[) ANA) ANA) ANA) ANA) ANA) ANAWQ) ANA) ANA) ANA) AoNA) ANAC) A?NADv) ANA) AONA) A?NA) ANA9) ANA`h) AONA.) ANA.) A/NA) AoNA+	) A_NA^	) ANAc	) ANA	) ANA	) ANA>) ANA) ANA8) ANA@) ANAk) ANAO) ANA) ANA.
) ANA]
) ANAt
) ANA) AOAWe) AOA) A OA) A@OA) APOA) ApOAX[) AOA9) A	OA) AOA͙)OA) A0OA) AOA) A`OAM) A
OAG) A
OA) AOA) A
OA) A
OAC) ApOAr) A	OAŨ) A`OA) ApOA) AOA5) A0OAvh) A OA) AOA 
) AOAW) AOA	) AOA]	) AOA	) AOA	) AOAV	) AOA5	) AOA!
) A_OAS
) A?OA
) AOA_
) AOA]
) AOA,) A/OAt) AOA|) AOA) AOA) A?OA8
) A/OA,<) AOA
k) AOA) AOAm) AOA
) AOA
) A OA?$) A0OA)S) A`OA) AOA) AOA) A	OA_) APA) APA5) A	PAh) A
 PAl) APPA:) APAR) APA) APA+) APA) APAb) APAX) A`PA) A`PA%) APPAP) A@PAg) A0PAK) A@PA1) A0PA) A PAu) APA) APA,) APA8) APAg) APA) A0PA) A PA+) A0PA2) A PA) A PA) APAl) APAR) APA^.	) AQAa) AQAd) AQAk) AQAȖ) AQA() AQAT') AQA/) AOQAZ) A?QAЌ) AQA) AQAx) AQAk) AQAAL) A/QA) AQA) AQA) AQAv) AQABB) AQA
u) AQA) AQA) AQA) AQAkj) AQA:	) A
help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1103623079.954.10.camel>