A failed reboot is either due to a failure to shutdown, or a failure to start again. A watchdog should help with the failure to shutdown: simply touch /dev/watchdog to start a countdown if you don't use a service or systemctl kill -s SIGSTOP watchdog.service if you use one. Your system will then have 15 seconds until a hardware reset is triggered.
If what ...
Interrupting an upgrade may leave your OS in corrupted state.
No one can tell you how to fix it; indeed most of us would just restore from backup or do a fresh install.
In fact there is NO RECOVERY partition on a normal Raspberry Pi OS OS.
If you want to attempt recovery of your data use a fresh SD Card.
"how would I attempt recovery with a fresh ...
Without going too much into details your steps would probably be:
set-up a WiFi server, either open or with known PSK on the Pi zero (f.e. http://www.penguintutor.com/news/raspberrypi/wireless-hotspot, https://thepi.io/how-to-use-your-raspberry-pi-as-a-wireless-access-point/ etc.)
use a simple web-server (Dancer-2, Flask, ...) to create a page that asks for ...
I think https://unix.stackexchange.com/questions/22757/how-to-run-an-app-in-a-framebuffer/22759 answers this well.
Framebuffer is a lot more basic than X protocol support, so the application has to be specially written to support it.
You'll need to use one of the browsers that has such a specialist port, not a general web-browser like Chromium or Firefox.
"What am I missing?" - reading the Raspberry Pi Imager Documentation.
Admittedly this is not easy to find, and the advanced options are "hidden", but these do require some expertise to use.
PS Raspberry Pi Imager has ABSOLUTELY nothing to do with NOOBS which is one of the worst ideas ever conceived.
For those of you who made the same mistake as I did, after combing through some F@H forum posts, the F@H control will not start the client. This is why it was stuck on connecting. It was trying to connect with the client but the client wasn't running. In order to run the client, you have to type FAHClient into the terminal. Then you can open F@H Control and ...
Start by finding out which device file you really need. This can be done by observing which file appears/disappears as you connect/disconnect the Arduino, or by inspecting kernel messages with dmesg immediately after the Arduino was connected.
Lines you have posted are not error messages. Go to File-> Preferences in Arduino IDE and check the corresponding ...
You probably don't have write access to the port.
Run sudo usermod -aG dialout pi in the terminal, log out and in again, and then switch to /dev/ttyAMA0 (the /dev/ttyS0 port is for serial, not USB).
The config warning is expected behavior if you haven't made that config file.
Arduino Uno uses a separate chip for USB to UART interface. As a result it will always look like a UART (/dev/ttyUSBx or /dev/ttyACMx) on the Pi, and the only way to exchange information will be to open the UART (with the right baudrate!) and send data to the Arduino, which then can reply and tell what's connected to it.
Arduino Leonardo / Due controllers ...
Okay, after some days of struggle and figuring this stuff out, I've finally made it happen. What I did was:
wrote a bash script that sends a magic packet with the mac address of the target pc to the local IP-address with a port of that pc.
sudo wakeonlan -i 22.214.171.124 -p 99 1a:2b:3c:4d:5e:6f
figured out the command which I ...
Finally I can solve it, seems the problem is with Chromium sign-in or Google authentication itself. After disabling Chromium sign-in, the session/login persists after closing and then reopening Chromium.
In Chromium, open Settings.
Click Sync and Google services.
Uncheck Allow Chromium sign-in.
Log in to Google like usual.
You could use tcpdump or wireshark to monitor the network interface on the Pi and set up a filter for the magic packet of your choice. For example, for a ping packet that could be:
tcpdump -i eth0 icmp and icmp[icmptype]=icmp-echo
Pipe the output of tcpdump to a script which wakes up the target computer on any new input:
while read line; do wakeonlan <...
It sounds like you've run out of free space:
Free space: 0.00 Byte
Linux expects some free space to always be available and may even fail to boot if you don't.
For a reference, here's what you could expect from a decent SD card (Samsung EVO, far from the fastest but OK):
pi@raspberrypi:~ $ sudo hdparm -tT /dev/mmcblk0
Timing cached ...
You should check whether the f3 tests measure just sequential read-write or random read-write performance as well.
In most real use cases, random read and write performance is more important since it is the class of transfer operations being utilized when large amounts of files are copy/pasted or when software is downloaded and installed.
I have had bad ...
Strange. I am using version 2 of the /dev/gpiochip API on my recently updated Pis (mainly because API 2 has broken API 1).
Version 2 of the gpiochip API is present in all the Pis I have recently updated (32 and 64 bit).
For instance my Pi3B+
Linux pi3bp 5.10.17-v7+ #1421 SMP Thu May 27 13:59:01 BST 2021 armv7l GNU/Linux
A fragment of /usr/include/...