I am running pre-built SD card image for the raspberry pi of nextcloudpi , but I figure I might get better help here. I noticed that the time and date was not automatically updated so I started debugging. I noticed that all lines in the file /etc/systemd/timesyncd.conf were commented out and the NTP line was empty. There's no additional timesyncd.conf.d subdirectory. So I uncommented lines and populated the NTP line. Here's how timesyncd.conf file looks now:

[Time]
NTP=0.europe.pool.ntp.org
FallbackNTP=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org
RootDistanceMaxSec=5
PollIntervalMinSec=32
PollIntervalMaxSec=2048
ConnectionRetrySec=30
SaveIntervalSec=60

It seems that the content is parsed successfully because:

pi@nextcloudpi:~$ timedatectl show-timesync --all
LinkNTPServers=
SystemNTPServers=0.europe.pool.ntp.org
RuntimeNTPServers=
FallbackNTPServers=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org
ServerName=
ServerAddress=
RootDistanceMaxUSec=5s
PollIntervalMinUSec=32s
PollIntervalMaxUSec=34min 8s
PollIntervalUSec=0
Frequency=0

However:

pi@nextcloudpi:~$ timedatectl
               Local time: Sat 2024-12-28 12:05:31 EET
           Universal time: Sat 2024-12-28 10:05:31 UTC
                 RTC time: n/a
                Time zone: Europe/Helsinki (EET, +0200)
System clock synchronized: no
              NTP service: active
          RTC in local TZ: no

pi@nextcloudpi:~$ timedatectl timesync-status
       Server: n/a (n/a)
Poll interval: 0 (min: 32s; max 34min 8s)
 Packet count: 0

The System clock synchronized always indicates no and the Server is always n/a. I tried

sudo timedatectl set-ntp false
sudo timedatectl set-ntp true

but it didn't change anything. The systemd-timesyncd service is running:

● systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; preset: enabled)
    Drop-In: /etc/systemd/system/systemd-timesyncd.service.d
             └─override.conf
     Active: active (running) since Fri 2024-12-27 22:38:50 EET; 13h ago
       Docs: man:systemd-timesyncd.service(8)
   Main PID: 3014 (systemd-timesyn)
     Status: "Daemon is running"
      Tasks: 1 (limit: 761)
     Memory: 576.0K
        CPU: 920ms
     CGroup: /system.slice/systemd-timesyncd.service
             └─3014 /lib/systemd/systemd-timesyncd

I tried enabling debug logging of this service, but nothing useful is printed there. There's never anything like Connecting to time server. It's not even trying. I also tried manually updating with ntpdate

sudo ntpdate -vd pool.ntp.org

and that worked fine. So I assume that this rules out possible DNS and other network related issues. I ran out of ideas. What am I missing here? Here's the version info:

pi@nextcloudpi:~$ sudo lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Armbian-unofficial 24.8.2 bookworm
Release:        12
Codename:       bookworm

pi@nextcloudpi:~$ cat /etc/armbian-release
# PLEASE DO NOT EDIT THIS FILE
BOARD=rpi4b
BOARD_NAME="Raspberry Pi 4"
BOARDFAMILY=bcm2711
BUILD_REPOSITORY_URL=https://github.com/armbian/build 
BUILD_REPOSITORY_COMMIT=549f321
LINUXFAMILY=bcm2711
ARCH=arm64
BOOT_SOC=
IMAGE_TYPE=user-built
BOARD_TYPE=conf
INITRD_ARCH=arm64
KERNEL_IMAGE_TYPE=Image
FORCE_BOOTSCRIPT_UPDATE=
FORCE_UBOOT_UPDATE=
VENDOR="Armbian-unofficial"
VENDORDOCS="https://docs.armbian.com/ "
VENDORURL="https://duckduckgo.com/ "
VENDORSUPPORT="https://community.armbian.com/ "
VENDORBUGS="https://armbian.atlassian.net/ "
VERSION=24.8.2
REVISION=24.8.2

Edit:

pi@nextcloudpi:~$ ntpq -np
-bash: ntpq: command not found

pi@nextcloudpi:~$ systemctl status ntp
Unit ntp.service could not be found.

Edit 2: So it seems to be a network related issue somehow. Until now I have been connected through WiFi only. But immediately when I connected also the Ethernet cable, the System clock synchronized turned to yes. But why is it not working over WiFi? Here's resolvectl status when connected to WiFi only:

Global
         Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
  resolv.conf mode: stub
Current DNS Server: 1.0.0.1
        DNS Servers 1.0.0.1

Link 2 (enxb827ebf2575c)
Current Scopes: none
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 3 (wlan0)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.1.1
       DNS Servers: 192.168.1.1

When the Ethernet cable is connected, it is otherwise the same, except for the Link 2 part:

Link 2 (enxb827ebf2575c)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.1.1
       DNS Servers: 192.168.1.1

Both WiFi and the Ethernet are the same network.

I am using Orange Pi Zero and running Armbian Stretch OS 5.59 on it. Problem is, it is giving wrong date and time even in the presence of the Internet. I have tried restarting "ntp" service but to no avail. I have also tried rebooting, but the same annoying result. I have already set the right timezone which is PKT, but it shouldn't matter. So what do I need to do or change? Thank you.

I have installed armbian on SD card and I cannot get no network. Neither ethernet, neither wireless. Only thing I managed is to connect to it via serial port. Here is some information about my network im connected to: Gateway: 192.168.8.1 Dhcp: 192.168.8.1 DNS: 192.168.8.1 Network DNS always assigns addresses from 100-200 root@orangepizero:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 - 255.255.255.0 ! 0 - 0 - 192.168.8.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 root@orangepizero:~# cat /etc/network/interfaces auto lo iface lo inet loopback iface eth0 inet dhcp gateway 192.168.8.1 netmask 255.255.255.0 auto wlan0 iface wlan0 inet dhcp wpa-ssid ***** wpa-psk ***** I have tried assigning static addresses, and some other tips I found on the internet, and I had no success. Device is still without connection. Here is my current ifconfig eth0 (although it has ip that I placed, it is not connected to the router) eth0 Link encap:Ethernet HWaddr e6:f5:19:a6:1b:e6 inet addr:192.168.8.121 Bcast:192.168.8.255 Mask:255.255.255.0 inet6 addr: fe80::e4f5:19ff:fea6:1be6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:237 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:10602 (10.3 KiB) Interrupt:114

I have an an orange pi zero running armbian I am having problem connecting to open networks using nmcli. I can very well connect to my home "WPA1 WPA2" secured network with no issue at all. Here is to list the network: # nmcli device wifi list IN-USE BSSID SSID MODE CHAN RATE SIGNAL BARS SECURITY XX:XX:XX:XX:XX:XX MyNetwork Infra 7 405 Mbit/s 100 ▂▄▆█ WPA1 WPA2 I use the following command to connect to it and it works perfect: # nmcli device wifi con MyNetwork password 'mypassword' Connection 'MyNetwork' successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/48) Now if I turn my android phone to a hotspot with no password, the nmcli can not connect to it. Here is how the nmcli sees the open hotspot (as you can see there are no security set): # nmcli device wifi list IN-USE BSSID SSID MODE CHAN RATE SIGNAL BARS SECURITY XX:XX:XX:XX:XX:XX MyNetwork Infra 7 405 Mbit/s 97 ▂▄▆█ WPA1 WPA2 XX:XX:XX:XX:XX:XX OpenNetwork Infra 1 130 Mbit/s 94 ▂▄▆█ -- My assumption is that I should just use the same command I used to connect to my secure WiFi, but omit the password part...but for some reason I get the following error: # nmcli device wifi con OpenNetwork Error: Connection activation failed: (53) The Wi-Fi network could not be found. I tried this with some other open networks, I get the same error. Is there something that I am missing? is the a driver issue? or is there some settings that I need to change/enable for nmcli to support open networks?

I'm new to linux an I installed armbian to an sd card and everything works fine. The SD-Card is 64GB. Then I installed docker.io, docker-compose and portainer, nothing else. When I check for disk space with lsblk: # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk0 179:0 0 59.5G 0 disk ├─mmcblk0p1 179:1 0 512M 0 part /boot └─mmcblk0p2 179:2 0 58.4G 0 part / mmcblk1 179:32 0 14.6G 0 disk mmcblk1boot0 179:64 0 4M 1 disk mmcblk1boot1 179:96 0 4M 1 disk zram0 254:0 0 50M 0 disk /var/log zram1 254:1 0 929.4M 0 disk [SWAP] Then with df: # df -h Filesystem Size Used Avail Use% Mounted on udev 796M 0 796M 0% /dev tmpfs 186M 8.0M 178M 5% /run /dev/mmcblk0p2 58G 2.2G 55G 4% / tmpfs 930M 0 930M 0% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 930M 0 930M 0% /tmp /dev/mmcblk0p1 511M 59M 453M 12% /boot /dev/zram0 49M 7.0M 38M 16% /var/log overlay 58G 2.2G 55G 4% /var/lib/docker/overlay2/b28da5a318945ac7ae1d17d26a635edb9a662c6116dea37fb4f6c13e1c76d7d2/merged tmpfs 186M 0 186M 0% /run/user/0 Why are there 2 remaining 55 GB (/dev/mmcblk0p2 and the overlay filesystem)? Does this mean that I can only use the 55 GB space on the /var/lib/docker/overlay2/.../merged folder?

I have an **Orange Pi** with **Armbian** installed. I find that when I use a CPU governor called schedutil a process called sugov:0 will exist in top. And the sugov:0 can spend about 13% CPU. When I use the governor ondemand this process will not exist. What's this process？ 

I'm using a Banana Pi BPI-F3 with Armbian-unofficial 24.11.0-trunk sid. I'm able to connect to the Banana Pi by connecting an ethernet cable between my (Ubuntu) laptop and the board, and using the "shared with other computers" IPv4 setting in the Ubuntu network manager. On the Banana Pi, I can see that it's able to complete DNS queries (e.g. running ping will resolve the address associated with a hostname), and I can connect to my laptop from the Banana Pi over the LAN just fine. However, I can't get it to connect to anything outside of my laptop, and the packets the Pi sends out don't seem to be forwarded onto the broader network. When I run Wireshark, I can see that packets for ping google.com are being received by my laptop's ethernet interface, but they seem to be getting dropped. Running route -n on the Banana Pi yields: Is there anything else I can try to get a working internet connection?

I want to make an automatic backup to a flash drive after auto-mounting it. To do this, I wrote in /etc/fstab... UUID=0698-A3CF /flash vfat noauto,nofail,x-systemd.automount,x-systemd.idle-timeout=15,x-systemd.device-timeout=15 And in /etc/systemd/system/ I created the my_backup.service unit. I filled it out according to these instructions . [Unit] Description=My backup script trigger Requires=flash.automount After=flash.automount [Service] ExecStart=/myfolder/python_backup.py [Install] WantedBy=flash.automount The Python script works great if I run it separately and almost perfectly if I run it by mounting a flash drive. Almost, except... actually copying the necessary files. The log says “No /flash device”. In addition, by commenting out the functions for working with files, using a delay in the Python script and the *ls /flash* command, I found out that the flash drive is not mounted until the script is completed to the end. But the unit says “After”! Is it possible to rewrite the unit so that the Python script starts executing after mounting the flash drive?

I'm trying to use the UART1 and UART2 of my device (a NanoPi NEO) to read serial data. So far, UART1 i fully functionnal and I can read and transmit data through /dev/ttyS1. I've enabled UART2 using the armbian-config hardware menu and it seems to have added the line in the armbianEnv.txt: # cat /boot/armbianEnv.txt verbosity=1 bootlogo=false console=serial disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 overlays=uart1 uart2 uart3 rootdev=UUID=f8644502-8a67-43df-8275-2953e5ef9c87 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u The config does not seem to be the same for the two UARTs: # cat /proc/tty/driver/serial serinfo:1.0 driver revision: 0: uart:U6_16550A mmio:0x01C28000 irq:137 tx:19080 rx:134 RTS|DTR 1: uart:U6_16550A mmio:0x01C28400 irq:138 tx:0 rx:4312 RTS|CTS|DTR 2: uart:U6_16550A mmio:0x01C28800 irq:139 tx:0 rx:0 CTS 3: uart:U6_16550A mmio:0x01C28C00 irq:140 tx:0 rx:0 RTS|CTS|DTR 4: uart:unknown port:00000000 irq:0 5: uart:unknown port:00000000 irq:0 6: uart:unknown port:00000000 irq:0 7: uart:unknown port:00000000 irq:0 Did I make something wrong or forget to run a command to enable UART2 through /dev/ttyS2 ? I've also tried to add the following line to armbianEnv.txt but didn't help: param_uart2_rtscts=1

I am having trouble with my [7-inch type C LCD screen](https://www.waveshare.com/wiki/7inch_HDMI_LCD_(C)).  ; When I try to display an application on it, I get the error Missing X server or $DISPLAY.  I use the command xrandr and get the message can't open display.  I found some solutions for Raspberry, but my Orange Pi lite board doesn't have config.txt. I tried adding the line disp_mode=1024x600p60 to armbianEnv.txt, but that doesn't seem to be the solution.  I currently use Armbian Minimal (a stripped-down version).  Could that be the problem?  xrandr -display :0.0 returns Can't open display :0.0.

I'm currently working with the [armbian build system](https://github.com/armbian/build) and it is using chroot inside docker to cross build armbian images (for aarch64 in my case on an amd64 host). However, for some reason, when the build script is executing apt-key add - takes literally hours on my machine while constantly using 100% of a single CPU core. Apt key is called like this: chroot bash -c 'cat armbian.key | apt-key add -', resulting in a process like /usr/bin/qemu-aarch64-static /bin/bash -c cat armbian.key | apt-key add - inside the container. Inside apt-key (which is a shell script) a few binaries are called which is what actually takes that long, such as: - multiple calls to /usr/bin/apt-config, e.g. /usr/bin/apt-config shell ARCHIVE_KEYRING_URI APT::Key::Archiv. - a call to /usr/bin/gpg-conf (/usr/bin/gpgconf --kill all to be exact) - possibly more, but I might have missed some (was looking at ps aux occasionally while waiting) I'm really clueless, why these calls, that are supposed to take seconds at most, take hours to terminate when executed via docker -> chroot -> qemu. I really don't understand what makes this so slow. I would be very thankful for any pointers on how to debug this further. **EDIT:** I should mention that the steps in question are significantly faster when executed directly on an ubuntu 22.04 VM (in which case the armbian build script doesn't use docker, because Ubuntu 22.04 is supported natively). **EDIT:** I managed to reproduce the issue like this:

docker run --name armbian-test -d --rm ghcr.io/armbian/docker-armbian-build:armbian-ubuntu-jammy-latest bash -c 'while sleep 1; do true; done'
docker exec armbian-test bash -c 'apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends bash git psmisc uuid-runtime bc binfmt-support bison libc6-dev make dpkg-dev gcc ca-certificates ccache cpio debootstrap device-tree-compiler dialog dirmngr dosfstools dwarves flex gawk gnupg gpg imagemagick jq kmod libbison-dev libelf-dev libfdt-dev libfile-fcntllock-perl libmpc-dev libfl-dev liblz4-tool libncurses-dev libssl-dev libusb-1.0-0-dev linux-base locales lsof ncurses-base ncurses-term ntpdate patchutils pkg-config pv qemu-user-static rsync swig u-boot-tools udev uuid-dev zlib1g-dev file tree expect colorized-logs unzip zip pigz xz-utils pbzip2 lzop zstd parted gdisk fdisk aria2 curl wget axel parallel python3-dev python3-distutils python3-setuptools python3-pip python2 python2-dev gcc-x86-64-linux-gnu gcc-aarch64-linux-gnu gcc-arm-linux-gnueabihf gcc-arm-linux-gnueabi gcc-riscv64-linux-gnu debian-archive-keyring libc6-amd64-cross g++-aarch64-linux-gnu g++ btrfs-progs cryptsetup openssh-client f2fs-tools nilfs-tools xfsprogs zerofree qemu-utils qemu-utils libudev-dev libusb-1.0-0-dev dh-autoreconf build-essential gcc-arm-linux-gnueabi gcc-or1k-elf time'
docker exec armbian-test debootstrap --variant=minbase --arch=arm64 bullseye /debootstrap
docker exec armbian-test time chroot /debootstrap /bin/bash -c '/usr/bin/apt-config shell ARCHIVE_KEYRING_URI APT::Key::Archiv'

I have an Armbian system SD card that I want to copy to another device. The system was 16GB but was previously imaged to 64GB card and now it is to big to handle for me. Is it any way to truncate unallocated space from the SD card?

I'm making a kiosk system using Armbian on an orangepi zero 3. The kiosk is a on a local server that I connect to using chromium browser launched from my ~/.bash_profile. Before chromium-browser starts up getty@tty1.service is launched and autologs in my user. When the getty terminal launches there's a line that prints and I can't seem to find the source. The line printed is Armbian 23.08.0-trunk Jammy tty1 I've tried changing sysctl kernel.printk to all zeros and dmesg -n 1 but neither of these work.

Waveshare makes a great CAN HAT for the Raspberry Pi (see here ), but the instructions only work for Raspberry Pi OS, not for Armbian. The Banana Pi BPI-M2 Zero has the same pin header layout as the Raspberry Pi, but runs Armbian. How do you setup the Waveshare CAN HAT using Armbian's overlay system?

Fish can't cd into a folder on a Webdav remote directory through Rclone:

Welcome to fish, the friendly interactive shell
Type help for instructions on how to use fish
drive ) ls
Documents/  Music/           Videos/
Gem/        Misc/            Pictures/
drive ) cd Documents
cd: The directory “Documents” does not exist
drive ) sh
$ cd Documents
$ pwd
/mnt/drive/Documents
$ exit
drive )

Perhaps because it uses a wrapper around cd, maybe it is a bug, or instead I have to disable or rename the cd function, not sure how to address it.

I am aware that there are other questions asking very similar questions, but none seems to answer my problem. I am running an odroid hc2 sbc with armbian for a nextcloud instance. Two days ago, it crashed, for the first time, after running stable for over a year. To rule out overheating as a reason, I'd like to write a script to monitor temperature, i.e. running the built in function "armbianmonitor", which creates this continous output: Stop monitoring using [ctrl]-[c] Time big.LITTLE load %cpu %sys %usr %nice %io %irq CPU C.St. 09:52:33: 600/ 600MHz 0.23 12% 1% 10% 0% 0% 0% 53.0°C 0/13 09:52:38: 1400/ 600MHz 0.21 2% 0% 1% 0% 0% 0% 53.0°C 0/13 09:52:43: 1400/ 600MHz 0.20 2% 0% 1% 0% 0% 0% 53.0°C 0/13^C with: sudo armbianmonitor -m | awk '$11 ~ "°C" {print $1; print $1;exit1}' ORS=' ' I get this results: 09:57:48: 53.0°C 09:57:53: 51.0°C 09:57:58: 51.0°C 09:58:03: 51.0°C but... I'd like to have only one pair (time and temperature) per run of the script. In other word, awk and /or (?) armbianmonitor are supposed to stop after they return the first pair. I've also tried to pipe the output of a script invoking this command to a file, but the file remains blank, maybe because armbianmonitor creates a continuous output?

"documentation" on Banana Pi Zero M2 is so chaotic it's even funny. goal: get PWM working. so I installed armbian, waited a week till my usb OTG cable came (because you'll just fail default SSH into it), configured ssh and followed steps in here to install modified wiring pi -- gpio utility. I can confirm setting pin L/H works. next step is to verify PWM works, so here fun begins. pinout looks to be the same as on Raspberry Pi and so they claim: I designed my board with last RPI 0 I had and I was using pin GPIO 12 (wiringPi 1) so I did:

# gpio mode 1 pwm
the pin you choose is not surport hardware PWM
you can select PA6 for PWM pin
or you can use it in softPwm mode

so as you can read it's not 'surpot' and I should try PA6. no idea what is PA6 so I was searching and found this on-the-topic thread . so I set :

# gpio mode 7 pwm
you choose the hardware PWM:1

and it informed me I have choosen PWM:1 whatever that should mean. (1 being on?) sure enough I tried to set duty cycle and waited to see my led come on, but just like the gentleman in the foermentioned thread I got:

# gpio pwm 7 100
val pwmWrite 0 <= X <= 1024
Or you can set new range by yourself by pwmSetRange(range

error that doesn't change with ducy cycle value I input it with. next best bet I found got me to adding pwm overlay, activating pwm, setting period and duty cycle. commands passed without an error but LED did not light up. as suggested at the begginging of the tread in limitations, my PWM line is now connected to GPIO 15 (UART_TXD) **--is this correct??**. this is my armbianEnv.txt

# cat /boot/armbianEnv.txt 
verbosity=1
bootlogo=false
console=both
disp_mode=1920x1080p60
overlay_prefix=sun8i-h3
rootdev=UUID=986b3dcb-01f8-4965-8a16-03b55c7341fd
rootfstype=ext4
overlays=i2c0 pwm w1-gpio
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

and I just have noticed i2c0 and w1-gpio were added to overlays probably by armbian-config utility so that might be ok. but if you ask me:

root@bananapim2zero:~# ls /boot/dtb/ | grep pwm
root@bananapim2zero:~# ls /boot/dtb-6.1.11-sunxi/ | grep pwm

shows no such overlay so I don't know. at the end, I would like to make sense of all that abbreviations as: PA, all the GPIO pin names listed in here mean, I mean there seem st be some logic in there, but I just don't know why are there two separate tables that prefix those names once with CON2- then CON3- following P{0-24} like there would be two different GPIOs? Why and what is UART _jumper_? and mainly: how do I get PWM work? i2c and w1 to follow. I'm sure answers will shed light to many more lost ones looking for RPI replacement. Thanks!

I have 2 wifi adapters on my odroid, wlan0 and wlan1, I connected to my wifi using nmcli with wlan1 successfully, but would like to be able to connect with wlan0 instead. However it seems no matter what I do (both removing the connection and deleting it from the network manager) nmcli will only allow the first adapter (wlan1) to connect to the connection. When I try the same command but replacing wlan1 with wlan0 nmcli d wifi connect --ask ifname wlan0 it gives me this Error: Connection activation failed: (7) Secrets were required, but not provided. but running the same command using wlan1 connects no issue. Does anyone know what I might be doing wrong? Also these are 2 identical adapters, both confirmed working before, just cant 'swap' them on my wifi for some reason. Extra info: Using odroid c4 with Armbian 22.11

I've cracked my head on this for a while. I can't ssh into my banana pi m2 zero(I don't have a mini-usb cord, I'm trying to boot wirelessly for the first time). I get 100% packet loss every time I try to ping it. I know it connected to the wifi. I'm using this armbian release: https://www.armbian.com/banana-pi-m2-plus/ Here's what I've done: 1. I made a blank ssh file in /boot 2. In the sshd_config file I set PermitRootLogin and PasswordAuthentication to yes 3. I added a before.rules file in etc/ufw/ it has this inside:

# Allow all incoming traffic
-A ufw-before-input -j ACCEPT

# Allow all outgoing traffic
-A ufw-before-output -j ACCEPT

# Allow all forwarded traffic
-A ufw-before-forward -j ACCEPT

# Allow SSH connections
-A ufw-before-input -p tcp --dport 22 -j ACCEPT

COMMIT

4. I made sure no other machine is using port 22 5. sudo systemctl start ssh 6. When I do nmap , I get:

Starting Nmap 7.80 ( https://nmap.org  ) at 2023-01-03 19:25 EST
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 5.03 seconds

P.S.: I've been editing the OS with a linux vm and I remember yesterday I was able to ping it with no packet loss(I think) but couldn't ssh into it. I don't remember what I did to break it though :P What I listed is what I currently did to the

I have a little device on ARM with armbian on it. It automatically loads after turning power on or after shutdown. But sometimes it doesn't until I turn off-on power. I added a script to crontab. The script reboots device each few minutes and puts current time in text file. Usually it reloads few times and then stops. LEDs are turned on but nothing on a monitor, the device isn't available through ssh and the script isn't working any more (no new timings of reboots in the text file). I turned on saving logs for previous boots, so I can watch journalctl for previous boots. But it contains a lot of information and normal shutdowns have the same log-ending as these, which ended with power off. What can I look for debugging this?