linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maciej Mrozowski <reavertm@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: [ath9k-devel] Wrt TP-Link TL-WN821N V3 (confusing/missing info on wiki)
Date: Thu, 28 Apr 2011 02:35:20 +0200	[thread overview]
Message-ID: <201104280235.20751.reavertm@gmail.com> (raw)
In-Reply-To: <19891.57900.438639.178988@gargle.gargle.HOWL>

[-- Attachment #1: Type: Text/Plain, Size: 8058 bytes --]

On Sunday 24 of April 2011 10:41:16 Sujith wrote:

Hello

> > (it stopped working completely recently in wireless-testing though:
> > ieee80211 phy0: device no longer idle - working
> > wlan0: direct probe to 68:7f:74:77:36:bc (try 1/3)
> > wlan0: direct probe to 68:7f:74:77:36:bc (try 2/3)
> > wlan0: direct probe to 68:7f:74:77:36:bc (try 3/3)
> > wlan0: direct probe to 68:7f:74:77:36:bc timed out
> > ieee80211 phy0: device now idle
> > but that's different a story)
> 
> How recent is your wireless-testing tree ?
> 
> Can you post the debug log ?
> See: http://wireless.kernel.org/en/users/Drivers/ath9k/debug

It was some wireless-testing master from around a week ago.
Now I've re-cloned it again (since git pull resulted in conflicts for some 
reason), I'm at 903e9c0102cb9b4b3b1560df31f9b46650cdea88 and using htc_7010.fw 
from http://wireless.kernel.org/download/htc_fw/1.1/ - and so far so good :)

I'll testfield it for a while and see whether it drops connection after some 
time or after "some bandwidth is exceeded" like it appeared to in a past (but 
if was at times when the most recent firmware was still sitting in linux-
firmware repo, I think I experienced the same results with stock kernel 2.6.37 
ath9k_htc driver and corresponding wireless-testing, many things has changes 
since then and I'm optimistic)

regards
MM

(that's not exactly full debug, just I quick look, if there are to be any 
issues, I'll provide full debug respectively)

usb 1-2: new high speed USB device number 5 using ehci_hcd
usb 1-2: ath9k_htc: Transferred FW: htc_7010.fw, size: 72996
ath9k_htc 1-2:1.0: ath9k_htc: HTC initialized with 45 credits
ath9k_htc 1-2:1.0: ath9k_htc: FW Version: 1.1
ath: EEPROM regdomain: 0x809c
ath: EEPROM indicates we should expect a country code
ath: doing EEPROM country->regdmn map search
ath: country maps to regdmn code: 0x52
ath: Country alpha2 being used: CN
ath: Regpair used: 0x52
cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (N/A mBi, 2000 mBm)
cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (N/A mBi, 2000 mBm)
cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (N/A mBi, 2000 mBm)
cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (N/A mBi, 2000 mBm)
cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (N/A mBi, 2000 mBm)
cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (N/A mBi, 2000 mBm)
cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (N/A mBi, 2000 mBm)
cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (N/A mBi, 2000 mBm)
cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (N/A mBi, 2000 mBm)
cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (N/A mBi, 2000 mBm)
cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (N/A mBi, 2000 mBm)
cfg80211: Disabling freq 2467 MHz as custom regd has no rule that fits a 20 
MHz wide channel
cfg80211: Disabling freq 2472 MHz as custom regd has no rule that fits a 20 
MHz wide channel
cfg80211: Disabling freq 2484 MHz as custom regd has no rule that fits a 20 
MHz wide channel
cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
cfg80211: Updating information on frequency 2467 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2457000 KHz - 2482000 KHz @  KHz), (600 mBi, 2000 mBm)
cfg80211: Updating information on frequency 2472 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2457000 KHz - 2482000 KHz @  KHz), (600 mBi, 2000 mBm)
cfg80211: Updating information on frequency 2484 MHz for a 20 MHz width 
channel with regulatory rule:
cfg80211: 2474000 KHz - 2494000 KHz @  KHz), (600 mBi, 2000 mBm)
cfg80211: Pending regulatory request, waiting for it to be processed...
ieee80211 phy2: Atheros AR9287 Rev:2
Registered led device: ath9k-phy2::radio
Registered led device: ath9k-phy2::assoc
Registered led device: ath9k-phy2::tx
Registered led device: ath9k-phy2::rx
usb 1-2: ath9k_htc: USB layer initialized
ieee80211 phy2: device now idle
cfg80211: Pending regulatory request, waiting for it to be processed...
ieee80211 phy2: device no longer idle - scanning
ieee80211 phy2: device now idle
ieee80211 phy2: device no longer idle - working
wlan0: authenticate with 68:7f:74:77:36:bc (try 1)
wlan0: authenticated
wlan0: associate with 68:7f:74:77:36:bc (try 1)
wlan0: RX AssocResp from 68:7f:74:77:36:bc (capab=0x531 status=0 aid=1)
wlan0: associated
ieee80211 phy2: Allocated STA 68:7f:74:77:36:bc
ieee80211 phy2: Inserted STA 68:7f:74:77:36:bc
ieee80211 phy2: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 txop=0 
uapsd=0
ieee80211 phy2: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 txop=0 
uapsd=0
ieee80211 phy2: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 txop=94 
uapsd=0
ieee80211 phy2: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 txop=47 uapsd=0
cfg80211: Pending regulatory request, waiting for it to be processed...
Rx A-MPDU request on tid 7 result 0
Open BA session requested for 68:7f:74:77:36:bc tid 0
activated addBA response timer on tid 0
switched off addBA timer for tid 0
Aggregation is on for tid 0
Rx A-MPDU request on tid 0 result 0

-- 
regards
MM

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

           reply	other threads:[~2011-04-28  0:35 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <19891.57900.438639.178988@gargle.gargle.HOWL>]

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=201104280235.20751.reavertm@gmail.com \
    --to=reavertm@gmail.com \
    --cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).