My current conclusion is that my clock problem is something more
serious than just a drift (the system clock gains a lot, and not
constant amounts), maybe involving acpi, timers (hpet++), rtc,
interrupts and whatnot, all of which I have just a limited
understanding.
(Probably not much of an
Matthew Burgess wrote:
Jens Olav Nygaard wrote:
Any ideas?
Yep, I just use ntp (see BLFS). My hardware clock seems to gain even
Tried this and went for the first option mentioned in the BLFS-book:
Option one is to run ntpd continuously and allow it to
synchronize the time in a
My system clock seems to gain an extra five minutes per hour,
as reported by 'date' compared to 'hwclock --show'.
(The hw clock seems to be reasonably accurate.)
(The gain also seems to be dependent on what I do, eg., if
the system is just idle, the system clock doesn't gain as
much.)
Googling
Jens Olav Nygaard wrote:
My system clock seems to gain an extra five minutes per hour,
snip
Any ideas?
Yep, I just use ntp (see BLFS). My hardware clock seems to gain even
when the system is switched off! I have a bootscript that syncs the
clock to an ntp server at bootup, ntpd runs
On Mon, 8 Aug 2005, Matthew Burgess wrote:
Jens Olav Nygaard wrote:
My system clock seems to gain an extra five minutes per hour,
snip
Any ideas?
Yep, I just use ntp (see BLFS). My hardware clock seems to gain even
when the system is switched off! I have a bootscript that syncs the
