Date: Tue, 21 Jun 2005 06:30:25 -0500 From: Eric Anderson <anderson@centtech.com> To: vova@fbsd.ru Cc: bluetooth <bluetooth@freebsd.org> Subject: Re: Problem with Logitech Mx900 again Message-ID: <42B7FA51.9030206@centtech.com> In-Reply-To: <1119334445.972.17.camel@localhost> References: <1119297124.1045.11.camel@localhost> <42B72DC4.2090104@savvis.net> <1119334445.972.17.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
Vladimir Grebenschikov wrote: > =D0=92 =D0=BF=D0=BD, 20/06/2005 =D0=B2 13:57 -0700, Maksim Yevmenkin =D0= =BF=D0=B8=D1=88=D0=B5=D1=82: >=20 >>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=20 >>using on your notebook? >=20 >=20 > Mostly 6-CURRENT :-), with FreeBSD NG bluetooth stack and userland > from /usr/src/usr.sbin/bluetooth/. >=20 > Sometimes Native WinXP Home, with Sony BluespaceNE bluetooth software. >=20 >=20 >>>It does not work in bot WinXP and FreeBSD (works for both before), but= =20 >>>it still works with native cradle. >> >>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= )? >=20 >=20 > 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). >=20 >=20 >>>Nothing was changed in notebook, nothing in FreeBSD kernel/userland wh= en >>>problem arise. >> >>ok >> >> >>>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 >> >>that is a strange sequence number, but i do not think this is your prob= lem. >=20 >=20 >=20 > 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. >=20 >=20 >>># bthidd -d >>>bthidd[1486]: Opening outbound session for 00:07:61:17:9b:27 (new_devi= ce=3D1, reconnect_initiate=3D1) >>>bthidd[1486]: Could not connect to 00:07:61:17:9b:27. Socket is not co= nnected (57) >> >>not good. >> >> >>>(cp /dev/null /var/db/bthidd.hids, before, all possible reset and reco= nnects on mouse initiated) >> >>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. >=20 >=20 > Yes, I've tried to remove batteries, even for some days (this I meant > under "all possible resets"). Have you tried *replacing* the batteries? I had this same thing happen, = when my batteries were on the edge of life. I replaced them, and voila! = it works perfectly again. Eric --=20 ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology A lost ounce of gold may be found, a lost moment of time never. ------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42B7FA51.9030206>