From: "John W. Linville" <linville@tuxdriver.com>
To: Thomas Fjellstrom <thomas@fjellstrom.ca>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: ath5k problem with 2.6.35
Date: Mon, 23 Aug 2010 14:31:55 -0400 [thread overview]
Message-ID: <20100823183155.GF2609@tuxdriver.com> (raw)
In-Reply-To: <20100823182903.GE2609@tuxdriver.com>
On Mon, Aug 23, 2010 at 02:29:03PM -0400, John W. Linville wrote:
> On Sun, Aug 22, 2010 at 01:53:41AM -0600, Thomas Fjellstrom wrote:
> > On August 22, 2010, Thomas Fjellstrom wrote:
> > > Hi, I'm running 2.6.35, and my wireless card fails to initialize properly
> > > on boot. I get the following messages in dmesg:
> >
> > Probably important, but I missed a couple lines:
> >
> > > [ 0.866525] ath5k 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ
> > > 17 [ 0.866536] ath5k 0000:02:00.0: setting latency timer to 64
> > > [ 0.866571] ath5k 0000:02:00.0: registered as 'phy0'
> > > [ 1.358241] ath: EEPROM regdomain: 0x67
> > > [ 1.358242] ath: EEPROM indicates we should expect a direct regpair map
> > > [ 1.358245] ath: Country alpha2 being used: 00
> > > [ 1.358247] ath: Regpair used: 0x67
> > [ 1.360589] phy0: Failed to initialize wep: -2
> > > [ 1.372021] ath5k phy0: can't register ieee80211 hw
> > > [ 1.372080] ath5k 0000:02:00.0: PCI INT A disabled
> > > [ 1.372084] ath5k: probe of 0000:02:00.0 failed with error -2
>
> Did you enable fips mode?
Presuming the answer is yes, you need this patch (available in 2.6.36-rc1):
commit 3473187d2459a078e00e5fac8aafc30af69c57fa
Author: John W. Linville <linville@tuxdriver.com>
Date: Wed Jul 7 15:07:49 2010 -0400
mac80211: remove wep dependency
The current mac80211 code assumes that WEP is always available. If WEP
fails to initialize, ieee80211_register_hw will always fail.
In some cases (e.g. FIPS certification), the cryptography used by WEP is
unavailable. However, in such cases there is no good reason why CCMP
encryption (or even no link level encryption) cannot be used. So, this
patch removes mac80211's assumption that WEP (and TKIP) will always be
available for use.
Signed-off-by: John W. Linville <linville@tuxdriver.com>
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:[~2010-08-23 18:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-22 6:05 ath5k problem with 2.6.35 Thomas Fjellstrom
2010-08-22 7:53 ` Thomas Fjellstrom
2010-08-23 18:29 ` John W. Linville
2010-08-23 18:31 ` John W. Linville [this message]
2010-08-24 0:49 ` Thomas Fjellstrom
2010-08-24 15:18 ` 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=20100823183155.GF2609@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=thomas@fjellstrom.ca \
/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).