Development list for the Linux ath9k (Atheros 802.11n) wireless driver ()

headers Nikki Chumakov | 4 Jan 2010 12:22

_______________________________________________
ath9k-devel mailing list
ath9k-devel <at> lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel

On Wed, Dec 30, 2009 at 12:58:51PM -0800, rootkit85 <at> yahoo.it wrote:
> 2009/12/29 Björn Smedman <bjorn.smedman <at> venatech.se>:
> > Nope, haven't solved it. I think I've patched the driver in 50 places
> > and it still goes up and down up and down in perfect cycles. Who needs
> > an atomic clock when you can just count the throughput cycles and know
> > exactly what time it is? :)
> >
> > My current theory is that it's some sort of tx beamforming algo that
> > screws up once signal gets below -78 dBm or so. But you see the stalls
> > even with perfect signal, right? That never happens to me (which is
> > fortunate as I would be in an asylum by now if it did).
> >
> > Does anybody know which register to fiddle with to turn off all
> > adaptive tx stuff (to debug)? It's an AR5416 MAC/BB with AR2133 radio.
> > Is it possible to get some hw documentation somewhere?
> >
> > BTW, my setup is an unencrypted HT20 access point.
> >
> > /Björn
> >
> > 2009/12/26  <rootkit85 <at> yahoo.it>:
> >> 2009/12/24 Björn Smedman <bjorn.smedman <at> venatech.se>:
> >>> Do the stalls occur at regular intervals? I have a similar problem on
> >>> an AR9103 in AP mode. See my previous post 'Cyclic throughput at a
> >>> distance'.
> >>>
> >>> /Björn
> >>>
> >>> On Thu, Dec 24, 2009 at 2:31 PM,  <rootkit85 <at> yahoo.it> wrote:
> >>>> On Thu, Dec 24, 2009 at 2:27 PM,  <rootkit85 <at> yahoo.it> wrote:
> >>>>> Hi,
> >>>>> I'm using an AR9223 in AP mode with latest compat-wireless-2009-12-11
> >>>>> drivers but I get bad performances.
> >>>>> SSH is unusable.
> >>>>> The link is fine when it works but sometimes it stalls for a few
> >>>>> seconds, which kills tcp performances:
> >>>>>
> >>>>> iperf -sui1
> >>>>> ------------------------------------------------------------
> >>>>> Server listening on UDP port 5001
> >>>>> Receiving 1470 byte datagrams
> >>>>> UDP buffer size:   106 KByte (default)
> >>>>> ------------------------------------------------------------
> >>>>> [  3] local 192.168.0.1 port 5001 connected with 192.168.0.79 port 33066
> >>>>> [ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total Datagrams
> >>>>> [  3]  0.0- 1.0 sec  7.98 MBytes  66.9 Mbits/sec  0.117 ms 1423/ 7115 (20%)
> >>>>> [  3]  1.0- 2.0 sec  11.3 MBytes  94.5 Mbits/sec  0.085 ms 2811/10849 (26%)
> >>>>> [  3]  2.0- 3.0 sec  11.1 MBytes  92.9 Mbits/sec  0.119 ms 2734/10632 (26%)
> >>>>> [  3]  3.0- 4.0 sec  6.63 MBytes  55.6 Mbits/sec  0.135 ms 1257/ 5986 (21%)
> >>>>> [  3]  4.0- 5.0 sec  1.95 MBytes  16.3 Mbits/sec  0.113 ms  186/ 1575 (12%)
> >>>>> [  3]  5.0- 6.0 sec  1.17 MBytes  9.81 Mbits/sec  0.083 ms  254/ 1088 (23%)
> >>>>> [  3]  6.0- 7.0 sec  0.00 Bytes  0.00 bits/sec  0.083 ms    0/    0 (nan%)
> >>>>> [  3]  7.0- 8.0 sec  0.00 Bytes  0.00 bits/sec  0.083 ms    0/    0 (nan%)
> >>>>> [  3]  8.0- 9.0 sec  0.00 Bytes  0.00 bits/sec  0.083 ms    0/    0 (nan%)
> >>>>> [  3]  9.0-10.0 sec  1.86 MBytes  15.6 Mbits/sec  0.144 ms  649/ 1973 (33%)
> >>>>> [  3] 10.0-11.0 sec  2.38 MBytes  19.9 Mbits/sec  0.097 ms  609/ 2304 (26%)
> >>>>> [  3] 11.0-12.0 sec    652 KBytes  5.34 Mbits/sec  0.068 ms  198/  652 (30%)
> >>>>> [  3] 12.0-13.0 sec  9.69 MBytes  81.3 Mbits/sec  0.085 ms 2563/ 9476 (27%)
> >>>>> [  3] 13.0-14.0 sec  6.38 MBytes  53.5 Mbits/sec  0.249 ms 1426/ 5977 (24%)
> >>>>> [  3] 14.0-15.0 sec  8.45 MBytes  70.9 Mbits/sec  1.677 ms 1940/ 7971 (24%)
> >>>>> [  3] 15.0-16.0 sec  8.03 MBytes  67.4 Mbits/sec  2.580 ms 1899/ 7628 (25%)
> >>>>> [  3] 16.0-17.0 sec  6.91 MBytes  57.9 Mbits/sec  0.157 ms  905/ 5832 (16%)
> >>>>> [  3] 17.0-18.0 sec    233 KBytes  1.91 Mbits/sec  0.788 ms   32/  194 (16%)
> >>>>> [  3] 18.0-19.0 sec  1.12 MBytes  9.38 Mbits/sec  0.620 ms  210/ 1008 (21%)
> >>>>> [  3] 19.0-20.0 sec  7.06 MBytes  59.3 Mbits/sec  0.159 ms 1027/ 6066 (17%)
> >>>>> [  3] 20.0-21.0 sec  6.07 MBytes  50.9 Mbits/sec  0.322 ms  720/ 5047 (14%)
> >>>>> [  3] 21.0-22.0 sec  6.13 MBytes  51.4 Mbits/sec  0.109 ms  619/ 4989 (12%)
> >>>>> [  3] 22.0-23.0 sec  4.84 MBytes  40.6 Mbits/sec  0.154 ms  365/ 3814 (9.6%)
> >>>>> [  3] 23.0-24.0 sec  5.26 MBytes  44.1 Mbits/sec  0.308 ms  224/ 3978 (5.6%)
> >>>>> [  3] 24.0-25.0 sec  6.06 MBytes  50.9 Mbits/sec  0.167 ms  757/ 5083 (15%)
> >>>>> [  3] 25.0-26.0 sec  6.84 MBytes  57.4 Mbits/sec  0.148 ms  902/ 5779 (16%)
> >>>>> [  3] 26.0-27.0 sec  7.66 MBytes  64.3 Mbits/sec  0.152 ms 1288/ 6755 (19%)
> >>>>> [  3] 27.0-28.0 sec  0.00 Bytes  0.00 bits/sec  0.152 ms    0/    0 (nan%)
> >>>>> [  3] 28.0-29.0 sec  84.7 KBytes    694 Kbits/sec  14.385 ms  141/  200 (70%)
> >>>>> [  3]  0.0-30.0 sec    145 MBytes  40.7 Mbits/sec  0.290 ms 27599/131272 (21%)
> >>>>> [  3]  0.0-30.0 sec  1 datagrams received out-of-order
> >>>>>
> >>>>>
> >>>>> $ ping 192.168.0.1
> >>>>> PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
> >>>>>
> >>>>> 64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=280 ms
> >>>>> 64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=1.95 ms
> >>>>> 64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=1002 ms
> >>>>> 64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=50.3 ms
> >>>>> 64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=264 ms
> >>>>> 64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=322 ms
> >>>>> 64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=1232 ms
> >>>>> 64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=5.11 ms
> >>>>> 64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=1.96 ms
> >>>>> ^C
> >>>>> --- 192.168.0.1 ping statistics ---
> >>>>> 11 packets transmitted, 9 received, 18% packet loss, time 10021ms
> >>>>> rtt min/avg/max/mdev = 1.957/351.321/1232.350/430.558 ms, pipe 2
> >>>>>
> >>>>>
> >>>>> there are no errors in the master and client syslog, all the clients
> >>>>> are using the same ath9k with an AR5416 card.
> >>>>> signal level is around -61 dBm at 3 meters, without walls.
> >>>>>
> >>>>
> >>>> This is an iperf from the AP to the client, definitely worse:
> >>>>
> >>>> ------------------------------------------------------------
> >>>> Server listening on UDP port 5001
> >>>> Receiving 1470 byte datagrams
> >>>> UDP buffer size:   112 KByte (default)
> >>>> ------------------------------------------------------------
> >>>> [  3] local 192.168.0.79 port 5001 connected with 192.168.0.1 port 59087
> >>>> [ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total Datagrams
> >>>> [  3]  0.0- 1.0 sec    159 KBytes  1.31 Mbits/sec  9.106 ms  100/  211 (47%)
> >>>> [  3]  1.0- 2.0 sec  2.83 MBytes  23.7 Mbits/sec  14.785 ms  221/ 2240 (9.9%)
> >>>> [  3]  2.0- 3.0 sec    876 KBytes  7.17 Mbits/sec  0.210 ms   45/  655 (6.9%)
> >>>> [  3]  3.0- 4.0 sec  2.29 MBytes  19.2 Mbits/sec  0.137 ms  122/ 1753 (7%)
> >>>> [  3]  4.0- 5.0 sec  4.36 MBytes  36.6 Mbits/sec  0.663 ms  231/ 3341 (6.9%)
> >>>> [  3]  5.0- 6.0 sec  1.59 MBytes  13.3 Mbits/sec  1.107 ms   16/ 1150 (1.4%)
> >>>> [  3]  6.0- 7.0 sec    705 KBytes  5.77 Mbits/sec  25.142 ms   87/  578 (15%)
> >>>> [  3]  7.0- 8.0 sec    924 KBytes  7.57 Mbits/sec  0.454 ms   36/  680 (5.3%)
> >>>> [  3]  8.0- 9.0 sec    577 KBytes  4.73 Mbits/sec  15.732 ms   55/  457 (12%)
> >>>> [  3]  9.0-10.0 sec  1.81 MBytes  15.2 Mbits/sec  0.297 ms   58/ 1352 (4.3%)
> >>>> [  3] 10.0-11.0 sec    728 KBytes  5.96 Mbits/sec  0.449 ms    0/  507 (0%)
> >>>> [  3] 11.0-12.0 sec  0.00 Bytes  0.00 bits/sec  0.449 ms    0/    0 (nan%)
> >>>> [  3] 12.0-13.0 sec  1.99 MBytes  16.7 Mbits/sec  0.545 ms   54/ 1472 (3.7%)
> >>>> [  3] 13.0-14.0 sec  2.13 MBytes  17.9 Mbits/sec  0.321 ms   62/ 1583 (3.9%)
> >>>> [  3] 14.0-15.0 sec  1.03 MBytes  8.64 Mbits/sec  0.716 ms   29/  764 (3.8%)
> >>>> [  3] 15.0-16.0 sec  2.14 MBytes  18.0 Mbits/sec  0.252 ms  214/ 1743 (12%)
> >>>> [  3] 16.0-17.0 sec  2.96 MBytes  24.8 Mbits/sec  19.672 ms   61/ 2170 (2.8%)
> >>>> [  3] 17.0-18.0 sec  40.2 KBytes    329 Kbits/sec  18.868 ms   16/   44 (36%)
> >>>> [  3] 18.0-19.0 sec  4.47 MBytes  37.5 Mbits/sec  0.185 ms  130/ 3316 (3.9%)
> >>>> [  3] 19.0-20.0 sec  7.84 MBytes  65.7 Mbits/sec  0.210 ms  359/ 5949 (6%)
> >>>> [  3] 20.0-21.0 sec  7.71 MBytes  64.7 Mbits/sec  0.149 ms  412/ 5914 (7%)
> >>>> [  3] 21.0-22.0 sec  7.46 MBytes  62.6 Mbits/sec  0.674 ms  398/ 5721 (7%)
> >>>> [  3] 22.0-23.0 sec  7.45 MBytes  62.5 Mbits/sec  0.725 ms  405/ 5719 (7.1%)
> >>>> [  3] 23.0-24.0 sec  6.80 MBytes  57.0 Mbits/sec  0.374 ms  256/ 5106 (5%)
> >>>> [  3] 24.0-25.0 sec  8.07 MBytes  67.7 Mbits/sec  0.163 ms  390/ 6145 (6.3%)
> >>>> [  3] 25.0-26.0 sec  7.56 MBytes  63.4 Mbits/sec  0.230 ms  417/ 5809 (7.2%)
> >>>> [  3] 26.0-27.0 sec  6.59 MBytes  55.3 Mbits/sec  1.414 ms  377/ 5080 (7.4%)
> >>>> [  3] 27.0-28.0 sec  6.83 MBytes  57.3 Mbits/sec  0.224 ms  438/ 5308 (8.3%)
> >>>> [  3] 28.0-29.0 sec  6.33 MBytes  53.1 Mbits/sec  7.292 ms  438/ 4954 (8.8%)
> >>>> [  3]  0.0-29.7 sec    105 MBytes  29.7 Mbits/sec  1.346 ms 5453/80421 (6.8%)
> >>>> [  3]  0.0-29.7 sec  1 datagrams received out-of-order
> >>>> _______________________________________________
> >>>> ath9k-devel mailing list
> >>>> ath9k-devel <at> lists.ath9k.org
> >>>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
> >>>>
> >>>
> >>
> >> yes it does at soem intervals as you can see.
> >> Have you solved or found the issue?
> >>
> >
> 
> Does the link quality drop when the throughput goes down?
> I have -81 dBm at ~5 meters from the AP, no walls...
> Is the AR922X a single chip device as the AR928X?

AR9280 is the PCI express device, but PCI devices exist as well
and those get the AR922x name, there should be no difference
other than the bus used so yes these are single chip as well.

  Luis

Any update on getting this card working with the ath9k?

Brian

Pavel Roskin wrote:
> Quoting Brian Walker <walkerbm <at> charter.net>:
>
>> Ok, so you're going to do testing/tracing and then perhaps submit a
>> patch to get these cards to work based on findings?
>
> Only if I find time for that.
>

Brian Walker wrote:
> Any update on getting this card working with the ath9k?

The logs that you posted earlier didn't contain debug information.
Can you make sure that you load the driver with debug=0x601 and
post the dmesg output on doing 'ifconfig wlan0 up' ?

Please see: http://wireless.kernel.org/en/users/Drivers/ath9k/debug

That would show what exactly goes wrong when bringing up the interface.

Sujith

_______________________________________________
ath9k-devel mailing list
ath9k-devel <at> lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel

Dear all,

I recently purchased a wireless-n card, namely the D-link DWA-547. It
has an atheros chipset and is nicely detected by the ath9k driver. I
have been trying to get this card working with the Ubuntu 9.10 kernel
(which is based on 2.6.31), as well as linux 2.6.32. I have also tried
Ubuntu 9.10 backport wireless modules.

lspci reports:
07:02.0 Network controller [0280]: Atheros Communications Inc. AR922X
Wireless Network Adapter [168c:0029] (rev 01)
    Subsystem: D-Link System Inc Device [1186:3a78]
    Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 12
    Memory at fbae0000 (32-bit, non-prefetchable) [size=64K]
    Capabilities: [44] Power Management version 2
    Kernel modules: ath9k

The problem is that after a few minutes - sometimes seconds - the
system halts to a complete freeze where the reset button is the only
way out. Sometimes this happens before X has started, sometimes it
happens right after a connection is established. There is no way for
me to gather any information after the freeze and I haven't found
anything in the logs. So, unfortunately, at the moment I have no clue
as of how to provide this list with more information (and that's why
this ended up being an email to the list, rather than a bug report).

The only thing that helped was to modprobe -r ath9k as soon as the
system booted up (the module is now blacklisted).

I also happened to have a windows 7 license, so I decided to try the
card under Windows 7 for comparison. Interestingly, the system behaved
in precisely the same way: Complete freeze. Later, I noticed that the
problem wasn't uncommon [1]. The retailer, however, insists that the
card I have worked flawlessly under Windows XP for them (I purchased a
demo ex for a discounted price), and that there simply are no Windows
7 drivers. About linux support, they had nothing to say.

So, is this a known issue? And more importantly, how can I even start
trouble shooting?

Best regards,
Khashayar

[1] http://www.google.se/search?sourceid=chrome&ie=UTF-8&q=d-link+dwa-547+complete+freeze

Hello

My laptop has a AR928X. Connections to an AVM3270 ("fritzbox") usually have a transfer rate of 216 MBit. The
maximal value i ever noticed so far has been 243MBit. If i run Windows 7, the connection is set up on 300MBit.
Please note, that all of these values are reported by the AP, so there should no "cosmetic effect" involved.

$ uname -a
Linux rubin 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC 2009 x86_64 GNU/Linux

i use the version from linux-backports-modules-wireless-karmic-generic 2.6.31.17.30

$ modinfo ath9k
filename:       /lib/modules/2.6.31-17-generic/updates/cw/ath9k.ko
license:        Dual BSD/GPL
description:    Support for Atheros 802.11n wireless LAN cards.
author:         Atheros Communications
srcversion:     918698AEA3CBE61D0E996E6

Is it possible to get the full 300Mbit with ath9k, too?

Another question:
Whenever i use ssh on my laptop to work on a remote system, the network connection (and therefore my shell
too) hangs for about 5 seconds every 120 seconds. Just in the moment when syslog reports a
"CTRL-EVENT-SCAN-RESULTS". As far as i understand this is because of a scan of all channels, which needs
much more time in the 802.11n system. Is this correct?
I also read that it should be possible to scan all the channels independently with a newer version of
wpa_supplicant, which should at least reduce the effect. Are there any "tutorials" how to achieve this?

kind regards
Henning
--

-- 
Preisknaller: GMX DSL Flatrate für nur 16,99 Euro/mtl.!
http://portal.gmx.net/de/go/dsl02

This is what I have in /etc/modprobe.d/local.conf (I run Fedora 11):

options ath9k debug=0xffffffff

In config.mk I have:

CONFIG_ATH9K_DEBUG=y
CONFIG_ATH9K_DEBUGFS=y

Is there something else I need to do to get the debugging information 
you're interested in?

Brian

On 01/07/2010 11:34 PM, Sujith wrote:
> Brian Walker wrote:
>    
>> Any update on getting this card working with the ath9k?
>>      
> The logs that you posted earlier didn't contain debug information.
> Can you make sure that you load the driver with debug=0x601 and
> post the dmesg output on doing 'ifconfig wlan0 up' ?
>
> Please see: http://wireless.kernel.org/en/users/Drivers/ath9k/debug
>
> That would show what exactly goes wrong when bringing up the interface.
>
> Sujith
>    

_______________________________________________
ath9k-devel mailing list
ath9k-devel <at> lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel

On Sat, 2010-01-09 at 17:57 +0300, Andrey Korolyov wrote:

> When i tried to set card in master mode, iwconfig gives me an error
> but nothing in dmesg
> iwconfig wlan0 mode master
> Error for wireless request "Set Mode" (8B06) :
>     SET failed on device wlan0 ; Invalid argument.

You can only set master mode in mac80211 based drivers by running
hostapd.

--

-- 
Regards,
Pavel Roskin

250	May 2013
666	April 2013
187	March 2013
109	February 2013
19	January 2013
43	December 2012
78	November 2012
82	October 2012
57	September 2012
28	August 2012
129	July 2012
122	June 2012
206	May 2012
274	April 2012
190	March 2012
107	February 2012
189	January 2012
88	December 2011
137	November 2011
156	October 2011
74	September 2011
209	August 2011
199	July 2011
230	June 2011
186	May 2011
250	April 2011
200	March 2011
238	February 2011
318	January 2011
164	December 2010
192	November 2010
144	October 2010
174	September 2010
77	August 2010
91	July 2010
70	June 2010
101	May 2010
97	April 2010
148	March 2010
119	February 2010
143	January 2010
67	December 2009
86	November 2009
95	October 2009
190	September 2009
142	August 2009
183	July 2009
265	June 2009
181	May 2009
72	April 2009
140	March 2009
253	February 2009
362	January 2009
254	December 2008
80	November 2008
90	October 2008
170	September 2008
167	August 2008
79	July 2008

AR9280 cannot associate with AP

Re: throughput is unstable

Re: trouble with DWA-552 and ath9k

Re: trouble with DWA-552 and ath9k

ath9k / base station compatibility

D-Link DWA-547 completely freezes system

Transfer rate issue

Re: trouble with DWA-552 and ath9k

AR5008 and master mode

Re: AR5008 and master mode

Mon	Tue	Wed	Thu	Fri	Sat	Sun

				1	2	3
4	5	6	7	8	9	10
11	12	13	14	15	16	17
18	19	20	21	22	23	24
25	26	27	28	29	30	31