linux-kernel - Re: ath5k problem with 2.6.35

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 24 Aug 2010 11:18:15 -0400
From:	"John W. Linville" <linville@...driver.com>
To:	Thomas Fjellstrom <thomas@...llstrom.ca>
Cc:	linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: ath5k problem with 2.6.35

On Mon, Aug 23, 2010 at 06:49:12PM -0600, Thomas Fjellstrom wrote:
> On August 23, 2010, 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?
> 
> I don't even know what that is, so no. At least I didn't do it. if wicd did, 
> then yes.

In any case, wep failed to init for some reason and the prevents
device registration.  You need the patch I referenced earlier.

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@...driver.com			might be all we have.  Be ready.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/