It may be a power issue - do you have anything else plugged into the Pi?
The 3B+ was prone to 'iffy' WiFi with cheap adapters but using the 'official' one normally sorted it.
I would check the country code is set correctly as well on both your AP and Pi
It's possible you are using a very popular channel - fix the working channel on the AP
StackExchange will not let me comment but I'm not convinced this is currently do-able as the ESP01 AT commands only provide raw data stream handling such as:
to send / receive.
Neither Circuit Python or Micropython has support built in for DNS / HTTP so you would be looking at fitting something like the Adafruit ESP32SPI ...
In my case the problem was caused by "File System Check on Root Device" task that timed-out.
The error output was actually the same as yours so it was not very clear to me.
What solved this issue for me was adding:
into /etc/systemd/system.conf (increasing time-out from the default 90s).
Explanation: The issue started ...
Get a powered hub seems to be the "offical" advice I always see on their forum when talking of drives plugged into it. These things are so flaky with their USB if I plug in my keyboard I cannot boot, is my problem with the Pi 4 8GB I have with their implementation of USB. My power supply in the Canakit I got is rated for 3.5A.
This took me far too long to figure out, but in the end I found this guide which shows exactly how to get it working, worked first try for me on a Raspberry Pi CM3: Edimax EW-7811UN V2 driver installation.
To quickly find your kernel version, use the command uname -r. Getting it working does require an existing internet connection, I was using a USB-Ethernet ...
There are USB adaptor hats (or a cable) for Raspberry Pi zero they allow you to plug in the Raspberry PI into your computer (and be power by) as if the Raspberry PI is a Network adaptor.
Which means your host computer can access you RPI0 over network in terms of ssh/NFS/Samba etc.
Add the following to your config.txt
Add the following to your ...
I'm by no means an expert in this, but it looks like you're trying to use the channel 42 (5170-5250 MHz), which appears to be disabled on the Pi 4. You claim to use channel 35, but I see no such channel on Wikipedia.
If fact, only 20MHz channels are actually listed as available on the Pi 4, and some HT40/HT80 channels are explicitly disabled. Perhaps the Pi ...
There are a few other errors that happen prior to this but I'm not sure if they're relevant
They're actually an hour previous (dunno if you noticed this).
The bit after the hostname, if it isn't kernel, is a process name and PID (eg. bluetoothd. The kernel stuff there isn't an error except for the note about dhcpcd (which is something that is spit out ...
I was able to resolve this issue by adding my region to the /etc/default/crda file.
# Set REGDOMAIN to a ISO/IEC 3166-1 alpha2 country code so that iw(8) may set
# the initial regulatory domain setting for IEEE 802.11 devices which operate
# on this system.
# Governments assert the right to regulate usage of radio spectrum within
# their respective ...
First link in a Google search it suggested top of the list after pasting the model of dongle into the search box lead to this on Ask Ubuntu. The detailed instructions are there for Debian too. Who knows if the source builds on arm.
Setting up a raspberry pi as a Access point is very easy these days I recommend the snap wifi-ap application.
I've always setup access points using hostapd, dnsmasqd by hand and this application makes it as simple as installing and configuring which can be done in a few minutes.
Howto install wifi-ap
Once you have it installed you can run:-
You are asking if an installation is available with the characteristics you described. The answer is No.
You have to setup an access point. There are many tutorials available how to do it. The other things you want, have to be created by yourself, I think. Maybe you will find some hints on the web, but I don't believe that you will find a ready to install ...
Option 1 - Using nohook wpa_supplicant
The /etc/dhcpcd.conf configuration file of dhcpcd can be edited to define which wireless interfaces need wpa_supplicant.
For each identified interface, dhcpcd executes all scripts (hooks) found in /lib/dhcpcd/dhcpcd-hooks in lexical order. One of the scripts is 10-wpa_supplicant, which starts wpa_supplicant. It can be ...
So it turns out it was a hardware issue rather than a software issue. Looking at my question again, I recalled that 2.4 GHz wireless connections are well known for dropping due to any kind of interference of other devices that give off the 2.4GHz noise frequency while 5GHz doesn't have that problem. One of the things I failed to mention earlier in the ...
The main problem is not the setup with the networking system. The problem is the USB/WiFi dongle "TP-Link TL-WN823N". It isn't supported by the kernel so it will not be available out of the box by showing its interface wlan1. As you mentioned, it needs a separate driver to achieve this. But all your log output does not show an interface wlan1 from ...
Depending on what tools you have in Ubuntu, you can try the following
For NetworkManager, edit /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
wifi.powersave = 2
For TLP, edit /etc/default/tlp
Regarding your second issue, you should check the kernel log after trying to bring the interface up. ...
If you have a broken or weak WiFi on-board device on your RasPi it can still be that it disrupts the connection. You should completely disable it by setting this option in /boot/config.txt:
Also don't forget to
rpi ~$ rfkill unblock wlan
I've been struggling with various issues to do with ping times and latency on my Pi 4.
Essentially the ping time will spike from a norm of 2-3ms to a single 200-900ms ping every 7-10 seconds. After quite a lot of investigation I found a cure; dramatically reduce the latency of the kernel scheduler.
To try it out first run:
sudo sysctl kernel....