Kiendeleo

I am attempting to use an Orange Pi Zero 2 as a NUT server (Network UPS Tools) server to be able to monitor all of the UPSs from a central location. The Zero2 is small and low power enough to provide the hardware that goes on each UPS, and wifi seems more than sufficient for this task. This is just one example of a "server" need for wifi.

Thank you for the prompt reply. The main thing I was looking for is wifi. What would be the first step in diagnosing and fixing that problem? Also is there something I can do to contribute the changes on the 1.5version board?

So there is some weirdness happening with Armbian on the Orange Pi Zero 2 that I bought from Amazon. These are the V1.5 version of the hardware. With the Orange Pi image (which looks strangely like armbian), once the device is booted, the red led goes off, and the green led turns on. With the armbian image, the red light stays on, and the HDMI output does not turn on in the CLI image. This led me initially to think this board was not working. Once I hooked up a USB to Serial interface, I noticed it booted. Well, at least when the SD card was seated correctly, but that is a hardware problem. Once booted, `armbian-config` does not show the wifi interface settings.

The first time I ran this command, I was only presented with "Boot from SD" and "Boot from SPI" as options. The only drives attached to the board were an eMMC and an NVME Drive. I chose the "Boot From SD" and selected my NVME drive as the target in the next step, which seems to work. After completing the conversion and rebooting, if I run the `sudo armbian-install` command, I am given options for the eMMC. It is working correctly. Is this a bug? Also, is there a manpage somewhere for the `armbian-install` command?

I know a solution is being worked on for the lack of NVME boot capability. In the meantime, is there a way to install only the necessary files to an eMMC drive and the rest to an NVME to work around this limitation?