Sorry I meant 2.9.4 Try not to get bogged down with latency. Test the machine running code, if it works don't worry too much about it. I took the gcode file that loads when you first start Axis, made it into a loop, loops thru the gcode about a hundred times,if I don't get any errors I'm confident it will be fine. I really don't think there will be much difference between a modular or monolithic kernel. You can gain a bit by fiddling with mount options, looking for any background services that aren't needed, I generally disable sound and I'll disable wifi if it's not required. You'll find this forum a lot different to cnczone, for one no one on here gets caught playing my rapids are this fast, also you won't here anyone saying that you need to be a programmer to use Linuxcnc. It works and works well. Almost any issues you have will have been discussed many many ten times over. 99.99% of the reason Linuxcnc won't start is a typo somewhere in the hal & ini files. Sometimes I think that running the latest kernel on older CPUs isn't the best course of action. Far better to have some extra latency and a stable system. Look you can spend a lot of time building different kernels and trying all the tricks in the book to lower latency, but as long as latency is, as a rule thumb, below 100,000 ns for an external step/direction generator you're good to go. Then again network latency can be a PITA to sort sometimes.
Yes i have Realtek card but i solved the problem with the r8168-dkms module.
root@cnc:/home/cnc/kernel/linux-6.12.27# cat .config | grep -i Preempt
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_PREEMPT_RT=y
CONFIG_PREEMPT_COUNT=y
CONFIG_PREEMPTION=y
CONFIG_PREEMPT_RCU=y
CONFIG_HAVE_PREEMPT_DYNAMIC=y
CONFIG_HAVE_PREEMPT_DYNAMIC_CALL=y
# CONFIG_DEBUG_PREEMPT is not set
# CONFIG_PREEMPT_TRACER is not set
# CONFIG_PREEMPTIRQ_DELAY_TEST is not set
Not quite true, disabling hyper threading is well worth it, as are a number of other generic options that have been discussed.
As for the kernel config, the most important settings are the preempt_rt ones, infact one of the easiest ways is to base the config for the new kernel on the running one.
If you really feel the issue is with the GPU I don't think a different kernel will fix much.
youtube.com/shorts/mWCeSrF2TUM
I did a new test 100 windows of glxgears and CPU stresstest active the PC is no longer responsive even the linuxcnc window but the servo continues to go and finishes the job. I don't understand why YouTube goes into error! I must say that today the drivers arrived and the new servos do not make a minimum of noise but I have to check them in the car better.
Yeah I think even anon realtime kernel running a text editor with 100 glx windows open would become unresponsive. Honestly I'm of the opinion that is an unrealistic and silly test, that doesn't prove anything. You're testing for a situation that no sensible person would subject a computer to whilst running gcode.
Obviously you are expecting unrealistic things, and any further interaction is at this point a worthless endeavour on my part.
