Latency problem after upgrading to Trixie

Hi
After many happy years on Bookworm LinuxCNC I have upgraded to Trixie. I ended up installing Debian OS and then installing LCNC ( I could not get the download from LCNC website to work).  Anyway, I have the machine running again, but as soon as I start the program, I get the dreaded latency error message.  I have turned off everything that is not needed in the bios, but still get the message. I understand there are ways to manipulate how the cores work in the computer.  Can someone point me to some step-by-step instructions?
Thanks

I assume you have installed the RT kernel...
As for the error message that appears immediately after starting LinuxCNC, I have been blocking it for a long time (I always compile LinuxCNC myself).
I suspect that the cause of this error is the procedure for checking it.
I reported it once, but no one was interested.
Anyway, the message was almost always displayed, but latency-test or latency-plot didn't show anything alarming...

Its nothing to do with building LinuxCNC. As time goes on, the hardware manufactuters add more power saving features which induce latency so it takes more work to get it under control. Trixie is no worse than Bookworm. The biggest issue is not using the dkms drivers with realtek NIC's. Try to always use Intel NIC's. I've covered this and other steps in a few videos over the last 12 months or so on my YouTube channel.

rodw wrote:

The biggest issue is not using the dkms drivers with realtek NIC's. Try to always use Intel NIC's.

Those will cause the "error finishing read", not latency error, so for now do not bother with it, see here:
forum.linuxcnc.org/38-general-linuxcnc-q...ead-and-irq-affinity

Once again.
Many times I had the problem with the "Unexpected realtime delay on task" message, which meant nothing and only annoyed the user because neither latency-test nor latency-plot showed anything wrong.
This has nothing to do with compiling LinuxCNC yourself, except that compiling it yourself allows you to disable this message.
As for the message itself, I suspect that either the procedure displaying it is bad, or it is called at the wrong moment (LinuxCNC starts and maybe something jams, but only then and only once).

tuxcnc wrote:

.... or it is called at the wrong moment (LinuxCNC starts and maybe something jams, but only then and only once).

Usually the call to OpenGL subsystem used by Gremlin will do this, more often with NVIDIA graphic cards and some integrated Intel ones.
Despite bumping into this occasionally, i could never invest more time in finding the exact issue is/was.
Gremlin is the tool path preview used on some LinuxCNC GUI's