From nobody Sun Jul 07 20:07:17 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 4WHJFP0w2Tz5PvvB for ; Sun, 07 Jul 2024 20:07:21 +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 4WHJFN6567z4FNV for ; Sun, 7 Jul 2024 20:07:20 +0000 (UTC) (envelope-from SRS0=E9WE=OH=klop.ws=ronald-lists@realworks.nl) Authentication-Results: mx1.freebsd.org; none Date: Sun, 7 Jul 2024 22:07:17 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1720382837; 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:references:references; bh=W4XDGlMrStNp4twWQjHRkDqVb8h0VtUjOpEM/IGj1Uc=; b=uRLWQtHEmbSFvS+c46VOqi/0yNH9cnegI4WC9TWzkNt81mkq9f6RglktdPf0nBt2ZRKK/t G1Q7OAJa/lhu5nfaSHKs6cs2GmEu0IskEc5jDT6hb3Wr3u/ZaCFe7uRqxG1V3NArdpgv9j rM6U33zcdhljBshLyqXs9E0wuNHrLxBHbiCtffgelZ2uyjJOrBbRXD3uXOYwRKqetyWMPs xeV3BpSDd+k+4baFNoLNJEhCkeXSEHV2S20qMh+63MP3GxFiJi6mu8mnmmrXD0CKR2HESA mZnHfHm53ElOSUfEXtD04V+gR5BCalNAWD+1R9G4qoikYWUs/JgYW57UZiXcZQ== From: Ronald Klop To: Warner Losh Cc: bob prohaska , "freebsd-arm@freebsd.org" Message-ID: <433162018.16507.1720382837193@localhost> In-Reply-To: References: <454282477.15929.1720372600841@localhost> 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_16506_15357732.1720382837137" 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: 4WHJFN6567z4FNV ------=_Part_16506_15357732.1720382837137 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Van: Warner Losh Datum: zondag, 7 juli 2024 19:18 Aan: Ronald Klop CC: bob prohaska , "freebsd-arm@freebsd.org" Onderwerp: Re: ntpd vs ntpdate with no hardware clock > > > On Sun, Jul 7, 2024, 11:16AM Ronald Klop wrote: >> >> 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. > > > Curious why the root mod time isn't firing... it whould alrwady do that > > Warner > __blockquote_end__ > > I'm using ZFS as root. AFAIK ZFS does not implement the usage of superblock unmount timestamp as time sync on boot like UFS. (or did you mean something else with "root mod time"?) > > Regards, > Ronald. > > >> >> >>> >>> Regards, >>> Ronald >>> >>> Van: bob prohaska >>> Datum: 7 juli 2024 18:01 >>> Aan: freebsd-arm@freebsd.org >>> Onderwerp: ntpd vs ntpdate with no hardware clock >> >> >> > ------=_Part_16506_15357732.1720382837137 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit  

Van: Warner Losh <imp@bsdimp.com>
Datum: zondag, 7 juli 2024 19:18
Aan: Ronald Klop <ronald-lists@klop.ws>
CC: bob prohaska <fbsd@www.zefox.net>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>
Onderwerp: Re: ntpd vs ntpdate with no hardware clock

 
On Sun, Jul 7, 2024, 11:16AM Ronald Klop <ronald-lists@klop.ws> wrote:
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.
 
Curious why the root mod time isn't firing... it whould alrwady do that
 
Warner 


I'm using ZFS as root. AFAIK ZFS does not implement the usage of superblock unmount timestamp as time sync on boot like UFS. (or did you mean something else with "root mod time"?)

Regards,
Ronald.

 
 
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_16506_15357732.1720382837137--