Fix for "FileNotFoundError" when running clusterctrl on Pi 5

[ClusterHAT]

Hi,

 When using Bookworm on a Pi 5 with the latest kernel (6.12.96+rpt-rpi) available via apt the /dev/gpiochipX name is no longer fixed to /dev/gpiochip0 (with gpiochip4 symlinked).

For Pi 5 users on Bookworm this causes an error when using clusterctrl tool.

$ clusterctrl status
Traceback (most recent call last):
  File "/usr/sbin/clusterctrl", line 379, in <module>
    GPIO = FakeGPIO('gpiochip4')
           ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/sbin/clusterctrl", line 356, in __init__
    self.chip = gpiod.Chip(chipname)
                ^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory

For those running into the problem the following command updates clusterctrl to access the gpiochip by label rather than using a fixed device name.

sudo sed -i 's#self.chip = gpiod.Chip(chipname)#self.chip = gpiod.Chip("pinctrl-rp1", gpiod.Chip.OPEN_BY_LABEL)#' /usr/sbin/clusterctrl

Chris.

[Ted Serreyn]

so fixed the issue with clusterctrl, however now it appears that the pi zeros are no longer booting.  I see the boot device, but never get the autoboot to start.

[Ted Serreyn]

Follow up, clusterctrl-rpiboot is now failing to start due to dependency.

Ted

--
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, visit https://groups.google.com/d/msgid/clusterhat/9e9c6d84-2910-48b4-bcd0-e0c3e2a63eacn%40googlegroups.com.

[ClusterHAT]

Hi,

Follow up, clusterctrl-rpiboot is now failing to start due to dependency.

Do you have a copy of the error? I assume you're using a Pi5 as the controller but with which release (bookworm/trixie/etc.) so I can replicate the issue?

Thanks,

 Chris. 

[Ted Serreyn]

I think I’ve resolved.  After fixing the clusterctrl program to address the gpis device problem, a reboot must be done to initialize things correctly.

Clusterctrl-rpiboot needs to run after clustertrl-init, both of which occur on initial boot up.

Ted

From: ClusterHAT <clust...@googlegroups.com>
Date: Friday, August 21, 2026 at 7:05 AM
To: ClusterHAT <clust...@googlegroups.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, visit https://groups.google.com/d/msgid/clusterhat/e24bf5a4-e5f1-4118-a38f-48ee15af28b4n%40googlegroups.com.

[Steffen Schlaer]

Hello together,

I also ran into this issue after running sudo apt update and sudo apt upgrade on my Bookworm based Pi 5 controller board. Before the upgrade all was working fine.

I applied provided sudo sed command snippet from Chris' initial post and triggered a reboot of Pi 5 cluster controller board. Then clusterctrl init and rpiboot services started without any issues again.

So maybe add also the hint to initial post, that a reboot is required or maybe restart of clusterctrl services, if this is enough :)

Thx Chris