TESTING: ClusterCTRL images (based on Raspberry Pi OS Bookworm 2023-10-10)

[ClusterHAT]

TESTING: ClusterCTRL images (based on Raspberry Pi OS Bookworm 2023-10-10)

I've uploaded test images (and usbboot archives) to https://dist.8086.net/clusterctrl/testing/ I'd be grateful if people could give them a test and let me know if you have any problems.

There are a few changes vs bullseye on top of the regular Bookworm changes.

rsyslog is installed alongside journald to allow easy access to logs in /var/log/ but it will increase disk usage/access so if you don't want it you can removing it with "sudo apt remove rsyslog".

If you need to configure a static IP for CBRIDGE (br0) or USBBOOT (usb0) these are configured in /etc/dhcp/dhclient.conf (dhcpcd is no longer used).

xclusterhat tool has been removed for now as it only works with ClusterHAT v1 and needs a complete rewrite.

When using USBBOOT (booting Pi Zeros without SD card) you must put ssh / userconf.txt files into /var/lib/clusterctrl/nfs/pX/boot/firmware/ and not /var/lib/clusterctrl/nfs/pX/boot/ as with bullseye and earlier versions.

If you want to try a Bookworm usbboot archive on an older distribution you will need a later version of the "clusterctrl" tool (due to the firmware now being in /boot/firmware).

sudo mv /usr/sbin/clusterctrl /usr/sbin/clusterctrl.bak
sudo wget https://raw.githubusercontent.com/burtyb/clusterhat-image/master/files/usr/sbin/clusterctrl -O /usr/sbin/clusterctrl
sudo chmod a+rx /usr/sbin/clusterctrl

The second USB Gadget serial interface is now disabled by default. If you need to add it back remove the comments in front of the "acm.usb1" lines in /usr/sbin/composite-clusterctrl and reboot.

Added "is_pi5:" the output of "clusterctrl status" to helps with support as the script uses gpiod on the Pi5 to access GPIO.

Please remember.

64-bit images will only work on 64-bit hardware.

Bookworm is needed when using a Pi5 but you can still mix different versions (bullseye/buster/etc.) on other controller/pi zeros/etc. components in the cluster.

Chris.

[Ted Serreyn]

Anyone trying to run with zero 2 W?  I really need to switch over to 64bit across the board.

 

Is power still an issue running with 4 of them?

 

 

[ClusterHAT]

Hi,

Anyone trying to run with zero 2 W?  I really need to switch over to 64bit across the board.

I've been testing Bookworm on the Pi Zero 2 and they look to work OK from what I've been doing with them.

Is power still an issue running with 4 of them?

Yes, you'd still need to think about the power usage.

Using a Pi 5 as the controller with the official 27W PSU would probably be sufficient, running stress on the Pi5 uses 9.7W and on four Pi Zero2 =4*3.4W so 23.3W in total but as normal it depends on what else you have plugged in and your real world power usage.

Chris. 

[ClusterHAT]

Using a Pi 5 as the controller with the official 27W PSU would probably be sufficient, running stress on the Pi5 uses 9.7W and on four Pi Zero2 =4*3.4W so 23.3W in total but as normal it depends on what else you have plugged in and your real world power usage.

I tested the Pi 5 with four Pi Zero 2W earlier with the Raspberry Pi 27W PSU and it powers them OK (all 5 Pi running stress-ng) but you'll need a 5V@5A capable PSU as it uses ~4.5 Amps.

https://widget.uk/@burtyb/111409986343625090

Chris.

[bowguy]

Password for pi?

[bowguy]

Nevermind - I remember now.

  When you get a chance, could you  add the directions to create the userconfig.txt and copy it to the boot directory near the end of :

https://8086.support/content/23/103/en/clusterctrl&colon-how-to-write-an-image-to-the-emmc&quest.html

Right now, I have burned the bookworm lite 64 bit imageto a CM4 module on a ClusterTriple.  Working fine so far.

[bowguy]

I need to set a fixed IP for the CM4 running Bookworm.  What shoud the file /etc/network/interfaces.d/clusterctrl look like for a fixed IP ?

Thanks

[Chris Burton]

Hi,

  When you get a chance, could you  add the directions to create the userconfig.txt and copy it to the boot directory near the end of :

https://8086.support/content/23/103/en/clusterctrl&colon-how-to-write-an-image-to-the-emmc&quest.html

Thanks for the suggestion, I've updated the article.

 

 I need to set a fixed IP for the CM4 running Bookworm.  What shoud the file /etc/network/interfaces.d/clusterctrl look like for a fixed IP ?

You need to use /etc/dhcp/dhclient.conf now to set a static IP, replacing the br0 (controller) or usb0 (Px) section with your own IPs.

Chris.

 

[Tony Brack]

Hi Chris,

I am assuming you are looking for feedback with this post. Apologies if I am mistaken.

Mainly using bookworm clients, 1 of each type in my test cluster, plus a back-rev BananaPi. I don't know if you are looking for feedback, but nothing insurmountable here, just a few unexpected behaviors.

1. only one serial device now, not login enabled, but easily fixed with:

• $ sudo systemctl enable serial...@ttyGS0.service
• $ sudo systemctl start serial...@ttyGS0.service

Having this enabled from the onset would make troubleshooting a lot easier.


Use of network-manager seems to be fighting itself. It comes enabled, so only the WiFi interface comes up on first boot for devices that are so equipped. For the pi zero I had to put the SD card in a pi zero W to configure the TTY to allow logins first, then I was off to the races. Once network-manager is disabled, then the USB network interface comes up and the physical WiFi connection goes down, if there is one. This shouldn't be too hard to deal with. Incidentally, I'm bridged and running an AlmaLinux controller (shouldn't matter).

That's as far as I am: still playing ...

Hope you are doing well, and best Holiday Wishes! 

[Ted Serreyn]

So finally got my RPi5 and Pi Zero 2 to rebuild the cluster.

 

I put active cooler on the rpi-5, its tight.

 

Clusterctrl says is_rpi5 is false?

 

Trying to get usbboot working too.

Clusterctrl fan on fails.

 

I presume this has to do with the gpiod that is mentioned.

 

root@cnat:/var/lib/clusterctril/nfs# clusterctrl status

lusterhat:1

lusterctrl:False

axpi:4

throttled:Ox0

hat_version:2.5

hat_version_major:2

hat_version_minor:5

hat_size:4

hat_uuid:16aeb902-9d28-11ea-bb37-0242ac130002

hat_vendor:8086 Consultancy

hat_product_id:0x0004

is_pi5:False

hat_alert:0

hat_hub:1

hat_wp:1

hat_led:1

hat_wplink:0

hat_xral200p:True

pl:0

p2:0

p3:0

p4:0

 

oot@cnat:/var/lib/clusterctrl/nfs# clusterctrl fan on

raceback (most recent call last):

File "/usr/sbin/clusterctrl", line 1051, in <module>

GPIO.setup(fangpio, GPIO.OUT)

RuntimeError: Cannot determine SOC peripheral base address

 

 

--
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/13864d8c-a877-44fd-9427-c8e366b0b774n%40googlegroups.com.

[Ted Serreyn]

One other error I am seeing with usb-booting attempts:

 

2024-01-27T718:29:41.261975-06:00 cnat systemd-udevd[358]: /etc/udev/rules.d/90-

clusterctrl.rules:18 Invalid value "/bin/bash -c 'echo 0x3171 Ox$ID_MODEL_ID >>|

/sys/bus/usb/drivers/i2c-tiny-usb/new_id'" for RUN (char 29: invalid substitut]

ion type), ignoring.

 

So far usb-booting is failing.

 

I went with the cnat bookworm desktop image for the RPi5 and the bookworm usbboot-lite for the pi zero 2’s

Ted Serreyn