Date: Mon, 24 Sep 2001 14:51:59 -0700 From: "Drew Tomlinson" <drewt@writeme.com> To: "'Beech Rintoul'" <akbeech@anchoragerescue.org> Cc: "FreeBSD Questions (E-mail)" <freebsd-questions@FreeBSD.org> Subject: RE: Clock question Message-ID: <5CD46247635BD511B6B100A0CC3F023925A0C9@ldcmsx01.lc.ca.gov> In-Reply-To: <5CD46247635BD511B6B100A0CC3F0239014F516D@ldcmsx01.lc.ca.gov>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: owner-freebsd-questions@FreeBSD.ORG > [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Beech Rintoul > Sent: Monday, September 24, 2001 2:38 PM > To: freebsd-questions@freebsd.org > Subject: Clock question > > > I have an old 486 on our net that works perfectly except for > the clock. > ntp resets the time constantly, and this box looks like it > gains about 2 > minutes an hour. Is there anything I can do to get this under control? > The box runs as secondary DNS and works great for that purpose. > BTW it's running 4.4-STABLE. When I setup ntpd on my old 486 some time ago, someone on the list suggested adding some options to the kernel and recompiling. I don't understand what it does but it worked for me and my clock was way off. Here's a clip from the message: <clip> Another thing you can try is changing your clock source. Add the following lines to your kernel config file and recompile: options CLK_USE_I8254_CALIBRATION options CLK_USE_TSC_CALIBRATION That should calibrate two internal clocks against the CMOS clock, which is usually pretty accurate. </clip> Good Luck! Drew > > Beech > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5CD46247635BD511B6B100A0CC3F023925A0C9>