From: Ben Greear <greearb@candelatech.com>
To: Mohammed Shafi <shafi.wireless@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: ath9k 9380: All 5Ghz channels flagged as passive-scanning
Date: Mon, 23 May 2011 11:52:35 -0700 [thread overview]
Message-ID: <4DDAACF3.3050705@candelatech.com> (raw)
In-Reply-To: <4DDAA9ED.1050606@candelatech.com>
On 05/23/2011 11:39 AM, Ben Greear wrote:
> On 05/23/2011 09:54 AM, Ben Greear wrote:
>> On 05/23/2011 04:28 AM, Mohammed Shafi wrote:
>>> On Sat, May 21, 2011 at 3:52 AM, Ben Greear<greearb@candelatech.com>
>>> wrote:
>>>> This is on 2.6.39-wl+
>>>>
>>>> All the 5Ghz channels are showing as passive scanning, which
>>>> makes them unusable for APs if nothing else.
>>>
>>> for me channels 36,40,44,48 are ok in 5ghz. used the latest
>>> wireless-testing just brought the card up as station mode.
>>
>> Most of my systems show the same, at least most of the time.
>>
>>
>>>> Any idea why this is happening?
>>>
>>> don't know, may be regulatory.
>>
>> After a reboot and an idle weekend, mine also look normal.
>> So, it's something transient it appears.
>
> Err, I mis-spoke..the 9380 system still shows passive
> scanning everywhere...
Busted one:
ath: EEPROM regdomain: 0x6a
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: 00
ath: Regpair used: 0x6a
cfg80211: Calling CRDA for country: US
cfg80211: Regulatory domain changed to country: US
cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
Bleh, seems my Sparklan 127 NIC is set to world-roam :(
What a total pain in the arse!
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-05-23 18:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 22:22 ath9k 9380: All 5Ghz channels flagged as passive-scanning Ben Greear
2011-05-23 11:28 ` Mohammed Shafi
2011-05-23 16:54 ` Ben Greear
2011-05-23 18:39 ` Ben Greear
2011-05-23 18:52 ` Ben Greear [this message]
2011-05-23 19:26 ` Luis R. Rodriguez
2011-05-23 20:09 ` Ben Greear
2011-05-23 20:25 ` Luis R. Rodriguez
2011-05-23 20:51 ` Ben Greear
2011-05-23 20:59 ` Luis R. Rodriguez
2011-05-23 21:19 ` Ben Greear
2011-05-23 21:28 ` Luis R. Rodriguez
2011-05-23 21:38 ` Ben Greear
2011-05-23 21:42 ` Luis R. Rodriguez
2011-05-23 21:46 ` Luis R. Rodriguez
2011-05-23 21:59 ` Ben Greear
2011-05-23 22:15 ` Luis R. Rodriguez
2011-05-24 4:48 ` Ben Greear
2011-05-24 11:33 ` Luis R. Rodriguez
2011-05-24 13:00 ` Brian Prodoehl
2011-05-24 13:11 ` Luis R. Rodriguez
2011-05-24 13:18 ` Brian Prodoehl
2011-05-24 21:39 ` Luis R. Rodriguez
2011-05-24 14:06 ` Mohammed Shafi
2011-05-24 14:08 ` Mohammed Shafi
2011-05-24 15:05 ` Ben Greear
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=4DDAACF3.3050705@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=shafi.wireless@gmail.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).