Udo van den Heuvel via devel writes: > Using tsc clocksource we get: > > # cat /sys/devices/system/clocksource/clocksource0/current_clocksource > tsc > # ntpq -pn > remote refid st t when poll reach delay offset > jitter > =============================================================================== > +NMEA(0) .GPS. 0 l 9 64 377 0.0000 0.0000 > 0.0019 > *192.168.10.98 .GPS. 1 u 27 64 377 0.3096 -0.0919 > 0.1178 > +fd00:c0a8:a00:1 .GPS. 1 u 37 64 377 0.3211 -0.0505 > 0.0775 > > I.e.: no system peer selection of GPS. > We tried HPET, AC PI_PM and now TSC. > None of them works to fix this issue.
Then the clock isn't really the problem I suppose. The GPS is reachable and has no offset and low jitter, but doesn't appear to use PPS; although from your boot log it's clear you were apparently expecting to use that. Have you set the flag to use the PPS and does the device deliver (stable) PPS signal? If so, does the device file expected by ntpd exist in your chroot environment (generally a symlink to the real /dev/pps* device) and is it readable by ntpd? Also, if there's an apparmor profile for ntpd, check in /var/log/audit/audit.log (or wherever that is under Fedora, also in the chroot maybe) that apparmor allows the access as well. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
