TL-wn722N driver problem

[DavisBre]

Hello!

I have problem with TL-wn722Ndriver I did everything what is written here: https://wiki.debian.org/ath9k
But without results.

More information about device:
https://wikidevi.com/wiki/TP-LINK_TL-WN722N
http://www.tp-link.com/us/download/TL-WN722N.html

Any suggestions?

Thanks,
Davis

[stevepusser]

Read that wikidevi page a bit more carefully. It uses the ath9k_htc driver for USB devices, not the ath9k driver for PCI hardware. As such, it requires the non-free firmware-atheros package to get it up and running. You can directly download and install the deb package from here: https://packages.debian.org/jessie/kern ... re-atheros if you don't want to go through the hassle of adding and enabling the non-free section.

[sunrat]

What version of that device do you have? Earlier ones were Atheros and should work with just installing firmware. The V4 is Realtek and requires compiling a driver from Github, and firmware-realtek.

[DavisBre]

I have Debian 8 Jessie. I did what stevepusser has written. Installed package with sudo dpkg -i, followed by sudo apt-get install -f. Configured wicd manager as written in instruction. and still my wifi antena does't run.

Can't find any other information on device, later today will take a look on windows pc, which companys driver is installed.

Thanks,
Davis

[stevepusser]

It should be easy to determine the chipset on Linux, just plug it in and type "lsusb" in the terminal.

Also you can check the output of the "dmesg" command to see what's happening when it's inserted. Usually missing firmware will throw an error message.

[DavisBre]

I'm pretty new to linux, so this is what i get from dsmeg:

Code: Select all

[  188.836052] usb 5-1: new high-speed USB device number 4 using ehci-pci
[  188.984883] usb 5-1: New USB device found, idVendor=0cf3, idProduct=9271
[  188.984891] usb 5-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
[  188.984895] usb 5-1: Product: USB2.0 WLAN
[  188.984898] usb 5-1: Manufacturer: ATHEROS
[  188.984901] usb 5-1: SerialNumber: 12345
[  190.132587] cfg80211: Calling CRDA to update world regulatory domain
[  190.197875] cfg80211: World regulatory domain updated:
[  190.197885] cfg80211:  DFS Master region: unset
[  190.197887] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[  190.197892] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[  190.197896] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[  190.197899] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[  190.197902] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[  190.197907] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[  190.197910] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[  190.197913] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[  190.197916] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[  190.264762] usb 5-1: ath9k_htc: Firmware htc_9271.fw requested
[  190.265886] usbcore: registered new interface driver ath9k_htc
[  190.276848] usb 5-1: firmware: direct-loading firmware htc_9271.fw
[  190.563503] usb 5-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
[  190.801332] ath9k_htc 5-1:1.0: ath9k_htc: HTC initialized with 33 credits
[  191.069914] ath9k_htc 5-1:1.0: ath9k_htc: FW Version: 1.3
[  191.069923] ath: EEPROM regdomain: 0x809c
[  191.069925] ath: EEPROM indicates we should expect a country code
[  191.069928] ath: doing EEPROM country->regdmn map search
[  191.069930] ath: country maps to regdmn code: 0x52
[  191.069932] ath: Country alpha2 being used: CN
[  191.069934] ath: Regpair used: 0x52
[  191.113835] ieee80211 phy0: Atheros AR9271 Rev:1
[  191.115677] cfg80211: Calling CRDA for country: CN
[  191.129431] cfg80211: Regulatory domain changed to country: CN
[  191.129440] cfg80211:  DFS Master region: FCC
[  191.129443] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[  191.129447] cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[  191.129452] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (N/A)
[  191.129456] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (0 s)
[  191.129459] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
[  191.129462] cfg80211:   (57240000 KHz - 59400000 KHz @ 2160000 KHz), (N/A, 2800 mBm), (N/A)
[  191.129466] cfg80211:   (59400000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4400 mBm), (N/A)
[  191.129469] cfg80211:   (63720000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 2800 mBm), (N/A)

I have installed that firmware, what could be seen in synaptic package manager, and that package should support my device. So what can I do to make it work?

[stevepusser]

Oh, you're using wicd. You probably have to tell wicd which wireless interface to use, since it doesn't load them automatically. See what network interfaces you have with (as root or with sudo) with the device plugged in:

Code: Select all

ifconfig -a

Then go into wicd's preferences and set it to use the wireless interface.

Code: Select all

[  191.129431] cfg80211: Regulatory domain changed to country: CN

I have one of these adapters too, and though that country code is China, it doesn't seem to affect it here in the US. It works just fine with the defaults and network-manager or wicd. If you have both installed at once, network-manager can try to grab the interface first and manage it, leaving wicd out in the cold--so you have to have tell network-manager to not manage wireless.

[dibl]

I use a TL-WN821N / TL-WN822N, which is an Atheros chip that uses the ath9k_htc driver, and had a similar problem. It was fixed by creating a file named /etc/modprobe.d/ath9k_htc.conf. The content of that file is the following:

Code: Select all

#Option required for ath9k_htc module on TP-Link WN-821N
options ath9k_htc nohwcrypt=1

[sunrat]

I use a TL-WN821N / TL-WN822N, which is an Atheros chip that uses the ath9k_htc driver, and had a similar problem. It was fixed by creating a file named /etc/modprobe.d/ath9k_htc.conf. The content of that file is the following:

Code: Select all

#Option required for ath9k_htc module on TP-Link WN-821N
options ath9k_htc nohwcrypt=1

I think that issue was fixed in the relevant packages some time ago. I'm using the same device with kernel 4.7 and backports firmware and it works well without it.

[DavisBre]

Thank you all for helping to find salution. I couldn't make this device working on Debian. My salution was Xubuntu. Enabled online update during installation and everything worked "out of the box".

Davis