New and Working RTAI debs for 2.9

Sometimes it takes a few minutes for the panel and menu to load, I'm not sure why but I've noticed this with custom kernels on Debian.

As for the segfaults, I have an idea but it'd require new kernel debs..

NTULINUX wrote:

The LinuxCNC debs are the latest git checkout of the 2.9 branch as of a few days ago with some minor modifications.

List of changes:

github.com/NTULINUX/linuxcnc-rtai/commits/ntulinux/2.9-rtai/

Hey, I just wanted to say thanks to everyone testing these out and being part of the RTAI project. I spent a lot of time on RTAI and making improvements over the years and it's great to see that it's still very much alive and kicking in LinuxCNC.

That's awesome to hear. Couldn't have hope more for you to recompile RTAI with the latest commits... was shy to ask as this is voluntary based. And so thanks again x1000 for that. ps. few bugs from the initial 2.9 release that were annoying in that Dec '23, although nothing that can't be easily managed. Pretty epic and low latency controller regardless! 

I'm going to upgrade to latest in that case. Are we good to use the OP/Bari's release? ( onelaboratories.us/rtai_lcnc/ ). Or these needs to be dwloaded from somewhere else? 

There seems to be an issue with segfaults that are popping up with these debs. I want to try and fix these, and I'll be bumping the 5.4 kernel patch series to the latest from kernel.org as well. You're free to try the debs posted but they might be updated again soon.

Standby and awaiting your go ahead. Too kind man.

I really hope I'd have your knowledge and be able to help in any way. If testing is required, shout out and hopefully I'll be able to help out that way.

Added another RTAI set to the original post

forum.linuxcnc.org/9-installing-linuxcnc...-debs-for-2-9#304599

The biggest issue I've found is segfaults when using PYQT (flex) without isolcpus set. Set it and things run smoothly so far with both 5.4.258 and 5.4.279. Still trying to break it...

Tom is still having segfaults on his system with the 5.4.279 kernel but this only happens when he doesn't use `isoclpus=n` on the kernel cli. I'm not sure what's triggering it at this point but at least the 5.4 kernel patch series is up to date again.

I also forcibly enabled some basic memory debugging to try and catch some errors there too.

If everything goes OK for the majority of LinuxCNC RTAI users with the 5.4.279 kernel, I'll finally mark a new RTAI stable release.