Debian Trixie upgrade/install to 2.9.4

MaxEkb77 wrote:

I upgrade from bookworm to trixie & ethercat work fine

I checked the ethercat repo and they had one for Debian_12 and one for Debian_Testing (trixie's pre-release name) I think the igh sources.list in /etc/apt/sources.list.d should be changed to this. The easiest way would  be to download and edit my script in a Ethercat sticky.

I have been running Trixie for several months now, based on daily builds, and also pre-releases of LinuxCNC, and everything worked fine. However, please notice that newer hardware may require to install a later kernel than what is provided in the standard repos (at least for Bookworm; I believe Trixie already has a newer kernel with its official release). Also install the newest drivers. Newer kernels usually have much better support for newer hardware, and if you have a system that hangs every now and then, driver support (especially iGPU support via MESA drivers; not to be confused with Mesa cards) is the most common cause. So, add backports to your repos and install the latest RT-kernel and drivers; this will most likely fix any hanging systems.
Also notice that open source drivers for Realtek ethernet can cause latency issues. It is best to blacklist them and install the official Realtek drivers. My N100 system has rt8168 ethernet ports, and by default Debian installs the open source r8169 driver. It is better to install the official Realtek driver (r8168 in my case); more stable and lower network latency.

To rodw: can you show us a Latency Histogram screenshot of your tuned system? Showing a graph of a system that is only running for 49 seconds with no glxgears gives a nice first impression, but I would be very curious to see how your system performs under load with:

• e-cores disabled (so only running P-cores)
• hyperthreading, C-states, virtualization etc. disabled in the BIOS
• isolating cores for the RT tasks
• IRQs kept away from those isolated cores,
• and IRQs for the mesa card ethernet port pinned to the isolated cores.
  
  I would like to see how an i7-12700 system with only p-cores enabled would compare to my cheap N100 with only e-cores. It would help me to decide what hardware I will buy for new CNC build. Thank you in advance!!!

rebelx wrote:

My N100 system has rt8168 ethernet ports, and by default Debian installs the open source r8169 driver. It is better to install the official Realtek driver (r8168 in my case); more stable and lower network latency.

To rodw: can you show us a Latency Histogram screenshot of your tuned system? 

Just use your N100, follow my tweaks to get the best out of it
erpx.au/shop/trixie-linuxcnc-debian-trix...tion-pdf-download-48

At this stage, I have only installed Trixie on my desktop. Yes, its a 20 core i7 but such hardware is totally wasted running linuxcnc. It's not relevant.

At this stage I don't think building the kernel will help much with Trixie because its running 6.12, which is the first kernel PREEMPT_RT entered the main line kernel code. In fact, its only one version behind the pointy end. Other than that, nothing much has changed from Bookworm.

Good morning,

I followed Rodw's instructions (thanks, Rodw), and upgraded from Bookworm to Trixie.
I can say that everything is fine. I only had two problems:

Several packages weren't installing automatically; they were always in the update list.
I installed them manually and solved the problem.

The Network Manager GUI in the top-right panel wouldn't start, and it was impossible to manage the network
with a graphical interface.
I solved the problem by searching online.

The thing that worries me is the warning that appears after I update from the terminal.


 


What does this warning mean?

Thanks

Great feedback. Nothing to worry about. The etherlabmaster's certificate in their repository only has a life of 2 years. If you are not using ethercat, there is nothing to worry about. It is outside of our control.

Thanks Rodw
I use EtherCAT, so I'm worried!
Is there a chance that etherlabmaster will decide not to update the certificates?
If so, what's the best course of action?