Hello everyone, First of all I apologize for my bad English.
I’m starting with Dietpi and I block to be able to operate in wifi with a TP-Link Archer T3U.
I have an RPI 2 Model B V1.1 I installed Dietpi V7.
I use Chromium in autostart only.
I have AUTO_SETUP_NET_WIFI_ENABLED=1
and in the “dietpi-wifi.txt” file I have filled in the information of my router.
It doesn’t seem to detect the wifi dongle.
How can I make this work?
Thank you in advance for your assistance.
I believe you need to select the country first to be able to select the proper channels. You can do this using the raspi-config application: select the ‘Localisation Options’ menu, then ‘Change Wi-Fi Country’.
changing the country code is possible using dietpi-config network settings as well. It’s shown on the screen shot.
Anyway what happen if you hit Scan? Does it show your WiFi network?
Thanks a lot for your help.
I added the country.
I did Apply: save all changes and restart networking then I went to scan.
I see my SSID of my open network (without password).
If I scan it doesn’t work.
It doesn’t seem to detect the dongle
one thing first. If possible, try to avoid screen prints. You simply could copy all content from SSH terminal and post it into a code tag within the forum.
The issue seems to be the wifi adapter and missing drivers. I found something on a Ubuntu forum. It’s might not fit 100% as it is Ubuntu https://community.tp-link.com/en/home/forum/topic/208022
Maybe you need to check with TP-Link if they are drivers needed for Debian or you try the solution from Ubuntu forum.
@Joulinar, I’ll give you a little feedback from yesterday’s tests.
I wanted to install the drivers that you send me in the link.
but it does not work, it would take drivers for ARM HF but I have the impression that it does not exist.
I will see on the forum of TP link.
I am not attached to using this device, if you have another solution to have Wifi I will gladly take it.
personally I don’t use WiFi dongle. Therefore I could not recommend one. But I know MichaIng has some.
For those WiFi 5 and higher adapters, the RPi kernel does not natively ship with drivers. So those need to be compiled currently. Here seem to be sources, but I just did a very quick search, would be good to find the official ones from Realtek or TP-Link: https://github.com/kevin-doolaeghe/rtl88x2bu_wifi_driver
I have two RTL8811CU chip adapters here, quite similar. I didn’t find the time to test them yet, but will do soon after Easter holidays. If compiling and using it goes well, I’ll see if we can host driver packages with the sources and making use of DKMS so that drivers are recompiled automatically on kernel updates.
I tested the link you sent me unfortunately the dongle still does not work.
I read on some forums that it was necessary to put it on hubs with power supply because in some cases the dongle consumes too much.
I’m surprised but I’ll give it a try. otherwise I would redirect to another model.
Here is the steps how to build and install it, using the sources which are closest to what one could call “official”:
curl -sSfLO 'https://github.com/cilynx/rtl88x2bu/archive/refs/heads/126.96.36.199_35809.20191129_COEX20191120-7777.tar.gz'
tar xf 188.8.131.52_35809.20191129_COEX20191120-7777.tar.gz
sed -i -e 's/I386_PC = y/I386_PC = n/' -e 's/ARM_RPI = n/ARM_RPI = y/' Makefile
Power consumption shouldn’t be an issue as long as you do not have other heavy USB devices attached, like 2.5" USB drives (which should be always powered with dedicated PSU) or such.
Not 100% sure in case of Archer T3U, but some WiFi adapters are in a data drive mode when being attached the first time: They contain a ROM with Windows drivers which can be installed then, which triggers the switch to WiFi adapter mode. There is a tool which can be used to manually switch modes on Linux: https://packages.debian.org/bullseye/usb-modeswitch
But whether this is really true should be easy to find out by checking e.g. fdisk -l for a new USB drive, respectively lsusb or dmesg about as what this USB device is detected.
The drivers don’t work but I’m making slow progress.
I can see my two wifi dongles
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 * 8192 270335 262144 128M c W95 FAT32 (LBA)
/dev/mmcblk0p2 270336 124735487 124465152 59,3G 83 Linux
Bus 001 Device 007: ID 2357:0109 TP-Link TL-WN823N v2/v3 [Realtek RTL8192EU]
Bus 001 Device 006: ID 1997:2433 Shenzhen Riitek Technology Co., Ltd wireless mi ni keyboard with touchpad
Bus 001 Device 005: ID 0483:5750 STMicroelectronics LED badge -- mini LED displa y -- 11x44
Bus 001 Device 004: ID 2357:012d TP-Link Archer T3U [Realtek RTL8812BU]
Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) SMSC 9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) SMC9 514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
With “dmesg” I see wifi :
[ 5.343678] systemd: Starting Load Kernel Module configfs...
[ 5.358232] systemd: Starting Load Kernel Module drm...
[ 5.367220] usb 1-1.5: New USB device found, idVendor=2357, idProduct=0109, b cdDevice= 2.00
[ 5.373074] systemd: Starting Load Kernel Module fuse...
[ 5.374610] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber =3
[ 5.384763] usb 1-1.5: Product: 802.11n NIC
[ 5.384793] usb 1-1.5: Manufacturer: Realtek
[ 5.384806] usb 1-1.5: SerialNumber: 00e04c000001
[ 5.405633] systemd: Condition check resulted in Set Up Additional Binary
I ordered a new RT5370N 150Mbps wifi dongle normally it should work. —> https://www.amazon.fr/gp/product/B073J3HXZH/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
I wouldn’t have the same speed but if it works it’s not bad. I receive it during the day.
I received my RT5370N 150Mbps and it works without problem. I will stick with this solution for now.
Thank you for your help.
ok that’s how it should be. Sorry that the first adaptor was not working well.
The Archer dongles were not visible as network interfaces, e.g. via “ip l”? Thats is sad. The RTL8811CU dongles I have do work well with compiled drivers, although tested on NanoPi R4S only so far. With next Armbian kernel release they will even work OOTB, the driver that ships with the kernel has just been updated to match the one I compiled. Since it’s a 3rd party driver, not merged into upstream Linux yet, the RPi Foundation however won’t ship it with the RPi kernel. I was thinking to provide them as DKMS based installer package. Probably the same can be done for the Archer T3U, when we find working driver sources.