1.1.6 build fails on FC30

Achim Gratz Stromeko at nexgo.de
Sun Nov 3 13:36:17 UTC 2019

Udo van den Heuvel via devel writes:
> On 03-11-2019 13:22, Udo van den Heuvel via devel wrote:
>> Thanks for your thoughts. I will post the results...
> # gzip -dc /proc/config.gz |grep NO_HZ
> # CONFIG_NO_HZ_IDLE is not set
> # CONFIG_NO_HZ_FULL is not set
> # CONFIG_NO_HZ is not set

Again, I was suggesting to start from a more standard kernel
configuration, like so:

# CONFIG_NO_HZ_FULL is not set

# CONFIG_PPS_DEBUG is not set
# PPS clients support
# PPS generators support

Once you have that working correctly you can try to enable hardpps, but
I suspect that it has bitrotted quite a bit except for the handful of
embedded platforms where it is still the standard config.  In other
words, there may be new incompatibilities on your platform that nobody
has yet encountered via interactions with other parts of the kernel
(power management and the like).

> Yet we still see:
> REFCLOCK: refclock_ppsapi: time_pps_create: Operation not supported

So does the PPS device exist and does it generate events?  If it's
coming in via a serial device, have you started an ldattach to enable
the PPS line discipline?  If it is a link to the actual device (as usual
/dev/gpspps0 -> /dev/pps0), does it point to the correct device?  Are
the permissions on the device correct?

lrwxrwxrwx 1 root root      5 Nov  3 12:59 /dev/gps0 -> ttyS0
lrwxrwxrwx 1 root root      4 Nov  3 12:59 /dev/gpspps0 -> pps0
crw-rw---- 1 root ntp  249, 0 Nov  3 12:59 /dev/pps0

Remember that running the PPS in via a serial line w/ PPS line
discipline and having hardpps configured the kernel will take over the
clock steering and NTP just needs to watch (which you need to tell it
via flag3).  The data you've shown indicates you run with hardpps _and_
try to steer the clock with ntpd as well.

+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:

More information about the devel mailing list