From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 23 01:49:23 2009 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A2AD106566C for ; Mon, 23 Nov 2009 01:49:23 +0000 (UTC) (envelope-from comp.john@googlemail.com) Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mx1.freebsd.org (Postfix) with ESMTP id 1599E8FC08 for ; Mon, 23 Nov 2009 01:49:22 +0000 (UTC) Received: by ewy26 with SMTP id 26so1545670ewy.3 for ; Sun, 22 Nov 2009 17:49:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=v1kc5dNgiDFezvpWtWi/chRx9rbM29Ma4h7ZVB/P5qc=; b=SojQKiiPQsU8aEmoKtkq5eNH68G78MX89zmxL5CjyZBrQzA7qb+Y7j1QqLYqYq3z7L /SmYIdelFe4yAxnoIWDuW2DarqRd+IGFf79+pbDMy8prH/9qrg7Evn6Xy8n1N0OXFHkY sSth/heWNiUkH4XnRDzGBrBY2Qi1fWSBkeE4A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=IkA89RNqfVM8G2bYiSm1ZQbul0gSL/SPtKj+fF9s7IXBq8OcGCHKvenlFNUNGqpHNQ xrbCdpqpAAGCMugzztL9JSw2B4w/CpPBTBM/x/1n7vcUqeTvZBUkmsI41tcfe604WmMg 13BA5Ty9lOiTXf0RYost0p3d6IpojZNWBu494= Received: by 10.213.102.129 with SMTP id g1mr2960656ebo.41.1258940961948; Sun, 22 Nov 2009 17:49:21 -0800 (PST) Received: from potato (potato.growveg.org [62.49.247.163]) by mx.google.com with ESMTPS id 23sm922467eya.19.2009.11.22.17.49.20 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 22 Nov 2009 17:49:20 -0800 (PST) Date: Mon, 23 Nov 2009 01:49:16 +0000 From: John To: Iain Hibbert Message-ID: <20091123014916.GA20648@potato> References: <20091121184335.GA2008@potato> <1258883126.052713.723.nullmailer@galant.ukfsn.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1258883126.052713.723.nullmailer@galant.ukfsn.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-bluetooth@freebsd.org Subject: Re: Problems getting the bluetooth stack to start 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, 23 Nov 2009 01:49:23 -0000 Hi, thanks for replying. On Sun, Nov 22, 2009 at 09:45:25AM +0000, Iain Hibbert wrote: > On Sat, 21 Nov 2009, John wrote: > > > Firstly, the small size of the device means that it is very awkward to > > pull the dongle out once it's pushed in. When restarting the computer, > > is it sufficient to reboot(8) then power the machine off, wait a few > > seconds then power it back up? I mean does this properly reset the > > dongle, or does it truly have to be pulled out and pushed back in for > > the system to re-read it? > > power down should be sufficient to reset the device entirely, internal > state is rarely kept (sometimes there is nvram for link keys but thats > all) Yeah I thought it should be, but it seems that is not the case on my hardware. (gigabyte motherboard & case, AMD Athalon 64 x2 6000+). Whilst trying to fix things, I brought the OS up-to-date with 7-STABLE (I was running 7.2-R p4) and went through mergemaster the long and hard way, making sure all the bluetooth-related stuff was the newest. Rebooted, still no joy. Then I pulled the dongle from the socket on the back and plugged it into one at the front, and this showed more promise. ubt0 didn't appear in messages before, now it did. Seems it needs to be unplugged then plugged back in. Additionally, I had to go through the routine of stopping the bluetooth stack, starting it again, getting the "Unable to setup Bluetooth stack for device ubt0" error, then starting it again and getting no error. Now I get: potato# kldstat Id Refs Address Size Name 1 14 0xffffffff80100000 bf99e0 kernel 2 1 0xffffffff80cfa000 7118 geom_concat.ko 3 1 0xffffffff80d02000 9808 ng_ubt.ko 4 6 0xffffffff80d0c000 14e98 netgraph.ko 5 1 0xffffffff80e22000 972 pflog.ko 6 1 0xffffffff80e23000 2aefc pf.ko 7 1 0xffffffff80e4e000 12c9e ng_btsocket.ko 8 3 0xffffffff80e61000 89a ng_bluetooth.ko 9 1 0xffffffff80e62000 aa7a fuse.ko 10 1 0xffffffff80e6d000 827 accf_http.ko 11 1 0xffffffff80e6e000 8b1a ng_hci.ko 12 1 0xffffffff80e77000 b498 ng_l2cap.ko 13 1 0xffffffff80e83000 19ba ng_socket.ko and potato# ngctl li There are 7 total nodes: Name: btsock_l2c_raw Type: btsock_l2c_raw ID: 00000002 Num hooks: 1 Name: ngctl23568 Type: socket ID: 00000063 Num hooks: 0 Name: ubt0hci Type: hci ID: 00000059 Num hooks: 3 Name: btsock_hci_raw Type: btsock_hci_raw ID: 00000001 Num hooks: 1 Name: ubt0l2cap Type: l2cap ID: 0000005d Num hooks: 3 Name: btsock_l2c Type: btsock_l2c ID: 00000003 Num hooks: 1 Name: ubt0 Type: ubt ID: 00000004 Num hooks: 1 so that looks OK potato# hccontrol -n ubt0hci inquiry Inquiry result, num_responses=1 Inquiry result #0 BD_ADDR: 00:0a:d9:3e:70:24 Page Scan Rep. Mode: 0x1 Page Scan Period Mode: 00 Page Scan Mode: 00 Class: 52:02:04 Clock offset: 0x273b Inquiry complete. Status: No error [00] potato# hccontrol -n ubt0hci remote_name_request 00:0a:d9:3e:70:24 BD_ADDR: 00:0a:d9:3e:70:24 Name: T610 so, in the parlance of the literature, the phone is my server and this is the server's MAC address: 00:0a:d9:3e:70:24 What I can't work out now is why i can't see the channels: potato# l2ping -a 00:0a:d9:3e:70:24 0 bytes from 00:0a:d9:3e:70:24 seq_no=0 time=500.567 ms result=0 0 bytes from 00:0a:d9:3e:70:24 seq_no=1 time=31.890 ms result=0 0 bytes from 00:0a:d9:3e:70:24 seq_no=2 time=31.895 ms result=0 0 bytes from 00:0a:d9:3e:70:24 seq_no=3 time=31.897 ms result=0 0 bytes from 00:0a:d9:3e:70:24 seq_no=4 time=32.900 ms result=0 0 bytes from 00:0a:d9:3e:70:24 seq_no=5 time=30.906 ms result=0 ^C potato# l2control -a 00:0a:d9:3e:70:24 Read_Channel_List l2control: Could not bind socket, bdaddr=00:0a:d9:3e:70:24: Network is down I have paired the handset with the device and it shows the fqdn of the freebsd machine. If I do sdpcontrol -a 00:0a:d9:3e:70:24 browse I get pages of output. But! If I do rfcomm_sppd -a 00:0a:d9:3e:70:24 -t /dev/ttyp6 I see this in messages: Nov 23 01:38:24 potato rfcomm_sppd: Could not open(/dev/ptyp6). Input/output error any ideas? I think the l2control error and the rfcomm one may be related, but I haven't a clue how to resolve the issue. -- John - comp dot john at googlemail dot com OpenBSD firewall | FreeBSD desktop | Ubuntu Karmic laptop GPG: 0xF08A33C5