From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 8 11:06:53 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 D29BE1065673 for ; Mon, 8 Nov 2010 11:06:53 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A51478FC25 for ; Mon, 8 Nov 2010 11:06:53 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oA8B6rHj088038 for ; Mon, 8 Nov 2010 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oA8B6rvS088036 for freebsd-bluetooth@FreeBSD.org; Mon, 8 Nov 2010 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 8 Nov 2010 11:06:53 GMT Message-Id: <201011081106.oA8B6rvS088036@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-bluetooth@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-bluetooth@FreeBSD.org 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: Mon, 08 Nov 2010 11:06:53 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- p kern/140590 bluetooth [bluetooth] ng_ubt(4) ng_l2cap_process_cmd_rej warning 1 problem total. 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 From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 9 02:33:38 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 42407106566B for ; Tue, 9 Nov 2010 02:33:38 +0000 (UTC) (envelope-from rnejdl@ringofsaturn.com) Received: from tethys.ringofsaturn.com (tethys.ringofsaturn.com [71.252.219.43]) by mx1.freebsd.org (Postfix) with ESMTP id E08798FC1C for ; Tue, 9 Nov 2010 02:33:37 +0000 (UTC) Received: from ASSP.nospam (tethys [71.252.219.43]) (authenticated bits=0) by tethys.ringofsaturn.com (8.14.4/8.14.4) with ESMTP id oA92Xaub093456; Mon, 8 Nov 2010 20:33:36 -0600 (CST) (envelope-from rnejdl@ringofsaturn.com) Received: from mail.ringofsaturn.com ([71.252.219.43] helo=mail.ringofsaturn.com) with IPv4:25 by ASSP.nospam; 8 Nov 2010 20:33:35 -0600 MIME-Version: 1.0 Date: Mon, 08 Nov 2010 20:33:35 -0600 From: Rusty Nejdl To: Maksim Yevmenkin In-Reply-To: References: <06b90815b84b40625e37317bc16b13ec@ringofsaturn.com> <8647f55a4e8dcce33036a0810564b9e0@ringofsaturn.com> Message-ID: <769713d670c5ad3db58c276b0e6e81a9@ringofsaturn.com> X-Sender: rnejdl@ringofsaturn.com User-Agent: RoundCube Webmail/0.5-trunk X-Assp-Version: 1.7.5.7(1.0.07) on ASSP.nospam X-Assp-Intended-For-IP: 71.252.219.43 X-Assp-Passing: authenticated X-Assp-ID: ASSP.nospam 70016-11573 X-Assp-Envelope-From: rnejdl@ringofsaturn.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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 Reply-To: rnejdl@ringofsaturn.com 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 02:33:38 -0000 Maksim, Well, that didn't quite go right: [tethys]:/home/rnejdl/Downloads/ath3k> sudo make -C ath3k-1/ load /sbin/kldload -v /home/rnejdl/Downloads/ath3k/ath3k-1/ath3k-1.ko kldload: can't load /home/rnejdl/Downloads/ath3k/ath3k-1/ath3k-1.ko: Exec format error*** Error code 1 Stop in /home/rnejdl/Downloads/ath3k/ath3k-1. Exit 1 [tethys]:/home/rnejdl/Downloads/ath3k> sudo make -C ubtath3kfw/ load /sbin/kldload -v /home/rnejdl/Downloads/ath3k/ubtath3kfw/ubtath3kfw.ko kldload: can't load /home/rnejdl/Downloads/ath3k/ubtath3kfw/ubtath3kfw.ko: Exec format error*** Error code 1 Stop in /home/rnejdl/Downloads/ath3k/ubtath3kfw. Exit 1 [tethys]:/home/rnejdl/Downloads/ath3k> I am running: uname -aFreeBSD tethys.ringofsaturn.com 8.1-STABLE FreeBSD 8.1-STABLE #0: Tue Oct 19 14:09:00 CDT 2010 root@tethys.ringofsaturn.com:/usr/obj/usr/src/sys/SATURN amd64 I can update my kernel if needed or move the above sources into the kernel directory as needed. This is from dmesg: KLD ath3k-1.ko: depends on kernel - not available or version mismatch linker_load_file: Unsupported file type KLD ubtath3kfw.ko: depends on kernel - not available or version mismatch linker_load_file: Unsupported file type KLD ath3k-1.ko: depends on kernel - not available or version mismatch linker_load_file: Unsupported file type KLD ubtath3kfw.ko: depends on kernel - not available or version mismatch linker_load_file: Unsupported file type KLD ath3k-1.ko: depends on kernel - not available or version mismatch linker_load_file: Unsupported file type KLD ubtath3kfw.ko: depends on kernel - not available or version mismatch linker_load_file: Unsupported file type And, you can keep the hardware and hopefully make some good use out of it. Thanks! Rusty On Mon, 8 Nov 2010 16:59:23 -0800, Maksim Yevmenkin wrote: > 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 [2] > > 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 (disconnected) > 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 wrote: 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 ASUS 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 Nov 2 16:08:02 tethys root: Unknown USB device: vendor 0x0cf3 product 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 dongle); 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 some 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 Links: ------ [1] mailto:rnejdl@ringofsaturn.com [2] http://people.freebsd.org/~emax/ath3k.tar.gz [3] mailto:rnejdl@ringofsaturn.com From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 9 02:37:55 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 1AD42106566B for ; Tue, 9 Nov 2010 02:37:55 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id CFD968FC18 for ; Tue, 9 Nov 2010 02:37:54 +0000 (UTC) Received: by iwn39 with SMTP id 39so6980576iwn.13 for ; Mon, 08 Nov 2010 18:37:54 -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=d7pIsdjmh3Tr0GSg3E4eSsaHPW35u1bGIiCeiZq5Cjs=; b=m9HcxOoCCUxKc1PDIB/FO1HPCb05vconFKYrZZ3UG8Je/8/AOBlc3eFyQFJL0L6uAF ZIz4KdsmsuQd+BWqi888tIb6w6bT9y33ZYyQwTT6Hez04wTT1P9hFmiMhSSqNyzZtUeT 3bjSvaVHJI5J0uhVJ4GA7YeYJiFx/Bg9vEqTU= 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=UQH2RaqKn/GX2WamlRWJAWNqWeVpJY8M0/T5HxCq6wrPk9fp/873RBqzBT/olDcsoc AbMxGK65HbJkBgzLeLJF9X4oUjdQXlX3ygJor6kXPZt3PLTRwvitnM8YsVLMeuUNqaTf 7v4Bhek8406Ow8rQvmh5C1sQqZ3bwzCGZcsVA= MIME-Version: 1.0 Received: by 10.231.14.136 with SMTP id g8mr4616875iba.188.1289270273965; Mon, 08 Nov 2010 18:37:53 -0800 (PST) Received: by 10.231.207.14 with HTTP; Mon, 8 Nov 2010 18:37:53 -0800 (PST) In-Reply-To: <769713d670c5ad3db58c276b0e6e81a9@ringofsaturn.com> References: <06b90815b84b40625e37317bc16b13ec@ringofsaturn.com> <8647f55a4e8dcce33036a0810564b9e0@ringofsaturn.com> <769713d670c5ad3db58c276b0e6e81a9@ringofsaturn.com> Date: Mon, 8 Nov 2010 18:37:53 -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 02:37:55 -0000 it looks like your kernel sources have changed since the time you have built the kernel. please re-build kernel and all the modules using the same source tree. thanks, max On Mon, Nov 8, 2010 at 6:33 PM, Rusty Nejdl wrote= : > Maksim, > > Well, that didn't quite go right: > > =EF=BB=BF[tethys]:/home/rnejdl/Downloads/ath3k> sudo make -C ath3k-1/ loa= d > > /sbin/kldload -v /home/rnejdl/Downloads/ath3k/ath3k-1/ath3k-1.ko > > kldload: can't load /home/rnejdl/Downloads/ath3k/ath3k-1/ath3k-1.ko: Exec > format error*** Error code 1 > Stop in /home/rnejdl/Downloads/ath3k/ath3k-1. > > Exit 1 > > [tethys]:/home/rnejdl/Downloads/ath3k> sudo make -C ubtath3kfw/ load > > /sbin/kldload -v /home/rnejdl/Downloads/ath3k/ubtath3kfw/ubtath3kfw.ko > > kldload: can't load /home/rnejdl/Downloads/ath3k/ubtath3kfw/ubtath3kfw.ko= : > Exec format error*** Error code 1 > Stop in /home/rnejdl/Downloads/ath3k/ubtath3kfw. > > Exit 1 > > [tethys]:/home/rnejdl/Downloads/ath3k> > > I am running: > > =EF=BB=BFuname -aFreeBSD tethys.ringofsaturn.com 8.1-STABLE FreeBSD 8.1-S= TABLE #0: > Tue Oct 19 14:09:00 CDT 2010 > root@tethys.ringofsaturn.com:/usr/obj/usr/src/sys/SATURN =C2=A0amd64 > > I can update my kernel if needed or move the above sources into the kerne= l > directory as needed. =C2=A0This is from dmesg: > > =EF=BB=BFKLD ath3k-1.ko: depends on kernel - not available or version mis= match > linker_load_file: Unsupported file type > KLD ubtath3kfw.ko: depends on kernel - not available or version mismatch > linker_load_file: Unsupported file type > KLD ath3k-1.ko: depends on kernel - not available or version mismatch > linker_load_file: Unsupported file type > KLD ubtath3kfw.ko: depends on kernel - not available or version mismatch > linker_load_file: Unsupported file type > KLD ath3k-1.ko: depends on kernel - not available or version mismatch > linker_load_file: Unsupported file type > KLD ubtath3kfw.ko: depends on kernel - not available or version mismatch > linker_load_file: Unsupported file type > > And, you can keep the hardware and hopefully make some good use out of it= . > > Thanks! > Rusty > > On Mon, 8 Nov 2010 16:59:23 -0800, Maksim Yevmenkin wrote: > > 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 (disconnected) > 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 wro= te: > > 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 > > From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 9 18:04:19 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 2E065106566C for ; Tue, 9 Nov 2010 18:04:19 +0000 (UTC) (envelope-from rnejdl@ringofsaturn.com) Received: from tethys.ringofsaturn.com (tethys.ringofsaturn.com [71.252.219.43]) by mx1.freebsd.org (Postfix) with ESMTP id E69D68FC15 for ; Tue, 9 Nov 2010 18:04:18 +0000 (UTC) Received: from ASSP.nospam (tethys [71.252.219.43]) (authenticated bits=0) by tethys.ringofsaturn.com (8.14.4/8.14.4) with ESMTP id oA9I4Ihl007808; Tue, 9 Nov 2010 12:04:18 -0600 (CST) (envelope-from rnejdl@ringofsaturn.com) Received: from mail.ringofsaturn.com ([71.252.219.43] helo=mail.ringofsaturn.com) with IPv4:25 by ASSP.nospam; 9 Nov 2010 12:04:17 -0600 MIME-Version: 1.0 Date: Tue, 09 Nov 2010 12:04:17 -0600 From: Rusty Nejdl To: Maksim Yevmenkin In-Reply-To: References: <06b90815b84b40625e37317bc16b13ec@ringofsaturn.com> <8647f55a4e8dcce33036a0810564b9e0@ringofsaturn.com> <769713d670c5ad3db58c276b0e6e81a9@ringofsaturn.com> Message-ID: <3cd2d26577db0aa6059db495c104d382@ringofsaturn.com> X-Sender: rnejdl@ringofsaturn.com User-Agent: RoundCube Webmail/0.5-trunk X-Assp-Version: 1.7.5.7(1.0.07) on ASSP.nospam X-Assp-Intended-For-IP: 71.252.219.43 X-Assp-Passing: authenticated X-Assp-ID: ASSP.nospam 25858-07160 X-Assp-Envelope-From: rnejdl@ringofsaturn.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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 Reply-To: rnejdl@ringofsaturn.com 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 18:04:19 -0000 Max, First, thank you so much for the work you did. After syncing everything up, I was able to get my bluetooth dongle to work. Oddly enough, I have to stop and then start /etc/rc.d/bluetooth to get it to work but that may be because I didn't completely clean out my first attempt. I was able to get my headset to pair : [tethys]:/dev> sudo hccontrol -n ubt0hci create_connection 01:23:45:67:89:84 BD_ADDR: 01:23:45:67:89:84 Connection handle: 21 Encryption mode: Disabled [0] hcsecd[6558]: Got PIN_Code_Request event from 'ubt0hci', remote bdaddr 01:23:45:67:89:84 hcsecd[6558]: Found matching entry, remote bdaddr 01:23:45:67:89:84, name 'AS1', PIN code exists hcsecd[6558]: Sending PIN_Code_Reply to 'ubt0hci' for remote bdaddr 01:23:45:67:89:84 hcsecd[6558]: Got Link_Key_Notification event from 'ubt0hci', remote bdaddr 01:23:45:67:89:84 hcsecd[6558]: Updating link key for the entry, remote bdaddr 01:23:45:67:89:84, name 'AS1', link key doesn't exist However, how do I get audio to actually output through the headset is the question? My apologies if this is an obvious question but I wasn't able to find much on this and in fact found threads going back to 2005. Sincerely, Rusty Nejdl On Mon, 8 Nov 2010 18:37:53 -0800, Maksim Yevmenkin wrote: > it looks like your kernel sources have changed since the time you have > built the kernel. please re-build kernel and all the modules using the > same source tree. > > thanks, > max > > On Mon, Nov 8, 2010 at 6:33 PM, Rusty Nejdl wrote: >> Maksim, Well, that didn't quite go right: [tethys]:/home/rnejdl/Downloads/ath3k> sudo make -C ath3k-1/ load /sbin/kldload -v /home/rnejdl/Downloads/ath3k/ath3k-1/ath3k-1.ko kldload: can't load /home/rnejdl/Downloads/ath3k/ath3k-1/ath3k-1.ko: Exec format error*** Error code 1 Stop in /home/rnejdl/Downloads/ath3k/ath3k-1. Exit 1 [tethys]:/home/rnejdl/Downloads/ath3k> sudo make -C ubtath3kfw/ load /sbin/kldload -v /home/rnejdl/Downloads/ath3k/ubtath3kfw/ubtath3kfw.ko kldload: can't load /home/rnejdl/Downloads/ath3k/ubtath3kfw/ubtath3kfw.ko: Exec format error*** Error code 1 Stop in /home/rnejdl/Downloads/ath3k/ubtath3kfw. Exit 1 [tethys]:/home/rnejdl/Downloads/ath3k> I am running: uname -aFreeBSD tethys.ringofsaturn.com 8.1-STABLE FreeBSD 8.1-STABLE #0: Tue Oct 19 14:09:00 CDT 2010 root@tethys.ringofsaturn.com [1]:/usr/obj/usr/src/sys/SATURN amd64 I can update my kernel if needed or move the above sources into the kernel directory as needed. This is from dmesg: KLD ath3k-1.ko: depends on kernel - not available or version mismatch linker_load_file: Unsupported file type KLD ubtath3kfw.ko: depends on kernel - not available or version mismatch linker_load_file: Unsupported file type KLD ath3k-1.ko: depends on kernel - not available or version mismatch linker_load_file: Unsupported file type KLD ubtath3kfw.ko: depends on kernel - not available or version mismatch linker_load_file: Unsupported file type KLD ath3k-1.ko: depends on kernel - not available or version mismatch linker_load_file: Unsupported file type KLD ubtath3kfw.ko: depends on kernel - not available or version mismatch linker_load_file: Unsupported file type And, you can keep the hardware and hopefully make some good use out of it. Thanks! Rusty On Mon, 8 Nov 2010 16:59:23 -0800, Maksim Yevmenkin wrote: 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 [2] 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 (disconnected) 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 wrote: 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 ASUS 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 Nov 2 16:08:02 tethys root: Unknown USB device: vendor 0x0cf3 product 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 dongle); 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 some 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 Links: ------ [1] mailto:root@tethys.ringofsaturn.com [2] http://people.freebsd.org/~emax/ath3k.tar.gz [3] mailto:rnejdl@ringofsaturn.com [4] mailto:rnejdl@ringofsaturn.com [5] mailto:rnejdl@ringofsaturn.com From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 9 18:19:43 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 401E410656A3 for ; Tue, 9 Nov 2010 18:19:43 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 007948FC1C for ; Tue, 9 Nov 2010 18:19:42 +0000 (UTC) Received: by iwn39 with SMTP id 39so7910950iwn.13 for ; Tue, 09 Nov 2010 10:19:42 -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; bh=sxGpIGap+/5R8O25V802t7qkvsE3SEa7xYl9pD8OMg4=; b=QKYPm9EIniREk6qvwopQzsxdeLbfJlgwc5im7W5bx+bmFyMxIA+AmhecJrZ3+2ziQm m2ocdiJVGk39i5IHHCDeBHFe38zd34GmTLfWUOf54b22CIpqKVNE77SqMxQ0crOdyvSb WuB3UcKW7Co9IR1DB+P+p6BA2eazVBLagbrQY= 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; b=svrdZzhlyKUJhw4+RhpuGzmeqeWfW3iU7LjLKlyaxbuCaTJ7hxWeyvTOm+J6wzQL85 ovTsxvqhj02kWeH9KLAOcZYJ6Uee47mbna89Y5x1dlfXMVeYMRk1hhxqzffzKoP3PZOz ihubNPC6cIBW0+Kwww68MuXWS8TKC3FvhuXSY= MIME-Version: 1.0 Received: by 10.231.16.67 with SMTP id n3mr5420588iba.113.1289326769136; Tue, 09 Nov 2010 10:19:29 -0800 (PST) Received: by 10.231.207.14 with HTTP; Tue, 9 Nov 2010 10:19:29 -0800 (PST) In-Reply-To: <3cd2d26577db0aa6059db495c104d382@ringofsaturn.com> References: <06b90815b84b40625e37317bc16b13ec@ringofsaturn.com> <8647f55a4e8dcce33036a0810564b9e0@ringofsaturn.com> <769713d670c5ad3db58c276b0e6e81a9@ringofsaturn.com> <3cd2d26577db0aa6059db495c104d382@ringofsaturn.com> Date: Tue, 9 Nov 2010 10:19:29 -0800 Message-ID: From: Maksim Yevmenkin To: rnejdl@ringofsaturn.com Content-Type: text/plain; charset=ISO-8859-1 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 18:19:43 -0000 Rusty, > First, thank you so much for the work you did. After syncing everything up, > I was able to get my bluetooth dongle to work. you are welcome :) i'm glad it worked for you :) and, once again, thanks for your hardware donation. > Oddly enough, I have to stop > and then start /etc/rc.d/bluetooth to get it to work but that may be because > I didn't completely clean out my first attempt. that's interesting... that should not be happening. does it happen all the time, or, did it happen just once? [...] > However, how do I get audio to actually output through the headset is the > question? My apologies if this is an obvious question but I wasn't able to > find much on this and in fact found threads going back to 2005. ahh... that's completely different (and long) story :) in short, freebsd still does not have full support for bluetooth audio :( that includes both real bluetooth audio (i.e. sco) and bluetooth audio that uses l2cap (i.e. a2dp). i kinda started to work on sco and put some preliminary code out there, but got distracted by $real_job. someone recently asked about a2dp, but not sure where it went from there. sorry to give you bad news thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 9 22:05:08 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 2C2CA1065696 for ; Tue, 9 Nov 2010 22:05:08 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id E46038FC21 for ; Tue, 9 Nov 2010 22:05:07 +0000 (UTC) Received: by iwn39 with SMTP id 39so8115413iwn.13 for ; Tue, 09 Nov 2010 14:05:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:cc:content-type; bh=YjiRw86JjPP/sfHrhpgzWKacOgAZJ77j+zTu7MpHPUY=; b=aBdhygjoaRwG50M8kqYKrnws1eHbtquPXuUKeP0utvBkrIVFiyEfWkJaMcHzeDEqwl 9mSOuJgNe8PSxy2AHJDa5T2/GS9P/1WK80rxzAUQZ0X5XTYM774HmOei+oaTkiLeTnNw uPqR4uOcqmrj6OTO7eYh3n6EzjTh3wrlL/Dqo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=DXjg0/jpcsmggPIfDkDwKFF/OVoT3pl2gKcj4FYik2Ujc6IDzeimmqMRbasDAxGu7x f5tntkJx9L++iV51EcnxTNxtpH0evAiEc+AFm5tK5gHkzi9XcoKCkuLh+wZ/q+uQ8GQC AGgzgj6Oc2MzuxGbZs75MLMeLctlUSv+YREJc= MIME-Version: 1.0 Received: by 10.231.167.146 with SMTP id q18mr5690968iby.163.1289340306315; Tue, 09 Nov 2010 14:05:06 -0800 (PST) Received: by 10.231.207.14 with HTTP; Tue, 9 Nov 2010 14:05:06 -0800 (PST) Date: Tue, 9 Nov 2010 14:05:06 -0800 Message-ID: From: Maksim Yevmenkin To: freebsd-bluetooth@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: [RFC] firmware downloader for atheros ar3011 based usb bluetooth devices 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 22:05:08 -0000 dear freebsd-bluetooth@ users, i'd like to request feedback/comments/etc. on a firmware downloader for atheros ar3011 based usb bluetooth devices. there are actually a couple of versions available: (1) kernel-based version. it includes a couple of kernel modules: one to hold firmware image and another to download it. it can be located at http://people.freebsd.org/~emax/ath3k.tar.gz (2) userspace-based version. basically it is a userspace tool that is invoked from devd(8) and uses libusb20(3) and ugen(4) interfaces to download the firmware. it can be located at http://people.freebsd.org/~emax/ath3kfw.tar.gz both seems to work for me. but, i'm leaning towards userspace option :) once again, options (1) and (2) are mutually exclusive, so, please, only try one at a time :) please take a look, try it out and let me know if it works. i'll probably commit something towards the end of the week. i also would like to thank Rusty Nejdl for donating hardware (ASUS USB-BT211 http://www.newegg.com/Product/Product.aspx?Item=N82E16833320057 dongle). this dongle has an awesome form factor :) its pretty darn small :) thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 10 15:52:28 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 DFABE1065672 for ; Wed, 10 Nov 2010 15:52:28 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5CFAA8FC1C for ; Wed, 10 Nov 2010 15:52:28 +0000 (UTC) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id oAAFqBkM055492; Wed, 10 Nov 2010 16:52:26 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id oAAFqBem055491; Wed, 10 Nov 2010 16:52:11 +0100 (CET) (envelope-from olli) Date: Wed, 10 Nov 2010 16:52:11 +0100 (CET) Message-Id: <201011101552.oAAFqBem055491@lurza.secnetix.de> From: Oliver Fromme To: freebsd-bluetooth@FreeBSD.ORG, maksim.yevmenkin@gmail.com In-Reply-To: X-Newsgroups: list.freebsd-bluetooth User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.4-PRERELEASE-20080904 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.3.5 (lurza.secnetix.de [127.0.0.1]); Wed, 10 Nov 2010 16:52:26 +0100 (CET) Cc: Subject: Re: [RFC] firmware downloader for atheros ar3011 based usb bluetooth ?devices X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-bluetooth@FreeBSD.ORG, maksim.yevmenkin@gmail.com List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Nov 2010 15:52:29 -0000 Maksim Yevmenkin wrote: > i'd like to request feedback/comments/etc. on a firmware downloader > for atheros ar3011 based usb bluetooth devices. > > there are actually a couple of versions available: > > (1) kernel-based version. [...] > (2) userspace-based version. [...] > > both seems to work for me. but, i'm leaning towards userspace option Me too. I think if something can be done in userland, then it should be done that way, be it just for the reason that a bug will likely result in a coredump instead of a panic. ;-) > i also would like to thank Rusty Nejdl for donating hardware (ASUS > USB-BT211 http://www.newegg.com/Product/Product.aspx?Item=N82E16833320057 > dongle). this dongle has an awesome form factor :) its pretty darn > small :) My older (non-atheros) dongle has about the same size. It disappears almost completely in the USB slot; I have to use my fingernails to get it out. It looks similar to this one: http://www.pollin.de/shop/suchergebnis.html?S_TEXT=721457 Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "Being really good at C++ is like being really good at using rocks to sharpen sticks." -- Thant Tessman From owner-freebsd-bluetooth@FreeBSD.ORG Fri Nov 12 05:29:10 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 0B71A106564A for ; Fri, 12 Nov 2010 05:29:10 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id C0F288FC0C for ; Fri, 12 Nov 2010 05:29:09 +0000 (UTC) Received: by iwn39 with SMTP id 39so3063755iwn.13 for ; Thu, 11 Nov 2010 21:29:09 -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=W0Y/lf8wTnwMj7XziVZD5Wra6UBiHa18qhcIka3uCPw=; b=oFxO2Ue6vB6LUc1alumyKBafoWN8VijoOg+xlQVO4zO5pkU1kaWNTkgzMN8fhd4z+C 95+Jz55+fAR/UB+7vJzyiEi++SHySCLo2jHOi2T1ZFkWQlIoS6Dc6qzdLADgS+ZOFGhP KtQCAK17TI7+geKOYtLchy6DPPz6QHR9bIduk= 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=qr9NOKfj0wz5j9vCT+lKO9zvLn9D4iF+qwFyRoAUQ9WvDAAKzcwetBQtPVtuRckfGd VMRflreeyGBBO0rIfOlJowhKKjZbJd8XdZuwmVenJMU85KLAo9G0KWuXYejrXlNfxyyk DjB0Z40VeLF/d8mRMypT0BoXX67CBQkQZpP4k= MIME-Version: 1.0 Received: by 10.42.18.135 with SMTP id x7mr50146ica.250.1289539748553; Thu, 11 Nov 2010 21:29:08 -0800 (PST) Received: by 10.231.207.14 with HTTP; Thu, 11 Nov 2010 21:29:08 -0800 (PST) In-Reply-To: <20101112050506.GA18796@amp2.iem.pw.edu.pl> References: <64FA2044DA694411995A309FF342396C@marekdesktop> <20101112050506.GA18796@amp2.iem.pw.edu.pl> Date: Thu, 11 Nov 2010 21:29:08 -0800 Message-ID: From: Maksim Yevmenkin To: Andrzej Tobola Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-bluetooth@freebsd.org, marek_sal@wp.pl Subject: Re: Atheros bluetooth unrecognizable 0cf3:3002 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: Fri, 12 Nov 2010 05:29:10 -0000 On Thu, Nov 11, 2010 at 9:05 PM, Andrzej Tobola wrote: > > On Thu, Nov 11, 2010 at 03:43:10PM -0800, maksim yevmenkin wrote: >> Please try fw dowloader from >> Http://people.freebsd.org/~emax/ath3kfw.tar.gz > > Hello Max, > > Can't build on amd64 current: > > % make > Warning: Object directory not changed from original /tmp/ath3kfw > cc -O2 -pipe -fomit-frame-pointer -march=3Dopteron -fomit-frame-pointer -= ggdb -std=3Dgnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-un= used-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wr= eturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter= -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls= -Wold-style-definition -Wno-pointer-sign -c ath3kfw.c > cc1: warnings being treated as errors > ath3kfw.c: In function 'download_firmware': > ath3kfw.c:236: warning: format '%d' expects type 'int', but argument 4 ha= s type 'long unsigned int' > *** Error code 1 please replace %d with %lu or just comment this line. > What is a difference between ath3k-1.fw and ath3k-2.fw ? not sure. those are obtained as is from linux-firmware rpm. ath3k-1.fw works for me. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Fri Nov 12 06:37:23 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 2BB39106564A for ; Fri, 12 Nov 2010 06:37:23 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id DD5D18FC17 for ; Fri, 12 Nov 2010 06:37:22 +0000 (UTC) Received: by iwn39 with SMTP id 39so3123013iwn.13 for ; Thu, 11 Nov 2010 22:37:22 -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=o+aqHl4th7QEoIBr4TFsCyyRl9kuPCdguGZlCDV4+pA=; b=IsRjbZwHTf7fnbr50NPk+8Tqa362/UneTQ3xksXJ9mniCPeUdr6JRYm1pYqFq1P1zU A4ak/7bi5ZR/j8az3oolry8RHXrgO07DW6xJvmnexmmU5EHqNvzOdn3+wbdckDOIjZff A3ilwSjcbPk5kkoq4Ijp0SntA45UwpiGA7d28= 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=NjufjKxOE96WBxr3Q45SRYp5Ar0I48WBUMUb9yjYTIJw5ZacI/xPBe5q2GZ4r415We xvQZ1jKX7hGTm/meZanLtbqkkPIiRFoIvSQu3DlofVB2In7BkTAkf8VkoeH5nhBIMzBo 8NKV+Has4MdPhXQW6hiimriA4ZRpUacWaMPe4= MIME-Version: 1.0 Received: by 10.231.16.67 with SMTP id n3mr1502678iba.113.1289543842149; Thu, 11 Nov 2010 22:37:22 -0800 (PST) Received: by 10.231.207.14 with HTTP; Thu, 11 Nov 2010 22:37:22 -0800 (PST) In-Reply-To: <20101112062852.GA39843@amp2.iem.pw.edu.pl> References: <64FA2044DA694411995A309FF342396C@marekdesktop> <20101112050506.GA18796@amp2.iem.pw.edu.pl> <20101112062852.GA39843@amp2.iem.pw.edu.pl> Date: Thu, 11 Nov 2010 22:37:22 -0800 Message-ID: From: Maksim Yevmenkin To: Andrzej Tobola Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-bluetooth@freebsd.org, Marek Salwerowicz Subject: Re: Atheros bluetooth unrecognizable 0cf3:3002 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: Fri, 12 Nov 2010 06:37:23 -0000 On Thu, Nov 11, 2010 at 10:28 PM, Andrzej Tobola wrote: [..] > Thanks! > Seems is working: cool. thanks for trying it out. > One qestion - is it necessary to correct "product" from "0x3000" to "0x30= 02" in devd.conf ? > becasue we have: > > =A0ubt0: on usbus0 > > (I named devd.conf as ath3k.conf and put it in /etc/devd/ ) no, product id changes _after_ firmware is downloaded. at attach time device presents itself as vendor 0x0cf3 product 0x3000. > Seems that you shoud commit it! yes, i will, probably tomorrow. > =A0WARNING: attempt to domain_add(bluetooth) after domainfinalize() > How can I eliminate it ? in short - you can't. its harmless. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Fri Nov 12 14:28:36 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 BFF3D106574E for ; Fri, 12 Nov 2010 14:28:36 +0000 (UTC) (envelope-from marek_sal@wp.pl) Received: from mx4.wp.pl (mx4.wp.pl [212.77.101.8]) by mx1.freebsd.org (Postfix) with ESMTP id 4D96A8FC18 for ; Fri, 12 Nov 2010 14:28:35 +0000 (UTC) Received: (wp-smtpd smtp.wp.pl 24355 invoked from network); 12 Nov 2010 15:01:54 +0100 Received: from cwx170.internetdsl.tpnet.pl (HELO marekdesktop) (marek_sal@[83.19.131.170]) (envelope-sender ) by smtp.wp.pl (WP-SMTPD) with SMTP for ; 12 Nov 2010 15:01:54 +0100 Message-ID: From: "Marek Salwerowicz" To: Date: Fri, 12 Nov 2010 15:01:48 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-2"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5843 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-WP-AV: skaner antywirusowy poczty Wirtualnej Polski S. A. X-WP-SPAM: NO 0000000 [QbIm] X-Mailman-Approved-At: Fri, 12 Nov 2010 16:31:45 +0000 Subject: Can't l2ping to BT device 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: Fri, 12 Nov 2010 14:28:36 -0000 Hi all, 'hccontrol inquiry' discovers the device I want to connect to, but l2ping can't ping to it: vv1% hccontrol inquiry Inquiry result, num_responses=1 Inquiry result #0 BD_ADDR: FF2 Page Scan Rep. Mode: 0x1 Page Scan Period Mode: 00 Page Scan Mode: 00 Class: 00:1f:00 Clock offset: 0x77cd Inquiry complete. Status: No error [00] vv1% l2ping -a FF2 0 bytes from FF2 seq_no=0 time=5127.835 ms result=0x4 0 bytes from FF2 seq_no=1 time=5128.129 ms result=0x4 0 bytes from FF2 seq_no=2 time=5127.133 ms result=0x4 0 bytes from FF2 seq_no=3 time=5128.159 ms result=0x4 ^C vv1% it's a new pair, so I typed config in hcsecd.conf: device { bdaddr 00:06:66:00:e2:84; # 'FF2' results in syntax error, need to be MAC address name "so51-FF2"; key nokey; pin "1234"; } and then restarted hcsecd during l2ping'ing hcsecd throws only this message: hcsecd[2315]: Received unexpected HCI event, event=0xff # hcidump : vv1% # hcidump HCIDump - HCI packet analyzer ver 1.5 device: any snap_len: 65535 filter: 0xffffffffffffffff > HCI Event: Vendor(0xff) plen 2 > HCI Event: Connect Complete(0x03) plen 11 < HCI Command: Create Connection(0x01|0x0005) plen 13 > HCI Event: Vendor(0xff) plen 2 > HCI Event: Command Status(0x0f) plen 4 > HCI Event: Vendor(0xff) plen 2 > HCI Event: Connect Complete(0x03) plen 11 < HCI Command: Create Connection(0x01|0x0005) plen 13 > HCI Event: Vendor(0xff) plen 2 > HCI Event: Command Status(0x0f) plen 4 > HCI Event: Vendor(0xff) plen 2 > HCI Event: Connect Complete(0x03) plen 11 ^C vv1% l2ping from other machine (stays next to vv1) to FF2 works great - the config is the same regards, -- Marek From owner-freebsd-bluetooth@FreeBSD.ORG Fri Nov 12 15:18:52 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 DC009106564A for ; Fri, 12 Nov 2010 15:18:51 +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 909448FC19 for ; Fri, 12 Nov 2010 15:18:51 +0000 (UTC) Received: by yxs7 with SMTP id 7so496224yxs.13 for ; Fri, 12 Nov 2010 07:18:50 -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:content-type; bh=/je33dz3dYG495csB89h7kIlL05FV4cnja3pm86YneU=; b=QQ9M57OiEzWBHgbBn95dHvKKkgTGlkJ1AKdbbSaUq2SlIxqvYG5+ZhNpj2UJHWcrEm N8WOCQ4H/26lcPNonnn4LIaW1oxwpJozsa+LF3L5AC/j8fjTTowq7kklEBkleiZsrzGN jUFhMzszsVoWoNetLHBc4c3599SV/2zqe4Ytg= 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 :content-type; b=ZebcFth9333FEja4powgPMFpxN2PzFaIIzDp3Y5+yEJRh2ThrMX2jmhinF+ybjRwS1 QjNyupmiAKiEyvcxVkyqvmm1wexyAf7qSw+p4UE52MdKHgN4adzX0l63RyggTzvoVrTl 9WP0QW1d3bO1IXmZ3nKlYhQngq6rIcvWIh1+I= MIME-Version: 1.0 Received: by 10.42.22.79 with SMTP id n15mr2182660icb.183.1289575126263; Fri, 12 Nov 2010 07:18:46 -0800 (PST) Received: by 10.231.207.14 with HTTP; Fri, 12 Nov 2010 07:18:46 -0800 (PST) In-Reply-To: <20101112070051.GA48569@amp2.iem.pw.edu.pl> References: <64FA2044DA694411995A309FF342396C@marekdesktop> <20101112050506.GA18796@amp2.iem.pw.edu.pl> <20101112062852.GA39843@amp2.iem.pw.edu.pl> <20101112064459.GA45107@amp2.iem.pw.edu.pl> <20101112070051.GA48569@amp2.iem.pw.edu.pl> Date: Fri, 12 Nov 2010 07:18:46 -0800 Message-ID: From: Maksim Yevmenkin To: Andrzej Tobola Content-Type: text/plain; charset=ISO-8859-1 X-Mailman-Approved-At: Fri, 12 Nov 2010 16:43:52 +0000 Cc: Subject: Re: l2ping - strange seq_no 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: Fri, 12 Nov 2010 15:18:52 -0000 Andrzej, > The last question - is it OK that seq_no has strange values or jumps: > > z2% l2ping -a FF1 > 4 bytes from FF1 seq_no=1633905441 time=798.277 ms result=0 > 4 bytes from FF1 seq_no=1633905441 time=13.756 ms result=0 > 4 bytes from FF1 seq_no=1633905441 time=28.755 ms result=0 > 4 bytes from FF1 seq_no=1633905441 time=25.755 ms result=0 > 4 bytes from FF1 seq_no=1633905441 time=28.761 ms result=0 > 4 bytes from FF1 seq_no=1633905441 time=32.018 ms result=0 > ^C > z2% l2ping -a FF2 > 0 bytes from FF2 seq_no=0 time=37.552 ms result=0x9 > 0 bytes from FF2 seq_no=1 time=5.754 ms result=0x9 > 0 bytes from FF2 seq_no=2 time=5.756 ms result=0x9 > 4 bytes from FF2 seq_no=1633905441 time=107.755 ms result=0 > 4 bytes from FF2 seq_no=1633905441 time=30.758 ms result=0 > 4 bytes from FF2 seq_no=1633905441 time=25.759 ms result=0 > 4 bytes from FF2 seq_no=1633905441 time=27.757 ms result=0 > 4 bytes from FF2 seq_no=1633905441 time=25.754 ms result=0 > 4 bytes from FF2 seq_no=1633905441 time=93.766 ms result=0 > 4 bytes from FF2 seq_no=1633905441 time=65.763 ms result=0 > 4 bytes from FF2 seq_no=1633905441 time=87.759 ms result=0 > 4 bytes from FF2 seq_no=1633905441 time=24.758 ms result=0 > ^C > z2% l2ping -a VV1 > 44 bytes from VV1 seq_no=0 time=3887.731 ms result=0 > 44 bytes from VV1 seq_no=1 time=21.762 ms result=0 > 44 bytes from VV1 seq_no=2 time=27.014 ms result=0 > 44 bytes from VV1 seq_no=3 time=9.761 ms result=0 > 44 bytes from VV1 seq_no=4 time=47.760 ms result=0 > 44 bytes from VV1 seq_no=5 time=14.017 ms result=0 > 44 bytes from VV1 seq_no=6 time=16.852 ms result=0 > 44 bytes from VV1 seq_no=7 time=27.762 ms result=0 > 44 bytes from VV1 seq_no=8 time=53.765 ms result=0 > 44 bytes from VV1 seq_no=9 time=31.762 ms result=0 > 44 bytes from VV1 seq_no=10 time=13.765 ms result=0 > 44 bytes from VV1 seq_no=11 time=34.762 ms result=0 > > or it signals some memory corruption ? not necessarily. l2cap does not have sequence numbers in protocol headers (like ip/icmp does), so l2cap(8) fakes sequence numbers by putting them into l2cap echo request packet payload. some devices return original payload in l2cap echo response thus making it easy to get sequence numbers back. some devices do not return any payload back (i.e. l2cap(8) will not get any sequence numbers back). in your case, payload is returned, but it appears to be different (constant?). what kind are FF1 and FF2 devices? could you please install hcidump utility from ports (i think its under net/comm) and get a trace to see what payload is being sent out and what payload is received back? thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Fri Nov 12 16:58:05 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 BE7841065672 for ; Fri, 12 Nov 2010 16:58:05 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 82BE98FC0A for ; Fri, 12 Nov 2010 16:58:05 +0000 (UTC) Received: by iwn39 with SMTP id 39so3701023iwn.13 for ; Fri, 12 Nov 2010 08:58:04 -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=+LezrfBVImSIB5ZxlOzMsNhV/E7RpsON/ddslPeW5ms=; b=npiTLoTNXlNhlRst8JpfuG4ciOo10uUaBYEKCr9+gJVAC0LUzqgzLIFFJhUh0iS+Tc BuMb1Ti11XcJUXjgDZ60C0baJQAi8kEaRDEOFe6CEjCtTXVRfhADn2G2CxuuSC25EwWn qZ60ILrCt5PyRiA4zf4BhNz1cn7bn4M9L3wdA= 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=olvSaKTifYia2BFzsmFDiGbir8cADjOe71cpdPfAdOslZ76pLjLZaN+2lWEBlY8omp mapd9kJBReG/A2sAbmAIAE2/Di650xbdOfq0yq1uOksWTRMTIY2sK9H8p8BtgVry/+PX TPcMy9stKSG9DkBjmz4CG+D6utHjKSNiS+57o= MIME-Version: 1.0 Received: by 10.231.12.130 with SMTP id x2mr622347ibx.138.1289581084545; Fri, 12 Nov 2010 08:58:04 -0800 (PST) Received: by 10.231.207.14 with HTTP; Fri, 12 Nov 2010 08:58:04 -0800 (PST) In-Reply-To: References: Date: Fri, 12 Nov 2010 08:58:04 -0800 Message-ID: From: Maksim Yevmenkin To: Marek Salwerowicz Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-bluetooth@freebsd.org Subject: Re: Can't l2ping to BT device 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: Fri, 12 Nov 2010 16:58:05 -0000 Marek, > 'hccontrol inquiry' discovers the device I want to connect to, but l2ping > can't ping to it: > > vv1% hccontrol inquiry > Inquiry result, num_responses=3D1 > Inquiry result #0 > =A0 =A0 =A0 BD_ADDR: FF2 > =A0 =A0 =A0 Page Scan Rep. Mode: 0x1 > =A0 =A0 =A0 Page Scan Period Mode: 00 > =A0 =A0 =A0 Page Scan Mode: 00 > =A0 =A0 =A0 Class: 00:1f:00 > =A0 =A0 =A0 Clock offset: 0x77cd > Inquiry complete. Status: No error [00] > > vv1% l2ping -a FF2 > 0 bytes from FF2 seq_no=3D0 time=3D5127.835 ms result=3D0x4 > 0 bytes from FF2 seq_no=3D1 time=3D5128.129 ms result=3D0x4 > 0 bytes from FF2 seq_no=3D2 time=3D5127.133 ms result=3D0x4 > 0 bytes from FF2 seq_no=3D3 time=3D5128.159 ms result=3D0x4 > ^C > vv1% 0x4 is page timeout, i.e. device does not answer page call. basically baseband connection timeout. > it's a new pair, so I typed config in hcsecd.conf: > > device { > =A0 =A0 =A0 bdaddr =A000:06:66:00:e2:84; # 'FF2' results in syntax error,= need to be > MAC address > =A0 =A0 =A0 name =A0 =A0"so51-FF2"; > =A0 =A0 =A0 key =A0 =A0 nokey; > =A0 =A0 =A0 pin =A0 =A0 "1234"; > } > and then restarted hcsecd > > during l2ping'ing hcsecd throws only this message: > > hcsecd[2315]: Received unexpected HCI event, event=3D0xff usually l2ping does not require any pairing. it works at l2cap control channel level, i.e. lower than any bluetooth profile. in any case, 0xff is a vendor specific event. hcisecd(8) can not do anything about it, so it just ignores it. > # hcidump : > > vv1% # hcidump > HCIDump - HCI packet analyzer ver 1.5 > device: any snap_len: 65535 filter: 0xffffffffffffffff >> >> HCI Event: Vendor(0xff) plen 2 >> HCI Event: Connect Complete(0x03) plen 11 > < HCI Command: Create Connection(0x01|0x0005) plen 13 >> HCI Event: Vendor(0xff) plen 2 >> HCI Event: Command Status(0x0f) plen 4 >> HCI Event: Vendor(0xff) plen 2 >> HCI Event: Connect Complete(0x03) plen 11 > < HCI Command: Create Connection(0x01|0x0005) plen 13 >> HCI Event: Vendor(0xff) plen 2 >> HCI Event: Command Status(0x0f) plen 4 >> HCI Event: Vendor(0xff) plen 2 >> HCI Event: Connect Complete(0x03) plen 11 interesting... there is a vendor event with every transaction with the device. next time please run hcidump -X or obtain a binary dump with hcidump -w (to get more information). timestamps would also be useful. what kind of devices you have? both local and remote > l2ping from other machine (stays next to vv1) to FF2 works great - the > config is the same so, are you saying that there is an already established connection between other machine and ff2? if so, then it explains page timeout. thanks, max