From owner-freebsd-bluetooth@FreeBSD.ORG Sun Nov 22 02:06: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 C2F52106566C for ; Sun, 22 Nov 2009 02:06: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 4E5DD8FC13 for ; Sun, 22 Nov 2009 02:06:22 +0000 (UTC) Received: by ewy26 with SMTP id 26so883175ewy.3 for ; Sat, 21 Nov 2009 18:06:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:resent-from:resent-date :resent-message-id:resent-to:received:date:from:to:subject :message-id:mime-version:content-type:content-disposition:user-agent; bh=81MOG9NHFbhZSxCfKW/9Itv+36IjNbxzVqW55kqVc/0=; b=xWGycOeun5yWR1YHBj16lkkY+W6M5FaJdZ9hMFULtRJMJwoAoDoi91PI+NnSPtcKOk rHPfP66admqc0vRWiPd1YpbH1CKIgOSc7cAnkKA0L1+uDRAMe1CJ0S/uO3BJvaqDlSOY 8oVqGv0HMx3maWFHK574LfWBD+jWYn5btD2Ko= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=resent-from:resent-date:resent-message-id:resent-to:date:from:to :subject:message-id:mime-version:content-type:content-disposition :user-agent; b=e9N0OpVh/nVHhJc1vzORIkOmcdqlL0NoLXBkOtsPv1rkBOiZNkmxIa/2vGXyfPlZCn 8aBpemcXT2xnhRfUp2iU3miHEvlwZMokLx+LsJuudLGqcooZ/zOuZ3Xzg0IRQZR5T/oi pzUxseoD11Q7rLjSWrSq/hmBVgVdWRcWHlaHg= Received: by 10.213.23.88 with SMTP id q24mr1973195ebb.13.1258853663648; Sat, 21 Nov 2009 17:34:23 -0800 (PST) Received: from potato (potato.growveg.org [62.49.247.163]) by mx.google.com with ESMTPS id 10sm712149eyd.45.2009.11.21.17.34.23 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 21 Nov 2009 17:34:23 -0800 (PST) Resent-From: John Resent-Date: Sun, 22 Nov 2009 01:34:19 +0000 Resent-Message-ID: <20091122013419.GA25773@potato> Resent-To: freebsd-bluetooth@freebsd.org Received: from potato (potato.growveg.org [62.49.247.163]) by mx.google.com with ESMTPS id 5sm275503eyf.0.2009.11.21.10.43.38 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 21 Nov 2009 10:43:38 -0800 (PST) Date: Sat, 21 Nov 2009 18:43:36 +0000 From: John To: bluetooth@freebsd.org Message-ID: <20091121184335.GA2008@potato> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Subject: 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: Sun, 22 Nov 2009 02:06:23 -0000 Hello list, my system: 7.2-RELEASE-p4 FreeBSD 7.2-RELEASE-p4 #1: Sat Nov 21 16:55:14 GMT 2009 root@potato:/usr/src/sys/amd64/compile/POTATO amd64 The kernel is generic apart from ehci being commented out. Sources cvsupped earlier today from cvsup.uk.freebsd.org I'm trying to get my sony erikson T610 to work with a nexus bluemicro pro dongle on 7.2-R. The galling thing is, I got it to work once, but it was late and I forgot how. I can't get the bluetooth stack to start, and I'm following the instructins as per the handbook 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? I've tried various suggestions while googling trying to find the answer. One suggestion (with a different device) was to disable ehci and recompile the kernel, which I've done. No difference. Another was to stop the bluetooth script before starting it: potato# /etc/rc.d/bluetooth start ubt0 /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0 potato# /etc/rc.d/bluetooth stop ubt0 potato# /etc/rc.d/bluetooth start ubt0 /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0 I find that when the system boots up, only one bluetooth-related kernel module is loaded: potato# kldstat Id Refs Address Size Name 1 9 0xffffffff80100000 768b98 kernel 2 1 0xffffffff80869000 7128 geom_concat.ko 3 1 0xffffffff80871000 9808 ng_ubt.ko 4 2 0xffffffff8087b000 14e08 netgraph.ko 5 1 0xffffffff80a22000 978 pflog.ko 6 1 0xffffffff80a23000 2ae8c pf.ko 7 1 0xffffffff80a4e000 aa7a fuse.ko 8 1 0xffffffff80a59000 82e accf_http.ko potato# ngctl li There are 1 total nodes: Name: ngctl1196 Type: socket ID: 00000001 Num hooks:0 When I try to start the stack, this happens: potato# /etc/rc.d/bluetooth start ubt0 /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0 potato# /etc/rc.d/bluetooth stop ubt0 potato# /etc/rc.d/bluetooth start ubt0 /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0 let's do a kldstat again: potato# kldstat Id Refs Address Size Name 1 14 0xffffffff80100000 768b98 kernel 2 1 0xffffffff80869000 7128 geom_concat.ko 3 1 0xffffffff80871000 9808 ng_ubt.ko 4 6 0xffffffff8087b000 14e08 netgraph.ko 5 1 0xffffffff80a22000 978 pflog.ko 6 1 0xffffffff80a23000 2ae8c pf.ko 7 1 0xffffffff80a4e000 aa7a fuse.ko 8 1 0xffffffff80a59000 82e accf_http.ko 9 1 0xffffffff80a5a000 19ba ng_socket.ko 10 4 0xffffffff80a5c000 89a ng_bluetooth.ko 11 1 0xffffffff80a5d000 8b1a ng_hci.ko 12 1 0xffffffff80a66000 b498 ng_l2cap.ko 13 1 0xffffffff80a72000 12c9e ng_btsocket.ko loads of stuff now. potato# ngctl li There are 4 total nodes: 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: btsock_l2c Type: btsock_l2c ID: 00000004 Num hooks: 0 Name: ngctl1781 Type: socket ID: 00000012 Num hooks: 0 but still I cannot get the stack to work! I have also tried commenting out the ubt* stuff in devd.conf and rebooting, no difference. The little light on the dongle flashes merrily, but if the stack won't start I won't be able to do anything. Can anyone help please? -- John - comp dot john at googlemail dot com OpenBSD firewall | FreeBSD desktop | Ubuntu Karmic laptop GPG: 0xF08A33C5 From owner-freebsd-bluetooth@FreeBSD.ORG Sun Nov 22 09:45:06 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 297E31065698 for ; Sun, 22 Nov 2009 09:45:06 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from smtp6.freeserve.com (smtp6.freeserve.com [193.252.22.192]) by mx1.freebsd.org (Postfix) with ESMTP id E14E78FC17 for ; Sun, 22 Nov 2009 09:45:05 +0000 (UTC) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3623.me.freeserve.com (SMTP Server) with ESMTP id 719A97000081; Sun, 22 Nov 2009 10:45:04 +0100 (CET) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3623.me.freeserve.com (SMTP Server) with ESMTP id 618737000084; Sun, 22 Nov 2009 10:45:04 +0100 (CET) Received: from rya-online.net (unknown [89.194.66.160]) by mwinf3623.me.freeserve.com (SMTP Server) with SMTP id A75B17000081; Sun, 22 Nov 2009 10:45:03 +0100 (CET) X-ME-UUID: 20091122094503685.A75B17000081@mwinf3623.me.freeserve.com Received: (nullmailer pid 750 invoked by uid 1000); Sun, 22 Nov 2009 09:45:26 -0000 Date: Sun, 22 Nov 2009 09:45:25 +0000 (GMT) To: John In-Reply-To: <20091121184335.GA2008@potato> References: <20091121184335.GA2008@potato> User-Agent: Alpine 2.00 (NEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1258883126.052713.723.nullmailer@galant.ukfsn.org> From: Iain Hibbert 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: Sun, 22 Nov 2009 09:45:06 -0000 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) it seems (to me) that your modules setup is ok, since the modules are loaded when you want them to be > potato# /etc/rc.d/bluetooth start ubt0 > /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device > ubt0 Not sure if I can really be of much assistance, does hccontrol show that the node is up and running? Also, before you do this can you run hcidump as root user? It might show something happening (or not) Then, you could enable some kind of debugging in the startup script (use sh -x at least) to see where it was failing iain From owner-freebsd-bluetooth@FreeBSD.ORG Sun Nov 22 18:52:36 2009 Return-Path: Delivered-To: bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2CE021065672 for ; Sun, 22 Nov 2009 18:52:36 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from smtp6.freeserve.com (smtp6.freeserve.com [193.252.22.191]) by mx1.freebsd.org (Postfix) with ESMTP id BD84E8FC0C for ; Sun, 22 Nov 2009 18:52:35 +0000 (UTC) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3606.me.freeserve.com (SMTP Server) with ESMTP id 4953E7000081 for ; Sun, 22 Nov 2009 19:52:34 +0100 (CET) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3606.me.freeserve.com (SMTP Server) with ESMTP id 3A38D7000084 for ; Sun, 22 Nov 2009 19:52:34 +0100 (CET) Received: from rya-online.net (unknown [89.194.66.160]) by mwinf3606.me.freeserve.com (SMTP Server) with SMTP id 5A6D77000081 for ; Sun, 22 Nov 2009 19:52:33 +0100 (CET) X-ME-UUID: 20091122185233370.5A6D77000081@mwinf3606.me.freeserve.com Received: (nullmailer pid 1163 invoked by uid 1000); Sun, 22 Nov 2009 18:52:55 -0000 Date: Sun, 22 Nov 2009 18:52:55 +0000 (GMT) To: bluetooth@freebsd.org In-Reply-To: <1258393046.949215.22427.nullmailer@galant.ukfsn.org> References: <1258393046.949215.22427.nullmailer@galant.ukfsn.org> User-Agent: Alpine 2.00 (NEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1258915975.435294.873.nullmailer@galant.ukfsn.org> From: Iain Hibbert Cc: Subject: Re: iPhone and bcm-2045b 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, 22 Nov 2009 18:52:36 -0000 On Mon, 16 Nov 2009, Iain Hibbert wrote: > A friend of mine just got an iPhone 3G, he was here the other day and I > tried to probe the device using my laptop (Thinkpad T60 with NetBSD) which > has bluetooth built in (a Broadcom BCM2045B connected via internal USB) > > I managed to discover it ok, but when I opened a connection to the device, > my controller detached from the USB bus! Just as a followup to this, my CSR dongle managed to connect just fine so I guess the Broadcom controller has a bug causing it to crash. Output of my SDP query tool below. (searched for L2CAP uuid) The iPhone bluetooth capability is kind of limited for a phone though, with no Object Push or File Transfer. The NAP service is advertised but returns "Not Allowed" to connection setup attempts (supposedly its disabled by the network operator). iain ServiceRecordHandle: 0x4f491116 ServiceClassIDList: Network Access Point ServiceRecordState: 0x00000000 ProtocolDescriptorList: L2CAP (PSM 0x000f) BNEP (v1.0; IPv4, ARP, 0x8100, IPv6) BrowseGroupList: Public Browse Root LanguageBaseAttributeIDList: en.UTF-8 base 0x0100 fr.UTF-8 base 0x0110 de.UTF-8 base 0x0120 ja.UTF-8 base 0x0130 ServiceAvailability: 255/255 BluetoothProfileDescriptorList: Network Access Point, v1.0 ServiceName: "PAN Network Access Profile" ServiceDescription: "Network Access Point" SecurityDescription: Service-level Security NetAccessType: 3G Cellular MaxNetAccessRate: 256000 ServiceRecordHandle: 0x4f49a620 ServiceClassIDList: 00000000-deca-fade-deca-deafdecacafe ServiceRecordState: 0x00000000 ProtocolDescriptorList: L2CAP RFCOMM (channel 2) BrowseGroupList: Public Browse Root LanguageBaseAttributeIDList: en.UTF-8 base 0x0100 fr.UTF-8 base 0x0110 de.UTF-8 base 0x0120 ja.UTF-8 base 0x0130 ServiceAvailability: 255/255 BluetoothProfileDescriptorList: Serial Port, v1.0 ServiceName: "Wireless iAP" ServiceRecordHandle: 0x4f49110c ServiceClassIDList: A/V Remote Control Target ServiceRecordState: 0x00000000 ProtocolDescriptorList: L2CAP (PSM 0x0017) AVCTP (v1.2) BrowseGroupList: Public Browse Root LanguageBaseAttributeIDList: en.UTF-8 base 0x0100 fr.UTF-8 base 0x0110 de.UTF-8 base 0x0120 ja.UTF-8 base 0x0130 ServiceAvailability: 255/255 BluetoothProfileDescriptorList: A/V Remote Control, v1.0 ServiceName: "AVRCP Device" ServiceDescription: "Remote Control Device" SupportedFeatures: Category 1 ServiceRecordHandle: 0x4f49110a ServiceClassIDList: Audio Source ServiceRecordState: 0x00000000 ProtocolDescriptorList: L2CAP (PSM 0x0019) AVDTP (v1.2) BrowseGroupList: Public Browse Root LanguageBaseAttributeIDList: en.UTF-8 base 0x0100 fr.UTF-8 base 0x0110 de.UTF-8 base 0x0120 ja.UTF-8 base 0x0130 ServiceAvailability: 255/255 BluetoothProfileDescriptorList: Advanced Audio Distribution, v1.2 ServiceName: "Audio Source" SupportedFeatures: Player ServiceRecordHandle: 0x4f49112f ServiceClassIDList: Phonebook Access Server ServiceRecordState: 0x00000000 ProtocolDescriptorList: L2CAP RFCOMM (channel 13) OBEX BrowseGroupList: Public Browse Root LanguageBaseAttributeIDList: en.UTF-8 base 0x0100 fr.UTF-8 base 0x0110 de.UTF-8 base 0x0120 ja.UTF-8 base 0x0130 ServiceAvailability: 255/255 BluetoothProfileDescriptorList: Phonebook Access, v1.0 ServiceName: "Phonebook" SupportedRepositories: Local Phonebook ServiceRecordHandle: 0x4f491104 ServiceClassIDList: IrMC Sync ServiceRecordState: 0x00000000 ProtocolDescriptorList: L2CAP RFCOMM (channel 1) OBEX BrowseGroupList: Public Browse Root LanguageBaseAttributeIDList: en.UTF-8 base 0x0100 fr.UTF-8 base 0x0110 de.UTF-8 base 0x0120 ja.UTF-8 base 0x0130 ServiceAvailability: 255/255 BluetoothProfileDescriptorList: IrMC Sync, v1.0 ServiceName: "IrMC Sync" SupportedDataStoresList: Phonebook ServiceRecordHandle: 0x4f49111f ServiceClassIDList: Handsfree Audio Gateway Generic Audio ServiceRecordState: 0x00000000 ProtocolDescriptorList: L2CAP RFCOMM (channel 8) BrowseGroupList: Public Browse Root LanguageBaseAttributeIDList: en.UTF-8 base 0x0100 fr.UTF-8 base 0x0110 de.UTF-8 base 0x0120 ja.UTF-8 base 0x0130 ServiceAvailability: 255/255 BluetoothProfileDescriptorList: Handsfree, v1.5 ServiceName: "Handsfree Gateway" Network: Ability to reject a call SupportedFeatures: 3 Way Calling Echo Cancellation/Noise Reduction ServiceRecordHandle: 0x00000000 ServiceClassIDList: Service Discovery Server ServiceRecordState: 0x00000000 ProtocolDescriptorList: L2CAP SDP LanguageBaseAttributeIDList: en.UTF-8 base 0x0100 fr.UTF-8 base 0x0110 de.UTF-8 base 0x0120 ja.UTF-8 base 0x0130 ServiceAvailability: 255/255 VersionNumberList: v1.0 ServiceDatabaseState: 0x00000008 AttributeID 0x0300: seq8(56) str8(3) "2.1" str8(49) "Copyright (c) 2007 Apple Inc. All rights rese ... AttributeID 0x0308: url8(13) "www%2eapple%2ecom" 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 From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 23 03:23:36 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 1E35510656AA for ; Mon, 23 Nov 2009 03:23:36 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by mx1.freebsd.org (Postfix) with ESMTP id E4EE28FC2F for ; Mon, 23 Nov 2009 03:23:35 +0000 (UTC) Received: by pwj15 with SMTP id 15so3459010pwj.3 for ; Sun, 22 Nov 2009 19:23:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=KyDk5sTvpKtrvXICGmFNe/jargnecH2PFsuUaRmJDOI=; b=ZcORgvy75lyUR4+NTzzD3xx52pT+AJyY6tAxtJA3NvU7YQFO+s0IPIBcvzL319MPnE otGlG41fid1Dwg/bsYOslB0Rzjk3uunEdsKnXODLu9zT09FTp98R/zncEmkMcNKb4O04 g25URI4Tcc1Ib4wP1vugbSqvfWKa3TyzixHkc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=A6BpzmK2FkCehIE2HJ0M7V/qjD5n4Q48JtG4RVusWflMyyoFl7nImEhHNoBy03Ri4u 06g/A6eaN/f4iq/UXy8CZl2Iz1Nxyf2hbPlSj2BU8dNRPowA50sybNP4YvNH8yvcDfsM uM35tikFvE540p4c6cTs3pJy+k+HlWV6odUi8= MIME-Version: 1.0 Received: by 10.114.165.20 with SMTP id n20mr5896379wae.6.1258946615378; Sun, 22 Nov 2009 19:23:35 -0800 (PST) In-Reply-To: <20091123014916.GA20648@potato> References: <20091121184335.GA2008@potato> <1258883126.052713.723.nullmailer@galant.ukfsn.org> <20091123014916.GA20648@potato> Date: Sun, 22 Nov 2009 19:23:35 -0800 Message-ID: From: Maksim Yevmenkin To: John Content-Type: text/plain; charset=ISO-8859-1 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 03:23:36 -0000 On Sun, Nov 22, 2009 at 5:49 PM, John wrote: [...] everything up to this point looks good > 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 this looks fine > 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 this will not work. as per l2control(8) man page " The l2control utility connects to the local device with the specified BD_ADDR and attempts to send the specified command. " i.e. l2control(8) will display _local_ l2cap channels (basically l2cap connections). you dont have any l2cap channels (i.e. connections). i'm guessing you want to see the services offered on your t610 phone. you need to use sdpcontrol(8) for this. > 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. yes, this will tell you service names and service parameters > 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 well, it could not open /dev/ptyp6? is it busy? did you try different terminal? > 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. l2control(8) is not an issue you. rfcomm_sppd(1) had problem with opening master pty. thanks max From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 23 08:39:43 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 D1F1A106566B for ; Mon, 23 Nov 2009 08:39:43 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from smtp6.freeserve.com (smtp5.freeserve.com [193.252.22.151]) by mx1.freebsd.org (Postfix) with ESMTP id 953AD8FC16 for ; Mon, 23 Nov 2009 08:39:43 +0000 (UTC) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3538.me.freeserve.com (SMTP Server) with ESMTP id 518141C00085; Mon, 23 Nov 2009 09:39:41 +0100 (CET) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3538.me.freeserve.com (SMTP Server) with ESMTP id 4084A1C00084; Mon, 23 Nov 2009 09:39:41 +0100 (CET) Received: from rya-online.net (unknown [89.194.128.250]) by mwinf3538.me.freeserve.com (SMTP Server) with SMTP id 6F7741C00081; Mon, 23 Nov 2009 09:39:40 +0100 (CET) X-ME-UUID: 20091123083940456.6F7741C00081@mwinf3538.me.freeserve.com Received: (nullmailer pid 162 invoked by uid 1000); Mon, 23 Nov 2009 08:40:05 -0000 Date: Mon, 23 Nov 2009 08:40:05 +0000 (GMT) To: John In-Reply-To: <20091123014916.GA20648@potato> References: <20091121184335.GA2008@potato> <1258883126.052713.723.nullmailer@galant.ukfsn.org> <20091123014916.GA20648@potato> User-Agent: Alpine 2.00 (NEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1258965605.415128.198.nullmailer@galant.ukfsn.org> From: Iain Hibbert 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 08:39:43 -0000 On Mon, 23 Nov 2009, John wrote: > Then I pulled the dongle from the socket on the back and > plugged it into one at the front, and this showed more promise. perhaps the one at the back is EHCI but the one at the front is not (or, full-speed and high-speed or whatever they call it) since you had to disable ehci to get it working..? iain From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 23 09:27:08 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 C69AE1065696 for ; Mon, 23 Nov 2009 09:27:08 +0000 (UTC) (envelope-from comp.john@googlemail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 523DC8FC26 for ; Mon, 23 Nov 2009 09:27:08 +0000 (UTC) Received: by bwz5 with SMTP id 5so5126322bwz.3 for ; Mon, 23 Nov 2009 01:27:07 -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=zv4SpXH/UamY+LFElgUZOZux/uL68K/el+m/qf4q6wc=; b=GcmUwPnNaZfPQaVDV8hJ4enYl9HZ/9c5/AcJZQFMqaCrBjad5HID2+8u/PqNuZaMZQ +MMbD2t40WlSH8x0vdojHkuvWZc0RP2zcwdF8TOcJ294EVkbcPXZCL4C5Hgnuw+WeVj6 Smpj6XZAIB0+x07/5tM7ciwPdqbHXiFdFN7PA= 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=WFibto+YMjqufCNzLtHF+mixfSYoZapw0AyPJCW2UaAumnZFvvfCpbmxyT2G+zEYb+ ty3l9HAUs33lY+pDVdExS3r44wFjCLBOCN0AWULPmrBGEybX8T0ttWKJycEoelvnfjDq F41X8VEK3eKdufsCUNom++yrr2QLqDTGEIf1U= Received: by 10.204.13.210 with SMTP id d18mr4379243bka.211.1258968427184; Mon, 23 Nov 2009 01:27:07 -0800 (PST) Received: from potato (potato.growveg.org [62.49.247.163]) by mx.google.com with ESMTPS id 16sm1295287fxm.8.2009.11.23.01.27.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 23 Nov 2009 01:27:06 -0800 (PST) Date: Mon, 23 Nov 2009 09:26:59 +0000 From: John To: Iain Hibbert Message-ID: <20091123092659.GA93373@potato> References: <20091121184335.GA2008@potato> <1258883126.052713.723.nullmailer@galant.ukfsn.org> <20091123014916.GA20648@potato> <1258965605.415128.198.nullmailer@galant.ukfsn.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1258965605.415128.198.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 09:27:08 -0000 On Mon, Nov 23, 2009 at 08:40:05AM +0000, Iain Hibbert wrote: > On Mon, 23 Nov 2009, John wrote: > > > Then I pulled the dongle from the socket on the back and > > plugged it into one at the front, and this showed more promise. > > perhaps the one at the back is EHCI but the one at the front is not (or, > full-speed and high-speed or whatever they call it) since you had to > disable ehci to get it working..? No, I recompiled without EHCI on the basis that there were issues with it enabled (I did a lot of googling before posting here, and it was advice though I think it pertained to netbsd and some other specific advice) but at that stage I was grasping at straws ;) -- John - comp dot john at googlemail dot com OpenBSD firewall | FreeBSD desktop | Ubuntu Karmic laptop GPG: 0xF08A33C5 From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 23 09:39:09 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 BB4EF1065679 for ; Mon, 23 Nov 2009 09:39:09 +0000 (UTC) (envelope-from comp.john@googlemail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 453068FC17 for ; Mon, 23 Nov 2009 09:39:09 +0000 (UTC) Received: by bwz5 with SMTP id 5so5133440bwz.3 for ; Mon, 23 Nov 2009 01:39:08 -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=mK8OvYgZR+G2Ar2nSFGK0K+LhALs4CVrB9yBdqraPik=; b=lBlhtdJX3O6Yk8PLCKTwgE+70fLB50Bw/SXkNeGvwp6GYHEN4bAQhGrhBRr4KMqZyB oFIW3aDEYcR7n0EVD6HhKznipqIqSpvV7AP9ijUyOo9eu3c+6fS5dzt2wvS3PVRxa3tw puie+CbhL8cHQsxjQMO5GGnou2qPLd9pNA+Gc= 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=Ywzf+drKIVsno2gS6gO4tu6Ez9gyhzvSIyCbax0ITAx1eGa7aZZyjf56UDr9vwSvCB XeLdx7k6eJRzmbXJizMXoT9WC0CpnJOhNtZp0mCO6H20hPVZG5zqSCKvD8LdpZrNRdNN WFP9OWVn+xHvt9+5ZFj7JMiH7GTG0j0/vRwQ8= Received: by 10.204.154.131 with SMTP id o3mr4535188bkw.66.1258969148332; Mon, 23 Nov 2009 01:39:08 -0800 (PST) Received: from potato (potato.growveg.org [62.49.247.163]) by mx.google.com with ESMTPS id 13sm1299293fxm.9.2009.11.23.01.39.04 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 23 Nov 2009 01:39:05 -0800 (PST) Date: Mon, 23 Nov 2009 09:38:58 +0000 From: John To: Maksim Yevmenkin Message-ID: <20091123093858.GB93373@potato> References: <20091121184335.GA2008@potato> <1258883126.052713.723.nullmailer@galant.ukfsn.org> <20091123014916.GA20648@potato> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 09:39:09 -0000 On Sun, Nov 22, 2009 at 07:23:35PM -0800, Maksim Yevmenkin wrote: > this will not work. as per l2control(8) man page oops! sorry for the noise. > well, it could not open /dev/ptyp6? is it busy? did you try different terminal? yep, got i/o error with them all. > l2control(8) is not an issue you. rfcomm_sppd(1) had problem with > opening master pty. I'm going to update and buildworld again, and remake all my devices. I saw some odd ownership for /dev/ttyp6 and friends. cheers -- John - comp dot john at googlemail dot com OpenBSD firewall | FreeBSD desktop | Ubuntu Karmic laptop GPG: 0xF08A33C5