Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 26 May 2016 07:27:51 -0700
From:      Maksim Yevmenkin <maksim.yevmenkin@gmail.com>
To:        Graham Menhennitt <graham@menhennitt.com.au>
Cc:        FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: bluetooth not working in recent current
Message-ID:  <CAFPOs6oMRqy4A4rguRKtCepqkxYzUdcF5GtgbyVrLhveo8ZkhQ@mail.gmail.com>
In-Reply-To: <ba6e1521-52e3-26b1-4748-7dc2ce4d4971@menhennitt.com.au>
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> <ba6e1521-52e3-26b1-4748-7dc2ce4d4971@menhennitt.com.au>

index | next in thread | previous in thread | raw e-mail

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: <USB Bluetooth Dongle Broadcom> 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


home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFPOs6oMRqy4A4rguRKtCepqkxYzUdcF5GtgbyVrLhveo8ZkhQ>