New and Working RTAI debs for 2.9

Just installed the latest RTAI deb set (5.4.290-rtai-amd64) (packaged with linuxcnc 2.9.4) from the usual place: onelaboratories.us/abc/ and i must say the latency is about half what 5.4.279 was on my pc. Also the GUI doesn't lag on boot like it did with 5.4.279.  Running a couple tests:

1: histogram with 4 glxgears, stress-ng & 2 yt the servo thread was 16.7us and 12.9us base thread.

2: histogram & unigine heaven the highest 23.8us base and 23.4us servo thread as seen in the histogram here.

Win! Win!

Hi, can you detail how you managed it, since other users have had problems? I'm having problems with rtai-modules-5.4.290_5.3.3-linuxcnc_amd64.deb
Another detail is that when I try to remove linuxcnc, I get another error. It says: Sub-process /usr/bin/dpkg returned an error code (1)

cnbbom wrote:

Hi, can you detail how you managed it, since other users have had problems? I'm having problems with rtai-modules-5.4.290_5.3.3-linuxcnc_amd64.deb
Another detail is that when I try to remove linuxcnc, I get another error. It says: Sub-process /usr/bin/dpkg returned an error code (1)
 

Guys, I found here what I needed to solve the problem, but when I open LinuxCNC, the screen goes black and restarts to the user login. However, I don't know if this is normal or if there is a problem, so I prefer to restart the machine.         forum.linuxcnc.org/9-installing-linuxcnc...ue-with-2-9-4#327437         

The 5.4.290 kernel debs are bugged, I was hitting that problem too with the screen going black. I need to downgrade the kernel and freeze the repo as there will be no more RTAI development. In the mean time, use the 5.4.279 kernel debs. 5.4.290 is broken. The latency test and everything else works, including the LinuxCNC sim, however when running an actual machine with 5.4.290, the system does indeed crash. I need to find the last working 5.4 kernel and make a few more changes to Kconfig, after that, RTAI will be considered frozen.

So, is RTAI over?

I'm already feeling nostalgic.

How difficult will it be to use RTAI from now on (from LinuxCNC 2.9.5 onward)?

The most recent setup I’ve been able to get working is kernel 5.4.258 + LinuxCNC 2.9.4, using the following .deb packages (with isolcpus=3):

linuxcnc.org/dists/bookworm/base/binary-amd64/
linux-image-5.4.258-rtai-amd64_5.4.258-rtai-amd64-2_amd64.deb
linux-headers-5.4.258-rtai-amd64_5.4.258-rtai-amd64-2_amd64.deb
rtai-modules-5.4.258_5.3.3-linuxcnc-delta_amd64.deb

linuxcnc.org/dists/bookworm/2.9-rt/binary-amd64/
linuxcnc_2.9.4_amd64.deb

I was not able to get 5.4.290 + 2.9.4 working, nor 5.4.279 + 2.9.2. (I will post the error messages later.)

The 2.9.7 release notes state: "RTAI is still supported, but in the short term, building from source is likely to be the most expedient way to get 2.9.7 on that platform."

I’m wondering whether this is a reasonably straightforward process, or if it requires deeper OS-level debugging knowledge.

If you use 2.10, there are some changes to make it easier by doing it the Debian way (to a Deb file). The Debian way installs all the required dependencies so check the 2.10 Docs. Otherwise there is a how to video on my MrRodW YouTube channel

Colleagues, I installed kernel 5.4.258-rtai-amd64 + LinuxCNC 2.9.4 (kernel 290 too). In all cases, the AXIS interface is launched only when you specify additional kernel options such as isolcpus=1 (I have two cores), etc. But it starts and shows good jitter.
However, the actual work does not last long, but is interrupted due to a constantly appearing error -
joint 1 following error(motor number may change).

Is this treatable?

There are lots of comments here abut running the 5.4.279 kernels, but I don't seem to be able to find them anywhere. Any clues?

The link in the first post of the thread says 5.4.279 but leads to 5.4.290 debs.

There is no point in looking for 279. Both versions of the same program start in the XYZ configuration and work normally. Both versions crash in the same way when working with XXYYZ.

abs32 wrote:

There is no point in looking for 279. Both versions of the same program start in the XYZ configuration and work normally. Both versions crash in the same way when working with XXYYZ.

This is a different question/issue. 

I was looking for the 279 kernel because I want to make a new 2.9.7 deb package (and possibly an ISO)

I am looking at your f-error and probe issues too, but I thought that a new package might be relatively easy.