* [ath9k-devel] ath9k regulatory
@ 2009-01-27 2:20 Lars Hardy
2009-01-27 2:42 ` Luis R. Rodriguez
0 siblings, 1 reply; 9+ messages in thread
From: Lars Hardy @ 2009-01-27 2:20 UTC (permalink / raw)
To: ath9k-devel
Hi.
Im using a Athereos mini-pci card (AR5416-AC1A VL4668.1C). (in a mini
pci/pci adapter)
Its used with hostap as my AP.
After the resent regulatory domain changes, I cannot enable 802.11a
anymore.
So it seems that its the same issue, its the eeprom on the card/.?/
Here is my dmesg utput after modprobe / iw reg set NO:
cfg80211: Calling CRDA to update world regulatory domain
ath9k: 0.1
ath9k 0000:01:0a.0: PCI INT A -> Link[APC3] -> GSI 18 (level, low) -> IRQ 18
ath9k: Country alpha2 being used: 00
Regpair detected: 0x64
wmaster0 (ath9k): not using net_device_ops yet
phy0: Selected rate control algorithm 'ath9k_rate_control'
wlan0 (ath9k): not using net_device_ops yet
Registered led device: ath9k-phy0:radio
Registered led device: ath9k-phy0:assoc
Registered led device: ath9k-phy0:tx
Registered led device: ath9k-phy0:rx
phy0: Atheros AR5416 MAC/BB Rev:2 AR5133 RF Rev:81: mem=0xf8220000, irq=18
cfg80211: Calling CRDA for country: NO
ath9k 0000:01:0a.0: PCI INT A disabled
ath9k: Driver unloaded
cfg80211: Calling CRDA to update world all-purpose
ath9k: 0.1
ath9k 0000:01:0a.0: PCI INT A -> Link[APC3] -> GSI 18 (level, low) -> IRQ 18
ath9k: Country alpha2 being used: 00
Regpair detected: 0x64
wmaster0 (ath9k): not using net_device_ops yet
phy0: Selected rate control algorithm 'ath9k_rate_control'
wlan0 (ath9k): not using net_device_ops yet
Registered led device: ath9k-phy0:radio
Registered led device: ath9k-phy0:assoc
Registered led device: ath9k-phy0:tx
Registered led device: ath9k-phy0:rx
phy0: Atheros AR5416 MAC/BB Rev:2 AR5133 RF Rev:81: mem=0xf81c0000, irq=18
root at UbuntuRuter:/usr/src/wireless-testing# iw --debug reg set NO
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE
---------------------------
[HEADER] 16 octets
.nlmsg_len = 36
.nlmsg_type = 2 <ERROR>
.nlmsg_flags = 0 <>
.nlmsg_seq = 1233019334
.nlmsg_pid = 5516
[ERRORMSG] 20 octets
.error = 0 "Success"
[ORIGINAL MESSAGE] 16 octets
.nlmsg_len = 16
.nlmsg_type = 26 <0x1a>
.nlmsg_flags = 5 <REQUEST,ACK>
.nlmsg_seq = 1233019334
.nlmsg_pid = 5516
--------------------------- END NETLINK MESSAGE
---------------------------
root at UbuntuRuter:/usr/src/wireless-testing# iw list
Wiphy phy0
Band 1:
HT capabilities: 0x104e
* 20/40 MHz operation
* SM PS disabled
* 40 MHz short GI
* max A-MSDU len 3839
* DSSS/CCK 40 MHz
HT A-MPDU factor: 0x0003 (65535 bytes)
HT A-MPDU density: 0x0006 (8 usec)
HT MCS set: ff ff 00 00 00 00 00 00 00 00 00 00 01 00 00 00
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)
Bitrates:
* 1.0 Mbps
* 2.0 Mbps
* 5.5 Mbps
* 11.0 Mbps
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Band 2:
HT capabilities: 0x104e
* 20/40 MHz operation
* SM PS disabled
* 40 MHz short GI
* max A-MSDU len 3839
* DSSS/CCK 40 MHz
HT A-MPDU factor: 0x0003 (65535 bytes)
HT A-MPDU density: 0x0006 (8 usec)
HT MCS set: ff ff 00 00 00 00 00 00 00 00 00 00 01 00 00 00
Frequencies:
* 5180 MHz [36] (30.0 dBm) (passive scanning, no
IBSS)
* 5200 MHz [40] (30.0 dBm) (passive scanning, no
IBSS)
* 5220 MHz [44] (30.0 dBm) (passive scanning, no
IBSS)
* 5240 MHz [48] (30.0 dBm) (passive scanning, no
IBSS)
* 5260 MHz [52] (30.0 dBm) (passive scanning, no
IBSS, radar detection)
* 5280 MHz [56] (30.0 dBm) (passive scanning, no
IBSS, radar detection)
* 5300 MHz [60] (30.0 dBm) (passive scanning, no
IBSS, radar detection)
* 5320 MHz [64] (30.0 dBm) (passive scanning, no
IBSS, radar detection)
* 5500 MHz [100] (disabled)
* 5520 MHz [104] (disabled)
* 5540 MHz [108] (disabled)
* 5560 MHz [112] (disabled)
* 5580 MHz [116] (disabled)
* 5600 MHz [120] (disabled)
* 5620 MHz [124] (disabled)
* 5640 MHz [128] (disabled)
* 5660 MHz [132] (disabled)
* 5680 MHz [136] (disabled)
* 5700 MHz [140] (disabled)
* 5745 MHz [149] (30.0 dBm) (passive scanning,
no IBSS)
* 5765 MHz [153] (30.0 dBm) (passive scanning,
no IBSS)
* 5785 MHz [157] (30.0 dBm) (passive scanning,
no IBSS)
* 5805 MHz [161] (30.0 dBm) (passive scanning,
no IBSS)
* 5825 MHz [165] (30.0 dBm) (passive scanning,
no IBSS)
Bitrates:
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Supported interface modes:
* IBSS
* Station
* AP
* AP(VLAN)
* Monitor
root at UbuntuRuter:/usr/src/wireless-testing#
^ permalink raw reply [flat|nested] 9+ messages in thread* [ath9k-devel] ath9k regulatory
2009-01-27 2:20 [ath9k-devel] ath9k regulatory Lars Hardy
@ 2009-01-27 2:42 ` Luis R. Rodriguez
0 siblings, 0 replies; 9+ messages in thread
From: Luis R. Rodriguez @ 2009-01-27 2:42 UTC (permalink / raw)
To: ath9k-devel
On Mon, Jan 26, 2009 at 06:20:04PM -0800, Lars Hardy wrote:
> Hi.
> Im using a Athereos mini-pci card (AR5416-AC1A VL4668.1C). (in a mini
> pci/pci adapter)
> Its used with hostap as my AP.
>
> After the resent regulatory domain changes, I cannot enable 802.11a
> anymore.
I see 11A enabled, do you mean you cannot use AP mode in 5 GHz anymore?
> So it seems that its the same issue, its the eeprom on the card/.?/
>
> Here is my dmesg utput after modprobe / iw reg set NO:
>
> cfg80211: Calling CRDA to update world regulatory domain
> ath9k: 0.1
> ath9k 0000:01:0a.0: PCI INT A -> Link[APC3] -> GSI 18 (level, low) -> IRQ 18
> ath9k: Country alpha2 being used: 00
> Regpair detected: 0x64
I just revised your regulatory domain settings and they are correct.
> wmaster0 (ath9k): not using net_device_ops yet
> phy0: Selected rate control algorithm 'ath9k_rate_control'
> wlan0 (ath9k): not using net_device_ops yet
> Registered led device: ath9k-phy0:radio
> Registered led device: ath9k-phy0:assoc
> Registered led device: ath9k-phy0:tx
> Registered led device: ath9k-phy0:rx
> phy0: Atheros AR5416 MAC/BB Rev:2 AR5133 RF Rev:81: mem=0xf8220000, irq=18
> cfg80211: Calling CRDA for country: NO
> ath9k 0000:01:0a.0: PCI INT A disabled
> ath9k: Driver unloaded
> cfg80211: Calling CRDA to update world all-purpose
> ath9k: 0.1
> ath9k 0000:01:0a.0: PCI INT A -> Link[APC3] -> GSI 18 (level, low) -> IRQ 18
> ath9k: Country alpha2 being used: 00
> Regpair detected: 0x64
> wmaster0 (ath9k): not using net_device_ops yet
> phy0: Selected rate control algorithm 'ath9k_rate_control'
> wlan0 (ath9k): not using net_device_ops yet
> Registered led device: ath9k-phy0:radio
> Registered led device: ath9k-phy0:assoc
> Registered led device: ath9k-phy0:tx
> Registered led device: ath9k-phy0:rx
> phy0: Atheros AR5416 MAC/BB Rev:2 AR5133 RF Rev:81: mem=0xf81c0000, irq=18
>
> root at UbuntuRuter:/usr/src/wireless-testing# iw --debug reg set NO
> -- Debug: Received Message:
> -------------------------- BEGIN NETLINK MESSAGE
> ---------------------------
> [HEADER] 16 octets
> .nlmsg_len = 36
> .nlmsg_type = 2 <ERROR>
> .nlmsg_flags = 0 <>
> .nlmsg_seq = 1233019334
> .nlmsg_pid = 5516
> [ERRORMSG] 20 octets
> .error = 0 "Success"
> [ORIGINAL MESSAGE] 16 octets
> .nlmsg_len = 16
> .nlmsg_type = 26 <0x1a>
> .nlmsg_flags = 5 <REQUEST,ACK>
> .nlmsg_seq = 1233019334
> .nlmsg_pid = 5516
> --------------------------- END NETLINK MESSAGE
> ---------------------------
Note that for ath9k users _help_ compliance, not override it.
> root at UbuntuRuter:/usr/src/wireless-testing# iw list
> Wiphy phy0
> Band 1:
> HT capabilities: 0x104e
> * 20/40 MHz operation
> * SM PS disabled
> * 40 MHz short GI
> * max A-MSDU len 3839
> * DSSS/CCK 40 MHz
> HT A-MPDU factor: 0x0003 (65535 bytes)
> HT A-MPDU density: 0x0006 (8 usec)
> HT MCS set: ff ff 00 00 00 00 00 00 00 00 00 00 01 00 00 00
> 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)
> Bitrates:
> * 1.0 Mbps
> * 2.0 Mbps
> * 5.5 Mbps
> * 11.0 Mbps
> * 6.0 Mbps
> * 9.0 Mbps
> * 12.0 Mbps
> * 18.0 Mbps
> * 24.0 Mbps
> * 36.0 Mbps
> * 48.0 Mbps
> * 54.0 Mbps
> Band 2:
> HT capabilities: 0x104e
> * 20/40 MHz operation
> * SM PS disabled
> * 40 MHz short GI
> * max A-MSDU len 3839
> * DSSS/CCK 40 MHz
> HT A-MPDU factor: 0x0003 (65535 bytes)
> HT A-MPDU density: 0x0006 (8 usec)
> HT MCS set: ff ff 00 00 00 00 00 00 00 00 00 00 01 00 00 00
> Frequencies:
> * 5180 MHz [36] (30.0 dBm) (passive scanning, no
> IBSS)
> * 5200 MHz [40] (30.0 dBm) (passive scanning, no
> IBSS)
> * 5220 MHz [44] (30.0 dBm) (passive scanning, no
> IBSS)
> * 5240 MHz [48] (30.0 dBm) (passive scanning, no
> IBSS)
You should be able to use the above.
> * 5260 MHz [52] (30.0 dBm) (passive scanning, no
> IBSS, radar detection)
> * 5280 MHz [56] (30.0 dBm) (passive scanning, no
> IBSS, radar detection)
> * 5300 MHz [60] (30.0 dBm) (passive scanning, no
> IBSS, radar detection)
> * 5320 MHz [64] (30.0 dBm) (passive scanning, no
> IBSS, radar detection)
These require radar detection which is not yet implemented.
> * 5500 MHz [100] (disabled)
> * 5520 MHz [104] (disabled)
> * 5540 MHz [108] (disabled)
> * 5560 MHz [112] (disabled)
> * 5580 MHz [116] (disabled)
> * 5600 MHz [120] (disabled)
> * 5620 MHz [124] (disabled)
> * 5640 MHz [128] (disabled)
> * 5660 MHz [132] (disabled)
> * 5680 MHz [136] (disabled)
> * 5700 MHz [140] (disabled)
These are disabled.
> * 5745 MHz [149] (30.0 dBm) (passive scanning,
> no IBSS)
> * 5765 MHz [153] (30.0 dBm) (passive scanning,
> no IBSS)
> * 5785 MHz [157] (30.0 dBm) (passive scanning,
> no IBSS)
> * 5805 MHz [161] (30.0 dBm) (passive scanning,
> no IBSS)
> * 5825 MHz [165] (30.0 dBm) (passive scanning,
> no IBSS)
you should also be able to use the above channels as well.
If you are having issues with the above 5 GHz channels on AP mode it may be that
hostapd doesn't let you use channels with passive scan requirements, not
sure will have to check. Try using channel 40 for example, see how that goes.
Luis
^ permalink raw reply [flat|nested] 9+ messages in thread
* [ath9k-devel] ath9k regulatory
@ 2009-01-26 13:35 Zoltan Devai
2009-01-26 15:13 ` Luis R. Rodriguez
0 siblings, 1 reply; 9+ messages in thread
From: Zoltan Devai @ 2009-01-26 13:35 UTC (permalink / raw)
To: ath9k-devel
Hi,
I'm using a TP-Link TL-WN861N card. What could be the reason that channels
12 and 13 are
not allowed ?
Using compat-wireless 2009-01-25.
Relevant dmesg output:
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: US
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
(5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: DE
cfg80211: Regulatory domain changed to country: DE
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
(2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A, 2000 mBm)
(5150000 KHz - 5255000 KHz @ 40000 KHz), (N/A, 2301 mBm)
(5470000 KHz - 5650000 KHz @ 40000 KHz), (N/A, 3000 mBm)
ath9k: 0.1
PCI: enabling device 0000:00:02.0 (0140 -> 0142)
ath9k: 2MHz channel: 2412, channelFlags: 0x300e0
ath9k: 2MHz channel: 2417, channelFlags: 0x300e0
ath9k: 2MHz channel: 2422, channelFlags: 0x300e0
ath9k: 2MHz channel: 2427, channelFlags: 0x300e0
ath9k: 2MHz channel: 2432, channelFlags: 0x700e0
ath9k: 2MHz channel: 2437, channelFlags: 0x700e0
ath9k: 2MHz channel: 2442, channelFlags: 0x700e0
ath9k: 2MHz channel: 2447, channelFlags: 0x500e0
ath9k: 2MHz channel: 2452, channelFlags: 0x500e0
ath9k: 2MHz channel: 2457, channelFlags: 0x500e0
ath9k: 2MHz channel: 2462, channelFlags: 0x500e0
ath9k: Rate: 1Mbps, ratecode: 27
ath9k: Rate: 2Mbps, ratecode: 26
ath9k: Rate: 5Mbps, ratecode: 25
ath9k: Rate: 11Mbps, ratecode: 24
ath9k: Rate: 6Mbps, ratecode: 11
ath9k: Rate: 9Mbps, ratecode: 15
ath9k: Rate: 12Mbps, ratecode: 10
ath9k: Rate: 18Mbps, ratecode: 14
ath9k: Rate: 24Mbps, ratecode: 9
ath9k: Rate: 36Mbps, ratecode: 13
ath9k: Rate: 48Mbps, ratecode: 8
ath9k: Rate: 54Mbps, ratecode: 12
ath9k: Rate: 6Mbps, ratecode: 11
ath9k: Rate: 9Mbps, ratecode: 15
ath9k: Rate: 12Mbps, ratecode: 10
ath9k: Rate: 18Mbps, ratecode: 14
ath9k: Rate: 24Mbps, ratecode: 9
ath9k: Rate: 36Mbps, ratecode: 13
ath9k: Rate: 48Mbps, ratecode: 8
ath9k: Rate: 54Mbps, ratecode: 12
ath9k: tx DMA: 512 buffers 1 desc/buf
ath9k: tx DMA map: ffc08000 (73728) -> 1f80000 (73728)
ath9k: beacon DMA: 1 buffers 1 desc/buf
ath9k: beacon DMA map: ffc1a000 (144) -> 1eb3000 (144)
ath9k: cachelsz 32 rxbufsize 3872
ath9k: rx DMA: 512 buffers 1 desc/buf
ath9k: rx DMA map: ffc1b000 (73728) -> 1fa0000 (73728)
phy0: Selected rate control algorithm 'ath9k_rate_control'
Registered led device: ath9k-phy0:radio
Registered led device: ath9k-phy0:assoc
Registered led device: ath9k-phy0:tx
Registered led device: ath9k-phy0:rx
phy0: Atheros AR5416 MAC/BB Rev:2 AR2122 RF Rev:81: mem=0xc2900000, irq=27
Cheers,
Zoltan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20090126/974e1d3d/attachment.htm
^ permalink raw reply [flat|nested] 9+ messages in thread* [ath9k-devel] ath9k regulatory
2009-01-26 13:35 Zoltan Devai
@ 2009-01-26 15:13 ` Luis R. Rodriguez
2009-01-26 15:15 ` Luis R. Rodriguez
2009-01-26 18:08 ` Zoltan Devai
0 siblings, 2 replies; 9+ messages in thread
From: Luis R. Rodriguez @ 2009-01-26 15:13 UTC (permalink / raw)
To: ath9k-devel
On Mon, Jan 26, 2009 at 05:35:13AM -0800, Zoltan Devai wrote:
> Hi,
>
> I'm using a TP-Link TL-WN861N card. What could be the reason that channels 12 and 13 are
> not allowed ?
> Using compat-wireless 2009-01-25.
> Relevant dmesg output:
>
> cfg80211: Using static regulatory domain info
> cfg80211: Regulatory domain: US
> (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
> (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
> cfg80211: Calling CRDA for country: DE
> cfg80211: Regulatory domain changed to country: DE
> (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> (2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A, 2000 mBm)
> (5150000 KHz - 5255000 KHz @ 40000 KHz), (N/A, 2301 mBm)
> (5470000 KHz - 5650000 KHz @ 40000 KHz), (N/A, 3000 mBm)
> ath9k: 0.1
> PCI: enabling device 0000:00:02.0 (0140 -> 0142)
> ath9k: 2MHz channel: 2412, channelFlags: 0x300e0
> ath9k: 2MHz channel: 2417, channelFlags: 0x300e0
> ath9k: 2MHz channel: 2422, channelFlags: 0x300e0
> ath9k: 2MHz channel: 2427, channelFlags: 0x300e0
> ath9k: 2MHz channel: 2432, channelFlags: 0x700e0
> ath9k: 2MHz channel: 2437, channelFlags: 0x700e0
> ath9k: 2MHz channel: 2442, channelFlags: 0x700e0
> ath9k: 2MHz channel: 2447, channelFlags: 0x500e0
> ath9k: 2MHz channel: 2452, channelFlags: 0x500e0
> ath9k: 2MHz channel: 2457, channelFlags: 0x500e0
> ath9k: 2MHz channel: 2462, channelFlags: 0x500e0
> ath9k: Rate: 1Mbps, ratecode: 27
> ath9k: Rate: 2Mbps, ratecode: 26
> ath9k: Rate: 5Mbps, ratecode: 25
> ath9k: Rate: 11Mbps, ratecode: 24
> ath9k: Rate: 6Mbps, ratecode: 11
> ath9k: Rate: 9Mbps, ratecode: 15
> ath9k: Rate: 12Mbps, ratecode: 10
> ath9k: Rate: 18Mbps, ratecode: 14
> ath9k: Rate: 24Mbps, ratecode: 9
> ath9k: Rate: 36Mbps, ratecode: 13
> ath9k: Rate: 48Mbps, ratecode: 8
> ath9k: Rate: 54Mbps, ratecode: 12
> ath9k: Rate: 6Mbps, ratecode: 11
> ath9k: Rate: 9Mbps, ratecode: 15
> ath9k: Rate: 12Mbps, ratecode: 10
> ath9k: Rate: 18Mbps, ratecode: 14
> ath9k: Rate: 24Mbps, ratecode: 9
> ath9k: Rate: 36Mbps, ratecode: 13
> ath9k: Rate: 48Mbps, ratecode: 8
> ath9k: Rate: 54Mbps, ratecode: 12
> ath9k: tx DMA: 512 buffers 1 desc/buf
> ath9k: tx DMA map: ffc08000 (73728) -> 1f80000 (73728)
> ath9k: beacon DMA: 1 buffers 1 desc/buf
> ath9k: beacon DMA map: ffc1a000 (144) -> 1eb3000 (144)
> ath9k: cachelsz 32 rxbufsize 3872
> ath9k: rx DMA: 512 buffers 1 desc/buf
> ath9k: rx DMA map: ffc1b000 (73728) -> 1fa0000 (73728)
> phy0: Selected rate control algorithm 'ath9k_rate_control'
> Registered led device: ath9k-phy0:radio
> Registered led device: ath9k-phy0:assoc
> Registered led device: ath9k-phy0:tx
> Registered led device: ath9k-phy0:rx
> phy0: Atheros AR5416 MAC/BB Rev:2 AR2122 RF Rev:81: mem=0xc2900000, irq=27
I take it the second DE regulatory request was yours? Anyway -- since
I am not seeing any print out during ath9k's initialization on regulatory
it would seem your card uses one of the built-in regulatory domains.
You can use iw to see your allowed channels:
iw list
If your regulatory domain does not allow for it you will not be able to use that
channel.
To confirm you can recompile ath9k with debugging enabled with the patch
attached applied. Then load ath9k as follows:
insmod drivers/net/wireless/ath9k/ath9k.ko debug=0x00000080
0x00000080 is ATH_DBG_REGULATORY so this will show all regulatory debug prints.
Luis
From: Luis R. Rodriguez <lrodriguez@atheros.com>
Date: Mon, 26 Jan 2009 06:41:48 -0800
Subject: [PATCH] ath9k: fix debug print on regd
With debugging enabled and with ATH_DBG_REGULATORY
selected we wouldn't get the full print out of one line,
reason is we used "," instead of nothing to separate two
lines.
Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
---
drivers/net/wireless/ath9k/regd.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/wireless/ath9k/regd.c b/drivers/net/wireless/ath9k/regd.c
index 90f0c98..ec88f78 100644
--- a/drivers/net/wireless/ath9k/regd.c
+++ b/drivers/net/wireless/ath9k/regd.c
@@ -447,7 +447,7 @@ int ath9k_regd_init(struct ath_hal *ah)
}
DPRINTF(ah->ah_sc, ATH_DBG_REGULATORY,
- "Country alpha2 being used: %c%c\n",
+ "Country alpha2 being used: %c%c\n"
"Regpair detected: 0x%0x\n",
ah->alpha2[0], ah->alpha2[1],
ah->regpair->regDmnEnum);
--
1.5.6.4
^ permalink raw reply related [flat|nested] 9+ messages in thread
* [ath9k-devel] ath9k regulatory
2009-01-26 15:13 ` Luis R. Rodriguez
@ 2009-01-26 15:15 ` Luis R. Rodriguez
2009-01-26 18:08 ` Zoltan Devai
1 sibling, 0 replies; 9+ messages in thread
From: Luis R. Rodriguez @ 2009-01-26 15:15 UTC (permalink / raw)
To: ath9k-devel
On Mon, Jan 26, 2009 at 07:13:02AM -0800, Luis Rodriguez wrote:
> To confirm you can recompile ath9k with debugging enabled
you do this in compat-wireless by editing config.mk and adding a line with:
CONFIG_ATH9K_DEBUG=y
Then recompile.
Luis
^ permalink raw reply [flat|nested] 9+ messages in thread
* [ath9k-devel] ath9k regulatory
2009-01-26 15:13 ` Luis R. Rodriguez
2009-01-26 15:15 ` Luis R. Rodriguez
@ 2009-01-26 18:08 ` Zoltan Devai
2009-01-26 18:38 ` Luis R. Rodriguez
1 sibling, 1 reply; 9+ messages in thread
From: Zoltan Devai @ 2009-01-26 18:08 UTC (permalink / raw)
To: ath9k-devel
2009/1/26 Luis R. Rodriguez <lrodriguez@atheros.com>
> On Mon, Jan 26, 2009 at 05:35:13AM -0800, Zoltan Devai wrote:
> > I'm using a TP-Link TL-WN861N card. What could be the reason that
> channels 12 and 13 are
> > not allowed ?
> > Using compat-wireless 2009-01-25.
>
<snip>
I take it the second DE regulatory request was yours?
That's coming from loading cfg80211 with ieee80211_regdom=DE.
> If your regulatory domain does not allow for it you will not be able to use
> that
> channel.
I'm a bit confused now about who tells what the regulatory domain is.
Does the (EEPROM on the) card override the user setting ?
Is there a way to give the users preference priority ?
> To confirm you can recompile ath9k with debugging enabled with the patch
> attached applied.
>
Gives me this:
# modprobe ath9k debug=0x00000080
ath9k: 0.1
PCI: enabling device 0000:00:02.0 (0140 -> 0142)
ath9k: Country alpha2 being used: US
Regpair detected: 0x3a
phy0: Selected rate control algorithm 'ath9k_rate_control'
cfg80211: Calling CRDA for country: US
Registered led device: ath9k-phy0:radio
Registered led device: ath9k-phy0:assoc
Registered led device: ath9k-phy0:tx
Registered led device: ath9k-phy0:rx
phy0: Atheros AR5416 MAC/BB Rev:2 AR2122 RF Rev:81: mem=0xc2900000, irq=27
cfg80211: Regulatory domain changed to country: US
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
(5170000 KHz - 5250000 KHz @ 40000 KHz), (600 mBi, 1700 mBm)
(5250000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
(5490000 KHz - 5710000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
If I do:
# iw reg set DE
cfg80211: Calling CRDA for country: DE
command failed: No such file or directory (-2)
cfg80211: Regulatory domain changed to country: DE
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
(2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A, 2000 mBm)
(5150000 KHz - 5255000 KHz @ 40000 KHz), (N/A, 2301 mBm)
(5470000 KHz - 5650000 KHz @ 40000 KHz), (N/A, 3000 mBm)
But iw list still is:
# iw list
Wiphy phy0
Band 1:
HT capabilities: 0x104e
* 20/40 MHz operation
* SM PS disabled
* 40 MHz short GI
* max A-MSDU len 3839
* DSSS/CCK 40 MHz
HT A-MPDU factor: 0x0003 (65535 bytes)
HT A-MPDU density: 0x0006 (8 usec)
HT MCS set: ff ff 00 00 00 00 00 00 00 00 00 00 01 00 00 00
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)
Thanks,
Zoltan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20090126/d39cc26f/attachment.htm
^ permalink raw reply [flat|nested] 9+ messages in thread* [ath9k-devel] ath9k regulatory
2009-01-26 18:08 ` Zoltan Devai
@ 2009-01-26 18:38 ` Luis R. Rodriguez
2009-01-26 23:37 ` Zoltan Devai
0 siblings, 1 reply; 9+ messages in thread
From: Luis R. Rodriguez @ 2009-01-26 18:38 UTC (permalink / raw)
To: ath9k-devel
On Mon, Jan 26, 2009 at 10:08:55AM -0800, Zoltan Devai wrote:
> 2009/1/26 Luis R. Rodriguez <lrodriguez at atheros.com<mailto:lrodriguez@atheros.com>>
> On Mon, Jan 26, 2009 at 05:35:13AM -0800, Zoltan Devai wrote:
> > I'm using a TP-Link TL-WN861N card. What could be the reason that channels 12 and 13 are
> > not allowed ?
> > Using compat-wireless 2009-01-25.
> <snip>
>
> I take it the second DE regulatory request was yours?
> That's coming from loading cfg80211 with ieee80211_regdom=DE.
ieee80211_regdom module parameter should be used with the only 3
old regulatory domains built into the kernel:
EU
US
JP
This is only available if you have the old regulatory option is enabled
in the kernel:
CONFIG_WIRELESS_OLD_REGULATORY=y
This will hopefully be removed soon (2.6.31), it provides three
regulatory domains statically into the kernel. The fact that CRDA is
called even though you selected "DE" is by chance I had forgotten
to make it only work for the 3 above. Regardless this is OK -- it is
calling CRDA for the DE regulatory domain to help you enhance your
regulatory settings.
> If your regulatory domain does not allow for it you will not be able to use that
> channel.
> I'm a bit confused now about who tells what the regulatory domain is.
Please have a read here:
http://wireless.kernel.org/en/developers/Regulatory
Let me try to summarize it for your case though. If the no one knows where we
are we will defualt to the world regulatory domain (unless OLD_REG is enabled
which defaults to the US), if a driver knows the regulatory domain it
should abide by then the wireless core is now switched to that regulatory
domain. If a user knows changes country and the card also has a programmed
regulatory domain the card will operate under the intersection of both.
> Does the (EEPROM on the) card override the user setting ?
It varies by driver, on some drivers, like rt2x00 drivers the documentation
provided indicates and recommends that the regulatory domain not be considered
from the EEPROM so alternatives are to be used. In some other cases the EEPROM
information must always be respected as is the case with Intel and Atheros'
drivers.
> Is there a way to give the users preference priority ?
The user can always specifify the regulatory domain that is the default. In
ath9k's case the EEPROM is always respected though.
> To confirm you can recompile ath9k with debugging enabled with the patch
> attached applied.
> Gives me this:
> # modprobe ath9k debug=0x00000080
> ath9k: 0.1
> PCI: enabling device 0000:00:02.0 (0140 -> 0142)
> ath9k: Country alpha2 being used: US
> Regpair detected: 0x3a
> phy0: Selected rate control algorithm 'ath9k_rate_control'
> cfg80211: Calling CRDA for country: US
> Registered led device: ath9k-phy0:radio
> Registered led device: ath9k-phy0:assoc
> Registered led device: ath9k-phy0:tx
> Registered led device: ath9k-phy0:rx
> phy0: Atheros AR5416 MAC/BB Rev:2 AR2122 RF Rev:81: mem=0xc2900000, irq=27
> cfg80211: Regulatory domain changed to country: US
> (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
> (5170000 KHz - 5250000 KHz @ 40000 KHz), (600 mBi, 1700 mBm)
> (5250000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
> (5490000 KHz - 5710000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
> (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
>
> If I do:
> # iw reg set DE
> cfg80211: Calling CRDA for country: DE
> command failed: No such file or directory (-2)
> cfg80211: Regulatory domain changed to country: DE
> (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> (2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A, 2000 mBm)
> (5150000 KHz - 5255000 KHz @ 40000 KHz), (N/A, 2301 mBm)
> (5470000 KHz - 5650000 KHz @ 40000 KHz), (N/A, 3000 mBm)
>
> But iw list still is:
> # iw list
> Wiphy phy0
> Band 1:
> HT capabilities: 0x104e
> * 20/40 MHz operation
> * SM PS disabled
> * 40 MHz short GI
> * max A-MSDU len 3839
> * DSSS/CCK 40 MHz
> HT A-MPDU factor: 0x0003 (65535 bytes)
> HT A-MPDU density: 0x0006 (8 usec)
> HT MCS set: ff ff 00 00 00 00 00 00 00 00 00 00 01 00 00 00
> 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)
Yeap, this is by design -- your card has the "US" regulatory domain
and as such has those channels are disabled and you cannot enable them.
Reason for this is the device was not calibrated to operate on those
channels and as such proper behaviour cannot be guaranteed. For cards
where proper behaviour can be guaranteed you will be able to enable
those channels like on the b43 driver.
Luis
^ permalink raw reply [flat|nested] 9+ messages in thread
* [ath9k-devel] ath9k regulatory
2009-01-26 18:38 ` Luis R. Rodriguez
@ 2009-01-26 23:37 ` Zoltan Devai
2009-01-26 23:53 ` Luis R. Rodriguez
0 siblings, 1 reply; 9+ messages in thread
From: Zoltan Devai @ 2009-01-26 23:37 UTC (permalink / raw)
To: ath9k-devel
Whoops, here's the CC for the list.
2009/1/26 Luis R. Rodriguez <lrodriguez@atheros.com>
> On Mon, Jan 26, 2009 at 10:08:55AM -0800, Zoltan Devai wrote:
> > 2009/1/26 Luis R. Rodriguez <lrodriguez at atheros.com<mailto:lrodriguez@atheros.com>>
> > On Mon, Jan 26, 2009 at 05:35:13AM -0800, Zoltan Devai wrote:
> > > I'm using a TP-Link TL-WN861N card. What could be the reason that channels 12 and 13 are
> > > not allowed ?
> > > Using compat-wireless 2009-01-25.
Thanks for the explanation on the regulatory.
> > Is there a way to give the users preference priority ?
>
> The user can always specifify the regulatory domain that is the default. In
> ath9k's case the EEPROM is always respected though.
> > * 2462 MHz [11] (20.0 dBm)
> > * 2467 MHz [12] (disabled)
> > * 2472 MHz [13] (disabled)
> > * 2484 MHz [14] (disabled)
>
> Yeap, this is by design -- your card has the "US" regulatory domain
> and as such has those channels are disabled and you cannot enable them.
> Reason for this is the device was not calibrated to operate on those
> channels and as such proper behaviour cannot be guaranteed. For cards
> where proper behaviour can be guaranteed you will be able to enable
> those channels like on the b43 driver.
The EEP_REG_0 is actually 0x0000 on my card and the driver defaults US for that.
Is that a valid value to put in the EEPROM ? Or was just the card
manufacturer sloppy and it rather means "don't care", in which case the driver
should enable all channels ?
Cheers,
Zoltan
^ permalink raw reply [flat|nested] 9+ messages in thread
* [ath9k-devel] ath9k regulatory
2009-01-26 23:37 ` Zoltan Devai
@ 2009-01-26 23:53 ` Luis R. Rodriguez
0 siblings, 0 replies; 9+ messages in thread
From: Luis R. Rodriguez @ 2009-01-26 23:53 UTC (permalink / raw)
To: ath9k-devel
On Mon, Jan 26, 2009 at 3:37 PM, Zoltan Devai <zdevai@gmail.com> wrote:
> Whoops, here's the CC for the list.
>
> 2009/1/26 Luis R. Rodriguez <lrodriguez@atheros.com>
>> On Mon, Jan 26, 2009 at 10:08:55AM -0800, Zoltan Devai wrote:
>> > 2009/1/26 Luis R. Rodriguez <lrodriguez at atheros.com<mailto:lrodriguez@atheros.com>>
>> > On Mon, Jan 26, 2009 at 05:35:13AM -0800, Zoltan Devai wrote:
>> > > I'm using a TP-Link TL-WN861N card. What could be the reason that channels 12 and 13 are
>> > > not allowed ?
>> > > Using compat-wireless 2009-01-25.
>
> Thanks for the explanation on the regulatory.
>
>> > Is there a way to give the users preference priority ?
>>
>> The user can always specifify the regulatory domain that is the default. In
>> ath9k's case the EEPROM is always respected though.
>
>> > * 2462 MHz [11] (20.0 dBm)
>> > * 2467 MHz [12] (disabled)
>> > * 2472 MHz [13] (disabled)
>> > * 2484 MHz [14] (disabled)
>>
>> Yeap, this is by design -- your card has the "US" regulatory domain
>> and as such has those channels are disabled and you cannot enable them.
>> Reason for this is the device was not calibrated to operate on those
>> channels and as such proper behaviour cannot be guaranteed. For cards
>> where proper behaviour can be guaranteed you will be able to enable
>> those channels like on the b43 driver.
>
> The EEP_REG_0 is actually 0x0000 on my card and the driver defaults US for that.
> Is that a valid value to put in the EEPROM ?
As per this implementation -- yes, it seems that is the case. I am
however not sure how common this is. I'll try to find out.
> Or was just the card
> manufacturer sloppy and it rather means "don't care", in which case the driver
> should enable all channels ?
It really depends on who manufactured the card and their decision on
how to support the device and how the vendor documents this for them.
The driver just follows this architectural design. That is why
regulatory is such a pain in the ass -- vendor involvement is key.
Luis
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2009-01-27 2:42 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-01-27 2:20 [ath9k-devel] ath9k regulatory Lars Hardy
2009-01-27 2:42 ` Luis R. Rodriguez
-- strict thread matches above, loose matches on Subject: below --
2009-01-26 13:35 Zoltan Devai
2009-01-26 15:13 ` Luis R. Rodriguez
2009-01-26 15:15 ` Luis R. Rodriguez
2009-01-26 18:08 ` Zoltan Devai
2009-01-26 18:38 ` Luis R. Rodriguez
2009-01-26 23:37 ` Zoltan Devai
2009-01-26 23:53 ` Luis R. Rodriguez
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.