linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John S. Skogtvedt" <jss@bzz.no>
To: Bob Copeland <me@bobcopeland.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Bug: 2.6.32 ath5k, unable to connect to AP on channel 13
Date: Mon, 25 Jan 2010 20:22:06 +0100	[thread overview]
Message-ID: <4B5DEF5E.8050502@bzz.no> (raw)
In-Reply-To: <b6c5339f1001250951u548e6a16raf661464660ec577@mail.gmail.com>

Bob Copeland skrev:
> On Sun, Jan 24, 2010 at 4:12 PM, John S. Skogtvedt <jss@bzz.no> wrote:
>> 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.
> 
>> dmesg output:
>> [    7.205952] cfg80211: Using static regulatory domain info
>> [    7.205956] cfg80211: Regulatory domain: US
>> [    7.206243] cfg80211: Calling CRDA for country: US
> 
> Well, there's your problem, AFAICT.  You have
> CONFIG_WIRELESS_OLD_REGULATORY=y?  And ieee80211_regdom=EU doesn't work?
> 

Yes, CONFIG_WIRELESS_OLD_REGULATORY=y. And neither ieee80211_regdom=EU
or ieee80211_regdom=NO works.

      parent reply	other threads:[~2010-01-25 19:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-24 21:12 Bug: 2.6.32 ath5k, unable to connect to AP on channel 13 John S. Skogtvedt
2010-01-25 17:51 ` 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 [this message]

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=4B5DEF5E.8050502@bzz.no \
    --to=jss@bzz.no \
    --cc=linux-wireless@vger.kernel.org \
    --cc=me@bobcopeland.com \
    /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).