RPI4 Raspbian 64 bit & LinuxCNC

What you to need to remember whilst the kernel is Raspbian , the underlying OS is pure Debian.

rodw wrote:

I thought the "normal" Raspberian style would use rpi-imager  www.raspberrypi.com/software/
Balena Etcher is also an alternative which runs on any platform and is way faster than dd

Getting a little OT but rpi-imager/etcher is primarily a means to create a bootable SD Card from a .img file. I was talking about migrating a live system running on an SD Card to a USB SSD on a RPi and yes there are pretty, gui ways of doing this in Raspian World for people that can't spell dd

Back on topic; as LinuxCNC is an official part of Debian Bookworm, given a bootable Bookworm for the RPi (which Cornholio seems to have given us; thank you) going forward users would just "apt update", "apt upgrade" to get the latest official LinuxCNC release and life is good (even then why would you if it's all working? My Mill is happily running on 2.8.0-pre1 of 2016 vintage ).

There isn't really a need to generate new .img files that I can see until, possibly, Trixie comes along in a couple of years time with a different kernel; and even then a dist-upgrade might work (note to Cornholio: should there be a repo in sources.list for the rt kernel?).

So thanks to both yourself and Cornholio. I now have LinuxCNC 2.9 on Bookworm on my RPi with which to continue my lathe conversion.
 

On the Pi, you are not able to just do an apt update to get the latest version of linuxcnc. You will either have to get a newer img from us or build from source because there are no pi images being created by the new linuxcnc buildbot. The one in Bookworm is dated February I think.

I told you I am not a pi user....image missing /media/kunena/emoticons/w00t.png

And not having much luck here, Somehow I have corrupted the linux internals so need to install linux again
Just trying to do the final mucking arround to save the linuxcnc debs in the output folder.

The rt kernel is built from source and as it stands there is only one branch of RPi 6.x sources that match an available set of real time patch set.
To have a repo for the kernel someone would have to have a server setup as repo. I did that once (for packages built for Linuxcnc on Mint) and no not again.

rodw wrote:

On the Pi, you are not able to just do an apt update to get the latest version of linuxcnc. You will either have to get a newer img from us or build from source because there are no pi images being created by the new linuxcnc buildbot. The one in Bookworm is dated February I think.

I told you I am not a pi user....image missing /media/kunena/emoticons/w00t.png
 

I'm going to try and scp to copy from the qemu guest (which is doing the build) to the host (the machine running image builder)

rodw wrote:

On the Pi, you are not able to just do an apt update to get the latest version of linuxcnc.
 

Now I'm confused again (easily done).

As LinuxCNC is an official Debian thing hosted in the Debian repository then the package maintainer will, presumably, have to love and care for it, push stable updates to Debian which then become available to update like any other Debian package. A Debian version isn't frozen; just look at the number of in-release updates.

This obviously won't get the latest bleeding edge dev version but should cover the stable released ones.

Or am I totaly misunderstanding the point of getting LinuxCNC into the official Debian repo?