8814au VS rtl88x2ce-dkms

I ended up returning AWUS036ACM and buying AWUS1900 (based on Realtek chipset). Installed appropriate drivers https://github.com/morrownr/8814au and everything is working as expected! No issues so far. Working on both the Kali virtual machine and the raw Debian machine. Lesson learned - stay away from Mediatek.

I have same and got it to work using this driver on Github. The thing u/LoveFOSS recommended didn't work for me at all, but ymmv.

I've installed the driver for my NIC here

I'm trying to setup a local mumble server which clients can connect to over wifi, all provided by my AWUS1900 network card. I've gotten to the point where the NIC works with these instructions, and I setup a local AP following these instructions, but I cannot see the Mumble server running on the Pi3. I am able to connect to the hotspot but I can't ping any devices including the host of the whole server, strangely. When the pi is connected to ethernet to my local network, the mumble server works however.

However, if you're after long range or high speed with the Pi, and don't mind having to custom build a driver, I have this TP-Link Archer T9UH with the Realtek RTL8814au chipset. It needs this driver, which I was able to build by following the instructions on that page. It works like a champ, until there's a new kernel release, in which case it breaks until I rebuild that driver. It does however offer USB3 and 11ac, and has no trouble connecting and maintaining a high speed link (100+mbps) between where it lives in my RV parked in the driveway, and the AP in the back bedroom of my house. This is enough distance where the onboard Pi4 wifi could barely see my network and couldn't even sustain megabit speeds reliably.

I would recommend trying https://github.com/morrownr/8814au this driver, but honestly, the driver and that hardware are trash in terms of Linux support, and I’d highly recommend getting something from https://github.com/morrownr/USB-WiFi/blob/main/The_Short_List.md

It made no sense as to why it was scanning, it's my desktop adapter and only has to connect to a singular network. Anyway i figured it might've been due to roaming so i went and reinstalled the driver i use (i use an adapter with the rtl8814au chip and use this driver: https://github.com/morrownr/8814au), just to be sure i manually set the BSSID in the network settings.

Here's the driver.

Do you really want to use Debian? https://github.com/juanro49/rtl88x2ce-dkms

Okay solved it, for anyone having the same issue, I installed this https://github.com/juanro49/rtl88x2ce-dkms and when I reboot I had to do "sudo modprobe rtl88x2ce" so the way to solve it was to "echo rtl88x2ce > /etc/modules-load.d/rtl88x2ce.conf" and this gets executed whenever you reboot, but I had another line in a file /etc/modprobe.d/*.conf that said "blacklist rtl88x2ce" so this wasn't executing at start, in case you need more help this was where I got the things from https://unix.stackexchange.com/questions/71064/systemd-automate-modprobe-command-at-boot-time

If you're still looking towards fedora or the linux mint drivers didn't work and you think you'll be fine compiling the drivers yourself and fixing issues that may arise then I'd recommend looking at this other project that seems to be more up to date and with proper instructions here, you'd have to follow the manual instructions indicated on the "desde codigo fuente" part. There are no guarantees that this will work flawlessly if at all, this is a solution the community came up with.