Update LinuxCNC 2.9.5 on debian 13

Here comes the "Grumpy Old Man Response".

1: That's your method. I was held back from including gnome network manager, a situation that didn't sit well with myself. Which is great as the user can have the option of enabling and disabling wifi as required. Adding this will be an improvement (as will the turnng off of the power saving features of the wifi, something I haven't recommended as thb I could see it being more hassle that it's worth to describe what is required, delving into systemd is required). Tho I did manage to sneak in gvfs-backends & gvfs-fuse. The zram swap thing was a bit of a debacle, something I blame myself for not fully checking the swap, which did rear it's head. Yes I get the ID Ten Tea award for that.
2: No patch was required for RT_PREEMPT, that was part of the Vanilla Kernel that was selected (which required thought put into it) and many thanks to a certain member that helped clarify a few things regarding that, any patches applied were those that the RPi Foundation has on their github, no trickery on our side. Until their particular patches make it to the mainline kernel they will always be applied.
3: You could of asked. Now this is really the bit I thought was a terrible assumption to make.You think those that manage Linuxcnc allow randoms to upload untested content to their server ? That is something extremely silly to assume, especially with 20 years of Linux experience.
4: Up to you.
5: That's people assuming things regarding the menu config. It has been clearly stated that whilst the image runs on the RPi and the kernel has been sourced via the RPi Foundation, it is Debian at is core and not RPi OS. Someone who thinks critically would assume that there would be differences in how things are done. Not understanding, excepting or realising that that things will always be the same way on a particular platform is rather naive (I would say silly myself).Apart from the kernel and a couple of RPi specific utilities, Debian was the easier solution. Basing anything on RPiOS requires removing a lot of Raspberry Pi Foundation branding from any image that was built and distributed. Hence the reason there was a switch from using Ubuntu in the emc2 days to Debian now.

Being able to actually install Linuxcnc & a required kernel onto a Raspi OS image would have been infinitely simpler, but the copyrighted branding becomes an issue. Which is their right and a good thing as well as it a protection for users, as a lot of people will blindly down load this or that. Hence scammers have it easy.
Supplying instructions for getting Linuxcnc on a Raspi image may have been one way, but people being what people are. I used to be a traffic controller and have lost confidence in people being able to follow instructions or wanting to.

Ok some further research has come up with some utils to build images based on 'the Rpi way".

Some of your comments have caused some rethink of the situation.

Now I think I should eat some humble pie. Would this be a situation where you would like to give a little more input. Consideration of your comments makes me thinks a more "Raspi OS" experience maybe a plus for the next generation of users. A new thread might be a better way to approach this. If you have the time it would be well appreciated.

Kind Regards
Rob

1. All of this is my method. I'm not implying it is better or worse than yours, it's just mine.
2. There still is/was a patch that exposed /sys/kernel/realtime that linuxcnc required before 2.9.5, and the kernel is still built from source and baked into the image, as opposed to being installed from an apt repo. That makes the kernel update path unclear to me.
3. I could have asked, but I didn't. I never implied that "those that manage Linuxcnc allow randoms to upload untested content to their server", I'm sure the images are well tested and vetted. All I said is that it is completely non-obvious where the image builder sources are - I've just spent 10 minutes to find them again and I couldn't - and the official github has obsolete sources. That doesn't inspire much confidence in how well those images would be maintained in the future, don't you think?
5. I understand there are differences, it is obvious, I just don't want those differences. I gain nothing by learning how yet another distro is organized, it is wasted brain cycles. Now, your copyrighted branding point makes a lot of sense - I honestly did not think about that, and yes, it certainly adds a huge deal of motivation for not using RPi OS for pre-built images, but as I said even before your point, I totally get why your images exist. You've done a great job, I'm just not in the target audience for your work.

unknown wrote:

Would this be a situation where you would like to give a little more input. 
 

Oh certainly and with pleasure! Feel free to create the new thread and shoot me a link.

f355 wrote:

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

please read the notes on the downloads page to install wifi SSID. It is included but in the interest of latency, a network manager is not included.

After some testing and having my machine up for 39 days a network manager doesn't really affect latency, well at least on the RPi5 (I replaced the Odroid with the RPi5). And it does make it easier to turn wifi off when needed.