From: "John S. Skogtvedt" <jss@bzz.no>
To: linux-wireless@vger.kernel.org
Subject: Bug: 2.6.32 ath5k, unable to connect to AP on channel 13
Date: Sun, 24 Jan 2010 22:12:11 +0100 [thread overview]
Message-ID: <4B5CB7AB.7010105@bzz.no> (raw)
Hello,
As the subject says, using ath5k on 2.6.32 I am not able to connect to
an AP on channel 13 (i.e. wpa_supplicant doesn't find the AP and thus
fails to associate). I'm in Norway, and the card is bought in Norway.
With 2.6.26 and 2.6.30, I am able to connect to the AP if I use the
cfg80211 ieee80211_regdom=EU option (necessary at least on 2.6.26).
For 2.6.32, I've tried without the option as well as ieee80211_regdom=NO.
I'm running Debian Squeeze, and the kernel version is
linux-image-2.6-686=2.6.32+23. The changelog for the kernel package is
available at:
http://packages.debian.org/changelogs/pool/main/l/linux-2.6/linux-2.6_2.6.32-5/changelog
As the AP doesn't appear when doing a scan, I didn't capture the
wpa_supplicant output.
dmesg output:
[ 7.205952] cfg80211: Using static regulatory domain info
[ 7.205956] cfg80211: Regulatory domain: US
[ 7.206243] cfg80211: Calling CRDA for country: US
[ 7.305635] ath5k 0000:01:0a.0: PCI INT A -> Link[APC1] -> GSI 16
(level, high) -> IRQ 16
[ 7.305709] ath5k 0000:01:0a.0: registered as 'phy0'
[ 7.887265] ath: EEPROM regdomain: 0x80d0
[ 7.887267] ath: EEPROM indicates we should expect a country code
[ 7.887270] ath: doing EEPROM country->regdmn map search
[ 7.887272] ath: country maps to regdmn code: 0x37
[ 7.887275] ath: Country alpha2 being used: DK
[ 7.887277] ath: Regpair used: 0x37
[ 8.288352] ath5k phy0: Atheros AR2414 chip found (MAC: 0x79, PHY: 0x45)
[ 8.288607] cfg80211: Calling CRDA for country: DK
lspci:
01:0a.0 Ethernet controller: Atheros Communications Inc. Atheros
AR5001X+ Wireless Network Adapter (rev 01)
Subsystem: D-Link System Inc D-Link AirPlus DWL-G520 Wireless
PCI Adapter(rev.B)
Kernel driver in use: ath5k
iw list output:
Wiphy phy0
Band 1:
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (disabled)
* 2472 MHz [13] (disabled)
* 2484 MHz [14] (disabled)
...
iw reg get output:
country US:
(2402 - 2472 @ 40), (6, 27)
(5170 - 5190 @ 40), (6, 23)
(5190 - 5210 @ 40), (6, 23)
(5210 - 5230 @ 40), (6, 23)
(5230 - 5330 @ 40), (6, 23)
(5735 - 5835 @ 40), (6, 30)
I tried "iw reg set NO" without effect.
Please let me know if you need any more information. (Also, please CC me
on replies as I'm not on the list.)
Thank you,
John.
next reply other threads:[~2010-01-24 22:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 21:12 John S. Skogtvedt [this message]
2010-01-25 17:51 ` Bug: 2.6.32 ath5k, unable to connect to AP on channel 13 Bob Copeland
2010-01-25 18:30 ` Gábor Stefanik
2010-01-25 19:20 ` Luis R. Rodriguez
2010-01-26 10:20 ` Kalle Valo
2010-01-26 19:06 ` Luis R. Rodriguez
2010-01-28 13:27 ` Kel Modderman
2010-01-28 18:01 ` Luis R. Rodriguez
2010-01-25 19:26 ` John S. Skogtvedt
2010-01-25 19:58 ` Luis R. Rodriguez
2010-01-25 19:22 ` John S. Skogtvedt
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=4B5CB7AB.7010105@bzz.no \
--to=jss@bzz.no \
--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).