From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jun 16 17:22:17 2011 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 A4FB0106566C for ; Thu, 16 Jun 2011 17:22:17 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2B27A8FC13 for ; Thu, 16 Jun 2011 17:22:16 +0000 (UTC) Received: by bwz12 with SMTP id 12so2165351bwz.13 for ; Thu, 16 Jun 2011 10:22:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=fPaI13HuuSjEI25U/kbDQxkL3Jg8b0dn+yT2BdDHSR4=; b=q1/Z3swYQNlMsOFZPtdTAJie3RyVKJNYkFf5hqwEleA5ya1eggZZyXdzFiUTKtpcD4 iC+FYpYLNir0HNhEe/H7IOhA2AMJkfivfYRR+PbB3pH0iAS7UCOCie0YkjqK+BHI0vQX NUNX0hOkuHLVJ8JLGFXfhSkZtKXP4YsQm/+lY= 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=gRFXDyQLGVh/cNdcpHKKDI6RejmZzOBcKN1hTQSk4HP/JvOCnuxAluUlEGfnZksrZz OP79wOXZngsk+DcxzFGylnJLrO38d79p2DgJTt3MvPP9E/5ANE8g4j7jifUdSYoqco+f JWSZ1qjDeNqZWrc7MQPHIkIN2uPElvE51kcYE= MIME-Version: 1.0 Received: by 10.205.82.199 with SMTP id ad7mr827810bkc.152.1308244935801; Thu, 16 Jun 2011 10:22:15 -0700 (PDT) Received: by 10.204.36.12 with HTTP; Thu, 16 Jun 2011 10:22:15 -0700 (PDT) In-Reply-To: <4DF8430C.3010104@herveybayaustralia.com.au> References: <4DF46049.6080206@herveybayaustralia.com.au> <4DF53A6F.9080701@herveybayaustralia.com.au> <4DF705C9.7020606@herveybayaustralia.com.au> <4DF7F13C.6090208@herveybayaustralia.com.au> <4DF8430C.3010104@herveybayaustralia.com.au> Date: Thu, 16 Jun 2011 10:22:15 -0700 Message-ID: From: Maksim Yevmenkin To: Da Rock Content-Type: text/plain; charset=ISO-8859-1 Cc: bluetooth@freebsd.org Subject: Re: Asus bluetooth device - 0x1712 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, 16 Jun 2011 17:22:17 -0000 [...] >>> Probably would if it recognised the product then. What is the correct way >>> to >>> do this then? I know about usbdevs, and the awk script to run, but does >>> anything then need to be added to the driver to pick it up, or should >>> that >>> be all thats needed? >> >> it does not look at the product. it looks at interface class, subclass >> and protocol. are you sure you are loading ng_ubt(4) from loader.conf? >> are there any error messages from ng_ubt(4) in /var/log/messages? > > devd.conf problem then? I haven't got it in loader.conf, but I did kldload- > dmesg output (although the last 2 lines disappear when unloaded/loaded: > > ubt0: on > usbus5 > WARNING: attempt to domain_add(bluetooth) after domainfinalize() > WARNING: attempt to domain_add(netgraph) after domainfinalize() if you get ubt0 line then device was recognized and attached. those two WARNING messages are harmless > But ls dev shows no devices, and I can't start bluetooth services: ng_ubt(4) does NOT create device nodes in /dev. this question pops up very often. handbook should really be updated to mention this. > /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0 > > If it should work, then what am I doing wrong? devd(8) will start/stop stack for you automatically. please check devd.conf (look at ubt secion). there is no need to start stack by hand any more. the error is because you are trying to start the stack when its already been started. again, handbook should be updated to reflect that. max