Hi Bruno,
* On 16.08.2013 05:59 PM, Bruno Alexandre Taraio dos Santos Antunes wrote:
Could you or anybody in the mailing list please tell me what are the steps to
enable DFS.
DFS has to be enabled on the kernel side and it's dependent on an option called
CFG80211_CERTIFICATION_ONUS which is
* On 19.08.2013 05:25 PM, Adrian Chadd wrote:
CERTIFICATION_ONUS means it's up to me to go and get this device actually
certified and yes I will and have done this.
That exactly what I meant. Thanks for clarifying that. :)
I figure OpenWrt won't support options like this officially as well, as
Hi,
I booted up a brand new 3.10.1 kernel with DFS support enabled and obviously in
use.
This AR9280 card is in AP mode on channel 40 (5GHz) with 802.11n/HT on (HT40-).
However, this boosts up latency to 50 - 90ms on average in pretty much idle mode
(100KB/s traffic), spiking up to several
* On 24.06.2013 04:17 PM, Adam Allred wrote:
Well, confoundable. I have recompiled both cfg80211 and mac80211 with
the DEBUGFS flags set to yes, and I'm still not seeing anything under
the phy0 directory.
I do. Albeit with a WPEA-127NI card.
Check:
CONFIG_CFG80211_DEBUGFS=y
* On 24.06.2013 05:31 PM, Adam Allred wrote:
I've checked all of those. They are all set.
I do. Albeit with a WPEA-127NI card.
Scratch that, it's WPEA-127N exactly. AR9380. Very same card you have. ;)
What about...
CONFIG_ATH_DEBUG
And just for good measure:
CONFIG_MAC80211_DEBUG_MENU
Hi all,
I am still experiencing huge problems with my ath9k cards (AR9380 and AR5416) in
master mode.
Both devices + some e1000e card are bridged together, with hostapd acting as a
WPA-PSK authenticator.
However, no station is able to successfully authenticate and create a
connection.
hostapd
* On 03.08.2012 05:24 AM, Seth Baker wrote:
Yes it makes AP mode not work when EEPROM and crda restrictions
overlap differently. Can you direct me where to get the patch?
I can only provide you with one for 3.2, latter versions may require editing
(though probably not much.) But I'll assume you
Hi Seth,
it is both, really.
Both cards likely have a world roaming regulatory roaming set in their EEPROM
(check dmesg...). On top of that information, restrictions for your current
country are added.
You cannot bypass the card's EEPROM value without hacking the kernel source
(well... with
Hi
I guess I see the problem on 3.2 (and compat-wireless) with two Atheros
cards - AR9380 and AR5416.
Debugging is impossible without special hardware, too, because there is
no panic/kernel output whatsoever.
At some point, the box hangs itself completely. A soft reset won't work,
I have to shut
Hm, shouldn't the kernel actually detect something like this (i.e.,
detect when it's running in kernel mode for too long and not letting
userspace processes run)?
* On 12.01.2012 09:51 PM, Adrian Chadd wrote:
Remember, kim though it was a hang until we enabled some ath9k
debugging. We then
At least I've seen messages like this when my kernel handled disk IO
(and actually the filesystem was buggy) - it echo'd a warning message
with a backtrace claiming that it has spend more than 120 seconds in
kernel mode or something.
* On 12.01.2012 09:56 PM, Mihai Moldovan wrote:
Hm, shouldn't
* On 31.07.2011 01:41 AM, Grant wrote:
It's fixed! The problem was actually interference from an ath5k
802.11g card I had in the same system. I've noticed that any wireless
card installed in the system will pump out enough RF to interfere with
any other card in the system even if the
Just a typo fix changing regulaotry to regulatory.
Signed-off-by: Mihai Moldovan io...@ionic.de
---
net/wireless/reg.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/net/wireless/reg.c b/net/wireless/reg.c
index 1ad0f39..d99ead3 100644
--- a/net/wireless/reg.c
+++ b
* On 24.07.2011 04:29 PM, Mohammed Shafi wrote:
please send to linux-wireless
http://linuxwireless.org/en/developers/Documentation/git-guide
Oh I'm sorry, I've seen several patches posted here and figured this was
the way to go. Will do.
smime.p7s
Description: S/MIME Cryptographic Signature
* On 21.07.2011 06:57 AM, Mohammed Shafi wrote:
*i guess this commit may be missing in 2.6.38.6, please give it a try
Aaah indeed, it's included in 3.0 too, and I want to give it a try.
Let's see whether it works. :S
Otherwise, I'll try compat-wireless (and I'll even upgrade if 3.0 works.)
Hi all,
quick question, is there any way to enable the LED on an ath9k supported
card?
I tried loading ath9k with blink=1 but it doesn't light anything.
Besides, the driver emits those messages:
[ 15.118448] Registered led device: ath9k-phy1::radio
[ 15.118471] Registered led device:
* On 16.07.2011 08:47 PM, Grant wrote:
Got it, thank you for taking the time to explain. I'll be referring
back to your message. How can I find out how the card I receive is
flashed? Will it show up with 'lspci -v'?
Nope, you'll find that kind of information in the kernel log ring buffer
* On 16.07.2011 09:54 PM, Grant wrote:
Still, I'll be putting the iwconfig txpower info you gave me to good
use. I noticed that if I set 'iwconfig wlan0 txpower 0' I can still
connect to the network. Do you know why that is?
No idea what '0' does, but turning the transmit power of is
* On 17.07.2011 03:58 AM, Adrian Chadd wrote:
I'm not sure.
txpower 0 (dBm) is a legitimate value. The AR5416/AR9130/AR9160 go
down to this value. It's not 0 mW, it's just $SMALL mW.
I see, thanks. :)
The AR9280 and later NICs can go down to -5 dBm.
Interestingly, this won't work on Linux
* On 15.07.2011 04:35 AM, Grant wrote:
Hmmm, so if I get a US EEPROM and travel to another country, I may
need to patch ath5k to connect to a particular AP?
Nope, this stuff doesn't apply to client cards only, however AP mode is
severely restricted by regulatory rules.
If you get an US flashed
* On 15.07.2011 04:54 AM, Grant wrote:
I don't feel anything as long as they're a few feet away. I tried a
Bluetooth headset a few times and it was good for an instant headache.
Too bad cause that would have been cool. Anyway, maybe I'm sensitive
to the 2.4Ghz band. I don't know.
Hum,
* On 14.07.2011 08:54 PM, Grant wrote:
Alright, you guys win. I'll buy a miniPCIe card and adapter.
_
_Really, there is no other good solution anyway, and using an adapter
let's you exchange cards/chips even more easily or maybe share them also
between Laptops and such, that's actually pretty
* On 14.07.2011 01:42 AM, Grant wrote:
Again, anything with an AR9280 on board will be fine. Some of the
antenna arrangements though are a bit .. special.
I'm told this one fits the bill:
http://www.tp-link.com/products/productDetails.asp?pmodel=TL-WN951N
It is said to have a AR5008 chip.
* On 03.06.2011 11:36 AM, Valeriy Kucherenko wrote:
I'm already using last git version :)
What iw version are you... actually screw that. Please get the source
and see, whether this patch is already included in your iw version:
http://www.spinics.net/lists/linux-wireless/msg52587.html
* On 03.06.2011 02:10 PM, Valeriy Kucherenko wrote:
I'm using iw version 0.9.19 on Ubuntu kernel 2.6.39 from kernel PPA so it would
be really pity if it contain drivers from compat-wireless from year 2010.
Yes, that's way too old. Please upgrade to 0.9.22.
smime.p7s
Description: S/MIME
* On 03.06.2011 02:10 PM, Valeriy Kucherenko wrote:
I'm using iw version 0.9.19 on Ubuntu kernel 2.6.39 from kernel PPA so it would
be really pity if it contain drivers from compat-wireless from year 2010.
Btw, the iw tool has nothing to do with the drivers. :)
It's just versions older than
Hi Kucherenko,
Is ath9k support Max AMSDU length 7935 bytes for AR5008 chip? The iw
list command shows that this option is supported but when I enable this
option in hostapd it won't start.
Are you sure you're looking at the right phy device?
My AR5008 (some D-Link DWA card) doesn't
* On 31.05.2011 10:00 PM, Mihai Moldovan wrote:
* On 31.05.2011 09:48 PM, Ben Greear wrote:
On 05/31/2011 12:36 PM, Mihai Moldovan wrote:
Frequencies:
* 5180 MHz [36] (18.0 dBm) (passive scanning, no IBSS)
* 5200 MHz [40] (18.0 dBm) (passive scanning, no IBSS)
* 5220 MHz [44] (18.0 dBm
Ok, some more information.
Kernel: 2.6.38.6
I first thought of a race condition, as the cfg80211 subsystem tries to
get an updated world entry of the regdb pretty early. However, at that
time udev was already started:
[ 14.319904] udev: starting version 151
[ 14.319960] udevd (2041):
Hi Ben,
* On 01.06.2011 07:53 PM, Ben Greear wrote:
Maybe the ath/regd.c just needs fixing to support DE regdomains?
Nope, something's broken in/with CRDA and the Kernel.
Compiling the regdb statically into the Kernel works fine, on both
3.6.38.6 and 3.6.39 (though 3.6.39 is panicing after
Hey all,
I'm having a problem again. ;)
Today I got my AR9380 card and wanted to set it up on 802.11a (5GHz)
with HT40 (802.11n).
Although enabling 802.11d and setting the regulatory domain to DE
(Germany), I wasn't able to bring up the card on any 5GHz channel in AP
mode.
Finding some
* On 31.05.2011 07:56 PM, Peter Stuge wrote:
If the card has a regdomain which requires passive scanning set in
it's EEPROM then setting regdomain in userspace will not change that.
True... the regdomain seems to be set to 0x30 and the alpha2 country
to 00 according to the Kernel messages:
* 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:
* On 31.05.2011 08:33 PM, Ben Greear wrote:
I'm just using Fedora 14 with whatever it comes with, though using
'iw' and hostapd etc from recent git repos.
Gentoo here :)
Rebuilding the Kernel soon... well as soon as I revert the regd.c patch. :)
What NIC? I had this problem with the Sparklan
* On 31.05.2011 08:38 PM, Mihai Moldovan wrote:
SparkLAN WPEA-127NI... ;)
Fail, sorry. SparkLAN WPEA-127N (NI is 9390.)
Mihai
smime.p7s
Description: S/MIME Cryptographic Signature
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https
* On 31.05.2011 08:38 PM, Mihai Moldovan wrote:
Rebuilding the Kernel soon... well as soon as I revert the regd.c patch. :)
Hmm, new patch, but also some bad news: all 5Ghz channels are AP-locked
when using German regdomain, most of them even disabled. iw list:
Frequencies
* On 31.05.2011 09:48 PM, Ben Greear wrote:
On 05/31/2011 12:36 PM, Mihai Moldovan wrote:
Frequencies:
* 5180 MHz [36] (18.0 dBm) (passive scanning, no IBSS)
* 5200 MHz [40] (18.0 dBm) (passive scanning, no IBSS)
* 5220 MHz [44] (18.0 dBm) (passive scanning, no IBSS)
* 5240 MHz [48] (18.0 dBm
Hey all,
are there any PCIe cards with the Atheros AR9380 chipset available?
So far, I was just able to find a SparkLAN card
(http://www.sparklan.com/product.php?func=viewprod_id=181), which is
only available as a miniPCIe card. I know there are miniPCIe to PCIe
expansion cards, but that's
Hello guys,
I'm searching for some by ath9k fully supported chipset/card for use in
AP mode, both for PCI and PCIe.
Currently, I do have two cards with the AR5008 chipset. Formally, it is
supported, but I've tried to get it running for three years without any
success and have lost the
Hi,
I've just tested the newest compat-wireless release today and the
problem still appears. :(
Any hints?
Best regards,
Mihai
signature.asc
Description: OpenPGP digital signature
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
of helping rants.
Best regards,
Mihai Moldovan
signature.asc
Description: OpenPGP digital signature
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
41 matches
Mail list logo
