Hi, I'm having the exact same problem.it also works that another wlan adapter is connected and you will see wlan1. The interesting thing - or to say the reason is at least mostly clear to myself.it works well until a firmware (raspberry) before End of March. Go back to rpi-update from feb or march and all will be fine. I also asked this several times now, nobody seemed to care.there is something wrong in the later firmware updates for Raspberry. Maybe one day it will be fixed. For me its annoying as I really would like to update to latest rpi updates but as soon as you do so - you again have the issue of vanishing WLAN1.

• Linux Ath9k

Maybe I'm wrong but from what I recently experience. Also your three commands will update the kernel version e.g., which in my case did result in this problem.kernel before april are fine, afterwards this problem is shown for any kernel until the most recent ones. At least if I do a rpi-update back to March and afterwards an apt-get update/upgrade with some libraspberrykernel aso.stuff that gets updated again the version if linux kernel will update to june/july and again the same problem arises.to seems not to be a rpi-update problem but a kernel/whatever comes with this apt-get upgrade packages along. OK, first off the PI 3 has its own built in wifi module so did you disable it before trying your two TL-WN722n wifi modules. If you didn't then only one of your additional wifi modules will work unless you modified the configuration files. I currently have a Pi 3 B running with the built in wifi and a TL-WN722N and another wifi module, a Netgear WNA1100 as I don't have a second WN722N, using the same ath9khtc driver, so have three wifi modules running, with the additional two using the same ath9khtc driver. To do this I had to add an extra section to file /etc/network/interfaces adding the following.

Direct firmware load for ath9k_htc/htc_9271-1.4.0.fw failed with. Ath9k_htc: Firmware htc_9271.fw requested [48] usb 2-1.1: ath9k_htc: Transferred FW. I am having trouble placing firmware properly on an Android device, I keep getting: [ 3590.997375] usb 3-1.4: ath9k_htc: Firmware - htc_7010.fw not found If on. USB WiFi adapter using ath9k_htc not working. To the one listed here on h-node which is supposed to work using the ath9k_htc. Firmware: failed to load htc.

Code: allow-hotplug wlan2 iface wlan2 inet manual wpa-conf /etc/wpasupplicant/wpasupplicant.conf If you disable the built in wifi module then you do not need to update file /etc/network/interfaces. Command ifconfig shows wlan0, wlan1 and wlan2. If I disable the built in wifi then the two modules using the ath9khtc driver run OK and ifconfig shows wlan0 and wlan1. I suppose there may be an issue when using two of the same modules but I've tried the Pi 3 B with several different pairs of other types of wifi modules, although none used the ath9khtc driver and I had no problems getting both modules working MrEngman.

Thanks for your feedback. Dowload gta san andreas tpb. YES as I do not like the internal WLAN i generally disable(blacklisted BT and WLAN onboard).but for your information, no matter if you disable or not, it simply would add another WLAN2 to the iflist. In my case never had any issues with the internal one, only disabled because of power consumption reasons.

As already said, in case you do not use 2 of the 722N sticks it is never an issue.only in case you use 2 of them and do a kernel update via apt-get that brings you to a kernel that is after March'2016. but I've tried the Pi 3 B with several different pairs of other types of wifi modules, although none used the ath9khtc driver and I had no problems getting both modules working. As said, me and the other guy only run into this issue when using two of the 722N radios.the reason for using them is the external antenna + AP mode + very good power gain. Hi together, first of all it is quite hard to find some content for using two tplink wn722n on a raspberri pi. As the previous writers already mentioned, this issue only occurs by using the two wn722n dongles at the same time (all other constellations with edimax or other tplink products works great). Because the last post is nearly a year old and that I couldnt find any solution yet I want to ask the community again if there are any ideas.

My current setup: - rpi3 - 2x tplink wn722n - raspbian jessie / Linux version 4.9.31-v7+ - latest pri firmware / raspberrypi-firmware soc:firmware: Attached to firmware from 2017-06-08 13:29 dmesg: 2.242176 systemd1: Starting Remote File Systems (Pre). Hi t1nk3r, I had a look at this issue when it was first raised but decided to take another look. I've done a bit of experimenting to see how things are now. First I tried with two TP-Link TL-WN722N wifi adapters connected to the Pi 3, with the built in wifi disabled.

The results were similar to your's. Only one wifi adapter started up. I then unplugged the non-working one, waited a short time, then plugged it back in again. This made no difference and the second wifi adapter would not work. Checking with command lsusb it showed two wifi adapters connected. I unplugged the non-working adapter and used command lsusb again and surprisingly it still showed two wif adapters were connected.

I then rebooted with a single wifi adapter connected and the Pi booted and the wifi came up OK. I then plugged in the second adapter and that then came up OK. Checking with command lsusb it showed two adapters. Unplugging the second adapter and checking with command lsusb and this time it only showed a single adapter connected so things appeared to be working OK now.

I then tried replacing the two TL-WN722Ns with two TP-Link TL-WN823N wifi adapters using the 8192cu driver. Booting the Pi with these two adapters connected and both came up OK. I then swapped these two adapters for two TP-Link TL-WN725N wifi adapters using the 8188eu driver and after the Pi booted again both wifi adapters came up OK. Finally I tried something slightly different.

I connected one TL-WN722N and a Netgear WNA1100 wifi adapter to the Pi. Both these adapters use the same ath9khtc driver. After booting the Pi only one adapter was working, just like when two TL-WN722N wifi adapters were used. The first time I tried the Netgear WNA1100 wifi was working. I then swapped the USB connectors the wifi adapters were connected to and this time after booting the TL-WN722N wifi was working. The other odd thing, similar to when I tried with two TL-WN722N adapters, unplugging the non-working adapter and checking with command lsusb and even though only one wifi adapter was connected to the Pi lsusb showed both adapters connected. The results I've seen today using the TL-WN722N and WNA1100 wifi adapters appear to contradict the result in my earlier post using the same adapters which appears to say the Pi will boot OK with these different adapters connected.

Think I need to try with an older version of the kernel to check unless I was plugging in the second adapter after the Pi had booted. Really can't remember.

Linux Ath9k

Just tried using kernel image 2016-02-26-raspbian-jessie-lite, kernel version 4.1.18-v7+ #846, and amazingly I have the Pi 3 booting with two TL-WN722n wifi adapters connected and both apparently running OK. Built in Broadcom wifi is disabled. Hi t1nk3r, Just done a couple of more tests. Looks like the problem occurs after the kernel is updated from kernel 4.1.xx to kernel 4.4.xx.

Just ran command sudo rpi-update to update the kernel to 4.9.31-v7+ #1005. Pi boots with only one TL-wn722N working. Did a modinfo ath9khtc to check wifi module info and noted the wifi driver used by kernel 4.9.31-v7+ #1005 uses a different firmware version to the one used by kernel 4.1.21-v7+ #911 which is the last one I had working OK. So now tried commands.

Really don't know what the problem is with the Atheros wifi driver but today I had problems with the SD card so had to create a new one. Formatted the SD card and installed the image 2016-02-26-raspbian-jessie-lite as I originally did. Both wifi modules worked OK. I then went through the steps I did previously and it all behaved very strangely.

First updated to kernel 4.1.21-v7+ and both wifis continue working OK. Then updated to kernel 4.4 and strangely, unlike before, both wifi modules continued to work OK. Then updated to kernel 4.9.31-v7+ and both wifi adapters again continued working OK. Really, really weird.

This was without updating anything to do with the wifi. Last time I updated the Atheros firmware but did not this time. I then looked at the wifi modules using command modinfo The original driver in kernel 4.1.18-v7+ from the 2016-02-26-raspbian-jessie-lite image using modinfo showed.

Code: filename: /lib/modules/4.9.31-v7+/kernel/drivers/net/wireless/ath/ath9k/ath9khtc.ko firmware: ath9khtc/htc9271-1.4.0.fw firmware: ath9khtc/htc7010-1.4.0.fw description: Atheros driver 802.11n HTC based wireless devices license: Dual BSD/GPL author: Atheros Communications srcversion: A3B5F06E4895CAF68FD140B with firmware ath9khtc/htc9271-1.4.0.fw and ath9khtc/htc7010-1.4.0.fw Looking at the firmware available in kernel 4.9.31-v7+ only htc9271.fw and htc7010.fw were available. The firmware which appears to be used by the Atheros driver in kernel 4.9.31-v7+, ath9khtc/htc9271-1.4.0.fw and ath9khtc/htc7010-1.4.0.fw, did not exist. I had a hunt around on the internet and found this site with the firmware referenced by the Atheros wifi driver. When I created the previous SD card and got things working I had done a firmware update but this did not install the ones the driver was referencing even though it appeared to get things working with my previous SD card.

I have now updated the firmware to use the ones from the link above and things are working OK. I updated the firmware using commands.

Code: wget wget sudo mkdir /lib/firmware/ath9khtc sudo mv htc.fw /lib/firmware/ath9khtc/. MrEngman Thank you! Your solution is the only thing that worked for me.

I don't know why I never noticed from the dmesg log that it was always having problems loading the firmware. The first try, it would always fail. There was no /lib/firmware/ath9khtc folder. So it makes sense it failed to load the drivers from that folder.

I no longer receive the error.