linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: rlwkayaker <rlwkayaker@charter.net>
To: Dan Williams <dcbw@redhat.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Howto remove rfkill from kernel
Date: Wed, 19 Jun 2013 20:03:56 -0400	[thread overview]
Message-ID: <20130619200356.741ec084@compuzoo> (raw)
In-Reply-To: <1371682734.1051.0.camel@dcbw.foobar.com>

On Wed, 19 Jun 2013 17:58:54 -0500
Dan Williams <dcbw@redhat.com> wrote:

> On Wed, 2013-06-19 at 13:36 -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?
> 
> Best thing to do is figure out why this is happening, and fix
> it.  What kernels worked?  What kernels fail?  What wifi card
> do you have, and was it the card the laptop originally came
> with?
> 
> Dan
> 
I have been using 2.6.32-5-686 successfully with Debian
Squeeze.  Earlier kernels native to Debian Lenny and Etch also
worked well.  I tried to update to Debian Wheezy which uses
3.2.0.4 and ran into many problems, including the rfkill
"feature".  I gave up on Wheezy and I tried Gentoo, with it's
3.? kernel and the same rfkill problem, among others. I am
currently using 3.7.10-antiX which works very well in this
laptop, except for rfkill "feature". rfkill has a hard block on
the wireless.  The internal card is original and uses the
rt2500pci module. I can, and do, temporarily, use a PCMCIA
wireless card in that laptop successfully and rfkill doesn't
interfere. I don't find this to be a good solution.  I would
rather go back to the internal card without the PCMCIA appendage
protruding from the side of the machine.

I have spent a lot of time trying various "fixes" identified on
the Internet.  I'm left with building a kernel without rfkill,
using the PCMCIA card or scrapping my favorite laptop because
somebody decided to put this "feature" in the kernel with
inadequate information.

Richard

  reply	other threads:[~2013-06-20  0:03 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
2013-06-19 22:58 ` Dan Williams
2013-06-20  0:03   ` rlwkayaker [this message]
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=20130619200356.741ec084@compuzoo \
    --to=rlwkayaker@charter.net \
    --cc=dcbw@redhat.com \
    --cc=linux-wireless@vger.kernel.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 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).