From owner-freebsd-bluetooth@FreeBSD.ORG Sun Nov 27 02:39:07 2005 Return-Path: X-Original-To: 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 A36EE16A48B for ; Sun, 27 Nov 2005 02:39:07 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72C2043D69 for ; Sun, 27 Nov 2005 02:39:05 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.25] ([192.168.42.25]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id jAR2d3Zx097990; Sat, 26 Nov 2005 20:39:04 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <43891C3A.5090401@centtech.com> Date: Sat, 26 Nov 2005 20:38:50 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051021 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Maksim Yevmenkin References: <437B2E58.50709@centtech.com> <437B52FF.9040407@savvis.net> <437B5CE2.5000601@centtech.com> <437B93CF.4000403@savvis.net> <437BA490.1010704@centtech.com> <437BAF32.5030502@savvis.net> <437C8547.3060708@centtech.com> <437CC544.6080509@savvis.net> <437D32F7.10706@centtech.com> <437DCBF8.1080000@centtech.com> <437E129A.9000204@savvis.net> In-Reply-To: <437E129A.9000204@savvis.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1195/Fri Nov 25 03:29:55 2005 on mh1.centtech.com X-Virus-Status: Clean Cc: bluetooth Subject: Re: No route to host for 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: Sun, 27 Nov 2005 02:39:08 -0000 Maksim Yevmenkin wrote: > Eric, > >>>>> Well, here's more information. First, it's reproducable every time >>>>> I boot up. Doing: >>>>> /etc/rc.d/bluetooth start ubt0 >>>>> does not fix it by itself, but doing: >>>>> /etc/rc.d/bluetooth stop ubt0 >>>>> /etc/rc.d/bluetooth start ubt0 >>>>> does. >>>> >>>> >>>> now, i really puzzled. because device fails on to start at boot >>>> time, /etc/rc.d/bluetooth should have backed out and removed all >>>> netgraph nodes it tried to create (except device node and socket >>>> nodes). so i do not understand why do you need to do 'stop' before >>>> 'start'. 'stop' should really be a noop in this case. >>>> >>>> could you please do the following >>>> >>>> 1) do a fresh boot with bluetooth device turned on >>>> >>>> 2) after system boots (and bluetooth device failed to start) please >>>> run as root >>>> >>>> # ngctl li >>> >>> >>> There are 7 total nodes: >>> Name: ngctl992 Type: socket ID: 0000001d Num >>> hooks: 0 >>> Name: ubt0l2cap Type: l2cap ID: 00000017 Num >>> hooks: 3 >>> Name: ubt0hci Type: hci ID: 00000013 Num >>> hooks: 3 >>> Name: btsock_l2c Type: btsock_l2c ID: 00000004 Num >>> hooks: 1 >>> Name: btsock_l2c_raw Type: btsock_l2c_raw ID: 00000003 Num >>> hooks: 1 >>> Name: btsock_hci_raw Type: btsock_hci_raw ID: 00000002 Num >>> hooks: 1 >>> Name: ubt0 Type: ubt ID: 00000001 Num >>> hooks: 1 > > > hmm... that does not make much sense to me. somehow you still have all > nodes connected even if bluetooth device failed to initialize! that > explains why do you need 'stop' command before 'start'. > > just a crazy idea. please double that you are not initializing device > twice, i.e. you use new rc.d scripts and some leftovers from old system. > or may be you have devd(8) configuration in both /etc in /usr/local/etc? > >>>>> I also tried a fresh boot, then switching the bluetooth off, >>>>> waiting about 20 seconds, and flipping it back on, which *did* in >>>>> fact work. I may not have waited long enough the previous time that >>>>> failed. >>>> >>>> >>>> ah, ok. could you please check the /var/log/messages file to see if >>>> you get a message saying ubt0 is detached/attached? >>> >>> >>> Here's the snippet upon boot: >>> >>> Nov 17 19:31:32 neutrino kernel: ubt0: ALPS UGX, rev 1.10/11.68, addr 3 >>> Nov 17 19:31:32 neutrino kernel: ubt0: ALPS UGX, rev 1.10/11.68, addr 3 >>> Nov 17 19:31:32 neutrino kernel: ubt0: Interface 0 endpoints: >>> interrupt=0x81, bulk-in=0x82, bulk-out=0x2 >>> Nov 17 19:31:32 neutrino kernel: ubt0: Interface 1 (alt.config 5) >>> endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, >>> buffer size=294 > > > [...] > >>> Nov 17 19:31:41 neutrino kernel: ng_hci_process_command_timeout: >>> ubt0hci - unable to complete HCI command OGF=0x3, OCF=0x3. Timeout > > > device failed to initialize and rc.d/bluetooth should have cleaned the > nodes, but it did not happen > >>> Nov 17 19:31:45 neutrino sdpd[659]: Could not bind control socket. >>> Permission denied (13) > > > hmm... this is bad too. can you double check if you have sdpd running? > >>> now I'll run the bluetooth stop, which produces no output. >>> >>> ngctl li now looks like: >>> There are 5 total nodes: >>> Name: ngctl1015 Type: socket ID: 00000020 Num >>> hooks: 0 >>> Name: btsock_l2c Type: btsock_l2c ID: 00000004 Num >>> hooks: 0 >>> Name: btsock_l2c_raw Type: btsock_l2c_raw ID: 00000003 Num >>> hooks: 0 >>> Name: btsock_hci_raw Type: btsock_hci_raw ID: 00000002 Num >>> hooks: 0 >>> Name: ubt0 Type: ubt ID: 00000001 Num >>> hooks: 0 > > > that is fine. that is what the output should look like when device is > failed to initialize. > >>> Now I ran bluetooth start, which produces no output, and nothing in >>> /var/log/messages. >>> >>> ngctl li now looks like this: >>> There are 7 total nodes: >>> Name: ngctl1045 Type: socket ID: 0000002c Num >>> hooks: 0 >>> Name: ubt0l2cap Type: l2cap ID: 00000026 Num >>> hooks: 3 >>> Name: ubt0hci Type: hci ID: 00000022 Num >>> hooks: 3 >>> Name: btsock_l2c Type: btsock_l2c ID: 00000004 Num >>> hooks: 1 >>> Name: btsock_l2c_raw Type: btsock_l2c_raw ID: 00000003 Num >>> hooks: 1 >>> Name: btsock_hci_raw Type: btsock_hci_raw ID: 00000002 Num >>> hooks: 1 >>> Name: ubt0 Type: ubt ID: 00000001 Num >>> hooks: 1 > > > and that is fine too - this is what output should look like when all > nodes are properly connected. > >>> Now I wiggle my mouse, and I see this in /var/log/messages: >>> Nov 17 19:47:58 neutrino bthidd[603]: Accepted control connection >>> from 00:07:61:31:27:15 >>> Nov 17 19:47:58 neutrino bthidd[603]: Accepted interrupt connection >>> from 00:07:61:31:27:15 >>> >>> and my mouse now works. >>> >>>>> Oddly enough, I never had a problem before now. I previously >>>>> started the bluetooth stuff from rc.local. The only things I have >>>>> changed are: updated to latest -current, removed inet6 from kernel, >>>>> rebuilt world/kernel, switched to new rc.d bluetooth scripts. I >>>>> can try anything you like. >>>> >>>> >>>> one thing you could try to do is to comment out ubt0 section in >>>> /etc/devd.conf and go back to old style rc.bluetooth script to see >>>> if you have the same problem. if you do - then its not bluetooth >>>> related, if you dont - then its related to new bluetooth rc.d scripts. >>> >>> >>> I can do that if you'd like.. > > > yes please, if you can. > >> Something else I just tried: booted up, no mouse as usual. Ran >> /etc/rc.d/bluetooth start ubt0, and got this error: >> >> # /etc/rc.d/bluetooth start ubt0 >> /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device >> ubt0 >> >> and mouse still does not work.. >> >> Then, ran it again: >> # /etc/rc.d/bluetooth start ubt0 >> >> no error, and voila! my mouse works. Didn't run the 'stop' part at >> all, just the 'start' twice. > > > again the explanation for this is: after the boot device failed to > initialize, but for whatever reason, all nodes are still connected. when > you do the 'start' command it tries to connect nodes, but it fails > because nodes are already connected. because it fails - it tries to > clean up after itself and removes all the nodes. thus resetting back to > defaults. the next 'start' runs fine, because now everything as it > should be. > > we need to figure out why nodes are still connected after your device > failed on boot. I haven't had time to try your suggestions above yet, however something weird happened a few times - I booted up my laptop, and walked away while it was booting. When I came back to it, it had booted, and had all the same messages/warnings as before, however the mouse worked without intervention. It seems as though maybe letting it just sit there for some number of minutes will finally make it work. I'll do more experimenting and reply with my results. Thanks! Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 28 20:58:30 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 032F016A41F for ; Mon, 28 Nov 2005 20:58:30 +0000 (GMT) (envelope-from C.H.Zhu@herts.ac.uk) Received: from mta07-winn.ispmail.ntl.com (mta07-winn.ispmail.ntl.com [81.103.221.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id BABB343D45 for ; Mon, 28 Nov 2005 20:58:27 +0000 (GMT) (envelope-from C.H.Zhu@herts.ac.uk) Received: from aamta12-winn.ispmail.ntl.com ([81.103.221.35]) by mta07-winn.ispmail.ntl.com with ESMTP id <20051128205826.DFBI21883.mta07-winn.ispmail.ntl.com@aamta12-winn.ispmail.ntl.com>; Mon, 28 Nov 2005 20:58:26 +0000 Received: from [82.23.211.112] by aamta12-winn.ispmail.ntl.com with ESMTP id <20051128205821.HDEL18425.aamta12-winn.ispmail.ntl.com@[82.23.211.112]>; Mon, 28 Nov 2005 20:58:21 +0000 To: freebsd-bluetooth@freebsd.org From: faigozhu Date: 28 Nov 2005 20:58:43 +0000 Message-ID: <863blgzdz0.fsf@fastmail.fm> Lines: 67 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Subject: Sdpcontrol search timeout in Motorola HS805 headset. 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, 28 Nov 2005 20:58:30 -0000 Dear, First of all, I would like to thank BSD bluetooth team for their great work enable bluetooth support in FreeBSD. I have a Motorola HS805 headset and got the following message. #sdpcontrol -a 00:0b:2e:32:65:12 search HSET Could not execute command "search". Operation timed out It seems no response from the headset after sending Link_Key_Reply? Any help would be appreciated. ------------uname -a----------- FreeBSD .local 6.0-RELEASE FreeBSD 6.0-RELEASE #1: Tue Nov 22 00:52:11 UTC 2005 user@.local:/usr/obj/usr/src/sys/mykernel i386 ------------hcidump------------------ HCIDump - HCI packet analyzer ver 1.5 device: any snap_len: 65535 filter: 0xffffffff < HCI Command: Create Connection(0x01|0x0005) plen 13 > HCI Event: Command Status(0x0f) plen 4 > HCI Event: Connect Complete(0x03) plen 11 < HCI Command: Create Connection(0x01|0x0005) plen 13 > HCI Event: Command Status(0x0f) plen 4 > HCI Event: Link Key Request(0x17) plen 6 < HCI Command: Link Key Request Reply(0x01|0x000b) plen 22 > HCI Event: Command Complete(0x0e) plen 10 > HCI Event: Connect Complete(0x03) plen 11 < HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4 < ACL data: handle 0x0006 flags 0x02 dlen 12 L2CAP(s): Connect req: psm 1 scid 0x0045 > HCI Event: Command Complete(0x0e) plen 6 > HCI Event: Number of Completed Packets(0x13) plen 5 > HCI Event: Max Slots Change(0x1b) plen 3 > HCI Event: Link Key Request(0x17) plen 6 < HCI Command: Link Key Request Reply(0x01|0x000b) plen 22 > HCI Event: Command Complete(0x0e) plen 10 < HCI Command: Disconnect(0x01|0x0006) plen 3 > HCI Event: Command Status(0x0f) plen 4 > HCI Event: Disconn Complete(0x05) plen 4 ------------hcsecd -d------------ hcsecd[98316]: Restored link key for the entry, remote bdaddr 00:0b:2e:32:65:12, name 'Motorola HS805' hcsecd[98316]: Got Link_Key_Request event from 'ubt0hci', remote bdaddr 00:0b:2e:32:65:12 hcsecd[98316]: Found matching entry, remote bdaddr 00:0b:2e:32:65:12, name 'Motorola HS805', link key exists hcsecd[98316]: Sending Link_Key_Reply to 'ubt0hci' for remote bdaddr 00:0b:2e:32:65:12 hcsecd[98316]: Got Link_Key_Request event from 'ubt0hci', remote bdaddr 00:0b:2e:32:65:12 hcsecd[98316]: Found matching entry, remote bdaddr 00:0b:2e:32:65:12, name 'Motorola HS805', link key exists hcsecd[98316]: Sending Link_Key_Reply to 'ubt0hci' for remote bdaddr 00:0b:2e:32:65:12 ------------hcsecd.conf---------- /etc/bluetooth/hcsecd.conf #headset device{ bdaddr 00:0b:2e:32:65:12; name "Motorola HS805"; key nokey; pin "0000"; } --------------- -- Best Regards, Faigozhu From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 28 22:07:49 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 A3B2A16A41F for ; Mon, 28 Nov 2005 22:07:49 +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 4178E43D66 for ; Mon, 28 Nov 2005 22:07:49 +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 jASM7kJ21026; Mon, 28 Nov 2005 17:07:47 -0500 Message-ID: <438B7FB0.5030704@savvis.net> Date: Mon, 28 Nov 2005 14:07:44 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: faigozhu References: <863blgzdz0.fsf@fastmail.fm> In-Reply-To: <863blgzdz0.fsf@fastmail.fm> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: Sdpcontrol search timeout in Motorola HS805 headset. 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, 28 Nov 2005 22:07:49 -0000 Hello, > First of all, I would like to thank BSD bluetooth team for their > great work enable bluetooth support in FreeBSD. > > I have a Motorola HS805 headset and got the following message. > > #sdpcontrol -a 00:0b:2e:32:65:12 search HSET > Could not execute command "search". Operation timed out did you try to repeat this command several times? does it always fail with timeout? > It seems no response from the headset after sending Link_Key_Reply? sigh... people, please, PLEASE, stop posting text hci dump. they are not very useful. they give me some idea, but what i really need is _binary_ hci dump. > ------------hcidump------------------ > > HCIDump - HCI packet analyzer ver 1.5 > device: any snap_len: 65535 filter: 0xffffffff > < HCI Command: Create Connection(0x01|0x0005) plen 13 > > HCI Event: Command Status(0x0f) plen 4 > > HCI Event: Connect Complete(0x03) plen 11 ?? what happened here? baseband connection failed? > < HCI Command: Create Connection(0x01|0x0005) plen 13 > > HCI Event: Command Status(0x0f) plen 4 > > HCI Event: Link Key Request(0x17) plen 6 > < HCI Command: Link Key Request Reply(0x01|0x000b) plen 22 > > HCI Event: Command Complete(0x0e) plen 10 > > HCI Event: Connect Complete(0x03) plen 11 seems like baseband connection established > < HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4 > < ACL data: handle 0x0006 flags 0x02 dlen 12 > L2CAP(s): Connect req: psm 1 scid 0x0045 here is the request to setup l2cap channel on psm 1 (sdp). > > HCI Event: Command Complete(0x0e) plen 6 > > HCI Event: Number of Completed Packets(0x13) plen 5 > > HCI Event: Max Slots Change(0x1b) plen 3 > > HCI Event: Link Key Request(0x17) plen 6 > < HCI Command: Link Key Request Reply(0x01|0x000b) plen 22 > > HCI Event: Command Complete(0x0e) plen 10 > < HCI Command: Disconnect(0x01|0x0006) plen 3 > > HCI Event: Command Status(0x0f) plen 4 > > HCI Event: Disconn Complete(0x05) plen 4 this block above does not make much sense to me. i'm confused why the device requests link key again. could you please make binary hci dump (-w option) and send it to me? > ------------hcsecd -d------------ > hcsecd[98316]: Restored link key for the entry, remote bdaddr 00:0b:2e:32:65:12, name 'Motorola HS805' > hcsecd[98316]: Got Link_Key_Request event from 'ubt0hci', remote bdaddr 00:0b:2e:32:65:12 > hcsecd[98316]: Found matching entry, remote bdaddr 00:0b:2e:32:65:12, name 'Motorola HS805', link key exists > hcsecd[98316]: Sending Link_Key_Reply to 'ubt0hci' for remote bdaddr 00:0b:2e:32:65:12 > hcsecd[98316]: Got Link_Key_Request event from 'ubt0hci', remote bdaddr 00:0b:2e:32:65:12 > hcsecd[98316]: Found matching entry, remote bdaddr 00:0b:2e:32:65:12, name 'Motorola HS805', link key exists > hcsecd[98316]: Sending Link_Key_Reply to 'ubt0hci' for remote bdaddr 00:0b:2e:32:65:12 looks fine to, but like i said before i'm confused why the device requests link key twice. > ------------hcsecd.conf---------- > /etc/bluetooth/hcsecd.conf > #headset > device{ > bdaddr 00:0b:2e:32:65:12; > name "Motorola HS805"; > key nokey; > pin "0000"; > } looks fine to. i assume you checked the pin code and it is correct, right? thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 28 22:40:53 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 D47AB16A41F for ; Mon, 28 Nov 2005 22:40:53 +0000 (GMT) (envelope-from C.H.Zhu@herts.ac.uk) Received: from mta09-winn.ispmail.ntl.com (mta09-winn.ispmail.ntl.com [81.103.221.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id B515F43D67 for ; Mon, 28 Nov 2005 22:40:51 +0000 (GMT) (envelope-from C.H.Zhu@herts.ac.uk) Received: from aamta10-winn.ispmail.ntl.com ([81.103.221.35]) by mta09-winn.ispmail.ntl.com with ESMTP id <20051128224050.EWUW8609.mta09-winn.ispmail.ntl.com@aamta10-winn.ispmail.ntl.com>; Mon, 28 Nov 2005 22:40:50 +0000 Received: from [82.23.211.112] by aamta10-winn.ispmail.ntl.com with ESMTP id <20051128224050.KTCD11396.aamta10-winn.ispmail.ntl.com@[82.23.211.112]>; Mon, 28 Nov 2005 22:40:50 +0000 To: Maksim Yevmenkin References: <863blgzdz0.fsf@fastmail.fm> <438B7FB0.5030704@savvis.net> From: faigozhu Date: 28 Nov 2005 22:41:25 +0000 In-Reply-To: <438B7FB0.5030704@savvis.net> Message-ID: <86psok1jl6.fsf@fastmail.fm> Lines: 112 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Cc: freebsd-bluetooth@freebsd.org Subject: Re: Sdpcontrol search timeout in Motorola HS805 headset. 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, 28 Nov 2005 22:40:53 -0000 --=-=-= Maksim Yevmenkin writes: > Hello, Hi. Thanks for you reply. > > > First of all, I would like to thank BSD bluetooth team for their > > great work enable bluetooth support in FreeBSD. > > I have a Motorola HS805 headset and got the following message. > > #sdpcontrol -a 00:0b:2e:32:65:12 search HSET > > Could not execute command "search". Operation timed out > > did you try to repeat this command several times? does it always fail > with timeout? yes. > > > It seems no response from the headset after sending Link_Key_Reply? > > sigh... people, please, PLEASE, stop posting text hci dump. they are > not very useful. they give me some idea, but what i really need is > _binary_ hci dump. Sorry for that. The attached file is a binary file of "hcidump -w hcidump.log". --=-=-= Content-Type: application/octet-stream Content-Disposition: attachment; filename=hcidump.log Content-Transfer-Encoding: base64 EQAAAJiBi0OtQQkAAQUEDRJlMi4LABjMAAAAAAEHAAEAmIGLQ1P+CQAEDwQAAQUECQABAJmBi0Py 8AgABBcGEmUyLgsAGgAAAJmBi0N78QgAAQsEFhJlMi4LACcZINaDEpxA5ufM/wvMH/wNAAEAmYGL Q2gECQAEDgoBCwQAEmUyLgsADgABAJmBi0OYzwkABAMLAAYAEmUyLgsAAQAIAAAAmYGLQ5vPCQAB DQgEBgAHABEAAACZgYtDnc8JAAIGIAwACAABAAIBBAABAEAACQABAJmBi0MH4wkABA4GAQ0IAAYA CAABAJmBi0P/DQoABBMFAQYAAQAGAAEAmYGLQ49zCgAEGwMGAAUJAAEAmYGLQ0LPCwAEFwYSZTIu CwAaAAAAmYGLQ67PCwABCwQWEmUyLgsAJxkg1oMSnEDm58z/C8wf/A0AAQCZgYtDu+YLAAQOCgEL BAASZTIuCwA= --=-=-= > > > ------------hcidump------------------ > > HCIDump - HCI packet analyzer ver 1.5 > > device: any snap_len: 65535 filter: 0xffffffff > > < HCI Command: Create Connection(0x01|0x0005) plen 13 > > > HCI Event: Command Status(0x0f) plen 4 > > > HCI Event: Connect Complete(0x03) plen 11 > > ?? what happened here? baseband connection failed? > It could be a previous action before the real connect. Following msg would be the the real connect. > > < HCI Command: Create Connection(0x01|0x0005) plen 13 > > > HCI Event: Command Status(0x0f) plen 4 > > > HCI Event: Link Key Request(0x17) plen 6 > > < HCI Command: Link Key Request Reply(0x01|0x000b) plen 22 > > > HCI Event: Command Complete(0x0e) plen 10 > > > HCI Event: Connect Complete(0x03) plen 11 > > seems like baseband connection established > > > < HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4 > > < ACL data: handle 0x0006 flags 0x02 dlen 12 > > L2CAP(s): Connect req: psm 1 scid 0x0045 > > here is the request to setup l2cap channel on psm 1 (sdp). > > > > HCI Event: Command Complete(0x0e) plen 6 > > > HCI Event: Number of Completed Packets(0x13) plen 5 > > > HCI Event: Max Slots Change(0x1b) plen 3 > > > HCI Event: Link Key Request(0x17) plen 6 > > < HCI Command: Link Key Request Reply(0x01|0x000b) plen 22 > > > HCI Event: Command Complete(0x0e) plen 10 no response from headset until sdpcontrol search timeout. The headset turn off(or stand by) in 1 minute if pairing unsuccess, that is why a disconnect occurs, I guest. > > < HCI Command: Disconnect(0x01|0x0006) plen 3 > > > HCI Event: Command Status(0x0f) plen 4 > > > HCI Event: Disconn Complete(0x05) plen 4 > > this block above does not make much sense to me. i'm confused why the > device requests link key again. could you please make binary hci dump > (-w option) and send it to me? > > > ------------hcsecd -d------------ > > hcsecd[98316]: Restored link key for the entry, remote bdaddr 00:0b:2e:32:65:12, name 'Motorola HS805' > > hcsecd[98316]: Got Link_Key_Request event from 'ubt0hci', remote bdaddr 00:0b:2e:32:65:12 > > hcsecd[98316]: Found matching entry, remote bdaddr 00:0b:2e:32:65:12, name 'Motorola HS805', link key exists > > hcsecd[98316]: Sending Link_Key_Reply to 'ubt0hci' for remote bdaddr 00:0b:2e:32:65:12 > > hcsecd[98316]: Got Link_Key_Request event from 'ubt0hci', remote bdaddr 00:0b:2e:32:65:12 > > hcsecd[98316]: Found matching entry, remote bdaddr 00:0b:2e:32:65:12, name 'Motorola HS805', link key exists > > hcsecd[98316]: Sending Link_Key_Reply to 'ubt0hci' for remote bdaddr 00:0b:2e:32:65:12 > > looks fine to, but like i said before i'm confused why the device > requests link key twice. > > > ------------hcsecd.conf---------- > > /etc/bluetooth/hcsecd.conf > > #headset > > device{ > > bdaddr 00:0b:2e:32:65:12; > > name "Motorola HS805"; > > key nokey; > > pin "0000"; > > } > > looks fine to. i assume you checked the pin code and it is correct, right? yes, it's a default pin. > > thanks, > max Many thanks, -- Faigozhu --=-=-=-- From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 29 00:18:24 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 6FEFC16A41F for ; Tue, 29 Nov 2005 00:18:24 +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 7C26A43D76 for ; Tue, 29 Nov 2005 00:18:11 +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 jAT0I8J24240; Mon, 28 Nov 2005 19:18:08 -0500 Message-ID: <438B9E3E.5020905@savvis.net> Date: Mon, 28 Nov 2005 16:18:06 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: faigozhu References: <863blgzdz0.fsf@fastmail.fm> <438B7FB0.5030704@savvis.net> <86psok1jl6.fsf@fastmail.fm> In-Reply-To: <86psok1jl6.fsf@fastmail.fm> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: Sdpcontrol search timeout in Motorola HS805 headset. 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, 29 Nov 2005 00:18:24 -0000 >>> I have a Motorola HS805 headset and got the following message. >>> #sdpcontrol -a 00:0b:2e:32:65:12 search HSET Could not execute >>> command "search". Operation timed out >> >> did you try to repeat this command several times? does it always >> fail with timeout? > > yes. ok >>> It seems no response from the headset after sending >>> Link_Key_Reply? >> >> sigh... people, please, PLEASE, stop posting text hci dump. they >> are not very useful. they give me some idea, but what i really need >> is _binary_ hci dump. > > Sorry for that. The attached file is a binary file of "hcidump -w hcidump.log". thanks. unfortunately, this binary dump did not reveal the problem. i'd like you to try the following: 1) reboot 2) attach usb bluetooth dongle and start bluetooth stack 3) as root # hcidump -w headset.dump 4) as root # hccontrol -n ubt0hci create_connection 00:0b:2e:32:65:12 make sure hccontrol succeeded and created baseband connection. it should print connection handle. 5) wait a few seconds, and run % sdpcontrol -a 00:0b:2e:32:65:12 search HSET you may try step 5) a couple more times. please wait few seconds between each try. 6) kill hcidump with ^c and send me the headset.dump file also, i assume, you have paired less then 8 devices with this headset, correct? some headsets can only remember one host, but this one seems to be able to remember up to 8 (according to specs). also, if this is not too much trouble, you could reset the headset and try the steps 1-6 from above again. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 29 02:16:52 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 5CF2116A41F for ; Tue, 29 Nov 2005 02:16:52 +0000 (GMT) (envelope-from C.H.Zhu@herts.ac.uk) Received: from mta07-winn.ispmail.ntl.com (mta07-winn.ispmail.ntl.com [81.103.221.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F17443D5E for ; Tue, 29 Nov 2005 02:16:48 +0000 (GMT) (envelope-from C.H.Zhu@herts.ac.uk) Received: from aamta12-winn.ispmail.ntl.com ([81.103.221.35]) by mta07-winn.ispmail.ntl.com with ESMTP id <20051129021647.MYPF21883.mta07-winn.ispmail.ntl.com@aamta12-winn.ispmail.ntl.com>; Tue, 29 Nov 2005 02:16:47 +0000 Received: from [82.23.211.112] by aamta12-winn.ispmail.ntl.com with ESMTP id <20051129021645.KQUB18425.aamta12-winn.ispmail.ntl.com@[82.23.211.112]>; Tue, 29 Nov 2005 02:16:45 +0000 To: Maksim Yevmenkin References: <863blgzdz0.fsf@fastmail.fm> <438B7FB0.5030704@savvis.net> <86psok1jl6.fsf@fastmail.fm> <438B9E3E.5020905@savvis.net> From: faigozhu Date: 29 Nov 2005 02:17:18 +0000 In-Reply-To: <438B9E3E.5020905@savvis.net> Message-ID: <86ek5019ld.fsf@fastmail.fm> Lines: 112 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Cc: freebsd-bluetooth@freebsd.org Subject: Re: Sdpcontrol search timeout in Motorola HS805 headset. 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, 29 Nov 2005 02:16:52 -0000 --=-=-= Maksim Yevmenkin writes: > >>> I have a Motorola HS805 headset and got the following > >>> message. #sdpcontrol -a 00:0b:2e:32:65:12 search HSET Could not > >>> execute > >>> command "search". Operation timed out > >> did you try to repeat this command several times? does it always > >> fail with timeout? > > yes. > > ok > > >>> It seems no response from the headset after sending > >>> Link_Key_Reply? > >> sigh... people, please, PLEASE, stop posting text hci dump. they > >> are not very useful. they give me some idea, but what i really need > >> is _binary_ hci dump. > > Sorry for that. The attached file is a binary file of "hcidump -w > hcidump.log". > > thanks. unfortunately, this binary dump did not reveal the > problem. i'd like you to try the following: > > 1) reboot > > 2) attach usb bluetooth dongle and start bluetooth stack # /etc/rc.bluetooth start ubt0 BD_ADDR: 00:0a:3a:63:de:86 Features: 0xff 0xfe 0xd 0x38 0x8 0x8 00 00 <3-Slot> <5-Slot> Max. ACL packet size: 377 bytes Number of ACL packets: 10 Max. SCO packet size: 16 bytes Number of SCO packets: 0 # hcidump -w headset.dump2 HCIDump - HCI packet analyzer ver 1.5 device: any snap_len: 65535 filter: 0xffffffff > > 3) as root > # hcidump -w headset.dump > > 4) as root > # hccontrol -n ubt0hci create_connection 00:0b:2e:32:65:12 > > make sure hccontrol succeeded and created baseband connection. > it should print connection handle. BD_ADDR: 00:0b:2e:32:65:12 Connection handle: 6 Encryption mode: Disabled [0] > > 5) wait a few seconds, and run > % sdpcontrol -a 00:0b:2e:32:65:12 search HSET Could not execute command "search". Operation timed out. > > you may try step 5) a couple more times. please wait few seconds > between each try. still timed out. > > 6) kill hcidump with ^c and send me the headset.dump file > --=-=-= Content-Type: application/octet-stream Content-Disposition: attachment; filename=headset.dump Content-Transfer-Encoding: base64 EQAAAEG1i0M+OQkAAQUEDRJlMi4LABhMAAAAAAEHAAEAQbWLQ7r1CQAEDwQAAQUECQABAES1i0MB VgkABBcGEmUyLgsAGgAAAES1i0OyVgkAAQsEFhJlMi4LACcZINaDEpxA5ufM/wvMH/wNAAEARLWL Qyb2CQAEDgoBCwQAEmUyLgsADgABAES1i0OUtQoABAMLAAYAEmUyLgsAAQAIAAAARLWLQ5i1CgAB DQgEBgAHAAkAAQBEtYtDBskKAAQOBgENCAAGAAYAAQBEtYtDmoQLAAQbAwYABREAAABatYtDYL4A AAIGIAwACAABAAIBBAABAEAACAABAFq1i0Nj7AAABBMFAQYAAQAJAAEAWrWLQ/WjAQAEFwYSZTIu CwAaAAAAWrWLQ4SkAQABCwQWEmUyLgsAJxkg1oMSnEDm58z/C8wf/A0AAQBatYtDibcBAAQOCgEL BAASZTIuCwAHAAAAm7WLQ326AAABBgQDBgATBwABAJu1i0NLVgEABA8EAAEGBAcAAQCbtYtDt2cC AAQFBAAGABY= --=-=-= Content-Type: application/octet-stream Content-Disposition: attachment; filename=headset.dump2 Content-Transfer-Encoding: base64 EQAAAMW2i0MYDwYAAQUEDRJlMi4LABhMAAAAAAEHAAEAxbaLQ6DPBgAEDwQAAQUECQABAMa2i0Np rQAABBcGEmUyLgsAGgAAAMa2i0MIrgAAAQsEFhJlMi4LACcZINaDEpxA5ufM/wvMH/wNAAEAxraL Q5FNAQAEDgoBCwQAEmUyLgsADgABAMa2i0PxDAIABAMLAAYAEmUyLgsAAQAIAAAAxraLQ/MMAgAB DQgEBgAHAAkAAQDGtotDeCACAAQOBgENCAAGAAYAAQDGtotDxzsCAAQbAwYABREAAADStotDmbUF AAIGIAwACAABAAIBBAABAEAACAABANK2i0P24gUABBMFAQYAAQAJAAEA0raLQ4iaBgAEFwYSZTIu CwAaAAAA0raLQxabBgABCwQWEmUyLgsAJxkg1oMSnEDm58z/C8wf/A0AAQDStotDHK4GAAQOCgEL BAASZTIuCwAHAAAAE7eLQ7ayBQABBgQDBgATBwABABO3i0PfTAYABA8EAAEGBAcAAQATt4tDelYH AAQFBAAGABY= --=-=-= > also, i assume, you have paired less then 8 devices with this headset, > correct? yes. >some headsets can only remember one host, but this one seems > to be able to remember up to 8 (according to specs). > > also, if this is not too much trouble, you could reset the headset and > try the steps 1-6 from above again. > > thanks, > max dmesg: ubt0: Broadcom Belkin Bluetooth Device, rev 1.10/0.01, addr 2 ubt0: Broadcom Belkin Bluetooth Device, rev 1.10/0.01, addr 2 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 ubt_bulk_in_complete2: ubt0 - Bulk-in xfer failed, IOERROR (13). No new xfer will be submitted! # hcsecd -d hcsecd[626]: Restored link key for the entry, remote bdaddr 00:0b:2e:32:65:12, name 'Motorola HS805' hcsecd[626]: Got Link_Key_Request event from 'ubt0hci', remote bdaddr 00:0b:2e:32:65:12 hcsecd[626]: Found matching entry, remote bdaddr 00:0b:2e:32:65:12, name 'Motorola HS805', link key exists hcsecd[626]: Sending Link_Key_Reply to 'ubt0hci' for remote bdaddr 00:0b:2e:32:65:12 hcsecd[626]: Got Link_Key_Request event from 'ubt0hci', remote bdaddr 00:0b:2e:32:65:12 hcsecd[626]: Found matching entry, remote bdaddr 00:0b:2e:32:65:12, name 'Motorola HS805', link key exists hcsecd[626]: Sending Link_Key_Reply to 'ubt0hci' for remote bdaddr 00:0b:2e:32:65:12 Many thanks, Faigozhu --=-=-=-- From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 29 03:42:52 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 B9B7516A41F for ; Tue, 29 Nov 2005 03:42:52 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from mta13.adelphia.net (mta13.mail.adelphia.net [68.168.78.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDA4643D77 for ; Tue, 29 Nov 2005 03:42:35 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [192.168.1.254] (really [70.32.199.60]) by mta13.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051129034232.RFLA12926.mta13.adelphia.net@[192.168.1.254]>; Mon, 28 Nov 2005 22:42:32 -0500 Message-ID: <438BCE22.3050901@savvis.net> Date: Mon, 28 Nov 2005 19:42:26 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: faigozhu References: <863blgzdz0.fsf@fastmail.fm> <438B7FB0.5030704@savvis.net> <86psok1jl6.fsf@fastmail.fm> <438B9E3E.5020905@savvis.net> <86ek5019ld.fsf@fastmail.fm> In-Reply-To: <86ek5019ld.fsf@fastmail.fm> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: Sdpcontrol search timeout in Motorola HS805 headset. 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, 29 Nov 2005 03:42:52 -0000 [...] >> thanks. unfortunately, this binary dump did not reveal the problem. >> i'd like you to try the following: >> >> 1) reboot >> >> 2) attach usb bluetooth dongle and start bluetooth stack > > # /etc/rc.bluetooth start ubt0 > BD_ADDR: 00:0a:3a:63:de:86 > Features: 0xff 0xfe 0xd 0x38 0x8 0x8 00 00 > <3-Slot> <5-Slot> > > > > > Max. ACL packet size: 377 bytes > Number of ACL packets: 10 > Max. SCO packet size: 16 bytes > Number of SCO packets: 0 this looks good. number of sco packets == 0 is strange, but its not your problem. i've seen this in other devices. is this a broadcom chip based device? >> 4) as root >> # hccontrol -n ubt0hci create_connection 00:0b:2e:32:65:12 >> >> make sure hccontrol succeeded and created baseband connection. >> it should print connection handle. > > BD_ADDR: 00:0b:2e:32:65:12 > Connection handle: 6 > Encryption mode: Disabled [0] this looks good as well >> 5) wait a few seconds, and run >> % sdpcontrol -a 00:0b:2e:32:65:12 search HSET > > Could not execute command "search". Operation timed out. well, at least it is consistent >> you may try step 5) a couple more times. please wait few seconds >> between each try. > > still timed out. ok >dmesg: [...] > ubt_bulk_in_complete2: ubt0 - Bulk-in xfer failed, IOERROR (13). No new xfer will be submitted! aha! this is your problem. usb bulk transfer failed. that explains why sdpcontrol failed. bluetooth usb device use usb control transfers to send hci command and usb interrupt transfers to receive hci event. bulk usb transfers used to transfer the data. so, in your case, usb control/interrupt transfers with your device work just fine. that explains why you can send commands to the device and get responses back. however, as soon as you try to transfer data (which require usb bulk transfer) the device chokes. that is why you never see sdp response from the headset - it probably never saw the sdp request, because bulk transfer failed and the data were never transmitted over the radio. what is the model of your bluetooth usb dongle? are you using usb hub? what is your usb controller type uhci, ohci or ehci? thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 29 04:22:20 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 AA2F316A41F for ; Tue, 29 Nov 2005 04:22:20 +0000 (GMT) (envelope-from C.H.Zhu@herts.ac.uk) Received: from mta07-winn.ispmail.ntl.com (mta07-winn.ispmail.ntl.com [81.103.221.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81BC343D72 for ; Tue, 29 Nov 2005 04:22:12 +0000 (GMT) (envelope-from C.H.Zhu@herts.ac.uk) Received: from aamta10-winn.ispmail.ntl.com ([81.103.221.35]) by mta07-winn.ispmail.ntl.com with ESMTP id <20051129042211.NYMY21883.mta07-winn.ispmail.ntl.com@aamta10-winn.ispmail.ntl.com>; Tue, 29 Nov 2005 04:22:11 +0000 Received: from [82.23.211.112] by aamta10-winn.ispmail.ntl.com with ESMTP id <20051129042201.MQDL11396.aamta10-winn.ispmail.ntl.com@[82.23.211.112]>; Tue, 29 Nov 2005 04:22:01 +0000 To: Maksim Yevmenkin References: <863blgzdz0.fsf@fastmail.fm> <438B7FB0.5030704@savvis.net> <86psok1jl6.fsf@fastmail.fm> <438B9E3E.5020905@savvis.net> <86ek5019ld.fsf@fastmail.fm> <438BCE22.3050901@savvis.net> From: faigozhu Date: 29 Nov 2005 04:22:23 +0000 In-Reply-To: <438BCE22.3050901@savvis.net> Message-ID: <86r79013sw.fsf@fastmail.fm> Lines: 94 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-bluetooth@freebsd.org Subject: Re: Sdpcontrol search timeout in Motorola HS805 headset. 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, 29 Nov 2005 04:22:20 -0000 Maksim Yevmenkin writes: > [...] > > >> thanks. unfortunately, this binary dump did not reveal the problem. > >> i'd like you to try the following: > >> 1) reboot > >> 2) attach usb bluetooth dongle and start bluetooth stack > > # /etc/rc.bluetooth start ubt0 > > BD_ADDR: 00:0a:3a:63:de:86 > > Features: 0xff 0xfe 0xd 0x38 0x8 0x8 00 00 <3-Slot> <5-Slot> > > > > > > > > > > Max. ACL packet size: 377 bytes > > Number of ACL packets: 10 > > Max. SCO packet size: 16 bytes > > Number of SCO packets: 0 > > this looks good. number of sco packets == 0 is strange, but its not > your problem. i've seen this in other devices. is this a broadcom chip > based device? Yes. ubt0: Broadcom Belkin Bluetooth Device, rev 1.10/0.01, addr 2 ubt0: Broadcom Belkin Bluetooth Device, rev 1.10/0.01, addr 2 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 > >dmesg: > > [...] [...] > > > ubt_bulk_in_complete2: ubt0 - Bulk-in xfer failed, IOERROR (13). No new xfer will be submitted! > > aha! this is your problem. usb bulk transfer failed. that explains why > sdpcontrol failed. bluetooth usb device use usb control transfers to > send hci command and usb interrupt transfers to receive hci > event. bulk usb transfers used to transfer the data. > > so, in your case, usb control/interrupt transfers with your device > work just fine. that explains why you can send commands to the device > and get responses back. however, as soon as you try to transfer data > (which require usb bulk transfer) the device chokes. that is why you > never see sdp response from the headset - it probably never saw the > sdp request, because bulk transfer failed and the data were never > transmitted over the radio. > > what is the model of your bluetooth usb dongle? are you using usb hub? > what is your usb controller type uhci, ohci or ehci? sigh, belkin again. It's a belkin bluetooth usb adapter, model F8T008. Another usb device is a usb mouse. Both of them directly connection to my laptop, no usb hub. dmesg|grep uhci uhci0: port 0x1820-0x183f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 uhci1: port 0x1840-0x185f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 uhci2: port 0x1860-0x187f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 %dmesg|grep ohci fwohci0: port 0x3400-0x347f mem 0xe0200000-0xe02007ff irq 20 at device 0.0 on pci2 fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:02:3f:3a:41:00:20:b8 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode %dmesg|grep echi % Is that any solution? Or, likely NDIS, to use windows native driver? > > thanks, > max > -- Many thanks, Faigozhu From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 29 04:54:35 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 7106516A41F for ; Tue, 29 Nov 2005 04:54:35 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from mta13.adelphia.net (mta13.adelphia.net [68.168.78.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E09A43D53 for ; Tue, 29 Nov 2005 04:54:34 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [192.168.1.254] (really [70.32.199.60]) by mta13.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051129045433.VXMI12926.mta13.adelphia.net@[192.168.1.254]>; Mon, 28 Nov 2005 23:54:33 -0500 Message-ID: <438BDEFE.4050400@savvis.net> Date: Mon, 28 Nov 2005 20:54:22 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: faigozhu References: <863blgzdz0.fsf@fastmail.fm> <438B7FB0.5030704@savvis.net> <86psok1jl6.fsf@fastmail.fm> <438B9E3E.5020905@savvis.net> <86ek5019ld.fsf@fastmail.fm> <438BCE22.3050901@savvis.net> <86r79013sw.fsf@fastmail.fm> In-Reply-To: <86r79013sw.fsf@fastmail.fm> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: Sdpcontrol search timeout in Motorola HS805 headset. 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, 29 Nov 2005 04:54:35 -0000 [...] >>># /etc/rc.bluetooth start ubt0 >>>BD_ADDR: 00:0a:3a:63:de:86 >>>Features: 0xff 0xfe 0xd 0x38 0x8 0x8 00 00 <3-Slot> <5-Slot> >>> >>> >>> >>> >>> Max. ACL packet size: 377 bytes >>>Number of ACL packets: 10 >>>Max. SCO packet size: 16 bytes >>>Number of SCO packets: 0 >> >>this looks good. number of sco packets == 0 is strange, but its not >>your problem. i've seen this in other devices. is this a broadcom chip >>based device? > > Yes. > > ubt0: Broadcom Belkin Bluetooth Device, rev 1.10/0.01, addr 2 > ubt0: Broadcom Belkin Bluetooth Device, rev 1.10/0.01, addr 2 > ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 > ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 i thought so :) >>>ubt_bulk_in_complete2: ubt0 - Bulk-in xfer failed, IOERROR (13). No new xfer will be submitted! >> >>aha! this is your problem. usb bulk transfer failed. that explains why >>sdpcontrol failed. bluetooth usb device use usb control transfers to >>send hci command and usb interrupt transfers to receive hci >>event. bulk usb transfers used to transfer the data. >> >>so, in your case, usb control/interrupt transfers with your device >>work just fine. that explains why you can send commands to the device >>and get responses back. however, as soon as you try to transfer data >>(which require usb bulk transfer) the device chokes. that is why you >>never see sdp response from the headset - it probably never saw the >>sdp request, because bulk transfer failed and the data were never >>transmitted over the radio. >> >>what is the model of your bluetooth usb dongle? are you using usb hub? >>what is your usb controller type uhci, ohci or ehci? > > sigh, belkin again. > > It's a belkin bluetooth usb adapter, model F8T008. Another usb device is a usb mouse. > Both of them directly connection to my laptop, no usb hub. i guess you could try to plug it into different usb slots. use # usbdevs -dv to see where it got connected. if you have usb hub around try to plug it through hub. i have f8t001 in my collection, and, it works for me. f8t001 is a broadcom bcm2033 chip based device, so i need to download firmware into it to make it work. i will see if i can get f8t008 cheap locally. > dmesg|grep uhci > uhci0: port 0x1820-0x183f irq 16 at device 29.0 on pci0 > uhci0: [GIANT-LOCKED] > usb0: on uhci0 > uhci1: port 0x1840-0x185f irq 19 at device 29.1 on pci0 > uhci1: [GIANT-LOCKED] > usb1: on uhci1 > uhci2: port 0x1860-0x187f irq 18 at device 29.2 on pci0 > uhci2: [GIANT-LOCKED] > usb2: on uhci2 what does # usbdevs -dv say? > Is that any solution? Or, likely NDIS, to use windows native driver? at this point, it does look like usb related problem. try different usb dongle. i recommend csr chip based devices. you can not use windows native driver with freebsd ndis'ulator. it wont work. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 29 05:24:22 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 CEBCF16A41F for ; Tue, 29 Nov 2005 05:24:22 +0000 (GMT) (envelope-from C.H.Zhu@herts.ac.uk) Received: from mta07-winn.ispmail.ntl.com (mta07-winn.ispmail.ntl.com [81.103.221.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id C36C043D53 for ; Tue, 29 Nov 2005 05:24:20 +0000 (GMT) (envelope-from C.H.Zhu@herts.ac.uk) Received: from aamta11-winn.ispmail.ntl.com ([81.103.221.35]) by mta07-winn.ispmail.ntl.com with ESMTP id <20051129052420.OLPF21883.mta07-winn.ispmail.ntl.com@aamta11-winn.ispmail.ntl.com>; Tue, 29 Nov 2005 05:24:20 +0000 Received: from [82.23.211.112] by aamta11-winn.ispmail.ntl.com with ESMTP id <20051129052418.OCBG16192.aamta11-winn.ispmail.ntl.com@[82.23.211.112]>; Tue, 29 Nov 2005 05:24:18 +0000 To: Maksim Yevmenkin References: <863blgzdz0.fsf@fastmail.fm> <438B7FB0.5030704@savvis.net> <86psok1jl6.fsf@fastmail.fm> <438B9E3E.5020905@savvis.net> <86ek5019ld.fsf@fastmail.fm> <438BCE22.3050901@savvis.net> <86r79013sw.fsf@fastmail.fm> <438BDEFE.4050400@savvis.net> From: faigozhu Date: 29 Nov 2005 05:24:36 +0000 In-Reply-To: <438BDEFE.4050400@savvis.net> Message-ID: <86mzjokovf.fsf@fastmail.fm> Lines: 86 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-bluetooth@freebsd.org Subject: Re: Sdpcontrol search timeout in Motorola HS805 headset. 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, 29 Nov 2005 05:24:23 -0000 Maksim Yevmenkin writes: ... ... > > F8T008. Another usb device is a usb mouse. > > Both of them directly connection to my laptop, no usb hub. > > i guess you could try to plug it into different usb slots. use > > # usbdevs -dv > > to see where it got connected. if you have usb hub around try to plug > it through hub. i have f8t001 in my collection, and, it works for > me. f8t001 is a broadcom bcm2033 chip based device, so i need to > download firmware into it to make it work. i will see if i can get > f8t008 cheap locally. > > > dmesg|grep uhci > > uhci0: port 0x1820-0x183f irq 16 at device 29.0 on pci0 > > uhci0: [GIANT-LOCKED] > > usb0: on uhci0 > > uhci1: port 0x1840-0x185f irq 19 at device 29.1 on pci0 > > uhci1: [GIANT-LOCKED] > > usb1: on uhci1 > > uhci2: port 0x1860-0x187f irq 18 at device 29.2 on pci0 > > uhci2: [GIANT-LOCKED] > > usb2: on uhci2 > > what does > > # usbdevs -dv > > say? usbdevs -dv Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 uhub0 port 1 powered port 2 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 uhub1 port 1 powered port 2 powered Controller /dev/usb2: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 uhub2 port 1 addr 2: low speed, power 100 mA, config 1, product 0x0000(0x0000), vendor 0x062a(0x062a), rev 0.00 ums0 port 2 powered Controller /dev/usb3: addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), Intel(0x0000), rev 1.00 uhub3 port 1 powered port 2 powered port 3 powered port 4 powered port 5 powered port 6 powered > > > Is that any solution? Or, likely NDIS, to use windows native driver? > > at this point, it does look like usb related problem. try different > usb dongle. i recommend csr chip based devices. you can not use > windows native driver with freebsd ndis'ulator. it wont work. > > thanks, > max I am pretty sure I got l2ping works by a script but I just can't repeat it. cat cmds.sh #!/bin/sh hccontrol -n ubt0hci create_connection 00:0b:2e:32:65:12 hccontrol -n ubt0hci read_connection_list #[msg:network is down]l2control -a 00:0b:2e:32:65:12 read_channel_list l2ping -a 00:0b:2e:32:65:12 -- Many thanks, Faigozhu From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 29 17:43:12 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 4D1EC16A41F for ; Tue, 29 Nov 2005 17:43:12 +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 7FFD343D6E for ; Tue, 29 Nov 2005 17:43:11 +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 jATHh9J17560; Tue, 29 Nov 2005 12:43:09 -0500 Message-ID: <438C932B.8090609@savvis.net> Date: Tue, 29 Nov 2005 09:43:07 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: faigozhu References: <863blgzdz0.fsf@fastmail.fm> <438B7FB0.5030704@savvis.net> <86psok1jl6.fsf@fastmail.fm> <438B9E3E.5020905@savvis.net> <86ek5019ld.fsf@fastmail.fm> <438BCE22.3050901@savvis.net> <86r79013sw.fsf@fastmail.fm> <438BDEFE.4050400@savvis.net> <86mzjokovf.fsf@fastmail.fm> In-Reply-To: <86mzjokovf.fsf@fastmail.fm> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: Sdpcontrol search timeout in Motorola HS805 headset. 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, 29 Nov 2005 17:43:12 -0000 ... >>>F8T008. Another usb device is a usb mouse. >>>Both of them directly connection to my laptop, no usb hub. >> >>i guess you could try to plug it into different usb slots. use >> >># usbdevs -dv >> >>to see where it got connected. if you have usb hub around try to plug >>it through hub. i have f8t001 in my collection, and, it works for >>me. f8t001 is a broadcom bcm2033 chip based device, so i need to >>download firmware into it to make it work. i will see if i can get >>f8t008 cheap locally. >> >>what does >> >># usbdevs -dv >> >>say? > > usbdevs -dv > Controller /dev/usb0: > addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 > uhub0 > port 1 powered > port 2 powered > Controller /dev/usb1: > addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 > uhub1 > port 1 powered > port 2 powered > Controller /dev/usb2: > addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 > uhub2 > port 1 addr 2: low speed, power 100 mA, config 1, product 0x0000(0x0000), vendor 0x062a(0x062a), rev 0.00 > ums0 > port 2 powered > Controller /dev/usb3: > addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), Intel(0x0000), rev 1.00 > uhub3 > port 1 powered > port 2 powered > port 3 powered > port 4 powered > port 5 powered > port 6 powered just try to re-plug the device in the different usb slots. see if it changes anything. > I am pretty sure I got l2ping works by a script but I just can't repeat it. > > cat cmds.sh > #!/bin/sh > hccontrol -n ubt0hci create_connection 00:0b:2e:32:65:12 > hccontrol -n ubt0hci read_connection_list > #[msg:network is down]l2control -a 00:0b:2e:32:65:12 read_channel_list l2control should use bd_addr of the _local_ device, i.e. bd_addr of your usb dongle. not headset's bd_addr. > l2ping -a 00:0b:2e:32:65:12 actually, if l2ping works then sdpcontrol should work too. l2ping requires l2cap transaction, which in turn requires acl data transfer and this requires usb bulk transfer. since usb bulk transfers do not work with your device, l2ping should fail too. it will timeout after about a minute and will print result anyway. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Dec 1 12:52:14 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 9038D16A41F for ; Thu, 1 Dec 2005 12:52:14 +0000 (GMT) (envelope-from nocturnal@swehack.se) Received: from mail2.swebase.com (mail2.swebase.com [82.99.44.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C3F243D55 for ; Thu, 1 Dec 2005 12:52:12 +0000 (GMT) (envelope-from nocturnal@swehack.se) Received: from [82.99.47.5] by mail2.swebase.com (MDaemon.PRO.v8.1.0.R) with ESMTP id md50004046604.msg for ; Thu, 01 Dec 2005 13:51:30 +0100 Message-ID: <438EF1BE.5050403@swehack.se> Date: Thu, 01 Dec 2005 13:51:10 +0100 From: nocturnal User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051129) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-bluetooth@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-MDRemoteIP: 82.99.47.5 X-Return-Path: nocturnal@swehack.se X-MDaemon-Deliver-To: freebsd-bluetooth@freebsd.org X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail2 X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.0.4 X-Spam-Level: X-Spam-Processed: mail2.swebase.com, Thu, 01 Dec 2005 13:51:33 +0100 Subject: Password authentication Sony K750i 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: Thu, 01 Dec 2005 12:52:14 -0000 Hi My phone asks for a passphrase whenever i try and connect to a bluetooth device and it expects me to enter the same passphrase on the other device before it can continue the connection. I can't find anything in the bluetooth docs and manuals about authentication so i thought i'd ask here. I get a lot of information using the commands in the handbook and i can even ping my phone with l2ping, which i thought was kinda cool. My real goal is to transfer files though. I tried using obexapp but i couldn't really figure it out and i guess i got errors because my phone wouldn't allow it to connect. I'm using FreeBSD 6.0 and my phone is a Sony Ericsson k750i. -- Med vänliga hälsningar Stefan Midjich aka nocturnal [Swehack] http://swehack.se From owner-freebsd-bluetooth@FreeBSD.ORG Thu Dec 1 13:19:49 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 DAED516A41F for ; Thu, 1 Dec 2005 13:19:49 +0000 (GMT) (envelope-from nocturnal@swehack.se) Received: from mail2.swebase.com (mail2.swebase.com [82.99.44.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id E534743D79 for ; Thu, 1 Dec 2005 13:19:37 +0000 (GMT) (envelope-from nocturnal@swehack.se) Received: from [82.99.47.5] by mail2.swebase.com (MDaemon.PRO.v8.1.0.R) with ESMTP id md50004047552.msg for ; Thu, 01 Dec 2005 14:18:54 +0100 Message-ID: <438EF83A.6090805@swehack.se> Date: Thu, 01 Dec 2005 14:18:50 +0100 From: nocturnal User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051129) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-bluetooth@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-MDRemoteIP: 82.99.47.5 X-Return-Path: nocturnal@swehack.se X-MDaemon-Deliver-To: freebsd-bluetooth@freebsd.org X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail2 X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.0.4 X-Spam-Level: X-Spam-Processed: mail2.swebase.com, Thu, 01 Dec 2005 14:18:56 +0100 Subject: Password authentication 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: Thu, 01 Dec 2005 13:19:50 -0000 Hi I sent the message about password authentication on k750i but i solved it after finding the hcsecd.conf file. -- Med vänliga hälsningar Stefan Midjich aka nocturnal [Swehack] http://swehack.se From owner-freebsd-bluetooth@FreeBSD.ORG Thu Dec 1 20:49:27 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 8C06516A41F; Thu, 1 Dec 2005 20:49:27 +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 0FBDF43D45; Thu, 1 Dec 2005 20:49:26 +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 jB1KnQJ20422; Thu, 1 Dec 2005 15:49:26 -0500 Message-ID: <438F61D4.9020507@savvis.net> Date: Thu, 01 Dec 2005 12:49:24 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD_Bluetooth Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: bluetooth gadgets donations please 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: Thu, 01 Dec 2005 20:49:27 -0000 Dear Bluetooth Users, i'm asking for donations please. any bluetooth enabled gadget will do. used, refurbished or demo units are welcome. i already purchased a couple of used sony ericsson cell phones (t630 and k700i), used nokia 3650 symbian cell phone, few usb bluetooth dongles (3com, belkin, trandnet), a couple of bluetooth pc-cards (3com and xircom) and headset (plantronis m2500). i'd like to get a handheld (ipaq, palm, etc.). if you can help, then please visit http://www.freebsd.org/donations/ and/or contact me directly. my freebsd commiter's id is "emax". donations will be used to enhance bluetooth support in freebsd. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Fri Dec 2 00:43:20 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 6C58B16A41F for ; Fri, 2 Dec 2005 00:43:20 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smtp-out1.tiscali.nl (smtp-out1.tiscali.nl [195.241.79.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0613F43D66 for ; Fri, 2 Dec 2005 00:43:20 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from [82.171.39.195] (helo=guido.klop.ws) by smtp-out1.tiscali.nl with smtp (Tiscali http://www.tiscali.nl) id 1Ehz1D-0005aa-Fy for ; Fri, 02 Dec 2005 01:43:19 +0100 Received: (qmail 2191 invoked from network); 2 Dec 2005 00:43:18 -0000 Received: from localhost.thuis.klop.ws (HELO outgoing.local) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; 2 Dec 2005 00:43:18 -0000 To: freebsd-bluetooth@freebsd.org Date: Fri, 02 Dec 2005 01:43:16 +0100 From: "Ronald Klop" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: User-Agent: Opera M2/8.51 (FreeBSD, build 1462) Subject: kde bluetooth support 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, 02 Dec 2005 00:43:20 -0000 Hello, In KDE their is a project which provides bluetooth support for Linux. It has very nice applications to browse the directories of a device, etc. Is somebody using this with FreeBSD? Or did somebody try it in the past? Are you willing to share experiences in this? Ronald. -- Ronald Klop Amsterdam, The Netherlands From owner-freebsd-bluetooth@FreeBSD.ORG Fri Dec 2 00:58:59 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 CEC0A16A41F for ; Fri, 2 Dec 2005 00:58:59 +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 199D943D46 for ; Fri, 2 Dec 2005 00:58:58 +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 jB20wuJ26033; Thu, 1 Dec 2005 19:58:56 -0500 Message-ID: <438F9C4F.8050600@savvis.net> Date: Thu, 01 Dec 2005 16:58:55 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ronald Klop References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: kde bluetooth support 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, 02 Dec 2005 00:58:59 -0000 Ronald, > In KDE their is a project which provides bluetooth support for Linux. > It has very nice applications to browse the directories of a device, etc. > Is somebody using this with FreeBSD? Or did somebody try it in the > past? Are you willing to share experiences in this? its probably not going to work on freebsd :( linux applications are *very* bluez specific. in theory it should be possible to port most (if not all) of the functionality to freebsd. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Sat Dec 3 01:02:14 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 CC84016A41F for ; Sat, 3 Dec 2005 01:02:14 +0000 (GMT) (envelope-from office@pershing.be) Received: from out-2.mail.amis.net (out-2.mail.amis.net [212.18.32.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11A3D43D60 for ; Sat, 3 Dec 2005 01:02:14 +0000 (GMT) (envelope-from office@pershing.be) Received: from localhost (in-4.mail.amis.net [212.18.32.23]) by out-2.mail.amis.net (Postfix) with ESMTP id 7B6F6108FBC for ; Sat, 3 Dec 2005 02:02:12 +0100 (CET) Received: from in-4.mail.amis.net ([127.0.0.1]) by localhost (in-4.mail.amis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 33396-01 for ; Sat, 3 Dec 2005 02:02:10 +0100 (CET) Received: from smtp.amis.net (smtp.amis.net [IPv6:2001:15c0::41]) by in-4.mail.amis.net (Postfix) with ESMTP id 1B16DB4792 for ; Sat, 3 Dec 2005 02:02:10 +0100 (CET) Received: from office.pershing.be (cpe-212-18-59-182.dynamic.amis.net [212.18.59.182]) by smtp.amis.net (Postfix) with SMTP id BEB48396801 for ; Sat, 3 Dec 2005 02:02:09 +0100 (CET) From: Branko To: freebsd-bluetooth@freebsd.org Organization: SOL X-Mailer: SOLmail ver 5.0.1 X-Operating-System: SOLos hack proof operating system Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20051203010209.BEB48396801@smtp.amis.net> Date: Sat, 3 Dec 2005 02:02:09 +0100 (CET) X-Virus-Scanned: by amavisd-new at amis.net X-Spam-Status: No, score=-5.669 required=5 tests=[ALL_TRUSTED=-3.3, AWL=0.230, BAYES_00=-2.599] X-Spam-Score: -5.669 X-Spam-Level: Subject: LAN 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: Sat, 03 Dec 2005 01:02:14 -0000 Hi, I tried to use PPP LAN connection over bluetooth. FreeBSD server for gateway and laptop with windows for client. This are my configs. hcsecd.conf device { bdaddr 00:20:E0:27:8C:0C; name "URKO"; key nokey; pin "1234"; } ppp.conf rfcomm-server: set timeout 0 set lqrperiod 10 set ifaddr 192.168.1.10 192.168.1.11-192.168.1.20 255.255.255.0 enable lqr accept lqr disable pap deny pap disable chap deny chap /etc/rc.bluetooth start ubt0 /usr/sbin/hcsecd /usr/sbin/sdpd /usr/sbin/rfcomm_pppd -s -C 7 -l rfcomm-server thats how i start rfcomm_server and others. Pairing of devices works fine. I can also connect both computers. Ethernet adapter Bluetooth Network: Media State . . . . . . . . . . . : Media disc Media State . . . . . . . . . . . : Media disconnected Description . . . . . . . . . . . : Bluetooth LAN Access Server Driver Physical Address. . . . . . . . . : 00-20-E0-27-8C-0C PPP adapter BluetoothNullConnection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface Physical Address. . . . . . . . . : 00-53-45-00-00-00 Dhcp Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.1.20 Subnet Mask . . . . . . . . . . . : 255.255.255.255 Default Gateway . . . . . . . . . : 192.168.1.20 But when i try to open lets say www.google.com connection always drop down. Thats * from logs Dec 3 01:27:46 office sdpd[934]: Client on L2CAP socket has disconnected Dec 3 01:27:47 office hcsecd[932]: Got Link_Key_Request event from 'ubt0hci', remote bdaddr 00:20:e0:27:8c:0c Dec 3 01:27:47 office hcsecd[932]: Found matching entry, remote bdaddr 00:20:e0:27:8c:0c, name 'URKO', link key exists Dec 3 01:27:47 office hcsecd[932]: Sending Link_Key_Reply to 'ubt0hci' for remote bdaddr 00:20:e0:27:8c:0c Dec 3 01:27:47 office ppp[1618]: Phase: Using interface: tun1 Dec 3 01:27:47 office ppp[1618]: Phase: deflink: Created in closed state Dec 3 01:27:47 office ppp[1618]: Phase: PPP Started (direct mode). Dec 3 01:27:47 office ppp[1618]: Phase: bundle: Establish Dec 3 01:27:47 office ppp[1618]: Phase: deflink: closed -> opening Dec 3 01:27:47 office ppp[1618]: Phase: deflink: Connected! Dec 3 01:27:47 office ppp[1618]: Phase: deflink: opening -> carrier Dec 3 01:27:47 office ppp[1618]: Phase: deflink: carrier -> lcp Dec 3 01:27:54 office ppp[1618]: Phase: deflink: lcp -> open Dec 3 01:27:54 office ppp[1618]: Phase: bundle: Network Dec 3 01:27:54 office ppp[1618]: Phase: deflink: IPV6CP protocol reject closes IPV6CP ! Dec 3 01:27:54 office ppp[1618]: Phase: deflink: IPV6CP protocol reject closes IPV6CP ! Dec 3 01:27:54 office ppp[1618]: Warning: ff02:6::/32: Change route failed: errno: Network is unreachable Dec 3 01:27:57 office ppp[1618]: Phase: deflink: IPV6CP protocol reject closes IPV6CP ! Dec 3 01:27:59 office kernel: ng_btsocket_rfcomm_session_send: Could not send data to L2CAP socket, error=40 Dec 3 01:27:59 office ppp[1618]: Phase: deflink: read (0): Connection reset by peer Dec 3 01:27:59 office ppp[1618]: Phase: deflink: open -> lcp Dec 3 01:27:59 office ppp[1618]: Warning: ff02:6::/32: Change route failed: errno: Network is unreachable Dec 3 01:27:59 office ppp[1618]: Phase: bundle: Terminate Dec 3 01:27:59 office ppp[1618]: Phase: deflink: Disconnected! Dec 3 01:27:59 office ppp[1618]: Phase: deflink: Connect time: 12 secs: 15749 octets in, 4416 octets out Dec 3 01:27:59 office ppp[1618]: Phase: deflink: 81 packets in, 61 packets out Dec 3 01:27:59 office kernel: ng_l2cap_l2ca_receive: ubt0l2cap - unexpected L2CAP data packet. Invalid channel state, cid=70, state=5 Dec 3 01:27:59 office ppp[1618]: Phase: total 1680 bytes/sec, peak 2707 bytes/sec on Sat Dec 3 01:27:58 2005 Dec 3 01:27:59 office ppp[1618]: Phase: deflink: lcp -> closed Dec 3 01:27:59 office ppp[1618]: Phase: bundle: Dead Dec 3 01:27:59 office ppp[1618]: Phase: PPP Terminated (normal). thanks, brane From owner-freebsd-bluetooth@FreeBSD.ORG Sat Dec 3 01:14:04 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 5D2B716A41F for ; Sat, 3 Dec 2005 01:14:04 +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 EC89943D62 for ; Sat, 3 Dec 2005 01:14:03 +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 jB31DuJ24619; Fri, 2 Dec 2005 20:14:01 -0500 Message-ID: <4390F151.5010604@savvis.net> Date: Fri, 02 Dec 2005 17:13:53 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Branko References: <20051203010209.BEB48396801@smtp.amis.net> In-Reply-To: <20051203010209.BEB48396801@smtp.amis.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: LAN 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: Sat, 03 Dec 2005 01:14:04 -0000 Hello, > Hi, I tried to use PPP LAN connection over bluetooth. FreeBSD server > for gateway and laptop with windows for client. > > This are my configs. configs looks fine and skipped. > But when i try to open lets say www.google.com connection always drop > down. [...] > ng_btsocket_rfcomm_session_send: Could not send data to L2CAP socket, > error=40 this is exactly the problem few people new reported and i can not reproduce it here :( it seems to affect windows (including windows mobile on at least ipaq handhelds). what bluetooth stack are you using on windows? the built-in bluetooth stack in xp does not seem to know how to do lan, or, at least, i could not find how to do it after 30 minutes i played with it. if this is a third party stack could you please put content of the cd, you installed it from, somewhere i can download it from? or if its available online just point me to it? thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Sat Dec 3 01:22:08 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 A3BD316A422 for ; Sat, 3 Dec 2005 01:22:07 +0000 (GMT) (envelope-from office@pershing.be) Received: from out-1.mail.amis.net (out-1.mail.amis.net [212.18.32.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2BFE43D49 for ; Sat, 3 Dec 2005 01:22:05 +0000 (GMT) (envelope-from office@pershing.be) Received: from localhost (in-1.mail.amis.net [212.18.32.15]) by out-1.mail.amis.net (Postfix) with ESMTP id 0EF395B577F for ; Sat, 3 Dec 2005 02:22:04 +0100 (CET) Received: from in-1.mail.amis.net ([127.0.0.1]) by localhost (in-1.mail.amis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 44020-03 for ; Sat, 3 Dec 2005 02:22:02 +0100 (CET) Received: from smtp.amis.net (smtp.amis.net [IPv6:2001:15c0::41]) by in-1.mail.amis.net (Postfix) with ESMTP id E14862D759F for ; Sat, 3 Dec 2005 02:22:01 +0100 (CET) Received: from office.pershing.be (cpe-212-18-59-182.dynamic.amis.net [212.18.59.182]) by smtp.amis.net (Postfix) with SMTP id C9DFF396801 for ; Sat, 3 Dec 2005 02:22:01 +0100 (CET) From: Branko To: freebsd-bluetooth@freebsd.org In-Reply-To: <4390F151.5010604@savvis.net> References: <20051203010209.BEB48396801@smtp.amis.net> <4390F151.5010604@savvis.net> Organization: SOL X-Mailer: SOLmail ver 5.0.1 X-Operating-System: SOLos hack proof operating system Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20051203012201.C9DFF396801@smtp.amis.net> Date: Sat, 3 Dec 2005 02:22:01 +0100 (CET) X-Virus-Scanned: by amavisd-new at amis.net X-Spam-Status: No, score=-5.894 required=5 tests=[ALL_TRUSTED=-3.3, AWL=0.005, BAYES_00=-2.599] X-Spam-Score: -5.894 X-Spam-Level: Subject: Re: LAN 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: Sat, 03 Dec 2005 01:22:08 -0000 http://h18007.www1.hp.com/support/files/hpcpqnk/us/download/21763.html Brane On Fri, 02 Dec 2005 17:13:53 -0800 Maksim Yevmenkin wrote: > Hello, > > > Hi, I tried to use PPP LAN connection over bluetooth. FreeBSD server > > for gateway and laptop with windows for client. > > > > This are my configs. > > configs looks fine and skipped. > > > But when i try to open lets say www.google.com connection always drop > > down. > > [...] > > > ng_btsocket_rfcomm_session_send: Could not send data to L2CAP socket, > > error=40 > > this is exactly the problem few people new reported and i can not > reproduce it here :( it seems to affect windows (including windows > mobile on at least ipaq handhelds). > > what bluetooth stack are you using on windows? the built-in bluetooth > stack in xp does not seem to know how to do lan, or, at least, i could > not find how to do it after 30 minutes i played with it. > > if this is a third party stack could you please put content of the cd, > you installed it from, somewhere i can download it from? or if its > available online just point me to it? > > thanks, > max > From owner-freebsd-bluetooth@FreeBSD.ORG Sat Dec 3 16:07:55 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 C62A216A41F for ; Sat, 3 Dec 2005 16:07:55 +0000 (GMT) (envelope-from shackan@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5221D43D58 for ; Sat, 3 Dec 2005 16:07:55 +0000 (GMT) (envelope-from shackan@gmail.com) Received: by wproxy.gmail.com with SMTP id i12so871436wra for ; Sat, 03 Dec 2005 08:07:54 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=iS54YgasY+KXZKkjoj4PSm9LOCsU21lfwIciPbO2DcHCXS8Bpiol0tF8yYEJGpPM2VgCQR27v21zZoLpbRqMtAEZurWJj3Tssr7Db9ufKWRJ0V1bfWPDMG+1tvG7GK8aHrbFMwa2g4tlvz6oNLTfzAZoez9YFu1VF8Kg6D0xU68= Received: by 10.65.126.16 with SMTP id d16mr1486892qbn; Sat, 03 Dec 2005 08:07:54 -0800 (PST) Received: by 10.65.196.7 with HTTP; Sat, 3 Dec 2005 08:07:54 -0800 (PST) Message-ID: <9307f5f20512030807x6eadc73cq9d9acc9dd5503a5b@mail.gmail.com> Date: Sat, 3 Dec 2005 08:07:54 -0800 From: "P. Durante" To: freebsd-bluetooth@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Automatic bluetooth device initialization 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: Sat, 03 Dec 2005 16:07:55 -0000 Hi, I'm writing a daemon which takes advantage of dbus to manage bluetooth devices, until now I focused development mainly on linux but I'm keeping all the bluez-specific bits in a layer on its own and I'm investigating the possibility of a freebsd layer as well. From the source code of hccontrol and sdpcontrol it seems that the programming paradigm is not very different from the one used for linux (although your bt stack has nothing or little in common with bluez), but there's a substantial difference I've stumbled upon today: in bluez it is possible to open a "control connection" with the bt stack and use this socket to asynchronously read stack internal events (like device added/removed), I used those events to trigger my daemon to send dbus signals and initialize some internal data structures which expose a bluetooth device over dbus, I'd like to know if something similar is available in the freebsd stack as well. regards, Paul From owner-freebsd-bluetooth@FreeBSD.ORG Sat Dec 3 18:25:49 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 36FC716A41F for ; Sat, 3 Dec 2005 18:25:49 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from mta11.adelphia.net (mta11.adelphia.net [68.168.78.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB9D243D64 for ; Sat, 3 Dec 2005 18:25:48 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [192.168.1.254] (really [70.32.199.60]) by mta11.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051203182547.VCSG26058.mta11.adelphia.net@[192.168.1.254]>; Sat, 3 Dec 2005 13:25:47 -0500 Message-ID: <4391E320.2090006@savvis.net> Date: Sat, 03 Dec 2005 10:25:36 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "P. Durante" References: <9307f5f20512030807x6eadc73cq9d9acc9dd5503a5b@mail.gmail.com> In-Reply-To: <9307f5f20512030807x6eadc73cq9d9acc9dd5503a5b@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: Automatic bluetooth device initialization 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: Sat, 03 Dec 2005 18:25:49 -0000 Paul, > I'm writing a daemon which takes advantage of dbus to manage bluetooth > devices, until now I focused development mainly on linux but I'm > keeping all the bluez-specific bits in a layer on its own and I'm > investigating the possibility of a freebsd layer as well. From the fine. if you could please tell us a little bit more and explain what is wrong with the current way of doing things in linux and/or freebsd. it was my understanding that linux has hcid daemon that takes care of bluetooth device configuration. in freebsd things where less flexible until recently. not so long ago i have committed few bits and pieces to integrate bluetooth into freebsd rc.d subsystem. i will update freebsd handbook bluetooth chapter shortly. > source code of hccontrol and sdpcontrol it seems that the programming > paradigm is not very different from the one used for linux (although > your bt stack has nothing or little in common with bluez), but there's correct. the concept of sockets in bluetooth domain is similar. > a substantial difference I've stumbled upon today: in bluez it is > possible to open a "control connection" with the bt stack and use this > socket to asynchronously read stack internal events (like device > added/removed), I used those events to trigger my daemon to send dbus > signals and initialize some internal data structures which expose a > bluetooth device over dbus, I'd like to know if something similar is > available in the freebsd stack as well. freebsd uses different approach. basically there is a devctl(4) driver and devd(8) daemon. whenever a device is added to or removed from the device tree, devd(8) will execute actions specified in its configuration file. devd(8) and devctl(4) man pages are available online at http://www.freebsd.org/cgi/man.cgi?query=devd&apropos=0&sektion=0&manpath=FreeBSD+6.0-RELEASE+and+Ports&format=html http://www.freebsd.org/cgi/man.cgi?query=devctl&sektion=4&apropos=0&manpath=FreeBSD+6.0-RELEASE+and+Ports thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Sat Dec 3 21:33:42 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 8B52916A420 for ; Sat, 3 Dec 2005 21:33:42 +0000 (GMT) (envelope-from shackan@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9DB643D7E for ; Sat, 3 Dec 2005 21:33:36 +0000 (GMT) (envelope-from shackan@gmail.com) Received: by wproxy.gmail.com with SMTP id i6so565166wra for ; Sat, 03 Dec 2005 13:33:32 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=diYLHKsNNpovnM5wWduN/Y7a/LGeV4o++Z+knAn/PCd3AAlqozxTEGUsCKDhInAzBBx7jXE9ZnKKOtZDycY9qY2t4du0rLzcYpirZ7wV4BdfSUJXyjBboQlG1JhJ33zgeHi2M4JHKAToctKnx1MLZkOOmEWU7oWkvFFTDspREo8= Received: by 10.64.91.2 with SMTP id o2mr2128909qbb; Sat, 03 Dec 2005 13:33:32 -0800 (PST) Received: by 10.65.196.7 with HTTP; Sat, 3 Dec 2005 13:33:32 -0800 (PST) Message-ID: <9307f5f20512031333x61e9d141u85ea578711740712@mail.gmail.com> Date: Sat, 3 Dec 2005 13:33:32 -0800 From: "P. Durante" To: Maksim Yevmenkin In-Reply-To: <4391E320.2090006@savvis.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <9307f5f20512030807x6eadc73cq9d9acc9dd5503a5b@mail.gmail.com> <4391E320.2090006@savvis.net> Cc: freebsd-bluetooth@freebsd.org Subject: Re: Automatic bluetooth device initialization 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: Sat, 03 Dec 2005 21:33:42 -0000 hi maksim, thanks for the quick answer > fine. if you could please tell us a little bit more and explain what is > wrong with the current way of doing things in linux and/or freebsd. don't get me wrong, there isn't anything wrong with the current state of bluetooth configuration utilities. If you've spent some time reading the freebsd handbook or some unofficial bluez tutorials and you're accustomed to the command line (like most of the people on this list, I assume) then you're just set.. ..but if you take into account the regular desktop user (like how linux and freebsd are trying to do right now) you see the need for something more intuitive and immediate than the 'current way of doing things', this basically involves some sort of user interface, at the very least. Even on this mailing list, little time ago, there was a request about porting the excellent kde bluetooth framework to freebsd, but, as you noted, in it's current form kdebluetooth has very deep roots in bluez, and it also has deep roots in KDE, so even adapting to another desktop manager would be difficult. To solve such (not uncommon) problems, the dbus system[=B9] is being developed, dbus is getting very popular (maybe too much) and it provides a simple and secure messaging system to let different programs talk to one another, in our example, let one program be the bluetooth daemon, it provides a well-known interface and hides platform-specific implementation details, on the other side we have the other programs, which are just frontends (with a Qt/Gtk/textual interface, it doesn't matter) and can run on every operating system where the aforementioned interface is available, I think something like this wouldn't hurt to any "desktop-unix" operating system. [=B9] http://www.freedesktop.org/wiki/Software_2fdbus > freebsd uses different approach. basically there is a devctl(4) driver > and devd(8) daemon. whenever a device is added to or removed from the > device tree, devd(8) will execute actions specified in its configuration > file. I'm looking at them right now, thanks again. regards, Paul