Date: Thu, 26 May 2016 11:26:36 +1000 From: Graham Menhennitt <graham@menhennitt.com.au> To: freebsd-current@freebsd.org Subject: Re: bluetooth not working in recent current Message-ID: <ba6e1521-52e3-26b1-4748-7dc2ce4d4971@menhennitt.com.au> In-Reply-To: <CAFPOs6q%2Bt35oyntbgxyDqeOP=AfipkeRY_7DyQAGbSRudfzx0g@mail.gmail.com> References: <5c480504-08e6-6d02-3123-9d66ba825426@menhennitt.com.au> <CAFPOs6of%2BxvDnTWTiPEP-fNYHtp_tSfQReVv5hQY9AfL32gb4Q@mail.gmail.com> <74db6c77-3080-6177-fbaa-250f884e5402@menhennitt.com.au> <CAFPOs6q%2Bt35oyntbgxyDqeOP=AfipkeRY_7DyQAGbSRudfzx0g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 26/05/2016 7:24 AM, Maksim Yevmenkin wrote: > >>> 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)? > dmesg shows: ubt0: <Broadcom USB Bluetooth Dongle, class 224/1, rev 1.10/0.01, addr 2> on usbus6 usbconfig dump_device_desc shows: ugen6.2: <USB Bluetooth Dongle Broadcom> at usbus6, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x00e0 <Wireless controller> bDeviceSubClass = 0x0001 bDeviceProtocol = 0x0001 bMaxPacketSize0 = 0x0040 idVendor = 0x0a5c idProduct = 0x200a bcdDevice = 0x0001 iManufacturer = 0x0001 <Broadcom> iProduct = 0x0002 <USB Bluetooth Dongle> iSerialNumber = 0x0003 <2035B0000001> bNumConfigurations = 0x0001 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. Thanks for your help, Graham
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ba6e1521-52e3-26b1-4748-7dc2ce4d4971>