From nobody Sun Jul 07 17:16:40 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WHDSd0PDYz5Q6s2 for ; Sun, 07 Jul 2024 17:16:49 +0000 (UTC) (envelope-from SRS0=E9WE=OH=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4WHDSc5Pbqz4mDT for ; Sun, 7 Jul 2024 17:16:48 +0000 (UTC) (envelope-from SRS0=E9WE=OH=klop.ws=ronald-lists@realworks.nl) Authentication-Results: mx1.freebsd.org; none Date: Sun, 7 Jul 2024 19:16:40 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1720372601; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to; bh=2aTo+IpYp39v8Hz1pWLt/Fe7PBaU+yeVyIVei2smerY=; b=N3XfV4myHpyiqfXlP31aEc5/fzxechp4LH75V75K0JUNILCg5FUO7B4cFPVP0pz2nNAXCe LFWPvIdwOAuvjhfgtFHm0u3P47P9R90jghhBoJf2J2xmZYdnuYnvs+URM1pswMevAtjbjL LHCslQLeW6s2LStchhv1Q6DZGIVNA1FCqignWTBU6S3L4mNLO9aCAGzWOEO7QsCSaVQ3SB fSl953A5mNB+5JVSLcV6UQSnIyZbCEvL25eIpLQgsoZfzY0Rs+ZC7vJo8OSl+JgihvyAyi sP2c20EhCiIDDwysYLaqo/eZPRtzFtDTtORhIL+mp30MSAT7MeSHMzSLiBruLg== From: Ronald Klop To: bob prohaska Cc: freebsd-arm@freebsd.org Message-ID: <454282477.15929.1720372600841@localhost> In-Reply-To: Subject: Re: ntpd vs ntpdate with no hardware clock List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_15928_2098316081.1720372600838" X-Mailer: Realworks (709.1) Importance: Normal X-Priority: 3 (Normal) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL] X-Rspamd-Queue-Id: 4WHDSc5Pbqz4mDT ------=_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 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 I created fakertc for my rpi4. 


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--