From: aep <aep@exys.org>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: <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 11:49:19 +0200 [thread overview]
Message-ID: <d62a71fa204a8a9e8568309b9c1d2f6b@exys.org> (raw)
In-Reply-To: <20120413093400.GC10780@x220.ger.corp.intel.com>
On Fri, 13 Apr 2012 12:34:00 +0300, Johan Hedberg wrote:
> I don't think that commit or that module parameter has anything to do
> with this.
Actually, i didn't respond again due to the embarrassing fact that i
added the parameter to the wrong module.
After adding bluetooth.enable_hs=1 to the kernel commandline (bluetooth
is compiled in here), it worked again.
> What user space version are you using?
bluez version 4.98
> What do you mean by
> "vanished without any trace"? Does hciconfig -a or hciconfig hci0 not
> show anything?
no, and no, and neither anything in dmesg other then that the module
was loaded.
> 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.
thanks
next prev parent reply other threads:[~2012-04-13 9:49 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 [this message]
2012-04-13 10:42 ` Anderson Lizardo
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=d62a71fa204a8a9e8568309b9c1d2f6b@exys.org \
--to=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.