On Wed, Jul 13, 2022 at 03:33:06PM +0200, Marco Davids (SIDN) via
Linuxptp-users wrote:
> Most of the time when I reboot this Linux server, ptp0 is connected to eno1:
>
> ptp4l: [18.144] eno1 selected /dev/ptp0 as PTP clock
>
> But sometimes this is ptp1, which is pretty annoying:
>
> ptp4l:
On Wed, Jul 13, 2022 at 04:22:31PM +0200, Fabian wrote:
> Hi,
>
> I had the same issue, systemd configurations did not affect the order of
> ptpX devices. I use chrony however. My script is attached. It's not the
> cleanest or nicest code but it works.
+1
Using 'ethtool' is way to discover the
Hi,
I had the same issue, systemd configurations did not affect the order of
ptpX devices. I use chrony however. My script is attached. It's not the
cleanest or nicest code but it works. Hope you find some inspiration
from that. Before chrony is started the script is executed via a
Hi,
Most of the time when I reboot this Linux server, ptp0 is connected to eno1:
ptp4l: [18.144] eno1 selected /dev/ptp0 as PTP clock
But sometimes this is ptp1, which is pretty annoying:
ptp4l: [18.745] eno1 selected /dev/ptp1 as PTP clock
Does anyone has a suggestion on how to prevent this
