Update LinuxCNC 2.9.5 on debian 13

SPI works fine, it is in fact what I'm using - my little pet project is here , it is basically a rewritten Remora for a particular off-the-shelf machine. The servo latency is alright too.

I'm not insisting my approach is better for everybody, I just found it easier for myself to write a few shell scripts (install.sh and linuxcnc/pi_init/ in the repo) that set up things on the stock RPi OS image. The official linuxcnc image might have ssh enabled, but the wifi is not, or at least I couldn't find a way to configure it with my SSID quickly, and connecting Ethernet is about as much hassle as connecting a display

f355 wrote:

I'm sorry if that came out sounding arrogant, that was not the intent. I totally understand why Tommy suggested apt update, I just wanted to quite literally save his and my time.

Writing is an inferior way of communicating for humans as it lacks the visual and auditory ques humans are used to, hence very often misunderstood.
BTW, i wrote a reply and promptly deleted it, as it was not obvious till you look at the version numbering, and back then i did not look, i just shot off the hip as that is usually what you get on a new install without updating first.
Thank you.

Like I said there's a large thread covering just about everything related to the RPi image, wifi works fine by the way even better when the power saving is turned off. And there is even a sticky thats an index to that thread with the intention being topics are grouped together.
But sometimes I wonder why I bother sometimes.

I'm sorry, what am I supposed to find in that thread? I don't have any questions about the LinuxCNC-provided image and never had. I came here to report a broken dependency in the apt repo, not to ask how to run LinuxCNC on an RPI.

Just to be clear, I have seen that thread, it is kinda hard to miss, and I've played with the image. For my personal preferences, I've decided to go with Raspberry Pi OS instead and I'm totally happy with it. What are we even discussing at this point?

Well I was the one that produced the image, so any feed back good or bad (bad seems to be more helpful for improvement) is welcome. That's why I was interested in the reasons for the way you went. Yeah I get it's for personal reasons, but I would like to improve it to make it a better experience for other users and maybe make a consideration for others.

That's the way some threads go, the discussion can go another way. But if you don't want to be involved in the way the discussion as gone, which would appear to be the case, I shall no longer ask for any opinions nor input from yourself.
Good day sir.

Ah, I did not realize the images were yours, I thought it was the great cornholio dude (is that your old account, maybe?) and rodw who worked on them for some reason. That explains your interest in my setup, cool, I can certainly give you some feedback on why I chose RPi OS.

1. as mentioned before, I can't connect to wi-fi without running menu-config, and to run it, I need either a console or Ethernet. Connecting either is a hassle for me, I tend to run my Pi's headless with TigerVNC/noVNC. I've briefly looked at the rpi-image-builder the images are based upon and it seems like it's possible to mount the boot partition and edit some text file there so it sets stuff up on the first boot, but I have not dug deep - with RPi OS I can set that up in RPi Imager, together with the ssh key, the username and other stuff, it's much easier and it just works.

2. The kernel is custom-built from source with an RT patch, which makes it tricky to update it if I ever need to. There are now official RT kernels in the RPi apt repo and I can just apt install the new kernel. In general, the update cadence/mechanisms for the entire thing were - and still are - unclear to me.

3. I couldn't find the git repo where these images are built from.  github.com/LinuxCNC/rpi-img-builder-lcnc is 2 years old, rodw's upstream is slightly newer but still older than the published images. It seemed like those images were built ad-hoc once by someone and just uploaded to the server, and that looked like a bit of a red flag to me.

4. cnc/cnc as default username/password is not something I want. I could create a user for myself, sure, but with RPi Imager I don't have to, so why bother.

5. this entire menu-config thing is not what RPi OS uses and what people - myself included - are familiar with. Not a big deal of course, but in general - Raspberry Pi has an official distro that is well-maintained and well-known, and I don't see why I, for one, should use something else in the second half of 2025. I understand why your images were built in the first place - PREEMPT_RT was not mainline at the time, RPi OS tended to push Wayland aggressively, you wanted a turn-key solution that less experienced people could just write to an SD card and use, my headless requirement is rather uncommon, etc., etc., but my personal preferences kicked in and I made a choice.

I hope that clarifies it!