From: "John W. Linville" <linville@tuxdriver.com>
To: rlwkayaker <rlwkayaker@charter.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Howto remove rfkill from kernel
Date: Wed, 19 Jun 2013 14:38:40 -0400 [thread overview]
Message-ID: <20130619183839.GD12079@tuxdriver.com> (raw)
In-Reply-To: <20130619133638.3d183a00@compuzoo>
On Wed, Jun 19, 2013 at 01:36:38PM -0400, rlwkayaker wrote:
> The rfkill "feature" has rendered the internal wireless of my
> Averatec 3260 laptop unusable. It works fine with earlier
> kernels without this "feature". How do I remove the rfkill
> "feature" from a custom built kernel?
The rfkill "feature" has been in the kernel for years. Exactly what
kernels are you using?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2013-06-19 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 17:36 Howto remove rfkill from kernel rlwkayaker
2013-06-19 18:38 ` John W. Linville [this message]
2013-06-19 22:58 ` Dan Williams
2013-06-20 0:03 ` rlwkayaker
2013-06-20 0:09 ` Jason Cooper
2013-06-20 0:21 ` rlwkayaker
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=20130619183839.GD12079@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rlwkayaker@charter.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).