linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <zbr@ioremap.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	Intel Linux Wireless <ilw@linux.intel.com>,
	netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
	wey-yi.w.guy@intel.com
Subject: Re: iwl rfkill suddenly dropped to hard block
Date: Thu, 16 Dec 2010 14:57:18 +0300	[thread overview]
Message-ID: <20101216115717.GA15075@ioremap.net> (raw)
In-Reply-To: <4D099444.5040703@lwfinger.net>

On Wed, Dec 15, 2010 at 10:23:32PM -0600, Larry Finger (Larry.Finger@lwfinger.net) wrote:
> >I would imagine this is just related to some dellish crap, but I saw a
> >number of exactly the same cases in the web including linux-kernel mail
> >lists in the past and also without 'slider on the back' case.
> 
> I doubt that it is Dell related, if that is what "dellish" means.
> 
> I have had some success in clearing this problem by unloading and
> reloading the wireless driver. I had the problem on one box that has
> no rfkill switch and an 802.11b card that uses b43legacy.

I tried that as well as disabling and enabling wifi in bios (or is it
newr loader), but without success. I called this 'dellish' crap
because of the hell list of problems I had with this laptop and i915
video chipset in it. Apparently brother model e4200 does not have them
at all.

-- 
	Evgeniy Polyakov

  reply	other threads:[~2010-12-16 11:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20101215195651.GA18545@ioremap.net>
2010-12-15 20:11 ` iwl rfkill suddenly dropped to hard block John W. Linville
2010-12-15 20:28   ` Guy, Wey-Yi
2010-12-16  3:22   ` Evgeniy Polyakov
2010-12-16  4:23     ` Larry Finger
2010-12-16 11:57       ` Evgeniy Polyakov [this message]
2010-12-16 14:40   ` Evgeniy Polyakov
2010-12-16 14:42     ` John W. Linville

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=20101216115717.GA15075@ioremap.net \
    --to=zbr@ioremap.net \
    --cc=Larry.Finger@lwfinger.net \
    --cc=ilw@linux.intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=wey-yi.w.guy@intel.com \
    /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).