Date: Mon, 20 Jun 2005 13:57:40 -0700 From: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> To: vova@fbsd.ru Cc: bluetooth <bluetooth@freebsd.org> Subject: Re: Problem with Logitech Mx900 again Message-ID: <42B72DC4.2090104@savvis.net> In-Reply-To: <1119297124.1045.11.camel@localhost> References: <1119297124.1045.11.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Vladimir, > At some moment my Mx900 stop work when connected directly to notebook BT > adapter. please explain. what os runs of your notebook? what software were you using on your notebook? > It does not work in bot WinXP and FreeBSD (works for both before), but > it still works with native cradle. what do you mean with native cradle? is it some sort of wired interface? bluetooth usb receiver? or bluetooth usb receiver which os detects as usb mouse (i.e. bluetooth usb receiver with hid proxy feature activated)? > Nothing was changed in notebook, nothing in FreeBSD kernel/userland when > problem arise. ok > mouse still pingable with l2ping: > # l2ping -a mouse > 44 bytes from mouse seq_no=-664775869 time=327.503 ms result=0 > 44 bytes from mouse seq_no=-664775869 time=22.231 ms result=0 > ^C that is a strange sequence number, but i do not think this is your problem. > # bthidd -d > bthidd[1486]: Opening outbound session for 00:07:61:17:9b:27 (new_device=1, reconnect_initiate=1) > bthidd[1486]: Could not connect to 00:07:61:17:9b:27. Socket is not connected (57) not good. > (cp /dev/null /var/db/bthidd.hids, before, all possible reset and reconnects on mouse initiated) just a suggestion - you might want to disconnect batteries from the mouse and leave it like that for few (10-15) minutes. just to make sure it "forgets" everything. > there hcidump while this operation > # hcidump next time *please* send me binary dump > HCIDump - HCI packet analyzer ver 1.5 > device: any snap_len: 65535 filter: 0xffffffff > < HCI Command: Create Connection(0x01|0x0005) plen 13 >>HCI Event: Command Status(0x0f) plen 4 >>HCI Event: Connect Complete(0x03) plen 11 ok, baseband link is established > < HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4 > < ACL data: handle 0x0029 flags 0x02 dlen 12 > L2CAP(s): Connect req: psm 17 scid 0x004d >>HCI Event: Number of Completed Packets(0x13) plen 5 >>HCI Event: Command Complete(0x0e) plen 6 >>ACL data: handle 0x0029 flags 0x02 dlen 16 > L2CAP(s): Connect rsp: dcid 0x004f scid 0x004d result 1 status 2 >>ACL data: handle 0x0029 flags 0x02 dlen 16 > L2CAP(s): Connect rsp: dcid 0x0000 scid 0x004d result 2 status 0 ok. bthidd(8) has failed to establish l2cap connection on psm 17 (0x11 - HID control). the mouse first has sent l2cap "connect rsp" message with PENDING (1) result and AUTHORIZATION PENDING (2) status. then it has sent l2cap "connect rsp" with PSM NOT SUPPORTED (2) result. >>HCI Event: QoS Setup Complete(0x0d) plen 21 >>HCI Event: Disconn Complete(0x05) plen 4 and finally baseband link goes down. > In attachment result of > # bthidcontrol -a mouse query looks fine to me. hcidump got confused about sdp packets, but its known problem and its fine. > Any hints what it is and how can be cured ? from what i can see, it looks like the mouse does not like new host. most hid devices will "lock" on the first device that contacted it. that is why you need to "reset" the mouse to make sure it "forgets" about previous host. another thing you could try to do is to force paring between the mouse and pc. you need to know default pin-code for the mouse. check the manual to see if its there, if not - try "0000" - four zeros. 1) man hcsecd(8) 2) man hcsecd.conf(5) 3) man hccontrol(8) 4) hccontrol help write_authentication_enable thanks, max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42B72DC4.2090104>