From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luis R. Rodriguez Date: Mon, 26 Jan 2009 18:42:11 -0800 Subject: [ath9k-devel] ath9k regulatory In-Reply-To: <497E6F54.60500@gmail.com> References: <497E6F54.60500@gmail.com> Message-ID: <20090127024211.GF19242@tesla> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org 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 > .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 > .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