All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] how to config AR9280 for operation as 1X1 or other ideas
Date: Tue, 29 Mar 2011 19:33:00 +0200	[thread overview]
Message-ID: <4D9217CC.5000102@openwrt.org> (raw)
In-Reply-To: <AANLkTimzMyswtE-476HyccLCBr6kREv_=x+yyNeYRJU-@mail.gmail.com>

On 2011-03-29 7:25 PM, Larry Vaden wrote:
> root at OpenWrt:~# uptime
>   00:07:40 up 7 min, load average: 0.00, 0.03, 0.04
> root at OpenWrt:~# cat /etc/config/wireless
> config wifi-device  radio0
>          option type     mac80211
>          option channel  3
>          option macaddr  00:15:6d:4e:f1:46
>          option hwmode   11ng
>          option htmode   HT20
>          list ht_capab   SHORT-GI-40
>          list ht_capab   TX-STBC
>          list ht_capab   RX-STBC1
>          list ht_capab   DSSS_CCK-40
>          # REMOVE THIS LINE TO ENABLE WIFI:
>          option disabled 0
>
> config wifi-iface
>          option device   radio0
>          option network  lan
>          option mode     ap
>          option ssid     OpenWrt
>          option encryption none
>
> root at OpenWrt:~# cat
> /sys/kernel/debug/ieee80211/phy0/netdev:wlan0/stations/*/rc_stats
> cat: can't open
> '/sys/kernel/debug/ieee80211/phy0/netdev:wlan0/stations/*/rc_stats':
> No such file or directory
That happens if it's not connected.

> root at OpenWrt:~# iw wlan0 survey dump
> Survey data from wlan0
>          frequency:                      2412 MHz
>          noise:                          -97 dBm
>          channel active time:            42 ms
>          channel busy time:              14 ms
>          channel receive time:           0 ms
>          channel transmit time:          0 ms
> Survey data from wlan0
>          frequency:                      2417 MHz
> Survey data from wlan0
>          frequency:                      2422 MHz [in use]
>          noise:                          -81 dBm
>          channel active time:            455133 ms
>          channel busy time:              59391 ms
>          channel receive time:           9327 ms
>          channel transmit time:          4375 ms
Still very noisy and high busy time, something is causing quite a bit of 
interference. No idea how to reduce that or track it down though.

- Felix

  reply	other threads:[~2011-03-29 17:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29 13:33 [ath9k-devel] how to config AR9280 for operation as 1X1 or other ideas Larry Vaden
2011-03-29 14:36 ` Felix Fietkau
2011-03-29 15:08   ` Larry Vaden
2011-03-29 15:31     ` Felix Fietkau
2011-03-29 15:16   ` Larry Vaden
2011-03-29 15:28     ` Felix Fietkau
2011-03-29 16:04       ` Larry Vaden
2011-03-29 17:23         ` Felix Fietkau
2011-03-29 17:55           ` Larry Vaden
2011-03-29 16:08       ` Larry Vaden
2011-03-29 17:21         ` Felix Fietkau
2011-03-29 17:25           ` Larry Vaden
2011-03-29 17:33             ` Felix Fietkau [this message]
2011-03-29 17:38               ` Larry Vaden
2011-03-29 17:43                 ` Felix Fietkau
2011-03-29 16:25       ` Larry Vaden
2011-03-29 17:20         ` Felix Fietkau
2011-03-29 18:16           ` Larry Vaden
2011-03-29 15:34   ` Larry Vaden
2011-03-29 15:38   ` Larry Vaden
2011-03-29 15:47   ` Larry Vaden

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=4D9217CC.5000102@openwrt.org \
    --to=nbd@openwrt.org \
    --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 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.