8814au VS 88x2bu

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.

I use an Archer T3U to use wifi off of my desktop machine. It doesn't have a linux native driver, but this one works for me so far.

I use this driver instead, but I think it all comes down to what does your wifi card need. You can download the driver in another computer and then pass it with a usb stick or, connect through your mobile phone via tethering and then download the driver directly in your computer

I installed DKMS and this 88x2 github driver recommended by this post.

Device connects and functions properly in normal operation with the following driver: https://github.com/morrownr/88x2bu.git

My original rEFInd configuration got overwritten by the non-graphical GRUB from HoloISO. However, I was still able to boot into all OSes. I went ahead and booted into SteamOS to test. My WIFI dongle was dead, so I used my phone in USB tether mode to have internet access. I downloaded the drivers for my WIFI dongle from my usual source off Github (https://github.com/morrownr/88x2bu). I booted back into Ubuntu and re-installed rEFInd so I can have the GUI OS selector.

Seems like you have to use a third-party driver from github. Probably this one. Carefully read the instructions. Also you should install additional firmware for your card. Good luck.

I use the TP Link Archer T3U which has an RTL8812BU WiFi chip. The driver can be found at https://github.com/morrownr/88x2bu but needs to be compiled (instructions are at the web page itself).

He'll have to compile the kernel module from scratch. Here's a git repository for the Realtek RTL8812BU and RTL8822BU driver: https://github.com/morrownr/88x2bu