Hello everyone,
my name is Geir, I'm an Icelander living in Ipswich and this is my first email to this user group.
I'm running Ubuntu, kernel 2.6.10, on and old Compaq pentium III machine.
My problem is that the system clock is running at approx 2x the speed it should be running on. The hardware clock is ok.
Solutions that don't seem to work: * adjtimex * ntpd * booting without apm or acpi
The required parameters for adjtimex are way outside the allowed parameters.
ntpd doesn't seem to cope either, if I'm running it correctly. It doesn't seem to do anything at all. How do I adjust the frequency of ntpd updates anyway? Some command in the /etc/ntp.conf I guess?
Booting without apm or acpi doesn't seem to work, if I'm doing it correctly.
I've seen in various forums that people running a 64-bit machine are having the same troubles but this isn't the case for me.
Any ideas?
Very best regards, Geir Freysson.
Hi,
my name is Geir, I'm an Icelander living in Ipswich and this is my first email to this user group.
Welcome!
I'm running Ubuntu, kernel 2.6.10, on and old Compaq pentium III machine.
My problem is that the system clock is running at approx 2x the speed it should be running on. The hardware clock is ok.
That sounds quite odd...
Solutions that don't seem to work:
- adjtimex
- ntpd
- booting without apm or acpi
My preference would be ntp.
ntpd doesn't seem to cope either, if I'm running it correctly. It doesn't seem to do anything at all. How do I adjust the frequency of ntpd updates anyway? Some command in the /etc/ntp.conf I guess?
One way of doing it (probably not the most elegant way) would be to cron it. Then you can choose the update frequency yourself and be sure that it works. Here is an example that runs on my work machine:
# cron to sync the time every 1/2 hour 15,45 * * * * root /usr/sbin/ntpdate -u pool.ntp.org > /dev/null 2>&1
Hope that helps.
Dave
On Tue, 2005-07-26 at 09:38 +0100, Geir Freysson wrote:
I've seen in various forums that people running a 64-bit machine are having the same troubles but this isn't the case for me.
I am having hardware clock troubles but not the one you mention.
I think your problem may be to do with your Kernel not detecting one of the hardware clocks at the correct frequency....on my system the kernel seems to use the Programmable Interrupt Timer (PIT) at 1.193182 Mhz and also seems to reference the CPU clock to regulate system time.
I vaguely recall some issues with Via chipsets and some kernels relating to the PIT.
I suggest you grep your kernel messages for time.c as that seems like a good place to start...certainly if the PIT is being incorrectly set then I can see how the system time would run fast or slow.
Maybe try adding no_timer_check to the kernel boot parameter in your bootloader
If not then try booting with no APIC....this is a different thing to ACPI...try adding noapic to the kernel boot parameter
But I am guessing that the first option will solve your problems....if not then seeing as you are running a 2.6 series kernel try clock=pit or clock=pmtmr ( I think 2.6 series kernels are supposed to default to pmtmr )
You can try these parameters by hitting the esc key and following the instructions as grub is starting at boot.
Hope that helps and welcome to the group.
-
David Reynolds -
Geir Freysson -
Wayne Stallwood