From: Mihai Moldovan <ionic@ionic.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AR9380 + hostapd + HT over 802.11a
Date: Tue, 31 May 2011 20:29:32 +0200 [thread overview]
Message-ID: <4DE5338C.507@ionic.de> (raw)
In-Reply-To: <4DE52E1E.90903@candelatech.com>
* On 31.05.2011 08:06 PM, Ben Greear wrote:
> Probably your NIC is in regdomain 0x6a or similar.
Exactly, see the last message.
> If you see something like this in your logs that is the problem:
>
>
> 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)
Interestingly, I'm not seeing those messages, even when changing the
domain via iw set reg DE or sorta.
The only message I get is following:
[ 16.719918] cfg80211: Calling CRDA to update world regulatory domain
I installed crda just recently without rebooting, maybe that's the
cause. udev was restarted manually after installing crda, but who knows
what else magic is required. I'll power cycle the machine to see whether
I can get more information.
Oh, and enabling CONFIG_CFG80211_REG_DEBUG may not be the worst idea
either. %)
> You can over-ride this with a patch similar to this one:
> http://patches.aircrack-ng.org/ath9k_regdomain_override.patch
Thanks, I'll rather try this than blindly enabling all channels in ath's
regd.c
> Note that you may lose 'official' support by doing this, but as far
> as I can tell, as long as you use the correct domain with 'iw reg set'
> you will still be in regulatory compliance as it chooses the minimal
> set of features supported by the NIC and whatever 'iw reg set' does.
Chances are AP mode on 5Ghz haven't been tested with this card and the
channels are thus disabled, but I'll have a look nonetheless.
Thanks again. :)
Mihai
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6111 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20110531/c2fb1240/attachment-0001.bin
next prev parent reply other threads:[~2011-05-31 18:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 17:36 [ath9k-devel] AR9380 + hostapd + HT over 802.11a Mihai Moldovan
2011-05-31 17:56 ` Peter Stuge
2011-05-31 18:17 ` Mihai Moldovan
2011-05-31 18:06 ` Ben Greear
2011-05-31 18:29 ` Mihai Moldovan [this message]
2011-05-31 18:33 ` Ben Greear
2011-05-31 18:38 ` Mihai Moldovan
2011-05-31 18:39 ` Mihai Moldovan
2011-05-31 19:36 ` Mihai Moldovan
2011-05-31 19:48 ` Ben Greear
2011-05-31 20:00 ` Mihai Moldovan
2011-06-01 7:01 ` Mihai Moldovan
2011-06-01 14:31 ` Mihai Moldovan
2011-06-01 14:45 ` Mihai Moldovan
2011-06-01 17:53 ` Ben Greear
2011-06-01 18:37 ` Mihai Moldovan
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=4DE5338C.507@ionic.de \
--to=ionic@ionic.de \
--cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.