I am sharing images for the Banana Pi M2 Zero, slots 1 to 4, that work on top of the ClusterHAT :They have only been tested with ClusterHAT 2.5 and usbboot is left out, so you will need to burn SD cards for normal USB boot. Serial is left out as well.
User name is "pi" and password is "clusterctrl" as with normal clusctrl images.After logging in, you will need to manually run a command to expand the filesystem:sudo systemctl start armbian-resize-filesystem.service
Enjoy!On a more technical note, this is based on the armbian system, a fork of raspbian for boards with a similar form factor as the Raspberry Pi. It features a custom 5.4 kernel with dwc2 and udc-core built-in and g_ether loaded as modules.The UDC binary was ported from the raspberry pi zero image too, and enabled as a service.Vassilis
--
You received this message because you are subscribed to the Google Groups "ClusterHAT" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clusterhat+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/clusterhat/a7f145f6-ffd2-4f75-820d-ed52a31229abn%40googlegroups.com.
Thank You Vassilis!If the “serial is out” do we have to use the M2’s WiFi for acces/ssh-ing into it?
I am sharing images for the Banana Pi M2 Zero, slots 1 to 4, that work on top of the ClusterHAT :They have only been tested with ClusterHAT 2.5 and usbboot is left out, so you will need to burn SD cards for normal USB boot. Serial is left out as well.Did you mean normal SD card boot?
User name is "pi" and password is "clusterctrl" as with normal clusctrl images.After logging in, you will need to manually run a command to expand the filesystem:sudo systemctl start armbian-resize-filesystem.serviceAfter only initial first boot?
--
You received this message because you are subscribed to the Google Groups "ClusterHAT" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clusterhat+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/clusterhat/0120d947-4318-4142-801a-f22ff718f22cn%40googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/clusterhat/4e34647e-649a-4e80-8f42-7fb9c3530d28n%40googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/clusterhat/b59a4415-781f-4780-9d1a-c80b54cb64cen%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "ClusterHAT" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clusterhat+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/clusterhat/f42a658a-ed56-4f26-aabc-26f6863140cfn%40googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/clusterhat/65bb744c-51e5-473f-a04e-fb4e9c6ccee0n%40googlegroups.com.
where X is replaced by either cbridge, cnat, p1, p2, p3, p4
pi@c4nat:~ $ kubectl get node -o wide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
c4nat Ready control-plane,master 81m v1.20.2+k3s1 192.168.100.164 <none> Raspbian GNU/Linux 10 (buster) 5.10.11-v7l+ containerd://1.4.3-k3s1
p1 Ready <none> 76m v1.20.2+k3s1 172.19.181.1 <none> Armbian 21.02.2 Buster 5.4.88-sunxi containerd://1.4.3-k3s1
p2 Ready <none> 76m v1.20.2+k3s1 172.19.181.2 <none> Armbian 21.02.2 Buster 5.4.88-sunxi containerd://1.4.3-k3s1
p3 Ready <none> 57m v1.20.2+k3s1 172.19.181.3 <none> Armbian 21.02.2 Buster 5.4.88-sunxi containerd://1.4.3-k3s1
p4 Ready <none> 27m v1.20.2+k3s1 172.19.181.4 <none> Armbian 21.02.2 Buster 5.4.88-sunxi containerd://1.4.3-k3s1
p3 Ready <none> 173d v1.21.3+k3s1 172.19.181.3 <none> Armbian 21.05.6 Buster 5.4.88-sunxi containerd://1.4.8-k3s1
c4nat Ready control-plane,master 173d v1.21.3+k3s1 192.168.100.164 <none> Raspbian GNU/Linux 10 (buster) 5.10.17-v7l+ containerd://1.4.8-k3s1
p4 Ready <none> 173d v1.21.3+k3s1 172.19.181.4 <none> Armbian 21.05.6 Buster 5.4.88-sunxi containerd://1.4.8-k3s1
To view this discussion on the web, visit https://groups.google.com/d/msgid/clusterhat/32ff38aa-2546-4dce-9792-7676f997602dn%40googlegroups.com.
but unclear of the process. I did try it to no avail. Do I do them one by one? Do I put multiple lines in the cmdline.txt such as
quiet init=/sbin/reconfig-clusterctrl cbridge
quiet init=/sbin/reconfig-clusterctrl p1
quiet init=/sbin/reconfig-clusterctrl p2
quiet init=/sbin/reconfig-clusterctrl p3
quiet init=/sbin/reconfig-clusterctrl p4
OR do I need to do them one at a time?
Thank you for replying back.
To view this discussion on the web, visit https://groups.google.com/d/msgid/clusterhat/37f9fae0-c6d7-4a60-8ac6-2626f1d59a6cn%40googlegroups.com.