Date: Tue, 21 Jun 2005 10:14:05 +0400 From: Vladimir Grebenschikov <vova@fbsd.ru> To: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> Cc: bluetooth <bluetooth@freebsd.org> Subject: Re: Problem with Logitech Mx900 again Message-ID: <1119334445.972.17.camel@localhost> In-Reply-To: <42B72DC4.2090104@savvis.net> References: <1119297124.1045.11.camel@localhost> <42B72DC4.2090104@savvis.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-h51vAuHZpi8mWDY4WkFv Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable =F7 =D0=CE, 20/06/2005 =D7 13:57 -0700, Maksim Yevmenkin =D0=C9=DB=C5=D4: > Hello Vladimir, >=20 > > At some moment my Mx900 stop work when connected directly to notebook B= T > > adapter. >=20 > please explain. what os runs of your notebook? what software were you=20 > using on your notebook? Mostly 6-CURRENT :-), with FreeBSD NG bluetooth stack and userland from /usr/src/usr.sbin/bluetooth/. Sometimes Native WinXP Home, with Sony BluespaceNE bluetooth software. > > It does not work in bot WinXP and FreeBSD (works for both before), but=20 > > it still works with native cradle. >=20 > what do you mean with native cradle? is it some sort of wired interface?=20 > bluetooth usb receiver? or bluetooth usb receiver which os detects as=20 > usb mouse (i.e. bluetooth usb receiver with hid proxy feature activated)? Native cradle of Mx900. It looks like hid proxy for me (seen from freebsd as usb mouse). But by manual it can work as BT hub with specil winXP drivers, never install these drivers and seen this feature (without drivers it looks like usb mouse under winXP too). > > Nothing was changed in notebook, nothing in FreeBSD kernel/userland whe= n > > problem arise. >=20 > ok >=20 > > mouse still pingable with l2ping: > > # l2ping -a mouse > > 44 bytes from mouse seq_no=3D-664775869 time=3D327.503 ms result=3D0=20 > > 44 bytes from mouse seq_no=3D-664775869 time=3D22.231 ms result=3D0=20 > > ^C >=20 > that is a strange sequence number, but i do not think this is your proble= m. Just after problem occurs ping responses was returned with huge timeout (like 5 sec). But after some reset cycles (with batteries removal) it start to reply faster. > > # bthidd -d > > bthidd[1486]: Opening outbound session for 00:07:61:17:9b:27 (new_devic= e=3D1, reconnect_initiate=3D1) > > bthidd[1486]: Could not connect to 00:07:61:17:9b:27. Socket is not con= nected (57) >=20 > not good. >=20 > > (cp /dev/null /var/db/bthidd.hids, before, all possible reset and recon= nects on mouse initiated) >=20 > just a suggestion - you might want to disconnect batteries from the=20 > mouse and leave it like that for few (10-15) minutes. just to make sure=20 > it "forgets" everything. Yes, I've tried to remove batteries, even for some days (this I meant under "all possible resets"). > > there hcidump while this operation > > # hcidump=20 >=20 > next time *please* send me binary dump ok=20 dump with last attempt with pin-code in attachment. > > Any hints what it is and how can be cured ?=20 >=20 > from what i can see, it looks like the mouse does not like new host.=20 > most hid devices will "lock" on the first device that contacted it. that=20 > is why you need to "reset" the mouse to make sure it "forgets" about=20 > previous host. Looks like it resets to native cradle and do not want to learn new pair. Sometimes, after my attempts to reset, it even does not want to connect with cradle. > another thing you could try to do is to force paring between the mouse=20 > and pc. you need to know default pin-code for the mouse. check the=20 > manual to see if its there, if not - try "0000" - four zeros. Yes, some on-line FAQ for that mouse mention 0000. It looks like hardware problem for me (over one night both OSes stop stop seen mouse) no reset was initiated, cradle was far-far away from place where it happens. But, probably there is software solution. > 1) man hcsecd(8) >=20 > 2) man hcsecd.conf(5) >=20 > 3) man hccontrol(8) Already. I've managed to make this mouse work before but ... > 4) hccontrol help write_authentication_enable No luck with both 0 and 1. > thanks, > max --=20 Vladimir B. Grebenschikov vova@fbsd.ru --=-h51vAuHZpi8mWDY4WkFv Content-Disposition: attachment; filename=bthidd.dump Content-Type: application/octet-stream; name=bthidd.dump Content-Transfer-Encoding: base64 EQAAAAist0Krxg4AAQUEDSebF2EHABjMAQAAAAEHAAEACKy3QszhDgAEDwQAAQUECQABAAmst0Ir YgQABBcGJ5sXYQcAGgAAAAmst0KCYwQAAQsEFiebF2EHAGEGs2shab5Xr4BJ+vp9sxcNAAEACay3 QmigBAAEDgoBCwQAJ5sXYQcADgABAAmst0KwngUABAMLACkAJ5sXYQcAAQAIAAAACay3QrWeBQAB DQgEKQAPABEAAAAJrLdCt54FAAIpIAwACAABAAIBBAARAEIACAABAAmst0KhtQUABBMFASkAAQAJ AAEACay3QiHNBQAEDgYBDQgAKQAVAAEACay3QrDkBQACKSAQAAwAAQADAQgAQgBCAAEAAgAVAAEA Cay3QnnDBgACKSAQAAwAAQADAQgAQgBCAAAAAAARAAAACay3QqPDBgACKSAMAAgAAQAEAgQAQgAA AAgAAQAJrLdCld4GAAQTBQEpAAEAGAABAAmst0L7RwcABA0VACkAAAEAAAAAAAAAAPIrAAD///// EwABAAmst0Jd4AcAAikgDgAKAAEABQIGAEIAAAAAACAAAQAJrLdClFkIAAIpIBsAJAABAAQBIABC AAAAAQIwAAMWAAEAAAAAAAAAEgABAAmst0JOYQgAAikQDQAAAAAAAPIrAAD/////EwAAAAmst0J5 YQgAAikgDgAKAAEABQEGAEIAAAAAABEAAAAJrLdCNmIIAAIpIAwACAABAAIDBAAZAEMACAABAAms t0KUfAgABBMFASkAAQAIAAEACay3QlGECAAEEwUBKQABABUAAQAJrLdCbNoIAAIpIBAADAABAAMD CAAAAEMAAgAAABEAAAAJrLdCVtsIAAIpIAwACAABAAYEBABCAEIACAABAAmst0K/8QgABBMFASkA AQARAAEACay3QiK9CQACKSAMAAgAAQAHBAQAQgBCAA== --=-h51vAuHZpi8mWDY4WkFv--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1119334445.972.17.camel>