From owner-freebsd-bluetooth@FreeBSD.ORG Wed May 4 05:02:48 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 9CCAF16A4CE for ; Wed, 4 May 2005 05:02:48 +0000 (GMT) Received: from mta9.adelphia.net (mta9.adelphia.net [68.168.78.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01B6D43D75 for ; Wed, 4 May 2005 05:02:48 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [192.168.1.254] (really [70.32.199.60]) by mta9.adelphia.net (InterMail vM.6.01.04.01 201-2131-118-101-20041129) with ESMTP id <20050504050247.CHUF8952.mta9.adelphia.net@[192.168.1.254]>; Wed, 4 May 2005 01:02:47 -0400 Message-ID: <4278578F.8070006@savvis.net> Date: Tue, 03 May 2005 22:03:11 -0700 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <4278433E.3050006@centtech.com> In-Reply-To: <4278433E.3050006@centtech.com> 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 05:02:48 -0000 [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. thanks, max