Arch Linux

I've experienced the same problem. The device won't be recognized even after unplugging and plugging it back, though.
Kernel: 5.4.47-1-lts

Has anyone bisected the kernel (5.7 or 5.4) to find the bad commit? I'm about to do this, but I'm using an old Core 2 Duo, so this might take a while unfortunately. Since I don't see anything useful in dmesg or the journal I think bisecting is the best way to help the kernel developers identify the bug.

You can use the ALA [1] to find a good kernel. If you can not locate a good kernel, bisection will not work.
Bisecting between two stable kernels will generally be quicker than between two mainline kernels.

[1] https://wiki.archlinux.org/index.php/Arch_Linux_Archive

5.7.2 is good. Downgrading is a workaround.

Please bisect between 5.7.2 and 5.7.3.

I'm using an old Core 2 Duo too, so it'll take time.

So the first build was actually good (the firmware was loaded correctly), but for some reason wpa_supplicant didn't work as it should and GDM broke and I couldn't switch to the tty. Perhaps some of the commits depend on each other and bisecting between them breaks things, so I will probably build a kernel (based on 5.7.4) without the bad commit when I have finished the bisection to be sure that this commit is really the bad one. Let's just hope that I don't run into a build failure.

There is already an upstream bug report [1], but we still have to find the bad commit.

[1] https://bugzilla.kernel.org/show_bug.cgi?id=208251

wpa_supplicant broken since 5.4 for me. Or actually even earlier, but since 5.4 there are kernel panics instead of minor fails. Not always, just sometimes when initializing the interface, other times it works fine. I don't think this bugs are related, i actually hope 5.7.3 changes (when properly fixed) will fix panics.

I finished the bisection and reported it upstream. I will test if reverting the bad commit helps.

Thanks a lot!

If you do not receive a response in a few days you could reply to [1] which added it to 5.7.Y or [2] the original commit or add the commits author to the bug report.

[1] https://lore.kernel.org/netdev/20200608230607.3361041-94-sashal%40kernel.org/
[2] https://lore.kernel.org/linux-wireless/20200404041838.10426-6-hqjagain%40gmail.com/

I can confirm that this bug still exists in kernel 5.6.7, checking dmesg the device seems to be correctly detected, and the driver correctly selected but never actually loaded.
The specific device I am testing is the exact same one as in the OP.

Running into the same issue with tp-link tl-wn722n on 5.7.7

Same problem with 5.4.50-1-lts, no problem on other distros

Can you confirm the issue is fixed in linux 5.7.8.arch1-1 and linux-lts 5.4.51-1 currently in testing?

On a TP-Link TL-WN722N, upgrading to `5.7.8.arch1-1` appears to resolve the issue for me.