From: "Robert M. Albrecht" <linux@romal.de>
To: Philip Langdale <philipl@overt.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bug 10173 / Bluetooth on Toshiba & Compal laptops
Date: Tue, 23 Dec 2008 08:04:43 +0100 [thread overview]
Message-ID: <49508D8B.20801@romal.de> (raw)
In-Reply-To: <5a670e0fe13a5f433ef207efefd71ca2@localhost>
Hi,
the module is loaded:
[root@tycho ~]# lsmod | grep kill
rfkill 11288 2 toshiba_acpi
[root@tycho ~]#
The wlan-devices works ok, it get's disabled and enabled via rfkill. But
the bluetooth-device does not get reeanbled after switching it off.
cu romal
Am 15.12.2008 23:47 Uhr, schrieb Philip Langdale:
> On Mon, 15 Dec 2008 23:34:52 +0100, "Robert M. Albrecht"<mail@romal.de>
> wrote:
>> Hi Phil,
>>
>> anything I can do ? Providing some logs or granting ssh access to the
>> machine to have a look ?
>
> If necessary, that would be useful. However, the first question to ask is
> actually
> related to my possibility C) - which I'm now re-evaluating as much more
> likely.
>
> If you don't load the 'rfkill-input' module, then there is no policy
> applied to
> killswitch handling. The core driver puts the device in the SOFT_BLOCKED
> state
> when the de-assert the hardware switch. rfkill-input contains the policy
> that
> decides to go one step further and re-enable the device. This module has no
> hardware dependencies so it is not automatically loaded - you must do it
> explicitly yourself.
>
> If that's not your problem, then we'll have to dig deeper.
>
> --phil
>
>
next prev parent reply other threads:[~2008-12-23 7:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 20:29 Bug 10173 / Bluetooth on Toshiba & Compal laptops Robert M. Albrecht
2008-12-15 22:35 ` Philip Langdale
2008-12-15 22:34 ` Robert M. Albrecht
2008-12-15 22:47 ` Philip Langdale
2008-12-23 7:04 ` Robert M. Albrecht [this message]
2008-12-23 9:06 ` Philip Langdale
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=49508D8B.20801@romal.de \
--to=linux@romal.de \
--cc=linux-kernel@vger.kernel.org \
--cc=philipl@overt.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.