From owner-freebsd-current@freebsd.org Thu May 26 14:27:53 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D6573B4BEEB for ; Thu, 26 May 2016 14:27:53 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6F15913AF for ; Thu, 26 May 2016 14:27:53 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by mail-wm0-x230.google.com with SMTP id n129so229959274wmn.1 for ; Thu, 26 May 2016 07:27:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=RLynbr8zUSaGl8LmJ7cgdjgq5zQXhopD1FlTLioVsCE=; b=m9C+ykaGYxGXepscx2bFNdHHyMXhoHBae6x2WIsPBNJ37xpx203HxnJoQ7uECJWfPF 6dEib8g04aXZuYptWOnx1HC1fgJnqroQQVqt6pafe0xRipq0WIEY1R5VG+OuUnigwe3+ APRWg3lBKB5+vIgdWdRcKC5/3LYdr8cDJVP96ueydA1aq9px7gL3NKUlTg1T0cHX59sB I9ByvKzGtHrJYSwKvHT4sQpzWd8mxTJwMYAnqY5CYoRGHytssEDMDvCgFmCrdXD7HyZe JIVWj7YXy8T+NGBR4DNAVAU7RXVaHoZuQLl82jNPxFp8txP0KJt+diLMtpCx79hAsQC+ KmxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=RLynbr8zUSaGl8LmJ7cgdjgq5zQXhopD1FlTLioVsCE=; b=DHPyHaxIQmRkzU8l9DelEXOv7GdBj8RtIxJrmvjLir1U23HI/gDM0GEK6QOs/4GAqg 9//IRriPCbzPLEvcYkTIRso+YXxbQZvVCe8uBzWC8d0/lDtIcWNQ4Q/nqKTPgVhR28jx 8UHMREEMvti9Mzy+4qlf1KNqJ+NTLMt9h/1EbkaIObPMPHcsDyLHniZ8v7bT8n35zbbq NGVAUWSkmoY30SCVM06Wo+2894YXYiUF/TnIhLQc2Fp1OQyew8CW57DZK/odKOE1RFeH zbfIQnVxsPI7pypMRGF4rTMpeQzf1QWamMXW9xbpZUJXfWVSR9iqLXAQsfCcqoVC9CNp XZ8w== X-Gm-Message-State: ALyK8tIl4DsuUj9U6PEXght9L4ZImRMFJAtskub6dax7WcySlTcq09jWDg97wRM072946+tL0yEbfXb4/AdL2w== MIME-Version: 1.0 X-Received: by 10.28.181.148 with SMTP id e142mr3878753wmf.38.1464272871629; Thu, 26 May 2016 07:27:51 -0700 (PDT) Received: by 10.28.54.150 with HTTP; Thu, 26 May 2016 07:27:51 -0700 (PDT) In-Reply-To: References: <5c480504-08e6-6d02-3123-9d66ba825426@menhennitt.com.au> <74db6c77-3080-6177-fbaa-250f884e5402@menhennitt.com.au> Date: Thu, 26 May 2016 07:27:51 -0700 Message-ID: Subject: Re: bluetooth not working in recent current From: Maksim Yevmenkin To: Graham Menhennitt Cc: FreeBSD Current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 May 2016 14:27:53 -0000 Graham, >>>> can you also please try to start it manually and see where it stops? >>>> i.e. something like >>>> >>>> # sh -x /etc/rc.d/bluetooth start ubt0 >>> >>> Thanks for responding. The output of that command is below. I'll do some >>> more diagnosis when I get home tonight. >> >> + /usr/sbin/hccontrol -n ubt0hci reset >> + return 1 >> so, "reset" command failed :( can you please tell me which exact >> broadcom device you have, i.e. vendor id and product id? some broadcom >> devices may require firmware download. you said it was working before, >> can you please tell if you had to download firmware before? i.e. use >> ubtbcmfw ? are you dual booting between freebsd and windows (or >> linux)? [...] > usbconfig dump_device_desc shows: > ugen6.2: at usbus6, cfg=0 md=HOST spd=FULL > (12Mbps) pwr=ON (100mA) > > idVendor = 0x0a5c > idProduct = 0x200a thanks! so, it does not look like it needs firmware download. > No, I don't dual boot anything. I have never loaded firmware - maybe it > happened automatically in the past, but I've never used ubtbcmfw explicitly. right. i does not appear that you have to do anything here. can you please modify /etc/rc.d/bluetooth and make sure it does not exit when hci reset command fails? it would be useful to know if any other hci commands fail. thanks! max