From: Thomas Fjellstrom <tfjellstrom@strangesoft.net>
To: linux-wireless@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: ath5k problem with 2.6.35
Date: Sun, 22 Aug 2010 00:05:38 -0600 [thread overview]
Message-ID: <201008220005.38969.tfjellstrom@strangesoft.net> (raw)
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
next reply other threads:[~2010-08-22 6:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-22 6:05 Thomas Fjellstrom [this message]
2010-08-22 7:53 ` ath5k problem with 2.6.35 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
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=201008220005.38969.tfjellstrom@strangesoft.net \
--to=tfjellstrom@strangesoft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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).