Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 7 Jul 2024 19:16:40 +0200 (CEST)
From:      Ronald Klop <ronald-lists@klop.ws>
To:        bob prohaska <fbsd@www.zefox.net>
Cc:        freebsd-arm@freebsd.org
Subject:   Re: ntpd vs ntpdate with no hardware clock
Message-ID:  <454282477.15929.1720372600841@localhost>
In-Reply-To: <Zoq7xD2BRT6YyF6l@www.zefox.net>

next in thread | previous in thread | raw e-mail | index | archive | help
------=_Part_15928_2098316081.1720372600838
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

I created fakertc for my rpi4. 

https://www.freshports.org/sysutils/fakertc/

Saves the time on shutdown and sets it back early at boot.

Plus I use ntpdate together with ntpd. Works fine.

Regards,
Ronald

Van: bob prohaska <fbsd@www.zefox.net>
Datum: 7 juli 2024 18:01
Aan: freebsd-arm@freebsd.org
Onderwerp: ntpd vs ntpdate with no hardware clock

> 
> 
> Just tried using ntpd with a fresh 14.1 installation on a Pi4.
> Near as I can tell, ntpd reports a failure due to the clock
> being off by too much, even if it's set manually to within
> a minute before reboot. Probably that's caused by the lack
> of a hardware clock on the Pi4, linux has a bodge called
> fake-hwclock. Is there an equivalent workaround for FreeBSD?
> 
> In the meantime ntpdate seems to work, though deprecated
> 
> Thanks for reading,
> 
> bob prohaska
> 
> 
> 
> 
> 
> 
------=_Part_15928_2098316081.1720372600838
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<html><head></head><body>I created fakertc for my rpi4.&nbsp;<div><br></div><div><a href="https://www.freshports.org/sysutils/fakertc/">https://www.freshports.org/sysutils/fakertc/</a></div><div><br></div><div>Saves the time on shutdown and sets it back early at boot.</div><div><br></div><div>Plus I use ntpdate together with ntpd. Works fine.</div><div><br></div><div>Regards,</div><div>Ronald</div><div><br><p><small><strong>Van:</strong> bob prohaska &lt;fbsd@www.zefox.net&gt;<br><strong>Datum:</strong> 7 juli 2024 18:01<br><strong>Aan:</strong> freebsd-arm@freebsd.org<br><strong>Onderwerp:</strong> ntpd vs ntpdate with no hardware clock<br></small></p><blockquote style="margin-left: 5px; border-left: 3px solid #ccc; margin-right: 0px; padding-left: 5px;"><div class="MessageRFC822Viewer do_not_remove" id="P"><!-- P -->
<!-- processMimeMessage --><div class="TextPlainViewer do_not_remove" id="P.P"><!-- P.P -->Just tried using ntpd with a fresh 14.1 installation on a Pi4.<br>
Near as I can tell, ntpd reports a failure due to the clock<br>
being off by too much, even if it's set manually to within<br>
a minute before reboot. Probably that's caused by the lack<br>
of a hardware clock on the Pi4, linux has a bodge called<br>
fake-hwclock. Is there an equivalent workaround for FreeBSD?<br>
<br>
In the meantime ntpdate seems to work, though deprecated<br>
<br>
Thanks for reading,<br>
<br>
bob prohaska<br>
<br>
<br>
</div><!-- TextPlainViewer -->
<hr>
</div><!-- MessageRFC822Viewer -->
</blockquote><br><br><br></div></body></html>
------=_Part_15928_2098316081.1720372600838--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?454282477.15929.1720372600841>