Gunjan Gupta

Easier method: create an device tree overlay and use the same.
 
/dts-v1/; /plugin/; &{/soc} { ehci0: usb@1c14000 { compatible = "allwinner,sun8i-r40-ehci", "generic-ehci"; reg = <0x01c14000 0x100>; interrupts = <0x00 0x27 0x04>; clocks = <&ccu 0x2f>; resets = <&ccu 0x17>; phys = <&usbphy 0>; phy-names = "usb"; status = "okay"; }; ohci0: usb@1c14400 { compatible = "allwinner,sun8i-r40-ohci", "generic-ohci"; reg = <0x01c14400 0x100>; interrupts = <0x00 0x28 0x04>; clocks = <&ccu 0x32>, <&ccu 0x7f>; phys = <&usbphy 0>; phy-names = "usb"; status = "okay"; }; };  
Assuming I didn't left any syntax errors in the above overlay, you should be able to create a dts file with the above content and then use "sudo armbian-add-overlay <dts-filename>" to enable the same

@Stephen GrafThats upto the maintainers of the boards. As of now, I don't have any H616 boards.
 
I am about to raise a PR that should get wifi running, so keep an eye on Armbian build repository.

Nice work. though this might all get overwritten on next upgrade. Hence I will suggest you to convert those dtb changes into a device tree overlay.
These might help you with the same
- https://bootlin.com/blog/using-device-tree-overlays-example-on-beaglebone-boards/
- https://docs.armbian.com/User-Guide_Allwinner_overlays/#using-custom-overlays

Fix has been merged and will be included in next release.

Fix is merged. Should work better once newer kernel is available via repository. Meanwhile you can use the above workaround.

Actually its quite easy to reproduce and already fixed for next release. The problem is caused by sprdwl_ng module aka uwe5622 wifi driver. For some reasons, It creates problem for cpufreq-dt when its loaded pretty early during boot process like using /etc/modules. This causes cpufreq-dt to crash and any attempt to check information about cpu like running lscpu simply hangs. I remember seeing that resize service also does some checks related to cpu and hangs when cpufreq-dt crashes.
 
If possible, Use images from the nightly/ rolling releases section of the Download page. They will work fine.

Bionic has been out of support for some time now. Try upgrading to focal and then to jammy to get to latest release. Alternatively, you can also download and flash latest image from the download page.

Thats sad. You can still try installing edge kernel to tezt it and then revert back to older kernel if it doesn't work as your liking
 
 
I can see the kernel modules for ST7735 is enabled in our kernels
config/kernel/linux-sunxi64-current.config:CONFIG_FB_TFT_ST7735R=m config/kernel/linux-sunxi64-edge.config:CONFIG_FB_TFT_ST7735R=m config/kernel/linux-sunxi64-legacy.config:CONFIG_FB_TFT_ST7735R=m  
 

This is interesting one. Kind of like how sd card names are different between different version of RPi.
 
You haven't mentioned the image you are using. But from the post I am deducing it was working fine for you until you installed an update?
 
I am not 100% sure as this is not a device I work with. But generally the root device is set in a file called armbianEnv.txt. Here is something for you to try 
 
mount your root partition
mount /dev/mmcblk0p1 /mnt check if /mnt/boot/armbianEnv.txt exists
ls /mnt/boot/armbianEnv.txt if it doesn't exists, create it. Replace <Your UUID> with UUID shown in output of blkid command
echo "rootdev=UUID="<Your UUID>" > /mnt/boot/armbianEnv.txt unmount your root partition
umount /mnt and reboot

try changing &pio to &r_pio when using PL8

I was able to narrow down the problem further. This seems to have caused because of net-phy-Support-yt8531c.patch. I am not sure why this patch is causing the issue but removing the stmmac part or changing config for stmmac from y to m solves it.