[Discuss] bluetooth

[johnhall2.0 at gmail.com (John Hall)]

I did not delve to deeply but scanning through ... have you shown the
hardware you have through a lower level hardware inspection command like
lspci lsusb ?  AH! and while I was writing looks like Mike knows just what
to use!

Could it be related to this?  If so I'm not suggesting you give up on it
but it might be much easier if your bluetooth hardware is not supported by
opensource drivers to get a dongle that is supported.
http://en.community.dell.com/techcenter/os-applications/f/4613/t/19657901?

Second thought is that prehaps there is a firmware related soft switch to
turn the bluetooth off and on that is specific to your hardware. While it's
best to do everything with commands be sure to try all the settings panels
as well because buttons on a panel could be doing hardware inspection and
executing appropriate commands based on your hardware.


On Thu, Jan 28, 2016 at 6:13 PM, dan moylan <jdm at moylan.us> wrote:

>
> mike small writes:
> >On Thu, Jan 28, 2016 at 12:07:35PM -0500, dan moylan wrote:
> >>
> >> i have recently been given an ivation boomering bluetooth
> >> speaker and am fumbling about trying to make use of it.
> >> i started by looking at:
> >>
> >> https://wiki.archlinux.org/index.php/bluetooth
> >>
> >> but seem to be doing something wrong.  e.g.
> >>
> >> moylan ~[1042] sudo bluetoothctl
> >> [sudo] password for moylan:
> >> [NEW] Controller B8:EE:65:34:F2:B4 aldeberon [default]
> >> [bluetooth]# power on
> >> Failed to set power on: org.bluez.Error.Blocked
> >> [bluetooth]# scan on
> >> Failed to start discovery: org.bluez.Error.NotReady
> >> [bluetooth]# quit
> >> [DEL] Controller B8:EE:65:34:F2:B4 aldeberon [default]
> >>
> >> the wiki says to turn the power on with bluetoothctl, but
> >> that seems not to work.
> >>
> >> what have i missed?
> >
> >Since no one who knows about this stuff has answered yet I'll ask
> >if there's any further information in your log files. Those errors
> >to me sound like bluez is waiting for something else to start up
> >before it can properly get going.
> >
> >Unfortunately, the only thing I know about bluez is that it's what
> >forced Pat Volkerding to finally include PulseAudio in the pending
> >release of Slackware. Apparently bluez recently made PA a hard
> >requirement. Say, do you have PulseAudio installed and running
> >properly?
>
> ran bluetoothctl power on and found this using journalctl -f
>
> Jan 28 17:59:13 aldeberon bluetoothd[734]: Failed to set mode: Blocked
> through rfkill (0x12)
>
> ps shows:
>  2113  1000 S<l  Jan25 /usr/bin/pulseaudio --start
>
> any thoughts?
>
> tia,
> ole dan
>
> j. daniel moylan
> 84 harvard ave
> brookline, ma 02446-6202
> 617-777-0207 (cel)
> jdm at moylan.us
> www.moylan.us
> [no html pls]
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://lists.blu.org/mailman/listinfo/discuss
>