I am not an expert and just cobbled this together based on a couple of searches but my guess would be that the adapter is supported by your current kernel drivers but not as well as whatever drivers Windows 10 was able to fetch. It looks to me like MX uses Debian Stable sources, so you may be able to update your kernel beyond what is normally available and see if that helps. If that doesn't work, based on this post and this post on the TP-Link forums, there's a github repo that you may be able to install a better driver from. To my eyes there's fairly good instructions there, including the potential need to disable the driver you're already using in favor of the new one once you build it.
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
i had something similar on my kubuntu/win7 dual-boot.
iirc i fixed it by disabling the powersave of my wifi-adapter.
don't remember the exact command at the moment though. 🤔
sudo iwconfig wlan0 power off
Replace "wlan0" with the name of your Wi-Fi interface if it's different.
Is this the one?