From owner-freebsd-bluetooth@FreeBSD.ORG Wed May 4 13:23:04 2005 Return-Path: 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 6EDB716A542 for ; Wed, 4 May 2005 13:23:04 +0000 (GMT) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6995F43D86 for ; Wed, 4 May 2005 13:23:03 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id j44DMjsI099038; Wed, 4 May 2005 08:22:45 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4278CCA3.5080406@centtech.com> Date: Wed, 04 May 2005 08:22:43 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050325 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Maksim Yevmenkin References: <4278433E.3050006@centtech.com> <4278578F.8070006@savvis.net> In-Reply-To: <4278578F.8070006@savvis.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-bluetooth@freebsd.org Subject: Re: Bluetooth device broken X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 May 2005 13:23:04 -0000 Maksim Yevmenkin wrote: > [moved to bluetooth@] > > Eric, > >> I'm trying to get the internal Bluetooth adapter in my Dell D610 >> working. I see these messages on boot: >> >> ubt0: vendor 0x413c product 0x8103, rev 2.00/16.57, addr 2 >> ubt0: vendor 0x413c product 0x8103, rev 2.00/16.57, 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 > > > that looks just fine to me. the usb device has been recognized and it > does seem to have all required usb interfaces/endpoints. > >> start_init: trying /sbin/init >> WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() >> WARNING: attempt to net_add_domain(netgraph) after domainfinalize() > > > those are harmless, imo. i have those too. > >> Partial output from usbdevs -v: >> Controller /dev/usb1: >> addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), >> Intel(0x0000), rev 1.00 >> port 1 addr 2: full speed, self powered, config 1, product >> 0x8103(0x8103), vendor 0x413c(0x413c), rev 16.57 > > > that looks fine too > >> Do I just need to add the device info in a table somewhere, or are >> there other issues (from the 'attempt to net_add_domain...' stuff)? > > > why do you think your bluetooth device is broken? the fact that you do > not see human readable name for your device's manufacturer/name does not > mean that the device will not work. > > and, yes, if you want to see human readable names you need to add > manufacturer (vendor) id and product id to the /sys/dev/usb/usbdevfs file. Hmm.. I guess I should have tried it with the tools again. I tried this a weeks or two ago, and it would never create a ubt0 device for me to use, but now it works. (I've updated several times since then). Sorry for the false alarm!! I guess it was fixed and I didn't realize it! Now that's good service!! :) Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology A lost ounce of gold may be found, a lost moment of time never. ------------------------------------------------------------------------