All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anderson Lizardo <anderson.lizardo@openbossa.org>
To: aep <aep@exys.org>
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
	linux-bluetooth@vger.kernel.org,
	Marcel Holtmann <marcel@holtmann.org>
Subject: Re: Lenovo W510 Bluetooth Controller stopped working in 3.4-rc1
Date: Fri, 13 Apr 2012 06:42:07 -0400	[thread overview]
Message-ID: <CAJdJm_PE-_3OZoDCXRf6wne_myQDCSV9wcvA9RnGt_W6uH5BRQ@mail.gmail.com> (raw)
In-Reply-To: <d62a71fa204a8a9e8568309b9c1d2f6b@exys.org>

Hi aep,

On Fri, Apr 13, 2012 at 5:49 AM, aep <aep@exys.org> wrote:
>> If this is related to mgmt being now enabled by default
>> could you try running user space with "bluetoothd -P mgmtops"?
>
> Not sure if that does any good, since adding the parameter did the job, and
> my /usr/lib/bluetooth/plugins/ is empty.
> Let me know if you still think this helps debugging, then i'll try later.

BlueZ plugins by default are "built-in", i.e. they are linked inside
the bluetoothd binary. But even built-in plugins can be disabled with
-P.

What Johan is suggesting is to disable the mgmtops plugin so that
hciops is used instead. If this works, it is due to a known regression
which happens with incompatible userspace tools and kernel versions.

Fortunately, a proper fix is on the way for the next upstream release.
So you can use this workaround for now.

Best Regards,
-- 
Anderson Lizardo
Instituto Nokia de Tecnologia - INdT
Manaus - Brazil

  reply	other threads:[~2012-04-13 10:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12 17:01 Lenovo W510 Bluetooth Controller stopped working in 3.4-rc1 aep
2012-04-13  9:34 ` Johan Hedberg
2012-04-13  9:49   ` aep
2012-04-13 10:42     ` Anderson Lizardo [this message]
2012-04-13 11:14       ` AVRCP Passthrough Commands issue with Kenwood Car stereo Michael McCallum
2012-04-13 11:15         ` Michael McCallum
2012-04-13 17:37         ` Lucas De Marchi
2012-04-13 12:24       ` Lenovo W510 Bluetooth Controller stopped working in 3.4-rc1 aep

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJdJm_PE-_3OZoDCXRf6wne_myQDCSV9wcvA9RnGt_W6uH5BRQ@mail.gmail.com \
    --to=anderson.lizardo@openbossa.org \
    --cc=aep@exys.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.