Advanced Search

The RPi doesn't require an installer the way the PC platform does.
Plus I'm looking at some other tools put out by the Raspberry guys that look pretty good.

I've been playing with pi-gen.....I think it is a little better, you get a more raspberry pi like experience. There's a link in my proposal thread. ATM the moment I've been building upto the "lite" stage burning & booting and installing the desktop,Xorg and the rest. Linuxcnc has been from the debian repo.....But I should be able to fine tune things.

Bookworm has been the target so far, Trixie shouldn't be an issue, but one thing I really need to know is the status of linuxcnc.org/docs/2.9/html/drivers/hal_gpio.html . I think there was an issue with the libgpiod library.
Bookworm version is 1.6.3-1
Trixie version is 2.2.1-2

You can burn to your boot device sing RPI-Imager and edit settings such via the imager.

There's realtime kernels available via the raspberry kernel repo. The Rpi4 4k page kernels run on the Rpi5.......so we may only need one image to cover both boards.

f355 wrote:

However, the debian package itself seems to have a broken python3 dependency. I'm on the latest Raspberry Pi OS Lite (which is basically trixie with a custom kernel and a few Pi-specific tools installed). Any particular reason for the arm64 package to want python3 < 3.12? amd64 one depends on 3.13, and so does linuxcnc-uspace 2.9.4 that comes with trixie.
 

It's possibly a consequence of the recent Pi .deb that I posted being built on Bookworm as I don't have a Pi running Trixie at the moment. 
The Debian package control files don't specify a version, but it is possible that a dependency is introduced by the configure step of the software build. 

I have a feeling that the package for the Pi in www.linuxcnc.org/dists/trixie might be the Bookworm package rather than one built on Pi/Trixie. I don't know how that happened at this point, I might just have been hoping that it would work and have now found out otherwise