* ath5k problem with 2.6.35
@ 2010-08-22 6:05 Thomas Fjellstrom
2010-08-22 7:53 ` Thomas Fjellstrom
0 siblings, 1 reply; 6+ messages in thread
From: Thomas Fjellstrom @ 2010-08-22 6:05 UTC (permalink / raw)
To: linux-wireless; +Cc: linux-kernel
Hi, I'm running 2.6.35, and my wireless card fails to initialize properly on
boot. I get the following messages in dmesg:
[ 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.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
That said, if I remove the ath5k module, and modprobe ath5k, it starts
working.
[ 2976.411770] ath5k 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 2976.411783] ath5k 0000:02:00.0: setting latency timer to 64
[ 2976.412767] ath5k 0000:02:00.0: registered as 'phy1'
[ 2976.912422] ath: EEPROM regdomain: 0x67
[ 2976.912424] ath: EEPROM indicates we should expect a direct regpair map
[ 2976.912427] ath: Country alpha2 being used: 00
[ 2976.912429] ath: Regpair used: 0x67
[ 2977.079190] ath5k phy1: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
Is this a known issue?
--
Thomas Fjellstrom
tfjellstrom@strangesoft.net
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ath5k problem with 2.6.35
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
0 siblings, 1 reply; 6+ messages in thread
From: Thomas Fjellstrom @ 2010-08-22 7:53 UTC (permalink / raw)
To: linux-wireless; +Cc: linux-kernel
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
>
> That said, if I remove the ath5k module, and modprobe ath5k, it starts
> working.
>
> [ 2976.411770] ath5k 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ
> 17 [ 2976.411783] ath5k 0000:02:00.0: setting latency timer to 64
> [ 2976.412767] ath5k 0000:02:00.0: registered as 'phy1'
> [ 2976.912422] ath: EEPROM regdomain: 0x67
> [ 2976.912424] ath: EEPROM indicates we should expect a direct regpair map
> [ 2976.912427] ath: Country alpha2 being used: 00
> [ 2976.912429] ath: Regpair used: 0x67
[ 2977.078747] phy1: Selected rate control algorithm 'minstrel'
> [ 2977.079190] ath5k phy1: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
>
> Is this a known issue?
Thanks
--
Thomas Fjellstrom
thomas@fjellstrom.ca
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ath5k problem with 2.6.35
2010-08-22 7:53 ` Thomas Fjellstrom
@ 2010-08-23 18:29 ` John W. Linville
2010-08-23 18:31 ` John W. Linville
2010-08-24 0:49 ` Thomas Fjellstrom
0 siblings, 2 replies; 6+ messages in thread
From: John W. Linville @ 2010-08-23 18:29 UTC (permalink / raw)
To: Thomas Fjellstrom; +Cc: linux-wireless, linux-kernel
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?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ath5k problem with 2.6.35
2010-08-23 18:29 ` John W. Linville
@ 2010-08-23 18:31 ` John W. Linville
2010-08-24 0:49 ` Thomas Fjellstrom
1 sibling, 0 replies; 6+ messages in thread
From: John W. Linville @ 2010-08-23 18:31 UTC (permalink / raw)
To: Thomas Fjellstrom; +Cc: linux-wireless, linux-kernel
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ath5k problem with 2.6.35
2010-08-23 18:29 ` John W. Linville
2010-08-23 18:31 ` John W. Linville
@ 2010-08-24 0:49 ` Thomas Fjellstrom
2010-08-24 15:18 ` John W. Linville
1 sibling, 1 reply; 6+ messages in thread
From: Thomas Fjellstrom @ 2010-08-24 0:49 UTC (permalink / raw)
To: John W. Linville; +Cc: linux-wireless, linux-kernel
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.
> John
--
Thomas Fjellstrom
thomas@fjellstrom.ca
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ath5k problem with 2.6.35
2010-08-24 0:49 ` Thomas Fjellstrom
@ 2010-08-24 15:18 ` John W. Linville
0 siblings, 0 replies; 6+ messages in thread
From: John W. Linville @ 2010-08-24 15:18 UTC (permalink / raw)
To: Thomas Fjellstrom; +Cc: linux-wireless, linux-kernel
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@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2010-08-24 15:29 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2010-08-24 0:49 ` Thomas Fjellstrom
2010-08-24 15:18 ` John W. Linville
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).