Closed choogenboom closed 4 years ago
@choogenboom Thanks so much. I will likely do cut n paste instead of a merge but I will get this information in. I do have Pi 3B and Pi 4B so I can test as I have time.
No problem, good luck! I've personally tested on a Pi 3 with Kali and raspbian image, Pi 4 will also be tested shortly.
After installing the driver on Kali for Raspberry Pi, the 88XXau driver included in the kernel took precedence over the newly installed 8812bu drivers. You can check if this is the case by running usb-devices (in the usbutils package), and see if the 8812bu or the 88XXau driver is used for the device. I'm also not sure why this is happening.
This might not be needed for every case, but in the tests I have run (Kali on Raspberry Pi 3 and 4), somehow the 88XXau driver needed to be blacklisted.
Okay. Copy all. Let me finish testing Raspberry Pi OS and I will try to get back to Kali on RPI when I have the time. The only explanation I have is that the 88XXau.ko driver has a bad device ID. I may need to investigate the device IDs...unless you want to investigate it?
Hi, I was working on support for the TP-Link Archer T4U v3 on a Raspberry Pi and finally got it to work. I've added a build configuration for arm and arm64, based on the Makefile from https://github.com/EntropicEffect/rtl8822bu. Let me know if you have any questions or if there is something I can adjust!