Successfully configured with stepconf: but +Y-axis "stutters" running G-code

Tommy,

Remember the prototype text-based "Adventure Game?"

"You are in a maze of twisty passages, all of which look alike."

Off I go to try that passage. (Thanks for doing my work for me and re-pasting the link; and repeating yourself.)

clunc wrote:

Remember the prototype text-based "Adventure Game?"

"You are in a maze of twisty passages, all of which look alike."

No!
Strange as i recall a lot, but definitely the most played game in the younger days was "Monty on the run" on a Commodore 16.

I sometimes get GUI lockup if I leave the dongle for the wireless keyboard plugged in. If i look at dmesg from a remote PC I can see that USB connect/disconnect messages are flooding the system.
I am not saying that your problem is caused by mu keyboard, but it could be something similar.

(I misremembered the name anyway; it was called "Colossal Cave" and it was played on pre-Commodore "mini-computers," like the PDP-11. I encountered it first on a VAX and then on a later port to the Zenith Z-100.)

Fear kept me dragging my feet on doing the RTAI install.  I am something of a fool however, as I quickly re-learned when finally forcing myself to the task.  One of the most trivial things I've done wrt to LinuxCNC.

Having followed the steps (Sec. 7.2) and rebooted, the 4.19.195-rtai kernel was not offered on the grub menu.

I located it on the boot partition associated with the version of Debian 10 I'd originally installed the RTAI on, but have not been successful getting it to be one of the menu choices. In trying to get it recognized (by update-grub) I managed to muck up the system so the original Debian 10 won't boot either.  (I am something of a fool...)

I still have a booting version of Linux Mint which I'm using to try to straighten out the booting.

(Debian's boot error says "file <old-vmlinuz-rt-amd64> not found" and that I have to "load the kernel first".)

When I learn how to edit a grub entry to add the paths to the rtai files, I'm sure it will boot again, after which I'll try to run update-grub again.

I managed to fix booting and even have Debian 10 with the 4.19 rtai kernel booting as the default.

The problem is that neither latency-test nor latency-histogram will run.

latency-histogram says:
insmod: ERROR: could not insert module /usr/realtime-4.19.195-rtai-amd64/modules/rtai_hal.ko: Unknown symbol in module

latency-test says:
insmod: ERROR: could not insert module /usr/realtime-4.19.195-rtai-amd64/modules/rtai_hal.ko: File exists

Running dmesg as directed:
thread: Unknown symbol hal_create_thread (err-2)
thread: Unknown symbol hal_ready (err-2)
thread: Unknown symbol hal_exit (err-2)
thread: Unknown symbol rtapi_print_msg (err-2)
thread: Unknown symbol hal_init (err-2)
 

I have just installed linuxcnc + rtai here, according to the instructions, and it seemed to work.

It is possible that your system has reverted to a non-rtai kernel, what does uname -a tell you?

You shouldn't need to update grub to choose the new kernel, it should be there under "advanced options" in the grub menu. (And, if all is well, should "stick" once you have chosen it, but I have had problems with that in the past)

The instructions to install the RTAI kernel and LinuxCNC should work on a fresh install of Debian or Mint as well as on top of a LinuxNC uspace installation from the ISO.