Hello everyone, I’m trying to get a TP-Link Archer T4U V3.2 USB WiFi adapter to work on my Raspberry Pi 2 with Raspberry Pi OS (5.15.32-v7+).

The amount of time spent tying to get this to work is killing me, every error I fix another pops up... A lot of the other forum posts I've found are out of date or don’t apply. Also, is it normal for the LEDs to not light up while in the PI2 but light up when plugged into a laptop? Doesn’t show up when I check ifconfig.

What I’ve tried so far:

Installing the official Linux drivers (not working)
https://www.tp-link.com/ca/support/download/archer-t4u/

Bypassing make file and installing other drivers (still not working)
http://downloads.fars-robotics.net/
http://downloads.fars-robotics.net/w...s/install-wifi

Updating the headers, trying the official again (nope)
https://github.com/gnab/rtl8812au/issues/147
sudo apt-get install raspberrypi-kernel-headers

Copying header files from one folder to another (further along but still no)
sudo cp -r /usr/src/linux-headers-5.15.32-v7+/* /lib/modules/5.15.32-v7+/build/

Now I get this error after trying to make the official drivers:

The Pi2 setup is headless meaning command line only (no Xwindows) and I SSH into it with different less powerful WiFi dongle (I need both to run at the same time). The end goal is the less powerful one will connect to my phone and the TP-Link Archer T4U V3.2 connects to other networks but I don't want to get ahead of myself, trying to get the TP-Link to work is the focus of this post.
Thanks.

net/ipx.h is /usr/include/net/ipx.h, part of glibc. You probably need to install glibc-devel, if there is such a package.

RPi OS is based on Debian, which installs skimpy but functional packages. You're compiling. You'll need devel packages for anything that's involved. A simple web search would probably have got you that much.

1 members found this post helpful.

Ok thanks, I'll update you when I try some more.

Interesting point, I didn't realize how important that would be.

If anyone has some experience with the TP-Link Archer T4U V3.2 USB WiFi dongle and Raspberry Pi 2 (5.15.32-v7+) or similar, don't hesitate to post! That one little idea you have could end up fixing everything.

I actually needed it and found it in /usr/include/netipx/ipx.h in glibc-2.33

EDIT: One other thing: These Pis are big users of usb wifi dongles, and distributions go to considerable lengths to bend some very dodgy drivers straight to support these dongles for you . Have a good hunt in /lib/modules/<kernel-version>/kernel/drivers/net/wireless, as there's probably more support for usb wifi than you'll find in the mainline kernel.

1 members found this post helpful.

Found another thread that's a little different but same error and fixed with newer drivers. Once I get a little more free time I'm going to try everything suggested so far.

https://forums.debian.net/viewtopic.php?t=151844

OMFG! IT LIGHTS UP NOW!! When I type ifconfig it shows the TP-Link Archer T4U V3.2 USB WiFi adapter as wlan1 and my other adapter as wlan0. No ethernet is plugged into eth0.

Here is what I did:

I copied /usr/include/netipx/ipx.h to /usr/include/net
cp /usr/include/netipx/./ipx.h /usr/include/net

Then I fallowed these instructions from https://github.com/cilynx/rtl88x2bu

Thanks for your help business_kid!

I'm going to test it out more and find out the command-line syntax to send, receive and connect to stuff only from TP-Link Archer T4U AKA wlan1 through wlan0 then I'll get back to you.

EDIT:
Also, when I ping it from other computers on the network I get a replay so that's good.

If you have two working wireless wifi adapters (wlan0, wlan1) and you only want to see the stats of one of them type (might need to put sudo before these commands and take out wlan1 to see for all):

sudo ifconfig wlan1
(this one is my TP-Link Archer T4U 3, if you only have one wifi adapter change wlan1 to wlan0 for all the commands below)

A way to list all network interfaces type:
ls /sys/class/net

To make sure it’s up and running type:
sudo ifconfig wlan1 up

To stop it type:
sudo ifconfig wlan1 down (it needs to be up to work)

Scan for wireless networks type (I’m doing this with wlan1 because the TP-Link Archer T4U has a better and bigger antenna then my other wifi adapter. If you only have one adapter you should probably use lwan0):
sudo iwlist wlan1 scan

To see just the wireless network names (ESSIDs, that strait line is called a “pipe” it takes output from one command and puts it in another) type:
sudo iwlist wlan1 scan | grep ESSID

To connect to a wifi network type:
iwconfig wlan1 essid NETWORK_NAME key s:WIRELESS_KEY_PASSWORD
(if the password is not ascii you might have to take out “s:” after key.)

Connect to a WPA/WPA2 wifi network with wpa_supplicant:
Here is a website to help you
https://linuxcommando.blogspot.com/2...i-network.html
and a video I found on the topic of connecting to WPA/WPA2 wifi networks using wpa_supplicant.
https://www.youtube.com/watch?v=QGyHDIYlLFA

If you are connected but not getting an IP address, get one by typing:
sudo dhclient wlan1

If you want more information type
sudo iwconfig wlan1

Quick hack, if you have a nub or crappy wifi antenna, plug your USB wifi adapter into a USB extension cable and move it around to a better spot but you are better off getting an adapter with a bigger antenna. If you want to do more advance stuff including monitoring mode, make sure to read up on your wifi adapters features and find out if it’s compatible with your system before you buy it.

Most routers have two bands 2.4GHz and 5GHz, you may want to separate your wireless adapters to other signals if you are getting slow speeds because of interference.

If you want to install graphical user interface for your Wifi adapters and Ethernet like nmtui (network-manager) it will force a change of your IP addresses (kick you off your headless connection) and you’ll have to go looking for those new IPs. Also, some commands will stop working (I had to remove it). If anyone has a suggestion of a CLI-Based GUI application for networking that wont change your settings post it here please.

If you have anything to add let me know.

Thanks for pointing out this method of compiling a loadable kernel module! It also worked for me on my Pi 4B.