Installing ethercat repositories

Tntmold: I think you have to build LinuxCNC from source for an Ethercat install, then build Ethercat master. It will not work from the downloaded ISO file.
Build from a Debian13 Netinstall(or full) image.

I stand corrected, and somewhat outdated!

There are still some reasons why its necessary to build the Ethercat master from source which is pretty easy anyway. In that case, go to the etherlab site, get their source and read their instructions in the PDF instructions
etherlab.org/en_GB/ethercat

@NIckH, the Etherlab repository also hosts the latest Ethercat hal driver thanks to Scott Laird. So it is possible to install everything without building anything!

Hello, First of my name is Samuel and I am completely new to the whole Linux enviroment but want to learn the process. I am experiencing some issues that I can go through whole setup process and everything is fine but the whole thing falls apart only when the sudo apt update followed by sudo apt upgrade messes everything up. And by evertyhing I mean I lose my link to mac address and some dependenciy files fail to complete and are left unconfigured. 
 What am i doing wrong I've MrRodW install and SZolkaa install and get the same result.

Below is what is not completing. Thanks again.

dpkg: error processing package linux-headers-rt-amd64 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-6.12.86+deb13-rt-amd64
 linux-image-rt-amd64
 linux-headers-6.12.86+deb13-rt-amd64
 linux-headers-rt-amd64
Error: Sub-process /usr/bin/dpkg returned an error code (1)

 

tommylight wrote:

That is not the issue, it is the result of the issue, see if there is "raspi" mentioned in the error report.

Kernel 6.12 is Debian Trixie and thankfully Debian fixed the Raspi issue on its release, so its not the issue.

I suspect its an EFI issue installing dkms. EFI/Secure boot prevents untrusted things from modifying the kernel and dkms does exactly that.
There is a spoiler in the very first post about how to fix this where you tell EFI that dkms can be trusted. Alternatively, consider disabling secure boot in the BIOS

Thanks