From: "Peter Vágner" <pvdeejay@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Tplink TL-WN822N drops out connections randomly on Arch Linux with Kernel 3.9.4 (Mark Lee)
Date: Tue, 18 Jun 2013 21:52:51 +0200 [thread overview]
Message-ID: <51C0BA93.8080109@gmail.com> (raw)
In-Reply-To: <51C0B7D2.50609@rempel-privat.de>
Hello,
I am afraid I don't know how to do this.
Do I have to recompile the whole kernel testing each commit or should I
just recompile the driver or even track firmware changes?
Can you please point me to somewhere where I can read on how to proceed?
Greetings
Peter
On 18.06.2013 21:41, Oleksij Rempel wrote:
> Hi Peter,
>
> if it is regression, can you please do git bisect to find commit
> affecting your connection. It can be outside of ath9k_htc source.
>
> Am 18.06.2013 20:20, schrieb Peter V?gner:
>> Hello,
>> I do also have similar device and am facing a strange problem with it.
>> After booting up the machine I am unable to connect to certain wireless
>> AP. That is an old Owislink WL5460 router set up in 2.4B+G mode with WPA
>> encryption.
>> After connecting to another AP e.g. non encrypted AP made up of my
>> Android phone or even encrypted AP created on an iphone I can then
>> connect to the problematic AP.
>> I am on arch linux currently with kernel 3.9.6. The issue started
>> happening as I have updated my kernel to 3.9.1. Previously everything
>> has been working fine wor me.
>>
>> Here are some more details
>>
>> $ lsusb | grep Ather
>> Bus 002 Device 005: ID 0cf3:9271 Atheros Communications, Inc. AR9271
>> 802.11n
>>
>> $ iw dev wlp0s26u1u6 get power_save
>> Power save: off
>>
>>
>> $ dmesg | grep 00:4f:62:05:df:2d
>> [ 23.237360] wlp0s26u1u6: authenticate with 00:4f:62:05:df:2d
>> [ 23.331989] wlp0s26u1u6: send auth to 00:4f:62:05:df:2d (try 1/3)
>> [ 26.376049] wlp0s26u1u6: send auth to 00:4f:62:05:df:2d (try 2/3)
>> [ 28.335490] wlp0s26u1u6: deauthenticating from 00:4f:62:05:df:2d by
>> local choice (reason=3)
>> --- snip ---
>> This is repeating over and over again until I connect to something else.
>> And then the final successfull connection to this AP looks like...
>> [ 252.381096] wlp0s26u1u6: authenticate with 00:4f:62:05:df:2d
>> [ 252.520920] wlp0s26u1u6: send auth to 00:4f:62:05:df:2d (try 1/3)
>> [ 252.524098] wlp0s26u1u6: associate with 00:4f:62:05:df:2d (try 1/3)
>> [ 252.538293] wlp0s26u1u6: RX AssocResp from 00:4f:62:05:df:2d
>> (capab=0x411 status=0 aid=3)
>>
>> $ dmesg | grep ath9k_htc
>> [ 7.353707] usb 2-1.6: ath9k_htc: Firmware htc_9271.fw requested
>> [ 7.353772] usbcore: registered new interface driver ath9k_htc
>> [ 7.829552] usb 2-1.6: ath9k_htc: Transferred FW: htc_9271.fw, size:
>> 51272
>> [ 8.064565] ath9k_htc 2-1.6:1.0: ath9k_htc: HTC initialized with 33
>> credits
>> [ 8.255145] ath9k_htc 2-1.6:1.0: ath9k_htc: FW Version: 1.3
>> [ 252.522905] ath9k_htc 2-1.6:1.0 wlp0s26u1u6: disabling HT as WMM/QoS
>> is not supported by the AP
>> [ 252.522908] ath9k_htc 2-1.6:1.0 wlp0s26u1u6: disabling VHT as WMM/QoS
>> is not supported by the AP
>>
>> $ sudo iw dev wlp0s26u1u6 scan dump
>> BSS 00:4f:62:05:df:2d(on wlp0s26u1u6) -- associated
>> TSF: 254735798022 usec (2d, 22:45:35)
>> freq: 2412
>> beacon interval: 100 TUs
>> capability: ESS Privacy ShortSlotTime (0x0411)
>> signal: -61.00 dBm
>> last seen: 103493 ms ago
>> Information elements from Probe Response frame:
>> SSID: predok
>> Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
>> DS Parameter set: channel 1
>> ERP: <no flags>
>> Extended supported rates: 24.0 36.0 48.0 54.0
>> WPA: * Version: 1
>> * Group cipher: TKIP
>> * Pairwise ciphers: TKIP
>> * Authentication suites: PSK
>> RSN: * Version: 1
>> * Group cipher: TKIP
>> * Pairwise ciphers: CCMP
>> * Authentication suites: PSK
>> * Capabilities: (0x0000)
>>
>> $ sudo iw dev wlp0s26u1u6 scan dump
>> [sudo] password for peto:
>> BSS 00:4f:62:05:df:2d(on wlp0s26u1u6)
>> TSF: 255417536590 usec (2d, 22:56:57)
>> freq: 2412
>> beacon interval: 100 TUs
>> capability: ESS Privacy ShortSlotTime (0x0411)
>> signal: -59.00 dBm
>> last seen: 386 ms ago
>> Information elements from Probe Response frame:
>> SSID: predok
>> Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
>> DS Parameter set: channel 1
>> ERP: <no flags>
>> Extended supported rates: 24.0 36.0 48.0 54.0
>> WPA: * Version: 1
>> * Group cipher: TKIP
>> * Pairwise ciphers: TKIP
>> * Authentication suites: PSK
>> RSN: * Version: 1
>> * Group cipher: TKIP
>> * Pairwise ciphers: CCMP
>> * Authentication suites: PSK
>> * Capabilities: (0x0000)
>>
>>
>>
>> Thanks and greetings
>
>
next prev parent reply other threads:[~2013-06-18 19:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1370167201.11487.ath9k-devel@lists.ath9k.org>
2013-06-02 16:39 ` [ath9k-devel] Tplink TL-WN822N drops out connections randomly on Arch Linux with Kernel 3.9.4 (Mark Lee) Mark E. Lee
2013-06-02 17:00 ` Oleksij Rempel
2013-06-18 18:20 ` Peter Vágner
2013-06-18 19:41 ` Oleksij Rempel
2013-06-18 19:52 ` Peter Vágner [this message]
2013-06-18 19:54 ` Mark E. Lee
2013-06-18 20:40 ` Oleksij Rempel
[not found] <mailman.1.1370340001.351.ath9k-devel@lists.ath9k.org>
2013-06-05 19:43 ` Mark E. Lee
2013-06-03 18:44 Mark E. Lee
2013-06-03 19:25 ` Adrian Chadd
-- strict thread matches above, loose matches on Subject: below --
2013-06-01 17:00 Mark E. Lee
2013-06-01 17:22 ` Oleksij Rempel
2013-06-01 16:55 Mark E. Lee
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=51C0BA93.8080109@gmail.com \
--to=pvdeejay@gmail.com \
--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