From owner-freebsd-bluetooth@FreeBSD.ORG Tue Jan 10 03:04:13 2006 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 2FBE116A41F for ; Tue, 10 Jan 2006 03:04:13 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49A1443D45 for ; Tue, 10 Jan 2006 03:04:11 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.22] (andersonbox2.centtech.com [192.168.42.22]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k0A34Aka045711 for ; Mon, 9 Jan 2006 21:04:11 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <43C32416.3030008@centtech.com> Date: Mon, 09 Jan 2006 21:03:50 -0600 From: Eric Anderson User-Agent: Mozilla Thunderbird 1.0.7 (X11/20060104) 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: 7bit X-Virus-Scanned: ClamAV 0.87.1/1235/Sun Jan 8 12:13:01 2006 on mh2.centtech.com X-Virus-Status: Clean Subject: Setting up a bluetooth mouse on FreeBSD 6 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, 10 Jan 2006 03:04:13 -0000 I've been asked several times how to do this, so I wrote up a quick howto from my notes. I've posted it here: http://destari.blogspot.com/2006/01/setting-up-bluetooth-mouse-on-freebsd.html Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 12 00:06:45 2006 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 1B03316A420 for ; Thu, 12 Jan 2006 00:06:45 +0000 (GMT) (envelope-from scycoon@internode.on.net) Received: from smtp1.adl2.internode.on.net (smtp1.adl2.internode.on.net [203.16.214.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CA5143D45 for ; Thu, 12 Jan 2006 00:06:43 +0000 (GMT) (envelope-from scycoon@internode.on.net) Received: from internode.on.net (webmail1.adl2.internode.on.net [203.16.214.245]) by smtp1.adl2.internode.on.net (8.13.5/8.13.5) with ESMTP id k0C06gnp092442 for ; Thu, 12 Jan 2006 10:36:43 +1030 (CST) (envelope-from scycoon@internode.on.net) Received: from 150.101.2.50 by HTTP Sender: scycoon@internode.on.net From: "scycoon@internode.on.net" To: freebsd-bluetooth@freebsd.org X-Mailer: scycoon - Internode Webmail v3.1r (http://www.internode.on.net/) X-Originating-IP: 150.101.2.50 Date: Thu, 12 Jan 2006 10:36:42 +1030 Message-id: <43c59d92.36a.33a6.26043@internode.on.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: Bluetooth Device Failing to Initialize X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: scycoon@internode.on.net List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2006 00:06:45 -0000 Hi There, I am have a problem with a linksys usbbt100 bluetooth dongle. I am running 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Sat Jan 7 08:48:40 CST 2006 >From dmesg I get this ubt0: vendor 0x0a12 product 0x0001, rev 1.10/5.25, addr 2 ubt0: vendor 0x0a12 product 0x0001, rev 1.10/5.25, addr 2 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, buffer size=294 I have setup the /etc/rc.bluetooth file as described in the handbook, and am using the ng_ubt module that is said to be the correct one. When i run /etc/rc.bluetooth start ubt0 I get bash-2.05b# /etc/rc.bluetooth start ubt0 BD_ADDR: 00:0c:41:e2:01:84 Features: 0xff 0xff 0xf 00 00 00 00 00 <3-Slot> <5-Slot> Max. ACL packet size: 192 bytes Number of ACL packets: 8 Max. SCO packet size: 64 bytes Number of SCO packets: 8 Could not execute command "initialize". Device not configured if i run hccontrol -n ubt0hci initialize i get bash-2.05b# hccontrol -n ubt0hci initialize Could not execute command "initialize". Device not configured I am running hcidump at the same time, which doesnt seem to see the initialize command; bash-2.05b# hcidump HCIDump - HCI packet analyzer ver 1.5 device: any snap_len: 65535 filter: 0xffffffff < HCI Command: Reset(0x03|0x0003) plen 0 > HCI Event: Command Complete(0x0e) plen 4 < HCI Command: Read BD ADDR(0x04|0x0009) plen 0 > HCI Event: Command Complete(0x0e) plen 10 < HCI Command: Read Local Supported Features(0x04|0x0003) plen 0 > HCI Event: Command Complete(0x0e) plen 12 < HCI Command: Read Buffer Size(0x04|0x0005) plen 0 > HCI Event: Command Complete(0x0e) plen 11 < HCI Command: Write Scan Enable(0x03|0x001a) plen 1 > HCI Event: Command Complete(0x0e) plen 4 < HCI Command: Write Class of Device(0x03|0x0024) plen 3 > HCI Event: Command Complete(0x0e) plen 4 < HCI Command: Change Local Name(0x03|0x0013) plen 248 > HCI Event: Command Complete(0x0e) plen 4 The device looks like it is ok, but something freaky is not allowing it to initialize properly and subsequent inquiry commands just time out. I should also point out that I have had the dongle working in Windows Land. Would this failure to initialize be preventing me from successfuly inquiring another device? Any help would be greatly appreciated. Regards Chriso From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 12 00:39:53 2006 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 61CF516A41F for ; Thu, 12 Jan 2006 00:39:53 +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 0770E43D45 for ; Thu, 12 Jan 2006 00:39:52 +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 k0C0dmP17363; Wed, 11 Jan 2006 19:39:48 -0500 Message-ID: <43C5A551.8000206@savvis.net> Date: Wed, 11 Jan 2006 16:39:45 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: scycoon@internode.on.net References: <43c59d92.36a.33a6.26043@internode.on.net> In-Reply-To: <43c59d92.36a.33a6.26043@internode.on.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: Bluetooth Device Failing to Initialize 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, 12 Jan 2006 00:39:53 -0000 Hello, > I am have a problem with a linksys usbbt100 bluetooth > dongle. lets see... > I am running > > 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Sat Jan 7 08:48:40 CST > 2006 ok >>From dmesg I get this > > ubt0: vendor 0x0a12 product 0x0001, rev 1.10/5.25, addr 2 > ubt0: vendor 0x0a12 product 0x0001, rev 1.10/5.25, addr 2 > ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, > bulk-out=0x2 > ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, > isoc-out=0x3; > wMaxPacketSize=49; nframes=6, buffer size=294 looks fine to me > I have setup the /etc/rc.bluetooth file as described in the > handbook, and am using the ng_ubt module that is said to be > the correct one. > > When i run > > /etc/rc.bluetooth start ubt0 > > I get > > bash-2.05b# /etc/rc.bluetooth start ubt0 > BD_ADDR: 00:0c:41:e2:01:84 > Features: 0xff 0xff 0xf 00 00 00 00 00 > <3-Slot> <5-Slot> > > > > > > Max. ACL packet size: 192 bytes > Number of ACL packets: 8 > Max. SCO packet size: 64 bytes > Number of SCO packets: 8 everything above looks fine > Could not execute command "initialize". Device not > configured this is *very* strange. 1) did you check your /var/log/messages to see if device has detached? 2) can you please run as root the following commands # ngctl types # ngctl li # ngctl status ubt0: # ngctl status ubt0hci: after you have executed "rc.bluetooth start ubt0" and got the error. > if i run > > hccontrol -n ubt0hci initialize > > i get > > bash-2.05b# hccontrol -n ubt0hci initialize > Could not execute command "initialize". Device not > configured please run the commands above and send me the output. > I am running hcidump at the same time, which doesnt seem to > see the initialize command; that is fine. "initialize" is an internal (to bluetooth stack) command. it only flips a bit inside hci node and tells it that initialization sequence was performed. you wont see "initialize" command in the hci dumps. [...] > The device looks like it is ok, but something freaky is not > allowing it to initialize properly and subsequent inquiry > commands just time out. I should also point out that I have > had the dongle working in Windows Land. i suspect that device is gone (detached). > Would this failure to initialize be preventing me from > successfuly inquiring another device? yes, because if i'm right and device is indeed gone then you cant do anything. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 12 07:35:20 2006 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 121AC16A41F for ; Thu, 12 Jan 2006 07:35:20 +0000 (GMT) (envelope-from scycoon@internode.on.net) Received: from smtp1.adl2.internode.on.net (smtp1.adl2.internode.on.net [203.16.214.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 574E743D46 for ; Thu, 12 Jan 2006 07:35:19 +0000 (GMT) (envelope-from scycoon@internode.on.net) Received: from bigboy.scycoon.soho.on.net (ppp122-249-76.static.internode.on.net [203.122.249.76]) by smtp1.adl2.internode.on.net (8.13.5/8.13.5) with ESMTP id k0C7ZGOq089689; Thu, 12 Jan 2006 18:05:17 +1030 (CST) (envelope-from scycoon@internode.on.net) From: Chriso Herring To: Maksim Yevmenkin In-Reply-To: <43C5A551.8000206@savvis.net> References: <43c59d92.36a.33a6.26043@internode.on.net> <43C5A551.8000206@savvis.net> Content-Type: text/plain Organization: Scycoon Date: Thu, 12 Jan 2006 18:05:15 +1030 Message-Id: <1137051315.613.7.camel@bigboy.scycoon.soho.on.net> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: Bluetooth Device Failing to Initialize X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: scycoon@internode.on.net List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2006 07:35:20 -0000 Max, I have included the requested output below, On Wed, 2006-01-11 at 16:39 -0800, Maksim Yevmenkin wrote: > Hello, > > > I am have a problem with a linksys usbbt100 bluetooth > > dongle. > > lets see... > > > I am running > > > > 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Sat Jan 7 08:48:40 CST > > 2006 > > ok > > >>From dmesg I get this > > > > ubt0: vendor 0x0a12 product 0x0001, rev 1.10/5.25, addr 2 > > ubt0: vendor 0x0a12 product 0x0001, rev 1.10/5.25, addr 2 > > ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, > > bulk-out=0x2 > > ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, > > isoc-out=0x3; > > wMaxPacketSize=49; nframes=6, buffer size=294 > > looks fine to me > > > I have setup the /etc/rc.bluetooth file as described in the > > handbook, and am using the ng_ubt module that is said to be > > the correct one. > > > > When i run > > > > /etc/rc.bluetooth start ubt0 > > > > I get > > > > bash-2.05b# /etc/rc.bluetooth start ubt0 > > BD_ADDR: 00:0c:41:e2:01:84 > > Features: 0xff 0xff 0xf 00 00 00 00 00 > > <3-Slot> <5-Slot> > > > > > > > > > > > > Max. ACL packet size: 192 bytes > > Number of ACL packets: 8 > > Max. SCO packet size: 64 bytes > > Number of SCO packets: 8 > > everything above looks fine > > > Could not execute command "initialize". Device not > > configured > > this is *very* strange. > > 1) did you check your /var/log/messages to see if device has detached? This is in the messages after I run /etc/rc.bluetooth after a fresh reboot; Jan 12 17:54:28 bigboy kernel: ng_hci_process_command_timeout: ubt0hci - unable to complete HCI command OGF=0x3, OCF=0x3. Timeout Jan 12 17:54:28 bigboy kernel: ng_hci_process_event: ubt0hci - got HCI event=0xe, length=4 Jan 12 17:54:28 bigboy kernel: complete_command: ubt0hci - no pending command, state=0x1 Jan 12 17:54:28 bigboy kernel: ubt_request_complete2: ubt0 - Control request failed. TIMEOUT (15) Jan 12 17:54:33 bigboy kernel: ng_hci_process_command_timeout: ubt0hci - unable to complete HCI command OGF=0x4, OCF=0x9. Timeout Jan 12 17:54:33 bigboy kernel: ng_hci_process_event: ubt0hci - got HCI event=0xe, length=10 Jan 12 17:54:33 bigboy kernel: complete_command: ubt0hci - no pending command, state=0x1 Jan 12 17:54:33 bigboy kernel: ubt_request_complete2: ubt0 - Control request failed. TIMEOUT (15) Jan 12 17:54:38 bigboy kernel: ng_hci_process_command_timeout: ubt0hci - unable to complete HCI command OGF=0x4, OCF=0x3. Timeout Jan 12 17:54:38 bigboy kernel: ng_hci_process_event: ubt0hci - got HCI event=0xe, length=12 Jan 12 17:54:38 bigboy kernel: complete_command: ubt0hci - no pending command, state=0x1 Jan 12 17:54:38 bigboy kernel: ubt_request_complete2: ubt0 - Control request failed. TIMEOUT (15) Jan 12 17:54:43 bigboy kernel: ng_hci_process_command_timeout: ubt0hci - unable to complete HCI command OGF=0x4, OCF=0x5. Timeout Jan 12 17:54:43 bigboy kernel: ng_hci_process_event: ubt0hci - got HCI event=0xe, length=11 Jan 12 17:54:43 bigboy kernel: complete_command: ubt0hci - no pending command, state=0x1 Jan 12 17:54:43 bigboy kernel: ubt_request_complete2: ubt0 - Control request failed. TIMEOUT (15) Jan 12 17:54:48 bigboy kernel: ng_hci_process_command_timeout: ubt0hci - unable to complete HCI command OGF=0x3, OCF=0x1a. Timeout Jan 12 17:54:48 bigboy kernel: ng_hci_process_event: ubt0hci - got HCI event=0xe, length=4 Jan 12 17:54:48 bigboy kernel: complete_command: ubt0hci - no pending command, state=0x1 Jan 12 17:54:48 bigboy kernel: ubt_request_complete2: ubt0 - Control request failed. TIMEOUT (15) Jan 12 17:54:53 bigboy kernel: ng_hci_process_command_timeout: ubt0hci - unable to complete HCI command OGF=0x3, OCF=0x24. Timeout Jan 12 17:54:53 bigboy kernel: ng_hci_process_event: ubt0hci - got HCI event=0xe, length=4 Jan 12 17:54:53 bigboy kernel: complete_command: ubt0hci - no pending command, state=0x1 Jan 12 17:54:53 bigboy kernel: ubt_request_complete2: ubt0 - Control request failed. TIMEOUT (15) Jan 12 17:54:58 bigboy kernel: ng_hci_process_command_timeout: ubt0hci - unable to complete HCI command OGF=0x3, OCF=0x13. Timeout Jan 12 17:54:58 bigboy kernel: ng_hci_process_event: ubt0hci - got HCI event=0xe, length=4 Jan 12 17:54:58 bigboy kernel: complete_command: ubt0hci - no pending command, state=0x1 Jan 12 17:54:58 bigboy kernel: ubt_request_complete2: ubt0 - Control request failed. TIMEOUT (15) > > 2) can you please run as root the following commands > > # ngctl types bash-2.05b# ngctl types There are 7 total types: Type name Number of living nodes --------- ---------------------- socket 1 btsock_l2c 1 btsock_l2c_raw 1 btsock_hci_raw 1 l2cap 1 hci 1 ubt 1 > > # ngctl li bash-2.05b# ngctl li There are 7 total nodes: Name: ngctl704 Type: socket ID: 00000013 Num hooks: 0 Name: ubt0l2cap Type: l2cap ID: 0000000c Num hooks: 3 Name: ubt0hci Type: hci ID: 00000008 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 > > # ngctl status ubt0: bash-2.05b# ngctl status ubt0: Status for "ubt0:": Hook: hook Flags: 0x30 Debug: 3 CMD queue: [have:0,max:12] ACL queue: [have:0,max:12] SCO queue: [have:0,max:12] > > # ngctl status ubt0hci: bash-2.05b# ngctl status ubt0hci: Status for "ubt0hci:": bdaddr 0:0:0:0:0:0 Hooks drv acl raw State 0x1 Queue cmd:0 Buffer cmd:1,acl:1,1,17,sco:1,1,10 > > after you have executed "rc.bluetooth start ubt0" and got the error. > > > if i run > > > > hccontrol -n ubt0hci initialize > > > > i get > > > > bash-2.05b# hccontrol -n ubt0hci initialize > > Could not execute command "initialize". Device not > > configured > > please run the commands above and send me the output. > > > I am running hcidump at the same time, which doesnt seem to > > see the initialize command; > > that is fine. "initialize" is an internal (to bluetooth stack) command. > it only flips a bit inside hci node and tells it that initialization > sequence was performed. you wont see "initialize" command in the hci dumps. > > [...] > > > The device looks like it is ok, but something freaky is not > > allowing it to initialize properly and subsequent inquiry > > commands just time out. I should also point out that I have > > had the dongle working in Windows Land. > > i suspect that device is gone (detached). > > > Would this failure to initialize be preventing me from > > successfuly inquiring another device? > > yes, because if i'm right and device is indeed gone then you cant do > anything. > > thanks, > max regards Chriso From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 12 19:24:50 2006 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 B6E2416A420 for ; Thu, 12 Jan 2006 19:24:50 +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 7A3B743D64 for ; Thu, 12 Jan 2006 19:24:27 +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 k0CJOEP09861; Thu, 12 Jan 2006 14:24:15 -0500 Message-ID: <43C6ACDC.10802@savvis.net> Date: Thu, 12 Jan 2006 11:24:12 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: scycoon@internode.on.net References: <43c59d92.36a.33a6.26043@internode.on.net> <43C5A551.8000206@savvis.net> <1137051315.613.7.camel@bigboy.scycoon.soho.on.net> In-Reply-To: <1137051315.613.7.camel@bigboy.scycoon.soho.on.net> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: Bluetooth Device Failing to Initialize 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, 12 Jan 2006 19:24:50 -0000 Chriso, > I have included the requested output below, thanks. lets see... [...] >>>Could not execute command "initialize". Device not >>>configured >> >>this is *very* strange. >> >>1) did you check your /var/log/messages to see if device has detached? > > This is in the messages after I run /etc/rc.bluetooth after a fresh > reboot; > > Jan 12 17:54:28 bigboy kernel: ng_hci_process_command_timeout: ubt0hci - > unable to complete HCI command OGF=0x3, OCF=0x3. Timeout > Jan 12 17:54:28 bigboy kernel: ng_hci_process_event: ubt0hci - got HCI > event=0xe, length=4 > Jan 12 17:54:28 bigboy kernel: complete_command: ubt0hci - no pending > command, state=0x1 > Jan 12 17:54:28 bigboy kernel: ubt_request_complete2: ubt0 - Control > request failed. TIMEOUT (15) hmm... this does not make much sense to me :( what it means is that the hci node tried to send command to the device, but it did not get any response back from the device in time (timed out). what happened next is that the hci node received response back from the device, but it did throw it away because it already timed out. i'm also concern about "ubt_request_complete2" error. it might indicate that something is wrong at usb level. > Jan 12 17:54:33 bigboy kernel: ng_hci_process_command_timeout: ubt0hci - > unable to complete HCI command OGF=0x4, OCF=0x9. Timeout > Jan 12 17:54:33 bigboy kernel: ng_hci_process_event: ubt0hci - got HCI > event=0xe, length=10 > Jan 12 17:54:33 bigboy kernel: complete_command: ubt0hci - no pending > command, state=0x1 > Jan 12 17:54:33 bigboy kernel: ubt_request_complete2: ubt0 - Control > request failed. TIMEOUT (15) here is the same sequence for another command (READ_BD_ADDR) > Jan 12 17:54:38 bigboy kernel: ng_hci_process_command_timeout: ubt0hci - > unable to complete HCI command OGF=0x4, OCF=0x3. Timeout > Jan 12 17:54:38 bigboy kernel: ng_hci_process_event: ubt0hci - got HCI > event=0xe, length=12 > Jan 12 17:54:38 bigboy kernel: complete_command: ubt0hci - no pending > command, state=0x1 > Jan 12 17:54:38 bigboy kernel: ubt_request_complete2: ubt0 - Control > request failed. TIMEOUT (15) and again (READ_LOCAL_FEATURES) > Jan 12 17:54:43 bigboy kernel: ng_hci_process_command_timeout: ubt0hci - > unable to complete HCI command OGF=0x4, OCF=0x5. Timeout > Jan 12 17:54:43 bigboy kernel: ng_hci_process_event: ubt0hci - got HCI > event=0xe, length=11 > Jan 12 17:54:43 bigboy kernel: complete_command: ubt0hci - no pending > command, state=0x1 > Jan 12 17:54:43 bigboy kernel: ubt_request_complete2: ubt0 - Control > request failed. TIMEOUT (15) and again (READ_BUFFER_SIZE) > Jan 12 17:54:48 bigboy kernel: ng_hci_process_command_timeout: ubt0hci - > unable to complete HCI command OGF=0x3, OCF=0x1a. Timeout > Jan 12 17:54:48 bigboy kernel: ng_hci_process_event: ubt0hci - got HCI > event=0xe, length=4 > Jan 12 17:54:48 bigboy kernel: complete_command: ubt0hci - no pending > command, state=0x1 > Jan 12 17:54:48 bigboy kernel: ubt_request_complete2: ubt0 - Control > request failed. TIMEOUT (15) and again (WRITE_SCAN_ENABLE) > Jan 12 17:54:53 bigboy kernel: ng_hci_process_command_timeout: ubt0hci - > unable to complete HCI command OGF=0x3, OCF=0x24. Timeout > Jan 12 17:54:53 bigboy kernel: ng_hci_process_event: ubt0hci - got HCI > event=0xe, length=4 > Jan 12 17:54:53 bigboy kernel: complete_command: ubt0hci - no pending > command, state=0x1 > Jan 12 17:54:53 bigboy kernel: ubt_request_complete2: ubt0 - Control > request failed. TIMEOUT (15) and again (WRITE_UNIT_CLASS) > Jan 12 17:54:58 bigboy kernel: ng_hci_process_command_timeout: ubt0hci - > unable to complete HCI command OGF=0x3, OCF=0x13. Timeout > Jan 12 17:54:58 bigboy kernel: ng_hci_process_event: ubt0hci - got HCI > event=0xe, length=4 > Jan 12 17:54:58 bigboy kernel: complete_command: ubt0hci - no pending > command, state=0x1 > Jan 12 17:54:58 bigboy kernel: ubt_request_complete2: ubt0 - Control > request failed. TIMEOUT (15) and again (CHANGE_LOCAL_NAME) also note interval between each chunks of errors - its 5 second. which is a hci command timeout. >>2) can you please run as root the following commands > > bash-2.05b# ngctl types > There are 7 total types: > Type name Number of living nodes > --------- ---------------------- > socket 1 > btsock_l2c 1 > btsock_l2c_raw 1 > btsock_hci_raw 1 > l2cap 1 > hci 1 > ubt 1 > > bash-2.05b# ngctl li > There are 7 total nodes: > Name: ngctl704 Type: socket ID: 00000013 Num hooks: 0 > Name: ubt0l2cap Type: l2cap ID: 0000000c Num hooks: 3 > Name: ubt0hci Type: hci ID: 00000008 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 good. all nodes are still present and connected. > bash-2.05b# ngctl status ubt0: > Status for "ubt0:": > Hook: hook > Flags: 0x30 > Debug: 3 > CMD queue: [have:0,max:12] > ACL queue: [have:0,max:12] > SCO queue: [have:0,max:12] looks good. > bash-2.05b# ngctl status ubt0hci: > Status for "ubt0hci:": > bdaddr 0:0:0:0:0:0 > Hooks drv acl raw > State 0x1 > Queue cmd:0 > Buffer cmd:1,acl:1,1,17,sco:1,1,10 aha! this is why "initialize" command failed. as i said above, the hci node did not get any response back from the device in time for every command in the initialization sequence. so, as far as the hci node is concerned the device was _not_ initialized correctly, i.e. note that bdaddr is 0:0:0:0:0:0 etc. the reason you see correct output on the screen is because data, received from the device, is copied to the "raw" hook (where socket gets connected) _before_ they processed by the hci node. this is a very strange failure mode that i have never seen before. you could try to do a couple of things 1) comment out "reset" command in the rc.bluetooth script, unplug/replug your device and run rc.bluetooth again. ## ${hccontrol} -n ${dev}hci reset || exit 1 2) try to adjust the command timeout, i.e. add a couple of lines before "reset" command ${sysctl} net.bluetooth.hci.command_timeout=10 ${sysctl} net.bluetooth.hci.sockets.raw.ioctl_timeout=10 also, just to be on the safe side, could you please check your /etc/devd.conf file and make sure you do not call anything in response to ubt(4) attach/detach events. also it would be nice if you could run hcidump (with timestamp option) while you are running rc.bluetooth, i.e. # hcidump -tX thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 12 20:17:11 2006 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 7416C16A420 for ; Thu, 12 Jan 2006 20:17:11 +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 CCEC343D46 for ; Thu, 12 Jan 2006 20:17:10 +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 k0CKH6P11271; Thu, 12 Jan 2006 15:17:08 -0500 Message-ID: <43C6B941.1010009@savvis.net> Date: Thu, 12 Jan 2006 12:17:05 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <43C32416.3030008@centtech.com> In-Reply-To: <43C32416.3030008@centtech.com> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: Setting up a bluetooth mouse on FreeBSD 6 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, 12 Jan 2006 20:17:11 -0000 Eric Anderson wrote: > I've been asked several times how to do this, so I wrote up a quick > howto from my notes. I've posted it here: > > http://destari.blogspot.com/2006/01/setting-up-bluetooth-mouse-on-freebsd.html this should probably be in handbook. also can someone volunteer and update bluetooth chapter in handbook (document new config system)? thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 12 23:25:14 2006 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 CEA4216A41F for ; Thu, 12 Jan 2006 23:25:14 +0000 (GMT) (envelope-from pav@FreeBSD.org) Received: from hood.oook.cz (hood.oook.cz [195.250.137.134]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02DE043D46 for ; Thu, 12 Jan 2006 23:25:13 +0000 (GMT) (envelope-from pav@FreeBSD.org) Received: from ikaros.oook.cz (localhost [127.0.0.1]) by hood.oook.cz (8.13.4/8.13.4) with ESMTP id k0CNP6ak003728 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 13 Jan 2006 00:25:07 +0100 (CET) (envelope-from pav@FreeBSD.org) Received: (from pav@localhost) by ikaros.oook.cz (8.13.4/8.13.4/Submit) id k0CNP66F003726; Fri, 13 Jan 2006 00:25:06 +0100 (CET) (envelope-from pav@FreeBSD.org) X-Authentication-Warning: ikaros.oook.cz: pav set sender to pav@FreeBSD.org using -f From: Pav Lucistnik To: Maksim Yevmenkin In-Reply-To: <43C6B941.1010009@savvis.net> References: <43C32416.3030008@centtech.com> <43C6B941.1010009@savvis.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-JneSGWQuyIlkbXF5XepC" Date: Fri, 13 Jan 2006 00:25:05 +0100 Message-Id: <1137108305.3236.2.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Cc: freebsd-bluetooth@FreeBSD.org Subject: Re: Setting up a bluetooth mouse on FreeBSD 6 X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pav@FreeBSD.org List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2006 23:25:15 -0000 --=-JneSGWQuyIlkbXF5XepC Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable Maksim Yevmenkin p=ED=B9e v =E8t 12. 01. 2006 v 12:17 -0800: > Eric Anderson wrote: > > I've been asked several times how to do this, so I wrote up a quick=20 > > howto from my notes. I've posted it here: > >=20 > > http://destari.blogspot.com/2006/01/setting-up-bluetooth-mouse-on-freeb= sd.html=20 >=20 > this should probably be in handbook. also can someone volunteer and=20 > update bluetooth chapter in handbook (document new config system)? I will take a look at it over weekend. Are the instructions same for bluetooth keyboard? --=20 Pav Lucistnik Linux is a happy free-for-all chaos. --=-JneSGWQuyIlkbXF5XepC Content-Type: application/pgp-signature; name=signature.asc Content-Description: Toto je =?iso-8859-2?Q?digit=E1ln=EC?= =?ISO-8859-1?Q?_podepsan=E1?= =?iso-8859-2?Q?_=E8=E1st?= =?ISO-8859-1?Q?_zpr=E1vy?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDxuVRntdYP8FOsoIRAtGeAKCs+GQ3qrbgu0iAV0IjXsZOFnruAACfb68f Cv9k42my+CYyEz5upIwj9pY= =/XZU -----END PGP SIGNATURE----- --=-JneSGWQuyIlkbXF5XepC-- From owner-freebsd-bluetooth@FreeBSD.ORG Fri Jan 13 00:20:57 2006 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 2775016A420 for ; Fri, 13 Jan 2006 00:20:57 +0000 (GMT) (envelope-from scycoon@internode.on.net) Received: from ash25e.internode.on.net (ash25e.internode.on.net [203.16.214.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9017243D46 for ; Fri, 13 Jan 2006 00:20:56 +0000 (GMT) (envelope-from scycoon@internode.on.net) Received: from internode.on.net (webmail1.adl2.internode.on.net [203.16.214.245]) by ash25e.internode.on.net (8.13.5/8.13.5) with ESMTP id k0D0KscH077378; Fri, 13 Jan 2006 10:50:54 +1030 (CST) (envelope-from scycoon@internode.on.net) Received: from 150.101.2.50 by HTTP Sender: scycoon@internode.on.net From: "scycoon@internode.on.net" To: Maksim Yevmenkin X-Mailer: scycoon - Internode Webmail v3.1r (http://www.internode.on.net/) X-Originating-IP: 150.101.2.50 Date: Fri, 13 Jan 2006 10:50:54 +1030 Message-id: <43c6f266.150.5ec4.2423@internode.on.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Cc: freebsd-bluetooth@freebsd.org Subject: Re: Bluetooth Device Failing to Initialize X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: scycoon@internode.on.net List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2006 00:20:57 -0000 Max, This morning I thought I would cut out any posibility of hardware errors and bring the dongle and headset to work. Where I run; FreeBSD tardis 5.4-RELEASE FreeBSD 5.4-RELEASE #0 It has behaved exactly as I would have hoped. I can query the device, establish a connection and have had no problems at all. So, I still would like to get the device working at home. I will try your suggestions, and also some of Eric's, howto for FreeBSD 6 and get back to you. Thanks again Chriso > Chriso, > > > I have included the requested output below, > > thanks. lets see... > > [...] > > >>>Could not execute command "initialize". Device not > >>>configured > >> > >>this is *very* strange. > >> > >>1) did you check your /var/log/messages to see if device > > has detached? > > This is in the messages after I run /etc/rc.bluetooth > > after a fresh reboot; > > > > Jan 12 17:54:28 bigboy kernel: > > ng_hci_process_command_timeout: ubt0hci - unable to > > complete HCI command OGF=0x3, OCF=0x3. Timeout Jan 12 > 17:54:28 bigboy kernel: ng_hci_process_event: ubt0hci - > > got HCI event=0xe, length=4 > > Jan 12 17:54:28 bigboy kernel: complete_command: ubt0hci > > - no pending command, state=0x1 > > Jan 12 17:54:28 bigboy kernel: ubt_request_complete2: > > ubt0 - Control request failed. TIMEOUT (15) > > hmm... this does not make much sense to me :( what it > means is that the hci node tried to send command to the > device, but it did not get any response back from the > device in time (timed out). what happened next is that > the hci node received response back from the device, but > it did throw it away because it already timed out. > > i'm also concern about "ubt_request_complete2" error. it > might indicate that something is wrong at usb level. > > > Jan 12 17:54:33 bigboy kernel: > > ng_hci_process_command_timeout: ubt0hci - unable to > > complete HCI command OGF=0x4, OCF=0x9. Timeout Jan 12 > 17:54:33 bigboy kernel: ng_hci_process_event: ubt0hci - > > got HCI event=0xe, length=10 > > Jan 12 17:54:33 bigboy kernel: complete_command: ubt0hci > > - no pending command, state=0x1 > > Jan 12 17:54:33 bigboy kernel: ubt_request_complete2: > > ubt0 - Control request failed. TIMEOUT (15) > > here is the same sequence for another command > (READ_BD_ADDR) > > > Jan 12 17:54:38 bigboy kernel: > > ng_hci_process_command_timeout: ubt0hci - unable to > > complete HCI command OGF=0x4, OCF=0x3. Timeout Jan 12 > 17:54:38 bigboy kernel: ng_hci_process_event: ubt0hci - > > got HCI event=0xe, length=12 > > Jan 12 17:54:38 bigboy kernel: complete_command: ubt0hci > > - no pending command, state=0x1 > > Jan 12 17:54:38 bigboy kernel: ubt_request_complete2: > > ubt0 - Control request failed. TIMEOUT (15) > > and again (READ_LOCAL_FEATURES) > > > Jan 12 17:54:43 bigboy kernel: > > ng_hci_process_command_timeout: ubt0hci - unable to > > complete HCI command OGF=0x4, OCF=0x5. Timeout Jan 12 > 17:54:43 bigboy kernel: ng_hci_process_event: ubt0hci - > > got HCI event=0xe, length=11 > > Jan 12 17:54:43 bigboy kernel: complete_command: ubt0hci > > - no pending command, state=0x1 > > Jan 12 17:54:43 bigboy kernel: ubt_request_complete2: > > ubt0 - Control request failed. TIMEOUT (15) > > and again (READ_BUFFER_SIZE) > > > Jan 12 17:54:48 bigboy kernel: > > ng_hci_process_command_timeout: ubt0hci - unable to > > complete HCI command OGF=0x3, OCF=0x1a. Timeout Jan 12 > 17:54:48 bigboy kernel: ng_hci_process_event: ubt0hci - > > got HCI event=0xe, length=4 > > Jan 12 17:54:48 bigboy kernel: complete_command: ubt0hci > > - no pending command, state=0x1 > > Jan 12 17:54:48 bigboy kernel: ubt_request_complete2: > > ubt0 - Control request failed. TIMEOUT (15) > > and again (WRITE_SCAN_ENABLE) > > > Jan 12 17:54:53 bigboy kernel: > > ng_hci_process_command_timeout: ubt0hci - unable to > > complete HCI command OGF=0x3, OCF=0x24. Timeout Jan 12 > 17:54:53 bigboy kernel: ng_hci_process_event: ubt0hci - > > got HCI event=0xe, length=4 > > Jan 12 17:54:53 bigboy kernel: complete_command: ubt0hci > > - no pending command, state=0x1 > > Jan 12 17:54:53 bigboy kernel: ubt_request_complete2: > > ubt0 - Control request failed. TIMEOUT (15) > > and again (WRITE_UNIT_CLASS) > > > Jan 12 17:54:58 bigboy kernel: > > ng_hci_process_command_timeout: ubt0hci - unable to > > complete HCI command OGF=0x3, OCF=0x13. Timeout Jan 12 > 17:54:58 bigboy kernel: ng_hci_process_event: ubt0hci - > > got HCI event=0xe, length=4 > > Jan 12 17:54:58 bigboy kernel: complete_command: ubt0hci > > - no pending command, state=0x1 > > Jan 12 17:54:58 bigboy kernel: ubt_request_complete2: > > ubt0 - Control request failed. TIMEOUT (15) > > and again (CHANGE_LOCAL_NAME) > > also note interval between each chunks of errors - its 5 > second. which is a hci command timeout. > > >>2) can you please run as root the following commands > > > > bash-2.05b# ngctl types > > There are 7 total types: > > Type name Number of living nodes > > --------- ---------------------- > > socket 1 > > btsock_l2c 1 > > btsock_l2c_raw 1 > > btsock_hci_raw 1 > > l2cap 1 > > hci 1 > > ubt 1 > > > > bash-2.05b# ngctl li > > There are 7 total nodes: > > Name: ngctl704 Type: socket ID: > > 00000013 Num hooks: 0 Name: ubt0l2cap Type: > > l2cap ID: 0000000c Num hooks: 3 Name: > ubt0hci Type: hci ID: 00000008 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 > > good. all nodes are still present and connected. > > > bash-2.05b# ngctl status ubt0: > > Status for "ubt0:": > > Hook: hook > > Flags: 0x30 > > Debug: 3 > > CMD queue: [have:0,max:12] > > ACL queue: [have:0,max:12] > > SCO queue: [have:0,max:12] > > looks good. > > > bash-2.05b# ngctl status ubt0hci: > > Status for "ubt0hci:": > > bdaddr 0:0:0:0:0:0 > > Hooks drv acl raw > > State 0x1 > > Queue cmd:0 > > Buffer cmd:1,acl:1,1,17,sco:1,1,10 > > aha! this is why "initialize" command failed. as i said > above, the hci node did not get any response back from > the device in time for every command in the > initialization sequence. so, as far as the hci node is > concerned the device was _not_ initialized correctly, i.e. > note that bdaddr is 0:0:0:0:0:0 etc. > > the reason you see correct output on the screen is because > data, received from the device, is copied to the "raw" > hook (where socket gets connected) _before_ they > processed by the hci node. > > this is a very strange failure mode that i have never seen > before. > > you could try to do a couple of things > > 1) comment out "reset" command in the rc.bluetooth script, > unplug/replug your device and run rc.bluetooth again. > > ## ${hccontrol} -n ${dev}hci reset || exit 1 > > 2) try to adjust the command timeout, i.e. add a couple of > lines before "reset" command > > ${sysctl} net.bluetooth.hci.command_timeout=10 > ${sysctl} net.bluetooth.hci.sockets.raw.ioctl_timeout=10 > > also, just to be on the safe side, could you please check > your /etc/devd.conf file and make sure you do not call > anything in response to ubt(4) attach/detach events. > > > also it would be nice if you could run hcidump (with > timestamp option) while you are running rc.bluetooth, > i.e. > > # hcidump -tX > > thanks, > max > From owner-freebsd-bluetooth@FreeBSD.ORG Fri Jan 13 21:51:19 2006 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 9703A16A41F; Fri, 13 Jan 2006 21:51:19 +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 22FBB43D70; Fri, 13 Jan 2006 21:51:16 +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 k0DLpFP22599; Fri, 13 Jan 2006 16:51:15 -0500 Message-ID: <43C820D1.2010903@savvis.net> Date: Fri, 13 Jan 2006 13:51:13 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pav@FreeBSD.org References: <43C32416.3030008@centtech.com> <43C6B941.1010009@savvis.net> <1137108305.3236.2.camel@localhost> In-Reply-To: <1137108305.3236.2.camel@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@FreeBSD.org Subject: Re: Setting up a bluetooth mouse on FreeBSD 6 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, 13 Jan 2006 21:51:19 -0000 Pav Lucistnik wrote: >>>I've been asked several times how to do this, so I wrote up a quick >>>howto from my notes. I've posted it here: >>> >>>http://destari.blogspot.com/2006/01/setting-up-bluetooth-mouse-on-freebsd.html >> >>this should probably be in handbook. also can someone volunteer and >>update bluetooth chapter in handbook (document new config system)? > > I will take a look at it over weekend. thanks! > Are the instructions same for bluetooth keyboard? no :( kbdmux(4) needs to be fixed first. max