From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 9 17:38:44 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1151616A420 for ; Wed, 9 Nov 2005 17:38:44 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22FB843D4C for ; Wed, 9 Nov 2005 17:38:43 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jA9HceJ13945; Wed, 9 Nov 2005 12:38:41 -0500 Message-ID: <4372341F.1020702@savvis.net> Date: Wed, 09 Nov 2005 09:38:39 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vladimir Grebenschikov References: <43519460.1090605@ebs.gr> <1129491219.1616.18.camel@localhost> <4353DBBC.2000508@savvis.net> <1131433259.1164.7.camel@localhost> <4370E826.7090007@savvis.net> <1131477683.1231.12.camel@localhost> <1131480921.1155.5.camel@localhost> In-Reply-To: <1131480921.1155.5.camel@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2005 17:38:44 -0000 Vladimir, > I have found the reason, it was really after make world > After turning off console pixel-mode I've see: [...] > /libexec/ld-elf.so.1: Shared object "libbluetooth.so.1" not found, required by " > bthidd" ok > After rebuilding bthidd and bthidcontrol it start work. > But, I still does understand why it starts ok with manual start after boot. > >>Probably something wrong with drivers, I've notice that ng bluetooth >>mice is disconnected without any notice. >> >>Reconnecting usb bluetooth device lead to following error: >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 >>ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 >>ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; >>wMaxPacketSize=49; nframes=6, buffer size=294 >>ng_ubt_connect: ubt0 - Could not start interrupt transfer. NOMEM (5) the drivers have not changed for a long time. perhaps something wrong with usb? the message above clearly says that driver was attempting to start interrupt transfer, but it failed (with strange NOMEM error). >>And after that error bt stack does not work until reboot, reconnecting >>dongle does not helps. >> >>Boot scenario was: >>booting >>... >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 >>ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 >>ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; >>wMaxPacketSize=49; nframes=6, buffer size=294 >>Timecounter "TSC" frequency 1686969804 Hz quality 800 >>... >>Trying to mount root from ufs:/dev/ad0s4a >>WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() >>WARNING: attempt to net_add_domain(netgraph) after domainfinalize() >>... >>there bthidd started but does not connect mice. >> >>I have turned on-board bt off, then on by notebook switch. >>kernel printed: >>ubt_bulk_in_complete2: ubt0 - Bulk-in xfer failed, IOERROR (13). No new xfer will be submitted! >>ubt_intr_complete2: ubt0 - Interrupt xfer failed, IOERROR (13). No new xfer will be submitted! >>ubt0: at uhub2 port 2 (addr 2) disconnected >>ubt0: detached >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 >>ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 >>ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, buffer size=294 >>kbd2 at vkbd0 >> >>BT mice start work here. >>after some hours of work it stop moving and l2pings also. >> >>Trying restart BT stack lead to error: >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 >>ubt0: ALPS UGX, rev 1.10/7.81, addr 2 >>ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 >>ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; >>wMaxPacketSize=49; nframes=6, buffer size=294 >>ng_ubt_connect: ubt0 - Could not start interrupt transfer. NOMEM (5) again you get all sorts of errors back from usb. this is _not_ driver's fault. i have to check what NOMEM really means and get back to you. thanks, max