Linux Mint Forums

by **sajukk** on Mon Feb 22, 2010 1:49 pm

Hello mint community

I have been using linuxmint for several months but i still consider myself a noob. Proof on that is, i bought a wireless usb network adapter, without first checking if it is compatible with linux. I connected it and, what a surprise, it wasn't compatible. The adapter is a TP-LINK TL-WN722N, with Atheros chipset.

I connect it into a usb port, but nothing happens. Absolutely nothing. The led does not flash, the systems seems to totally ignore it. It was the same in windows, but when i installed the driver found on the cd, it came to life and is working normally.

However, there is nothing like a driver for linux. No surprise there. The instruction manual has installation instructions only for windows, nothing about linux. No surprise there either. I checked on the manufacturer site, and all over the web, but no references about linux issues. Just some other users asking how to make it work, without any useful answers.

Time for work then. I read something about a command named lsusb. This is the output:

Code: Select all: Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 006: ID 0cf3:9271 Atheros Communications, Inc. Bus 001 Device 003: ID 05e3:0505 Genesys Logic, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I guess this means that the device is there. (bus 001, device 006). Now what. Doing a man lsusb i came up using the -v option. So i gave the command :

Code: Select all: sudo lsusb -s 001:006 -v

which came up with this:

Code: Select all: Bus 001 Device 006: ID 0cf3:9271 Atheros Communications, Inc. 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 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)

Please bear in mind that i am a total noob. This is all japanese to me. In fact, i am quite proud of myself that I even discovered those commands. I hope they help.

I also found the program resting under mintmenu > administration > windows wireless drivers. I read this is some "ndiswrapper" program. I installed the windows drivers found on the cd. It says "unable to see if hardware is present", but when i click ok, it says Hardware present : yes. Well maybe that's one thing I can't complain about.

Doing some search in the mint forums, i also learned about the "mintwifi" command, which i gave on the terminal. This is the output:

Code: Select all: sajukk@compu-terataki ~ $ mintwifi ------------------------- * I. scanning WIFI PCI devices... -- RaLink RT2860 ==> PCI ID = 1814:0781 ------------------------- * II. querying ndiswrapper... WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release. netathur : driver installed device (0CF3:9271) present ------------------------- * III. querying iwconfig... lo no wireless extensions. ra0 RT2860 Wireless ESSID:"" Nickname:"RT2860STA" Mode:Auto Frequency=2.462 GHz Access Point: Not-Associated Bit Rate:1 Mb/s RTS thr:off Fragment thr:off Link Quality=10/100 Signal level:0 dBm Noise level:-97 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 eth0 no wireless extensions. pan0 no wireless extensions. ------------------------- * IV. querying ifconfig... eth0 Link encap:Ethernet HWaddr 40:61:86:16:9c:40 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:253 Base address:0x2000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:581 errors:0 dropped:0 overruns:0 frame:0 TX packets:581 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:57728 (57.7 KB) TX bytes:57728 (57.7 KB) pan0 Link encap:Ethernet HWaddr 9e:6c:4b:98:32:47 inet6 addr: fe80::9c6c:4bff:fe98:3247/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:1494 (1.4 KB) ra0 Link encap:Ethernet HWaddr 00:24:21:97:41:75 inet6 addr: fe80::224:21ff:fe97:4175/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:17 ------------------------- * V. querying DHCP... Internet Systems Consortium DHCP Client V3.1.1 Copyright 2004-2008 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/pan0/9e:6c:4b:98:32:47 Sending on LPF/pan0/9e:6c:4b:98:32:47 Listening on LPF/eth0/40:61:86:16:9c:40 Sending on LPF/eth0/40:61:86:16:9c:40 Listening on LPF/ra0/00:24:21:97:41:75 Sending on LPF/ra0/00:24:21:97:41:75 Sending on Socket/fallback DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 14 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 19 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 18 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 20 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16 DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 13 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on pan0 to 255.255.255.255 port 67 interval 1 No DHCPOFFERS received. No working leases in persistent database - sleeping. * Reloading /etc/samba/smb.conf smbd only ...done. ------------------------- * VI. querying nslookup google.com... ;; connection timed out; no servers could be reached

Finally an inxi command, to help you have a picture of my system:

Code: Select all: sajukk@compu-terataki ~ $ inxi CPU[-Single core Intel Atom N270 (HT) clocked at 800.000 Mhz-] Kernel[-2.6.28-11-generic i686-] Up[-1:22-] Mem[-338.1/2003.4MB-] HDD[-250.1GB(29.1% used)-] Procs[-137-] Client[-Shell-] inxi[-1.0.6-]

And the same command with the -F option:

Code: Select all: sajukk@compu-terataki ~ $ inxi -F System: Host compu-terataki Kernel 2.6.28-11-generic i686 (32 bit) Distro Linux Mint 7 Gloria - Main Edition CPU: Single core Intel Atom N270 (HT) cache 512 KB flags (sse3 nx) bmips 3199.78 Clock Speeds: (1) 1600.00 MHz (2) 800.00 MHz Graphics: Card Intel Mobile 945GME Express Integrated Graphics Controller X.Org 1.6.0 Res 1024x600@60.0hz Audio: Card Intel 82801G (ICH7 Family) High Definition Audio Controller driver HDA Intel Sound: Advanced Linux Sound Architecture Version 1.0.18rc3 Network: Card-1 RaLink RT2860 driver rt2860 v: 1.8.0.0 Card-2 Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller driver r8169 v: 2.3LK-NAPI at port d000 Disks: HDD Total Size: 250.1GB (29.1% used) 1: /dev/sda ST9250315AS 250.1GB Partition: ID:/ size: 186G used: 68G (39%) ID:swap-1 size: 1.00GB used: 0.00GB (0%) Info: Processes 137 Uptime 1:24 Memory 338.0/2003.4MB Client Shell inxi 1.0.6

My computer is a netbook which already has a wired ethernet adapter (eth0 above), and a wireless one (ra0) as well. However, I still want to make the new adapter work, because it is a high-gain one with external antenna, which i really need. So please don't criticize me for wanting a second wireless adapter, but please try to help because I am beginning to lose my faith in linux, and my buddy who is a windows lover (yuck!) says this is proof that windows is better, but that is a matter for psychiatrists to work on.

I KNOW the device is there. lsusb does not lie. I just need to make the system use it, but i have no idea where to start from.
Thanks in advance. Hope to find some help on this.

by **remoulder** on Mon Feb 22, 2010 3:24 pm

sajukk wrote:TP-LINK TL-WN722N, with Atheros chipset

Sorry, this device is currently not supported by any open source driver. A driver is in development, see http://linuxwireless.org/en/users/Drivers/ath9k_htc, and you may get this by the latest installing compat-wireless, see http://forums.linuxmint.com/viewtopic.php?f=53&t=39238 and updating your kernel.

The only other way, which you have already tried, is to use the Windows drivers but I don't thing ndiswrapper, the software that allows you to use Windows drivers, currently supports that chipset either.

It is detected as a usb device but without the drivers the system cannot initialize the wireless connection.

by **sajukk** on Mon Feb 22, 2010 8:10 pm

That's really sad to hear, I thought there was always a way to make something work in linux...

One last question: How do you know what EXACTLY my chipset is?
In the site you gave me, it mentions quite a lot of them
# AR2427 (no 802.11n hardware support, its bonded out)
# AR5008
# AR5418+AR5133
# AR5416+AR5133
# AR5416+AR2133
# AR9160
# AR9280
# AR9281
#AR9285 (>= 2.6.29)
#AR9287 (>= 2.6.32)
#AR9102 (AHB) (>= 2.6.30)
#AR9103 (AHB) (>= 2.6.30)

Is there a way to find which chipset exactly a card has? All the commands i have run said i just have atheros, without any other info

Thanks again

by **remoulder** on Tue Feb 23, 2010 12:19 pm

sajukk wrote:Is there a way to find which chipset exactly a card has

From lspci

ID 0cf3:9271 Atheros Communications, Inc.

Now see http://linux-wless.passys.nl/query_part.php?brandname=TP-Link and http://linuxwireless.org/en/users/Devices/USB

by **Nanoduck** on Sat Mar 05, 2011 11:37 am

I have the same wireless card. I can't get it to work with Linux Mint either but it works with Ubuntu flawlessly...all I did was plug it in and it detected it. Wonder why Linux Mint (which is based on Ubuntu) doesn't do the same.

by **Digital_Resistance** on Thu Apr 28, 2011 4:58 pm

Nanoduck wrote:[...] it works with Ubuntu flawlessly...all I did was plug it in and it detected it. Wonder why Linux Mint (which is based on Ubuntu) doesn't do the same.

Exactly which releases, respectively, of Ubuntu and Mint did you try it with? If your edition of Mint is based on a different edition of Ubuntu than the one you tried, that might be the answer.

Reviews on NewEgg for this adapter are quite interesting.

The latest one, dated April 27th, says,

Works with Ubuntu well, had to find a place to download the driver, ath9k_htc, found a .deb package that does the install for you as it didn't work out of box on 10.10. Search sourceforge for that driver if you use Ubuntu.

But many others say this adapter worked right out of the box in Ubuntu and some other distros as well.

Here are some resources I came across that list the Linux status for a number of wireless adapters:

http://linuxwireless.org/
http://linux-wless.passys.nl/query_host ... hostif=USB
http://www.cyberciti.biz/tips/linux-usb ... -list.html

I came across these, as well as this thread, while researching wireless adapters to buy. I currently have the Rosewill RNX-G1W , which has worked plug-n-play for me in several distros, including Mint, but it only supports the b and g protocols and I'm looking for something that supports n now.

by **reff67** on Wed Feb 22, 2012 4:54 pm

Perhaps These 2 Website can Help You

http://www.wikidevi.com/wiki/TP-LINK_TL-WN722N

http://www.backtrack-linux.org/forums/s ... hp?t=47385

by **Digital_Resistance** on Fri Apr 20, 2012 10:11 am

reff67 wrote:Perhaps These 2 Website can Help You

http://www.wikidevi.com/wiki/TP-LINK_TL-WN722N

http://www.backtrack-linux.org/forums/s ... hp?t=47385

Thanks for the links.

Since my last post, I have purchased this adpater (TP-LINK TL-WN722N) and tried it with several different distros. Most recognized the adapter as as soon as I plugged it in but some didn't.

Mac spoofing with Gnu Mac Changer ("macchanger" in the repos) did not work for me with this adapter.

In contrast, the Rosewil RNX-N2X, another wireless "n" adapter that I also got after making my previous post, has:
a) been recognized by more distros than the TP-LINK, and,
b) never given me any trouble with macchanger that I can recall

Lubuntu 11.10 recognized both adapters upon plugging them in.

Ubuntu 10.04.4 recognized the Rosewill but not the TP-LINK.

As for Mint, I'm afraid I cannot recall any specific releases/outcomes with any certainty but I would be rather surprised if at least one of the two adapters did not work in most, if not all, Mint releases.

Lest anyone is really desperate to know whether one or both of these adapters is recognized by Mint 12 KDE (and you've already tried searching here, Google, NewEgg reviews, etc.), I may be able to help.

As of this posting, I still have Mint 12 KDE on a USB stick. So if you want me to test it for you, you can reply here and if I still have it, I will try to boot into the live USB and report back.

by **tecke** on Sun Sep 02, 2012 11:59 pm

Old post but who ever still is having issues with this wireless card can use this fix.

echo 'install rt2800usb modprobe --ignore-install rt2800usb ; /bin/echo "148f 5370" > /sys/bus/usb/drivers/rt2800usb/new_id' | sudo tee /etc/modprobe.d/rt2800usb.conf

sudo modprobe -v rt2800usb

Linux Mint Forums

War with a TP-LINK TL-WN722N usb wireless adapter

War with a TP-LINK TL-WN722N usb wireless adapter

Re: War with a TP-LINK TL-WN722N usb wireless adapter

Re: War with a TP-LINK TL-WN722N usb wireless adapter

Re: War with a TP-LINK TL-WN722N usb wireless adapter

Re: War with a TP-LINK TL-WN722N usb wireless adapter

Re: War with a TP-LINK TL-WN722N usb wireless adapter

Re: War with a TP-LINK TL-WN722N usb wireless adapter

Update: Recognized by Some, Not All

Re: War with a TP-LINK TL-WN722N usb wireless adapter

Who is online