Myron

@Igor, seems to be a bit of a problem. Server returning error 500. myron@loki:~/Install Armbian repo key$ sudo wget https://apt.armbian.com/armbian.key -O key --2022-08-16 18:04:47-- https://apt.armbian.com/armbian.key Resolving apt.armbian.com (apt.armbian.com)... 107.175.134.226 Connecting to apt.armbian.com (apt.armbian.com)|107.175.134.226|:443... connected. HTTP request sent, awaiting response... 500 Internal Server Error 2022-08-16 18:04:47 ERROR 500: Internal Server Error.

Try use this SD card formatting software. https://www.sdcard.org/downloads/formatter/

Recently, successfully, upgraded from Ubuntu Focal to Ubuntu Jammy. Does anyone know the correct procedure to sort out the apt-key deprecation issue? I've read apt-key(8), but I don't fully understand what I need to do. I think a Linux guru is needed here. 🙂 ~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. myron@loki:~$ s apt-get update Hit:1 http://ports.ubuntu.com jammy InRelease Hit:2 http://ports.ubuntu.com jammy-security InRelease Hit:3 http://ports.ubuntu.com jammy-updates InRelease Hit:4 http://ports.ubuntu.com jammy-backports InRelease Hit:5 http://packages.azlux.fr/debian bullseye InRelease Hit:7 https://armbian.github.io/configurator stable InRelease Hit:6 http://armbian.hosthatch.com/apt jammy InRelease Reading package lists... Done W: http://apt.armbian.com/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.

There were two unexpected events. The ssh group got renamed to _ssh and chrony got renamed to _chrony. Not sure why.

I'm back with my findings. It worked, with the only problem not being able to login by SSH. I had set up a group ssh and had AllowGroups ssh in the configuration and for some reason, commented that line out and used AllowUsers myron in and SSH access is restored after restarting the sshd service. I had to answer the questions about installing either the maintainers configuration or keeping the current configuration carefully. So.... Result..... I've upgraded to Jammy. 🙂

Use armbian-config to enable UART4.

I think I had a similar issue with Focal. I ended up using a USB to RS232 card and set-up the SBC through TTYS0.

I think this is done by editing the device tree using ... sudo armbian-config Why do you want to edit the model name?

Only reason I discovered the same is that when I shutdown Linux with poweroff, the SBC remained powered yet the OS has shutdown, so out came the USB to serial adaptor and I noticed the same. As mentioned before, it's not really an issue unless something that's pretty important that needs to be done before OS shutdown that does not get done as the exception terminates the shutdown process. I think in Kernel 5.10.x the Banana Pro SBC did power off correctly.

Providing logs with armbianmonitor -u helps with troubleshooting. Just a thought. during our auto start, what if you introduce a delay before attempting to play your wav file. The delay is to give time for things to initialise first.

Baud rate will be 115200. If that does not work then try 38400 and 9600. Set the jumper to 3.3v. If you try to use 5v you may end up destroying the board. You should be able to use a HDMI monitor and USB keyboard. For my (Lemaker Banana Pro) board that didn't work so I had to use an USB to RS232 converter to start and complete the initial set-up. Power the board using USB-C and do not use the 5V pin on the USB to RS232 converter? Not sure about which gpio pins to use. I advise you look-up the required documentation that should be available on Mango's web-site.

You can build the Armbian distribution yourself from source and how this is done is within the Armbian documentation. The only think you need to remember that if you build your image using the Armbian build framework then there is no official support. Regarding support: https://docs.armbian.com/User-Guide_Board-Support-Rules/ Regarding building your own image: https://docs.armbian.com/Developer-Guide_Build-Preparation/ You may need to customise the build environment to specifically accommodate the Banana Pi M2 Zero.

Yep. From your diagnostic logs: 793 2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 794 link/ether 02:81:6e:ea:b6:35 brd ff:ff:ff:ff:ff:ff 2072 [ 25.939521] dwmac-sun8i 1c30000.ethernet eth0: PHY [0.1:01] driver [Generic PHY] (irq=POLL) 2073 [ 25.947754] dwmac-sun8i 1c30000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0 2074 [ 25.949767] dwmac-sun8i 1c30000.ethernet eth0: No Safety Features support found 2075 [ 25.949785] dwmac-sun8i 1c30000.ethernet eth0: No MAC Management Counters available 2076 [ 25.949798] dwmac-sun8i 1c30000.ethernet eth0: PTP not supported by HW 2077 [ 25.955635] dwmac-sun8i 1c30000.ethernet eth0: configuring for phy/mii link mode 2078 [ 25.969182] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx 2079 [ 25.969259] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready This needs to be sorted out first. Try this command to try enable eth0 /sbin/ifconfig eth0 up

Providing logs with armbianmonitor -u might help with troubleshooting and significantly does raise the chances that issues gets addressed. Someone, hopefully, might spot a clue to the fault in the diagnostic report.

I have the same problem, but the OS does seem to cleanly shutdown, just does not power-off the board? @teknoid are you are aware of this kernel panic when shutting down the Banana Pro?

@Fuchsia You will need to connect a serial RS232 to USB board to the debug serial port of the orange Pi (if possible) and then use a serial terminal on your computer to see exactly what the Orange Pi is doing when it is powered up? I have a different board, but had the same problem. on @Werner's advice I got one of these boards connected it up and my board (A Banana Pro) was starting-up normally. Once I completed the initial setup over the serial debug port then everything fired up fine. Also, yes, what exact image are you trying to put on the SD card and are you using one of the two Armbian recommended SC card image writing programs?

What sub-net are you using? I'm assuming it's 255.255.255.0

When you connect a Serial UART to USB adaptor to your board, what output is shown?

If you can, providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Still, worth checking. Maybe there is some setting on a NIC that has disabled auto-MDI-X?

Erm... If this is a direct Ethernet connection between PC and SBC, is a cross-over cable required?

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Clutching at straws here as I'm not familiar with this SBC. What is the rated output of the PSU you are using to power your SBC? I believe it needs to be a minimum of 3 amps at 5 volts. Also, some of the hardware on the LTS version is different to the non-LTS version of the Orange Pi 3. I'm assuming the device tree will be different? At an absolute guess, is the device tree for the Orange Pi 3 incompatible with Orange Pi 3 LTS?

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.