thank you.... thank you. you all are wonderful. i did ysctl -w kern.timecounter.hardware=i8254 and after 33 minutes i was off .04 seconds. better than 250 seconds.:)
again thank you all for your help. dean ---------------------------------------- > From: [EMAIL PROTECTED] > To: support@pfsense.com > Date: Sat, 10 May 2008 19:55:03 -0700 > Subject: Re: [pfSense Support] setting time > > Hi Dean, > > You can see what FreeBSD (pfSense) is using to keep time with the > following command: > > firewall:~# sysctl kern.timecounter.hardware > kern.timecounter.hardware: TSC > > You can see what is available with the command: > > firewall:~# dmesg | grep Timecounter > Timecounter "i8254" frequency 1193182 Hz quality 0 > Timecounter "TSC" frequency 499904486 Hz quality 800 > Timecounters tick every 10.000 msec > > You can try one of your other options with this command (e.g., to try > i8254): > > sysctl -w kern.timecounter.hardware=i8254 > > If it keeps better time, you can add a line to /etc/sysctl.conf (so a > reboot will use your new choice): > > kern.timecounter.hardware=i8254 > > John > > > On May 10, 2008, at 7:14 PM, Dean Larson wrote: > >> >> tried flashing the bios... didn't seem to help. i guess we have a >> strange computer -- old, but i should be happy it works. it is a >> msi computer with 350 processor. >> >> >> thank you for all your help. >> >> dean >>> Date: Sat, 10 May 2008 16:13:11 -0400 >>> From: [EMAIL PROTECTED] >>> To: support@pfsense.com >>> Subject: Re: [pfSense Support] setting time >>> >>> On Sat, May 10, 2008 at 11:16 AM, Dean Larson wrote: >>>> >>>> i have a cron job of 15 * * * * /usr/sbin/ntpdate -u -s >>>> tick.usno.navy.mil >>>> >>>> i did the command you said ntpdate pool.ntp.org. and yes it sets >>>> the time, but it doesn't stay. for long. >>>> >>>> computer kept near perfect time before under different o/s. this >>>> seems real strange. >>>> >>> >>> Sounds familiar. I've seen and/or heard of this under 3 >>> circumstances. >>> >>> 1) Buggy BIOS - I've redeployed older hardware that ran fine for >>> years >>> with Windows, but as soon as I redeployed with FreeBSD, it wouldn't >>> keep time for anything. Updated to the latest BIOS and the problem >>> was >>> gone. It was several revisions out of date, one of which included a >>> timekeeping fix that apparently didn't apply to Windows. I >>> specifically saw this with Dell hardware, but it's possible with any >>> hardware and have heard of others seeing the same with other >>> hardware. >>> >>> 2) PNP OS turned on - if PNP OS is on in your BIOS, turn it off. >>> >>> 3) ACPI issues - try disabling ACPI, sometimes it causes time >>> keeping issues. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >> >> _________________________________________________________________ >> Stay in touch when you're away with Windows Live Messenger. >> http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_messenger_052008 >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > _________________________________________________________________ Stay in touch when you're away with Windows Live Messenger. http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_messenger_052008 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
