From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 9 00:59:25 2010 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0418B106566B for ; Tue, 9 Nov 2010 00:59:25 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id AE5638FC0A for ; Tue, 9 Nov 2010 00:59:24 +0000 (UTC) Received: by yxn35 with SMTP id 35so396377yxn.13 for ; Mon, 08 Nov 2010 16:59:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=6lZuFy4iDH2fVritZDiqrLlMfc26U2MEhzh3w7Sx0Qk=; b=gc5hhDxWQdZouJ+9w097z4HYVlYAtO7fxAWO3/w3+T3cWw2Uk4rHzrfvOJUIQvNTGb JLv+mMDBlnzadoHWWSYpYmDI5wIVuNIEx8G0YtoErqMj66ofppYz5lXGr4vy+FVPKWBW 44NXQMPE6CgP4hE6KhwYZdvP1ddYp/te1OQs4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=dXrDzMRt8942PXHNelFjNbVMDWb24m5AUTZRCP4v6CXkFFQr4OGxhLechT3un8ZnLv gbtqrEBoSbFttp+XHESj+lhpfMX7juxLCJRcPwqNEFydf6y4tACQ2fooKEbPhHnLh+1o qFrdy7HtTeZMpmwXEMaXZcbN+bh7zj1WK8VKw= MIME-Version: 1.0 Received: by 10.42.226.72 with SMTP id iv8mr4395204icb.116.1289264363646; Mon, 08 Nov 2010 16:59:23 -0800 (PST) Received: by 10.231.207.14 with HTTP; Mon, 8 Nov 2010 16:59:23 -0800 (PST) In-Reply-To: References: <06b90815b84b40625e37317bc16b13ec@ringofsaturn.com> <8647f55a4e8dcce33036a0810564b9e0@ringofsaturn.com> Date: Mon, 8 Nov 2010 16:59:23 -0800 Message-ID: From: Maksim Yevmenkin To: rnejdl@ringofsaturn.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-bluetooth@freebsd.org Subject: Re: Troubleshooting a USB Bluetooth Dongle 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: Tue, 09 Nov 2010 00:59:25 -0000 Rusty, i've got something for you to test. could you please download fw driver package from http://people.freebsd.org/~emax/ath3k.tar.gz this package contains two drivers: 1) ath3k-1 -- driver to hold ath3k-1.fw image (obtained from fedora) 2) ubtath3kfw -- fw download driver you need to build both drivers from source. after you untar the package, please execute % make depend % make if everything goes well, you should have .ko files in both directories. please kldload both modules, i.e. # make -C ath3k-1/ load # make -C ubtath3kfw/ load then you need to load ng_ubt(4) module, i.e. # kldload ng_ubt now you should be able to attach your dongle and after few seconds ng_ubt(4) should pick it up, i.e. i have in my /var/log/messages Nov 8 16:46:02 beetle kernel: ugen2.2: at usbus2 Nov 8 16:46:02 beetle kernel: ubtath3kfw0: on usbus2 Nov 8 16:46:03 beetle kernel: ugen2.2: at usbus2 (disconne= cted) Nov 8 16:46:03 beetle kernel: ubtath3kfw0: at uhub2, port 1, addr 2 (disconnected) Nov 8 16:46:06 beetle kernel: ugen2.2: at usbus2 Nov 8 16:46:06 beetle kernel: ubt0: on usbus2 Nov 8 16:46:06 beetle root: Unknown USB device: vendor 0x0cf3 product 0x3002 bus uhub2 after that you should be able to use it as regular bluetooth dongle. thank you very much for providing the hardware. please let me know if you need it back. thanks, max On Tue, Nov 2, 2010 at 2:54 PM, Rusty Nejdl wrote= : > On Tue, 2 Nov 2010 14:29:06 -0700, Maksim Yevmenkin wrote: > > On Tue, Nov 2, 2010 at 2:18 PM, Rusty Nejdl wro= te: > > On Tue, 2 Nov 2010 13:36:56 -0700, Maksim Yevmenkin wrote: > > Hello, > > I am trying to find a working bluetooth dongle or get the one I have > working. I purchased a =EF=BB=BFASUS USB-BT211 [1] which is cheap but is = not > picked up by FreeBSD. All of the bluetooth devices mentioned on the > website are not manufactured any more and I was hoping to be able to > utilize something more recent. So, if anyone can recommend a recent > device like the above or how I can assist in troubleshooting the device > I purchased, I would appreciate any feedback. > > i assume that you have kldload(8)ed ng_ubt(4) driver, correct? > > if you did, and it still does not work, then could you please dump usb > descriptor for the device? quick google search suggests that at least > some of those adapters are based on atheros ar3011 chip (vendor/device > id 0x0cf3/0x3000) , and require firmware download. basically, very > similar to a certain broadcom chip, for which we have ubtbcmfw(4) > driver. > > [...] > > thanks for the information > > =EF=BB=BFNov 2 16:08:02 tethys root: Unknown USB device: vendor 0x0cf3 p= roduct > 0x3000 bus uhub8 > Nov 2 16:08:02 tethys kernel: ugen3.3: at usbus3 > > Which doesn't give me much. Doing a config dump: > > i disagree :) it gives you vendor/device id pair which is > 0x0cf3/0x3000. in other words, your adapter is based on atheros ar3011 > chip and will require a special (new) driver that would download > firmware. ubtbcmfw(4) will not work, because its for broadcom chip. i > only mentioned this because it would be similar, but not the same :) > > [...] > > So, any suggestions on where to go next? > > 1) need to write a special ubtathfw(4) driver; > > 2) obtain firmware (i assume it would be on a cd that came with the dongl= e); > > the good thing is that linux 2.6.33.7 kernel already has firmware > driver, so, it makes it easier to port. i can probably take a stab at > it, but, without device, you would have to test it (and likely to > crash your machine several times :) are you up for it? > > thanks, > max > > Max, > > Well, I have 3 different options: > > 1) Sure, I would be happy to test. > > 2) I am also testing out USB Pass through into VirtualBox and so can do s= ome > sandbox testing there. > > 3) I would be happy to order one and have it sent your way if you would > like. Just let me know your address. > > Thanks! > Rusty Nejdl