av4625

@ag123 I appreciate the help thanks. I was hoping to use `nmcli` so that I could keep my "setup script" as similar as possible between the Zero and Zero3. Its frustrating that the same commands work on one and not the other, but I know there are some differences between the two. Did you get a hotspot to work with hostapd? Cause I'd move away from `nmcli` for a working solution of course. I found out a few things since my first post with the help from your links. I was able to use `nmcli` to connect to my router over Wi-Fi and that seemed to work fine. The ethernet is unmanaged by `NetworkManager` on the Zero3 but it is managed on the Zero. I tried the exact commands from your second link at the heading "Configuring WiFi Access Point with NetworkManager" to setup a hotspot incase mine were a bit weird and the result is exactly the same, it shows up and appears to work but nothing can connect. I'd love to be able to see some logging on why things can't connect to it. The only thing I didn't do was add this to the config: [main] dns=dnsmasq The reason I didn't do that is because I want it to use the default `systemd-resolved` as I found it easier to setup to be able to work with mdns and access a server the pi hosts using hostname.local over the hotspot. Some outputs that might be useful: $ nmcli wlan0: connected to access_point "wlan0" wifi (unisoc_wifi), 44:FA:6D:94:C1:36, hw, mtu 1500 inet4 10.42.0.1/24 route4 10.42.0.0/24 metric 600 inet6 fe80::3cba:c8ea:4090:3d0b/64 route6 fe80::/64 metric 1024 lo: connected (externally) to lo "lo" loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536 inet4 127.0.0.1/8 inet6 ::1/128 p2p-dev-wlan0: disconnected "p2p-dev-wlan0" wifi-p2p, hw end0: unmanaged "end0" ethernet (dwmac-sun8i), 02:00:97:9B:CB:C0, hw, mtu 1500 $ nmcli con show NAME UUID TYPE DEVICE access_point f19de078-4acb-4406-a250-08e2edc3d01e wifi wlan0 lo 883ee445-38e7-4ec0-903b-48312d0cee87 loopback lo $ sudo systemctl status NetworkManager.service ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; preset: enabled) Active: active (running) since Tue 2024-10-01 19:02:25 BST; 18min ago Docs: man:NetworkManager(8) Main PID: 1779 (NetworkManager) Tasks: 4 (limit: 4548) Memory: 4.3M CPU: 1.275s CGroup: /system.slice/NetworkManager.service ├─1779 /usr/sbin/NetworkManager --no-daemon └─1985 /usr/sbin/dnsmasq --conf-file=/dev/null --no-hosts --keep-in-foreground --bind-interfaces --except-interface=lo --clear-on-reload --strict-order --listen-address=10.42.0.1 --dhcp-range=10.42.0.10,10.42.0.254,60m --dhcp> Oct 01 19:10:39 orangepizero3 NetworkManager[1779]: <info> [1727809839.9410] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Oct 01 19:10:39 orangepizero3 NetworkManager[1779]: <info> [1727809839.9422] manager: NetworkManager state is now CONNECTED_LOCAL Oct 01 19:10:39 orangepizero3 NetworkManager[1779]: <info> [1727809839.9437] device (wlan0): Activation: successful, device activated. Oct 01 19:10:39 orangepizero3 dnsmasq[1985]: started, version 2.89 cachesize 150 Oct 01 19:10:39 orangepizero3 dnsmasq[1985]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset nftset auth cryptohash DNSSEC loop-detect inotify dumpfile Oct 01 19:10:39 orangepizero3 dnsmasq[1985]: chown of PID file /run/nm-dnsmasq-wlan0.pid failed: Operation not permitted Oct 01 19:10:39 orangepizero3 dnsmasq-dhcp[1985]: DHCP, IP range 10.42.0.10 -- 10.42.0.254, lease time 1h Oct 01 19:10:39 orangepizero3 dnsmasq[1985]: reading /etc/resolv.conf Oct 01 19:10:39 orangepizero3 dnsmasq[1985]: using nameserver 127.0.0.53#53 Oct 01 19:10:39 orangepizero3 dnsmasq[1985]: cleared cache All the output looks as it should as far as I know. I wanted to note some differences between my Zero and Zero3 incase anyone spotted something that might cause an issue: Zero * Runs a CLI build of Ubuntu 24.2.1 (6.6.20) * I can run my `nmcli` commands from the first post without `sudo` * Has files here: `/etc/polkit-1/localauthority` * NetworkManager permissions (when logging in over SSH): $ nmcli general permissions PERMISSION VALUE org.freedesktop.NetworkManager.checkpoint-rollback yes org.freedesktop.NetworkManager.enable-disable-connectivity-check yes org.freedesktop.NetworkManager.enable-disable-network yes org.freedesktop.NetworkManager.enable-disable-statistics yes org.freedesktop.NetworkManager.enable-disable-wifi yes org.freedesktop.NetworkManager.enable-disable-wimax yes org.freedesktop.NetworkManager.enable-disable-wwan yes org.freedesktop.NetworkManager.network-control yes org.freedesktop.NetworkManager.reload yes org.freedesktop.NetworkManager.settings.modify.global-dns yes org.freedesktop.NetworkManager.settings.modify.hostname yes org.freedesktop.NetworkManager.settings.modify.own yes org.freedesktop.NetworkManager.settings.modify.system yes org.freedesktop.NetworkManager.sleep-wake yes org.freedesktop.NetworkManager.wifi.scan yes org.freedesktop.NetworkManager.wifi.share.open yes org.freedesktop.NetworkManager.wifi.share.protected yes Zero3 * Runs a minimal build of Debian (Bookworm) 24.11.0 (6.6.44) * I can not run my `nmcli` commands from the first post without `sudo` * Does not have files here: `/etc/polkit-1/localauthority` * NetworkManager permissions (when logging in over SSH): $ nmcli general permissions PERMISSION VALUE org.freedesktop.NetworkManager.checkpoint-rollback auth org.freedesktop.NetworkManager.enable-disable-connectivity-check no org.freedesktop.NetworkManager.enable-disable-network no org.freedesktop.NetworkManager.enable-disable-statistics no org.freedesktop.NetworkManager.enable-disable-wifi no org.freedesktop.NetworkManager.enable-disable-wimax no org.freedesktop.NetworkManager.enable-disable-wwan no org.freedesktop.NetworkManager.network-control auth org.freedesktop.NetworkManager.reload auth org.freedesktop.NetworkManager.settings.modify.global-dns auth org.freedesktop.NetworkManager.settings.modify.hostname auth org.freedesktop.NetworkManager.settings.modify.own auth org.freedesktop.NetworkManager.settings.modify.system auth org.freedesktop.NetworkManager.sleep-wake no org.freedesktop.NetworkManager.wifi.scan auth org.freedesktop.NetworkManager.wifi.share.open no org.freedesktop.NetworkManager.wifi.share.protected no When logging in directly with a keyboard more than half are yes, some auth and one no I think, is that strange? I wonder does the answer to this and its comments point to a change in Debian Bookworm around this? https://unix.stackexchange.com/questions/692316/cant-get-right-to-add-wifi-in-nmcli-polkit The permissions thing is interesting as the only warning I see in the logs which I don't see on the Zero is: Oct 01 19:10:39 orangepizero3 dnsmasq[1985]: chown of PID file /run/nm-dnsmasq-wlan0.pid failed: Operation not permitted I'm not using `dnsmasq` but I believe `NetworkManager` does start an instance not using a service which is why I had to install `dnsmasq-base`. If anyone has anything else I can try or anyway to maybe see a log or something on why the devices won't connect please shout! Thanks!

I had an OrangePi Zero LTS and set up an access point using the following commands: % sudo apt install dnsmasq-base -y % sudo sed -i "s/#MulticastDNS=no/MulticastDNS=yes/g" /etc/systemd/resolved.conf % sudo nmcli connection add type wifi ifname wlan0 con-name access_point autoconnect yes ssid <ssid> % sudo nmcli connection modify access_point 802-11-wireless.mode ap 802-11-wireless.band bg ipv4.method shared % sudo nmcli connection modify access_point connection.mdns 2 % sudo nmcli connection modify access_point wifi-sec.key-mgmt wpa-psk % sudo nmcli connection modify access_point wifi-sec.psk "<password>" % sudo nmcli connection up access_point % sudo hostnamectl set-hostname <hostname> This worked fine, I can connect and ssh using `hostname.local` etc etc I recently just got a OrangePi Zero 3 and tried the minimal OS, I did the commands above along with: sudo apt install network-manager -y The access point does seem to appear and I can see it from phones and laptops etc but I can't connect to it. What is the best way to debug the issue? This is what it shows from the following commands: $ nmcli device DEVICE TYPE STATE CONNECTION wlan0 wifi connected access_point lo loopback connected (externally) lo p2p-dev-wlan0 wifi-p2p disconnected -- end0 ethernet unmanaged -- $ nmcli connection NAME UUID TYPE DEVICE access_point d7a42b9e-63bd-4e76-9457-018cbd43d712 wifi wlan0 lo a0764323-619d-4bd9-b029-fa8da5ed24c4 loopback lo Any help is appreciated! I should mention that the OrangePI Zero LTS OS wasn't the minimal one it was the server one so I'm not sure if I'm just missing something in the minimal OS for OrangePi Zero 3. I get these debug logs if I try and connect to the access point: Sep 29 13:41:35 <hostname> NetworkManager[846]: <debug> [1727613695.7400] ndisc-lndp[0xaaaae75732f0,"wlan0"]: processing libndp events Sep 29 13:41:35 <hostname> NetworkManager[846]: <debug> [1727613695.7409] platform: (end0) signal: address 6 changed: fd00::97ff:fe9b:cbc0/64 lft 7200sec pref 3600sec lifetime 1394-1394[3600,7200] dev 2 flags mngtmpaddr,noprefixroute src kernel Sep 29 13:41:35 <hostname> NetworkManager[846]: <debug> [1727613695.7412] platform: (end0) signal: address 6 changed: fd00::5bc2:4133:f0ea:931d/64 lft 7200sec pref 3600sec lifetime 1394-1394[3600,7200] dev 2 flags secondary src kernel Sep 29 13:41:35 <hostname> NetworkManager[846]: <debug> [1727613695.7441] manager: (end0): assume: don't assume because device is not managed Sep 29 13:41:40 <hostname> NetworkManager[846]: <debug> [1727613700.3462] ndisc-lndp[0xaaaae75732f0,"wlan0"]: processing libndp events Sep 29 13:41:40 <hostname> NetworkManager[846]: <debug> [1727613700.3471] platform: (end0) signal: address 6 changed: fd00::97ff:fe9b:cbc0/64 lft 7200sec pref 3600sec lifetime 1398-1398[3600,7200] dev 2 flags mngtmpaddr,noprefixroute src kernel Sep 29 13:41:40 <hostname> NetworkManager[846]: <debug> [1727613700.3474] platform: (end0) signal: address 6 changed: fd00::5bc2:4133:f0ea:931d/64 lft 7200sec pref 3600sec lifetime 1398-1398[3600,7200] dev 2 flags secondary src kernel Sep 29 13:41:40 <hostname> NetworkManager[846]: <debug> [1727613700.3499] manager: (end0): assume: don't assume because device is not managed Sep 29 13:41:44 <hostname> NetworkManager[846]: <debug> [1727613704.8566] ndisc-lndp[0xaaaae75732f0,"wlan0"]: processing libndp events Sep 29 13:41:44 <hostname> NetworkManager[846]: <debug> [1727613704.8575] platform: (end0) signal: address 6 changed: fd00::97ff:fe9b:cbc0/64 lft 7200sec pref 3600sec lifetime 1403-1403[3600,7200] dev 2 flags mngtmpaddr,noprefixroute src kernel Sep 29 13:41:44 <hostname> NetworkManager[846]: <debug> [1727613704.8578] platform: (end0) signal: address 6 changed: fd00::5bc2:4133:f0ea:931d/64 lft 7200sec pref 3600sec lifetime 1403-1403[3600,7200] dev 2 flags secondary src kernel Sep 29 13:41:44 <hostname> NetworkManager[846]: <debug> [1727613704.8603] manager: (end0): assume: don't assume because device is not managed

Thats exactly what I was looking for thanks

Thanks for the answer. So just to make sure that I'm clear there is no way to see what builds had what support levels for a specific device? Like no timeline for the support the device had? For example: March 2020 -> Community June 2022 -> Standard December 2023 -> Community Thats the sort of thing I mean. Maybe this information just isn't kept, just thought I'd ask incase it was.

I completely understand this and I am not trying to pick a fight with anyone about what is and isn't supported I had read that link earlier on the different support levels to understand the differences between them. But what I am asking is from all the builds on here: https://armbian.hosthatch.com/archive/orangepizero/archive/ Is there a way for me to know which builds were produced when this particular device was considered standard support and which builds were produced when this particular device was considered community support? I would like to pick the most recent build that was produced when it was considered standard support. Basically I would like the most recent build that didn't have the disclaimer here: https://www.armbian.com/orange-pi-zero/ about the possibility of things not working (hopefully that makes sense). This is sad because in my limited experience Armbian works very well on OrangePi, its a pity that they wouldn't support it themselves.

Hi robertoj, I’m not specifically having issues, my current device is running an older version. I bought a new second device and came to download an up to date OS and thats when I noticed its not got standard support anymore and the download page mentions there might be wifi issues. I more made the post to see if there is a way of telling which older builds had standard support and when that support stopped. Then I could download the latest build that still had standard support and hopefully less issues. Thanks!

Hi, I think I'm right in saying that this board once had standard support? I noticed it is now community support and the download page lists that there might be Wi-Fi issues. I have this link for previous builds: https://armbian.hosthatch.com/archive/orangepizero/archive/ Is there a way of knowing when standard support stopped and community support started etc? Thanks!

Hi, I really apologise if the information is out there and I just haven't found it. I was looking to buy a board for a small embedded GUI application and this one seems to fit the bill. I would like to use Wi-Fi, Bluetooth and HDMI. Is there a list of what is working or not working on each build/version? (This is probably a more general question to Armbian for any device) The only thing I could find is this: But it's not that recent. On the download page: https://www.armbian.com/orange-pi-zero-2/ under specifications it does list, Bluetooth and Wi-Fi but I'm not sure if this means its now working? I also saw some forum posts talk about old builds, where can they be found, all I can see is this (linked on the download page): https://fi.mirror.armbian.de/archive/orangepizero2/archive/ and it only has 1 version. One last question, if Wi-Fi or Bluetooth don't work, does that only mean onboard Wi-Fi and Bluetooth and that a dongle would work? Thanks!

Unfortunately I don’t know enough about what isn’t there on minimal. I have read this: Minimal images comes only with essentials and without armbian-config, armbian-zsh, build-essentials, Python, DKMS I run a hotspot from the orange pi, along with a C++ application that interacts with 2 serial connections. I should have a play with minimal and see if I can get it working. It would likely boot faster which is one thing I’d really like from the OrangePi!

I have my Orange Pi running for a while on the CLI release of Jammy with kernel version: 6.6.16. It has been working well. I was building another one up and I went to download Armbian and I noticed that OrangePiZero is community supported now (Don't think it was before?). The current version to download says that network issues are expected. I never had this on 6.6.16 so wanted to stay on that. I looked here: https://armbian.hosthatch.com/archive/orangepizero/archive/ But there is only minimal for 6.6.16, all/most others have minimal and CLI (typical, the one I want lol) Is there somewhere else I could find the CLI version of 6.6.16, it definitely used to exist as I have it on another OrangePiZero. Thanks!

I will have to check for you. It will be after the weekend as I need it for then and I have to take it out of an enclosure to get at the serial debug pins

It wouldn’t boot. I put the SD card back in the original Pi and it was fine. I flashed a new SD card with the exact same image and it booted straight away. I have a script to setup new images, setup the new one the same as the old one and its working fine. just can’t seem to swap SD cards

Should it be possible to take a working SD card out of one OrangePi Zero and put it in a new one? Same board and amount of RAM and everything.

Sync has done the trick! I agree that some sort of battery that that has enough capacity to let it shutdown properly is the better solution, but a phone power bank is too big and bulky. It needs to be mounted in a car so needs to be as neat and small as possible

Hi, I use an OrangePi Zero as a race timer for a car. It is powered from the car. So when the car starts the OrangePi gets power and boots and when the car is turned off the OrangePi loses power and "turns off". This isn't ideal but I don't have a lot of options. I feel like this is a fairly common use case for electronics in cars especially ones like race timers etc. Unless I have a battery as well. I was wondering what are the best things to do to protect against the sudden power loss so that I don't corrupt anything? Is it possible to make parts of the file system read only maybe? All I do with the OrangePi is run a C++ application, it uses two serial ports and runs a server on port 80. The application does read and write its own configuration files and log files. But these are not OS files, only files that the application created itself. I have noticed that after writing or appending to a file from C++, if the power is pulled and then plugged back in the change to the file does not persist. I can ssh on before the power is pulled and `cat` the file and see that it is updated. Seems that the file data is held in RAM for a little while before actually writing. Is there anyway to force file writes to actually be flushed and written straight away?

Hi, This will be my first time using Armbian and OrangePi, sorry if theres stupid questions. I want to write a C++ application that uses LVGL to display information on a USB screen and have a few questions. 1) Will I be able to this screen in this setup. It uses the frame buffer (/dev/fb0). There are instructions for RaspberryPi, where its just plugged in and the frame buffer is available to use. 2) If I just use the latest Armbian Ubuntu version for this board what is the newest version of C++ I can use? (C++11/14/17 etc) 3) Is there a tool chain available to be able to cross compile my application (specifically from MacOS) then put the binary on the OrangePi? Or will I have to use something like docker and build for ARM? Thanks!