Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Oleksij Rempel <linux@rempel-privat.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AR9280 AP mode - 5GHz band
Date: Tue, 22 Jul 2014 17:56:38 +0200	[thread overview]
Message-ID: <53CE89B6.4090905@rempel-privat.de> (raw)
In-Reply-To: <5FDAC1A6-0F70-42C4-93D1-8EBEC89DED24@gmail.com>

Thank you for your feedback! :)

Am 22.07.2014 14:38, schrieb Hosam Hittini:
> I could get it to work by compiling backports-3.15.1-1.tar.xz package,
> there is no need to recompile a whole kernel
> I first extracted the source files, then used ?make defconfig-ath9k?
> Then, thanks to your suggestions I used ?make menuconfig? to changes
> some settings, the following are the ones I marked
>     cfg80211 regulatory debugging
>     cfg80211 certification onus
>     use statically compiled regulatory rules database
>     cfg80211 wireless extensions compatibility
>     Atheros wireless debugging
>     Atheros dynamic user regulatory hints
>     Atheros dynamic user regulatory testing
>     Atheros ath9k debugging
>     Detailed station statistics
>     Atheros DFS support for certified platforms
>     Atheros ath9k TX99 testing support
>     Atheros ath9k rfkill support
>     Atheros HTC based wireless cards support
>     Atheros ath9k_htc debugging
> My db.txt is consisted of the following, it should be copied to
>  backports-3.15.1-1/net/wireless/
> country 00:
> (2402 - 2482 @ 20), (3, 20)
> (5170 - 5250 @ 40), (3, 20)
> (5250 - 5330 @ 40), (3, 20)
> (5490 - 5710 @ 40), (3, 20)
> (5735 - 5835 @ 40), (3, 20)
> After that I used ?make? and ?make install? and it works like a charm
> However, this caused a conflict with my RTL8187B driver, I needed to
> recompile both drivers together to fix that, ( I used ?make
> defconfig-wifi? instead of ?make defconfig-ath9k?)
> I felt that my db.txt did not work but that doesn?t matter, because the
> 5GHz channels are opened in most countries now
> I used ?iw reg set AU? and ?iw reg get? to check that
> 
> Regards,
> Eng. Hosam Hittini
> 
> On Jul 15, 2014, at 10:33 AM, Oleksij Rempel <linux@rempel-privat.de
> <mailto:linux@rempel-privat.de>> wrote:
> 
>> Hi Hosam,
>>
>> currently no one can give you good answer on it. If you can do some
>> research on this issue and give some feedback or even fix it, it will be
>> awesome.
>>
>> Am 12.07.2014 00:21, schrieb Hosam Hittini:
>>> I managed to change the CRDA settings by getting backports
>>> package
>>> http://www.kernel.org/pub/linux/kernel/projects/backports/stable/v3.15.1/,
>>> modifying the db.txt and forcing the driver to follow my db.txt
>>> This how my db.txt looks like
>>> country 00:
>>> (2402 - 2482 @ 20), (N/A, 20)
>>> (5170 - 5250 @ 40), (N/A, 20)
>>> (5250 - 5330 @ 40), (N/A, 20)
>>> (5490 - 5710 @ 40), (N/A, 20)
>>> (5735 - 5835 @ 40), (N/A, 20)Regards,
>>> However, when I try to configure the AP on a 5GHz channel I still get
>>> the same error
>>> wlan0: IEEE 802.11 Configured channel (36) not found from the channel
>>> list of current mode (2) IEEE 802.11a
>>> There is one more strange thing, the output of iw reg get and iw list
>>> have a conflict
>>> hosam at SanDisk-16:~$ iw reg get
>>> country 00:
>>> (2402 - 2482 @ 20), (N/A, 20)
>>> (5170 - 5250 @ 40), (N/A, 20)
>>> (5250 - 5330 @ 40), (N/A, 20)
>>> (5490 - 5710 @ 40), (N/A, 20)
>>> (5735 - 5835 @ 40), (N/A, 20)
>>> iw list
>>> 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] (30.0 dBm) (passive scanning, no IBSS, radar detection)
>>> * 5520 MHz [104] (30.0 dBm) (passive scanning, no IBSS, radar detection)
>>> * 5540 MHz [108] (30.0 dBm) (passive scanning, no IBSS, radar detection)
>>> * 5560 MHz [112] (30.0 dBm) (passive scanning, no IBSS, radar detection)
>>> * 5580 MHz [116] (30.0 dBm) (passive scanning, no IBSS, radar detection)
>>> * 5600 MHz [120] (30.0 dBm) (passive scanning, no IBSS, radar detection)
>>> * 5620 MHz [124] (30.0 dBm) (passive scanning, no IBSS, radar detection)
>>> * 5640 MHz [128] (30.0 dBm) (passive scanning, no IBSS, radar detection)
>>> * 5660 MHz [132] (30.0 dBm) (passive scanning, no IBSS, radar detection)
>>> * 5680 MHz [136] (30.0 dBm) (passive scanning, no IBSS, radar detection)
>>> * 5700 MHz [140] (30.0 dBm) (passive scanning, no IBSS, radar detection)
>>> * 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)
>>>
>>> Regards,
>>> Eng. Hosam Hittini
>>>
>>> On Jul 9, 2014, at 12:50 PM, Oleksij Rempel <linux@rempel-privat.de
>>> <mailto:linux@rempel-privat.de>
>>> <mailto:linux@rempel-privat.de>> wrote:
>>>
>>>> Am 09.07.2014 07:47, schrieb Hosam Hittini:
>>>>> I?m afraid you are right
>>>>> I have the following modules running
>>>>> ath9k_htc              85879  0 
>>>>> ath9k_common           13619  1 ath9k_htc
>>>>> ath9k_hw              429197  2 ath9k_common,ath9k_htc
>>>>> ath                    19187  3 ath9k_common,ath9k_htc,ath9k_hw
>>>>> mac80211              513247  2 rtl8187,ath9k_htc
>>>>> cfg80211              401436  4 ath,mac80211,rtl8187,ath9k_htc
>>>>> Does recompiling the kernel work?
>>>>> And if it works, do I need to install certain patch before recompiling?
>>>>
>>>> Why do you wont to recompile the kernel? If you won't to make work ath9k
>>>> driver with your usb adapter, then it will not work.
>>>>
>>>>
>>>>> Regards,
>>>>> Eng. Hosam Hittini
>>>>>
>>>>> On Jul 9, 2014, at 8:41 AM, Oleksij Rempel <linux@rempel-privat.de
>>>>> <mailto:linux@rempel-privat.de>
>>>>> <mailto:linux@rempel-privat.de>
>>>>> <mailto:linux@rempel-privat.de>> wrote:
>>>>>
>>>>>> Am 08.07.2014 13:37, schrieb Janusz Dziedzic:
>>>>>>> On 8 July 2014 08:20, Hosam Hittini <h.hittini@gmail.com
>>>>>>> <mailto:h.hittini@gmail.com>
>>>>>>> <mailto:h.hittini@gmail.com>
>>>>>>> <mailto:h.hittini@gmail.com>> wrote:
>>>>>>>> Hello there,
>>>>>>>>
>>>>>>>> I have this dual band wireless adapter
>>>>>>>> https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-dual-band-usb-adapter-gnu-linux-tpe-nusbdb
>>>>>>>> and it uses AR9280 chipset for the 5GHz communication
>>>>>>>> It?s using ath9k driver; I have Ubuntu 13.10 running 3.11 kernel
>>>>>>>> and the
>>>>>>>> adapter worked out of the box
>>>>>>>> I?m using hostapd to configure the adapter as a software AP
>>>>>>>> When I tried to configure the adapter as an AP on the 2.4GHz
>>>>>>>> channels it
>>>>>>>> worked fine
>>>>>>>> When tried the 5GHz channels it gives me the following error
>>>>>>>>
>>>>>>>> channel [1] (40) is disabled for use in AP mode, flags: 0x77
>>>>>>>> wlan1: IEEE 802.11 Configured channel (40) not found from the
>>>>>>>> channel list
>>>>>>>> of current mode (2) IEEE 802.11a
>>>>>>>> wlan1: IEEE 802.11 Hardware does not support configured channel
>>>>>>>>
>>>>>>>> In addition, iw list command shows that the 5GHz channels have the
>>>>>>>> ?passive
>>>>>>>> scanning? and ?no IBSS? flags
>>>>>>>> I can associate with an AP on the 5GHz though
>>>>>>>> How to solve that
>>>>>>>
>>>>>>> You can try this - works fine with my 9280
>>>>>>> Compile your kernel with options:
>>>>>>> CONFIG_ATH_REG_DYNAMIC_USER_REG_HINTS=y
>>>>>>> CONFIG_ATH_REG_DYNAMIC_USER_CERT_TESTING=y
>>>>>>>
>>>>>>> Next set country, eg. iw reg set US
>>>>>>> And check channels available (iw list). You should get 36-48 and
>>>>>>> 149-165 available.
>>>>>>> If available, next you can check hostapd.
>>>>>>>
>>>>>>> DFS channels should works as well when you enable DFS:
>>>>>>> CONFIG_ATH9K_DFS_CERTIFIED required
>>>>>>
>>>>>> He is not using ath9k driver. It is about ath9k_htc :)
>>>>>>
>>>>>>
>>>>>> -- 
>>>>>> Regards,
>>>>>> Oleksij
>>>>>
>>>>
>>>>
>>>> -- 
>>>> Regards,
>>>> Oleksij
>>>
>>
>>
>> -- 
>> Regards,
>> Oleksij
> 


-- 
Regards,
Oleksij

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 278 bytes
Desc: OpenPGP digital signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20140722/d149bb01/attachment.pgp 

  reply	other threads:[~2014-07-22 15:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08  6:20 [ath9k-devel] AR9280 AP mode - 5GHz band Hosam Hittini
2014-07-08  7:35 ` Oleksij Rempel
2014-07-08  7:48   ` Hosam Hittini
2014-07-08  7:55     ` Oleksij Rempel
2014-07-08 11:37 ` Janusz Dziedzic
2014-07-09  4:41   ` Oleksij Rempel
2014-07-09  5:47     ` Hosam Hittini
2014-07-09  8:50       ` Oleksij Rempel
2014-07-09  9:01         ` Hosam Hittini
2014-07-11 22:21         ` Hosam Hittini
2014-07-15  6:33           ` Oleksij Rempel
2014-07-22 12:38             ` Hosam Hittini
2014-07-22 15:56               ` Oleksij Rempel [this message]
2014-07-14  7:07   ` Hosam Hittini

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=53CE89B6.4090905@rempel-privat.de \
    --to=linux@rempel-privat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox