TP-Link WN722N refuses to work

randolf101 · 2012-07-08 10:00:29

Hi Guys,

I've recently purchased this TP-Link WN722N wifi adapter to work with my Goflex Home running on Archlinux-Arm5vTe. Since purchase haven't quite got it to work. It authenticates and associates to the AP alright using wpa_supplicant command and netcfg. But when I run a dhcpcd wlan0 it fails to get me a valid IP and pulls a 169.254.x.x on me. I've seen you guys resolve tedious problems than these so I feel mine will not take much of your time.

Here are few pasties for reference, do ask for more if you need any:
Please help me out guys!!

[root@alarm ~]# lsusb -v
Bus 001 Device 002: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass       255 Vendor Specific Subclass
  bDeviceProtocol       255 Vendor Specific Protocol
  bMaxPacketSize0        64
  idVendor           0x0cf3 Atheros Communications, Inc.
  idProduct          0x9271 AR9271 802.11n
  bcdDevice            1.08
  iManufacturer          16 ATHEROS
  iProduct               32 USB2.0 WLAN
  iSerial                48 12345
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           60
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           6
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x05  EP 5 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x06  EP 6 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass       255 Vendor Specific Subclass
  bDeviceProtocol       255 Vendor Specific Protocol
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)

[root@alarm ~]# lsmod
Module                  Size  Used by
ipv6                  259702  16
ath9k_htc              52522  0
ath9k_common            1750  1 ath9k_htc
ath9k_hw              334697  2 ath9k_common,ath9k_htc
ath                    13797  3 ath9k_hw,ath9k_common,ath9k_htc
mac80211              364072  1 ath9k_htc
cfg80211              154815  3 mac80211,ath,ath9k_htc
compat                  4252  5 cfg80211,mac80211,ath9k_hw,ath9k_common,ath9k_htc
rfkill                 14400  1 cfg80211
mv_cesa                 9120  0


[root@alarm ~]# ifconfig wlan0
wlan0: flags=4098<BROADCAST,MULTICAST>  mtu 1500  metric 1
        ether 90:f6:52:14:ba:1e  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0     Scan completed :
          Cell 01 - Address:
                    Channel:6
                    Frequency:2.437 GHz (Channel 6)
                    Quality=45/70  Signal level=-65 dBm
                    Encryption key:on
                    ESSID:"my_wireless"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
                              36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=0000005d5f9b7184
                    Extra: Last beacon: 350ms ago
                    IE: Unknown: 00084E4D494D535F4833
                    IE: Unknown: 010482848B96
                    IE: Unknown: 030106
                    IE: Unknown: 2A0104
                    IE: Unknown: 32080C1218243048606C
                    IE: WPA Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD07000C4303000000


[root@alarm ~]# cat /etc/wpa_supplicant.conf
network={
        ssid="my_wireless"
        #psk="passphrase"
        psk=fba5a669904c99eebb810d4734ba4ed3e1019b07fcdcab9d620b61c6d687b6be
}


[root@alarm ~]# wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf -B
[root@alarm ~]# iwconfig wlan0
wlan0     IEEE 802.11bgn  ESSID:"my_wireless"
          Mode:Managed  Frequency:2.437 GHz  Access Point:
          Bit Rate=48 Mb/s   Tx-Power=20 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=49/70  Signal level=-61 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:2   Missed beacon:0

[root@alarm ~]# dhcpcd wlan0
dhcpcd[668]: version 5.5.6 starting
dhcpcd[668]: wlan0: sending IPv6 Router Solicitation
dhcpcd[668]: wlan0: checking for 169.254.19.72
dhcpcd[668]: wlan0: sending IPv6 Router Solicitation
dhcpcd[668]: wlan0: using IPv4LL address 169.254.19.72
dhcpcd[668]: forked to background, child pid 689


[root@alarm ~]# cat /etc/conf.d/dhcpcd
#
# Arguments to be passed to the DHCP client daemon
#

DHCPCD_ARGS="-q "


[root@alarm ~]# dmesg | tail
[   22.070767] eth0: no IPv6 routers present
[  538.338943] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  690.927111] wlan0: authenticate with
[  691.017965] wlan0: send auth to  (try 1/3)
[  691.022140] wlan0: authenticated
[  691.070776] wlan0: associate with  (try 1/3)
[  691.076006] wlan0: RX AssocResp from  (capab=0x411 status=0 aid=7)
[  691.076021] wlan0: associated
[  691.081955] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  701.430747] wlan0: no IPv6 routers present

Last edited by randolf101 (2012-07-08 12:18:32)

Inxsible · 2012-07-08 22:22:04

have yau searched the forums? a bunch of threads on issues with ath9k and the latest updates.

randolf101 · 2012-07-09 09:35:53

Haven't checked up on ath9k par se. But looked for this particular adapter model and got nothing on it. Will get back after reading up on the ath9k.

In the meanwhile if some one has the same WiFi adapter please come forward.

randolf101 · 2012-07-13 12:49:59

@Inxsible I tried reading up on the ath9k driver you mentioned. turns out the WN722N accepts a ath9k_htc driver which is not the same. So in that context i did not find anything relevant to my wifi adapter. please guide me from here.

Gusar · 2012-07-13 14:16:06

randolf101 wrote:

So in that context i did not find anything relevant to my wifi adapter.

Seriously? Third result in putting ath9k_htc into the forum's search: https://bbs.archlinux.org/viewtopic.php?id=143848. There's at least four other threads, also on the first page of the search results.

stevepa · 2012-07-13 14:32:54

randolf101 wrote:

Haven't checked up on ath9k par se. But looked for this particular adapter model and got nothing on it. Will get back after reading up on the ath9k.

In the meanwhile if some one has the same WiFi adapter please come forward.

FWIW, I did some testing on this adaptor at https://bbs.archlinux.org/viewtopic.php?id=144644

Unfortunately, that post is about all I can offer.

Good luck.

Last edited by stevepa (2012-07-13 14:34:40)

zigiless · 2012-07-13 14:49:54

There's also my thread here (https://bbs.archlinux.org/viewtopic.php?id=143937)
There's no solution yet in any of the threads, except setting the card to "promiscuous mode" which is a workaround rather than a fix.
However, I did notice that my card seems to be performing worse in that mode than it used to out of the box in kernels < 3.4.2

Last edited by zigiless (2012-07-13 14:53:06)

Gusar · 2012-07-13 15:05:28

zigiless wrote:

There's no solution yet in any of the threads

There is a solution, I pointed to it in several of the threads - a kernel patch.

zigiless · 2012-07-13 15:17:31

I didn't think of trying the kernel patch, because as mfncl explained in that thread, I have a different problem.
I don't get random disconnects, my adapter refuses to connect at all. It stops with "reason=3".
But since I have nothing more to try, I'll give the patch a try when I have some time tomorrow. Hopefully it'll help.
Thanks

Gusar · 2012-07-13 15:34:34

zigiless wrote:

I didn't think of trying the kernel patch, because as mfncl explained in that thread, I have a different problem.
I don't get random disconnects, my adapter refuses to connect at all. It stops with "reason=3".

Well, what that patch primarily addresses is yet a third issue. However it seems all these issues have a common cause - flaky packet transmission. And that's what the patch addresses, to quote it's description:

... Not doing so, is affecting the packet transmission.

All I can say is, I have the patch applied, and my TL-WN721N works. I just tested it, connecting to a typical WPA2-PSK network. It connected immediately, and ping is stable, there aren't any fluctuations.

For the benefit of others reading this thread, the patch discussed is this one: http://www.spinics.net/lists/linux-wire … 92517.html

Edit: Yesterday, Greg KH posted a review of what will be released as kernel 3.4.5 early next week. This ath9k_htc patch is part of it. Also some other ath9k patches, as well as an important ipw2200 patch for networkmanager users, and some other wireless stuff too. All in all, should be an exciting release.

Last edited by Gusar (2012-07-13 16:14:04)

randolf101 · 2012-07-13 17:35:57

thanks Gusar stevepa zigiless : I did go through all your posts before posting here, i thought i must have overlooked and read it in a hurry !! ...my apologies.

Btw i did try the promiscuous mode and voila !! it works .. fetched me a genuine dhcp ip.

but here comes that bad part - I can't see my rpi on the network, neither can I ping the acquired IP nor can I ssh into it !

To access it now i'm using my laptop's ethernet port set at 192.168.2.2 ----and the rpi's ethernet using a lan cable --- 192.168.2.3 ... and using the wlan0 on the side which has acquired dhcp ip

Pres · 2012-07-13 18:27:56

You can try using the linux-lts kernel. If it's an issue with the newest kernel like the other posts have suggested, then it should work fine with the lts kernel. I use it as I generally experience less problems with it.

randolf101 · 2012-07-14 04:46:01

Pres, how do I apply it on my archlinux-arm5vTe ?

# pacman -S linux-lts

is that it ? or more to it ? also will I be losing on something by doing so ?

Pres · 2012-07-14 12:45:40

Just install it and add an entry for it in your bootloader. Then boot from that. If you are using certain applications (nvidia drivers, virtualbox) you will also need to install the proper *-lts packages to get the modules for the lts kernel.

randolf101 · 2012-07-16 14:07:49

Guys just to clarify my device is a Goflex Home : http://archlinuxarm.org/platforms/armv5 … oflex-home

and not a Raspberry Pi. I said so to escape confusion wrt the device, turns out they're not similar. my bad. please suggest wrt Goflex Home from here.

thanks.

randolf101 · 2012-07-16 17:35:42

zigiless wrote:

There's also my thread here (https://bbs.archlinux.org/viewtopic.php?id=143937)
There's no solution yet in any of the threads, except setting the card to "promiscuous mode" which is a workaround rather than a fix.
However, I did notice that my card seems to be performing worse in that mode than it used to out of the box in kernels < 3.4.2

Fantastic workaround, at least i have my armbox on the network and can ssh into it now !!
Downside:
- Cannot access the armbox through other devices except my laptop - which is strange
- File transfer speeds are... lets just say it's less than my internet connection.
can't wait to run it the way it was intended to be.. any updates on a possible fix to this issue ?

Ok so now I got the latest version of compat-wireless driver and I can use the adapter in managed mode !!

But there still one last thing which worries me --- the AP that my adapter connects to does not allow other devices on the same AP to ssh into it or even ping it's IP. So I have to use a different AP for my laptop and fone so I could ssh into my arm-box.

Last edited by randolf101 (2012-07-17 18:27:18)

Arch Linux

#1 2012-07-08 10:00:29

TP-Link WN722N refuses to work

#2 2012-07-08 22:22:04

Re: TP-Link WN722N refuses to work

#3 2012-07-09 09:35:53

Re: TP-Link WN722N refuses to work

#4 2012-07-13 12:49:59

Re: TP-Link WN722N refuses to work

#5 2012-07-13 14:16:06

Re: TP-Link WN722N refuses to work

#6 2012-07-13 14:32:54

Re: TP-Link WN722N refuses to work

#7 2012-07-13 14:49:54

Re: TP-Link WN722N refuses to work

#8 2012-07-13 15:05:28

Re: TP-Link WN722N refuses to work

#9 2012-07-13 15:17:31

Re: TP-Link WN722N refuses to work

#10 2012-07-13 15:34:34

Re: TP-Link WN722N refuses to work

#11 2012-07-13 17:35:57

Re: TP-Link WN722N refuses to work

#12 2012-07-13 18:27:56

Re: TP-Link WN722N refuses to work

#13 2012-07-14 04:46:01

Re: TP-Link WN722N refuses to work

#14 2012-07-14 12:45:40

Re: TP-Link WN722N refuses to work

#15 2012-07-16 14:07:49

Re: TP-Link WN722N refuses to work

#16 2012-07-16 17:35:42

Re: TP-Link WN722N refuses to work

Board footer