Return-path: <linux-wireless-owner@vger.kernel.org>
Received: from mta21.charter.net ([216.33.127.81]:56758 "EHLO
	mta21.charter.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S934375Ab3FTAVp (ORCPT
	<rfc822;linux-wireless@vger.kernel.org>);
	Wed, 19 Jun 2013 20:21:45 -0400
Date: Wed, 19 Jun 2013 20:21:42 -0400
From: rlwkayaker <rlwkayaker@charter.net>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Dan Williams <dcbw@redhat.com>, linux-wireless@vger.kernel.org
Subject: Re: Howto remove rfkill from kernel
Message-ID: <20130619202142.25307130@compuzoo> (sfid-20130620_022200_384215_A5B74561)
In-Reply-To: <20130620000941.GL31667@titan.lakedaemon.net>
References: <20130619133638.3d183a00@compuzoo>
	<1371682734.1051.0.camel@dcbw.foobar.com>
	<20130619200356.741ec084@compuzoo>
	<20130620000941.GL31667@titan.lakedaemon.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-wireless-owner@vger.kernel.org
List-ID: <linux-wireless.vger.kernel.org>

On Wed, 19 Jun 2013 20:09:41 -0400
Jason Cooper <jason@lakedaemon.net> wrote:

> On Wed, Jun 19, 2013 at 08:03:56PM -0400, rlwkayaker wrote:
> > rfkill has a hard block on the wireless.
> 
> Is this system dual-boot with windows?  If so, boot into
> windows and enable wireless via the usual mechanisms.  Then
> reboot into Linux.
> 
> hth,
> 
> Jason.

No, there is nothing on this system but Linux.  At the moment,
only antiX-13.

Richard