New and Working RTAI debs for 2.9

More
2 years 3 months ago - 2 years 3 months ago #304786 by tlightus
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...
Last edit: 2 years 3 months ago by tlightus.

Please Log in or Create an account to join the conversation.

More
2 years 3 months ago #304787 by NTULINUX
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.
The following user(s) said Thank You: tlightus, JT, NickH

Please Log in or Create an account to join the conversation.

More
2 years 3 months ago #304794 by NickH
Newby Linux user, successful install(well software starts anyway!) exactly as Bari' instructions. I did have to purge the previous RTAI version.
Now to Ethercat, do I need to recompile for Ethercat servo, or is that package part of what I have just installed?

Please Log in or Create an account to join the conversation.

More
2 years 3 months ago #304806 by Mecanix
Well snap, jealous of those which .279 works. Doesn't seem to like my lenovo & 4ax milling machine for some reason :(
Reverting back to 5.4.258 sorts it in my case. 

Observations:
1. Upgrade from .258 -> .279 went smooth. RTAI starts and everything. (That's all good).
2. The isocpu grub init is indeed mandatory. Does not start otherwise. (I personally don't care!)
3. On a PC cold boot I can; start linuxcnc, home the machine, jog. (That's all good).
4. I do however get a new RTAPI ERROR. I didn't had this with 5.4.258. (see visual). 
5. If I close linuxcnc, it's impossible to start it up again. Needs a full machine reboot. (see attached logs/traces). 



 

Please Log in or Create an account to join the conversation.

More
2 years 3 months ago #304845 by NTULINUX
Hey Mecanix, are you able to start and close the latency histogram without rebooting? If not, try a more simple test. The RTAI testsuite is built-in and you can try running that as well.

It's: /usr/realtime*/testsuite/run (Ctrl+C to cancel)

Please Log in or Create an account to join the conversation.

More
2 years 3 months ago #304853 by Mecanix
Good and bad news. Bad news first; I've put back 5.4.258 temporarily. I really terrorized myself yesterday when I saw it broken (sweats man lol), knowing I desperately need this mill all of this coming Saturday and Sunday (important project). And so the bad news is I won't be able to test this out, at least not before the coming week.

The good news is; I'll surely reinstall 5.4.279 and give it another go. Let's get to the bottom of this, if not only to improve the making of RTAI. I'll update in 4~5 days max.

Side note. I've just placed a Dell Optiplex 780 w/ a built-in parport on order to backup with. That way I can test on real hardware before making changes to the production-ready kit - yesterday's self-terrorism just can't happen again.

Please Log in or Create an account to join the conversation.

Time to create page: 0.426 seconds
Powered by Kunena Forum