Date: Tue, 26 Nov 2019 14:29:45 -0800 From: Bakul Shah <bakul@bitblocks.com> To: James Shuriff <james@opentech.cc> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: rpi3 clock drift Message-ID: <20191126222952.6BCFA156E80B@mail.bitblocks.com> In-Reply-To: Your message of "Tue, 26 Nov 2019 22:03:30 %2B0000." <MWHPR06MB3134CD05551D36CC3B45D368AA450@MWHPR06MB3134.namprd06.prod.outlook.com> References: <MWHPR06MB3134CD05551D36CC3B45D368AA450@MWHPR06MB3134.namprd06.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 26 Nov 2019 22:03:30 +0000 James Shuriff <james@opentech.cc> wrote= : > My Raspberry Pi 3 Model B is having some serious clock drift issues. Ntp= d doe > sn't function even with ntpd_sync_on_start, which calls ntpd with -g and= allo > ws the initial adjustment to exceed the panic threshold. This doesn't he= lp me > much because the system will continue to drift very quickly and that op= tion = > only helps for the initial adjustment. > > I was thinking of ordering an I2C RTC but I'm unsure how to make FreeBSD= awar > e of the clock. > > There is a file in the Raspberry Pi firmware repo called i2c-rtc.dtbo an= d it = > contains defs for clocks like DS1307 so I am assuming I can add this to = confi > g.txt, build U-Boot with CONFIG_RTC_DS1307 (or whatever model), and buil= d the > kernel with device support for the clock but I'm not completely sure if= I'm = > going about this the right way. Beyond just getting FreeBSD to see the c= lock = > I'm unsure how to tell FreeBSD to use it. Any advice? Is the clock really drifting or is this due the initial time being waaay off from the current time due to a lack of RTC? If the latter do the initial time setup using ntpdate. Add ntpdate_enable=3D"YES" to /etc/rc.conf. If you can already use ntpd, there is not much point in using a local rtc.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191126222952.6BCFA156E80B>