Jeff Geerling

Well that's fun... after reading through various forum topics about the i226-V, I found many people had connection issues (often flaky, some resolved by disabling ASPM, others not...), and since...

Oddly, when I plug it into a 2.5 Gbps port again, I get: ``` pi@time-pi:~ $ nmcli con show 'Wired connection 2' ... 802-3-ethernet.speed: 1000 802-3-ethernet.duplex: full ``` However, `ethtool`...

Visualizing some GPS data... ``` # Install prerequisites sudo apt-get install gpsd gpsd-clients # Configure gpsd - edit `/etc/default/gpsd` and set these options: DEVICES="/dev/ttyAMA0" GPSD_OPTIONS="-s 115200 -n" # Restart gpsd...

Well, now I'm getting data when observing with `tio -b 115200 /dev/ttyAMA0`, but `gpsmon /dev/ttyAMA0` and `gpsd`/`cgps` are blank. Though it looks like `gpsd` and `gpsmon` are negotiating `9600 8N1`:...

I've been working on getting PPS data out, as I do see a time signal, and it's updating every second with offsets and such... but right now I see nothing...

@ahmadexp recommended using the PHC (Physical Hardware Clock) of the i226 for the source, and then use Chronyd for NTP server. That way the NIC's PHC would be the source...

Setting up Chrony, first just checking on current system time: ``` pi@time-pi:~ $ timedatectl Local time: Thu 2024-12-12 09:17:10 CST Universal time: Thu 2024-12-12 15:17:10 UTC RTC time: Thu 2024-12-12...

Going to test with the following inside `/etc/chrony/conf.d/refclock.conf`: ``` local stratum 1 refclock PHC /dev/ptp0 tai poll 0 trust hwtimestamp * ``` After a restart (`sudo systemctl restart chrony`), I...

Exploring syncing the system clock... - `ptp4l` config is in `/etc/linuxptp/ptp4l.conf` — this is used to designate interfaces being grandmaster (e.g. `masterOnly`) or not - `phc2sys -a -rr` will attempt...

I also realized I may still have NTP running somewhere on this Pi, as timedatectl is showing the correct time and the hardware clock is also showing the correct time!...