I've noticed that after a week of setting my hardware clock, throught the bios, to the same time as an alarm clock in my bedroom, that my Linux-box has slowed down time. To be more precised, after a week, the clock on my laptop now reads 10 mins slower than my alarm clock.

This is quite annoying, since I've been late for events because I read my laptop clock not remembering the problem it suffers from, so in all it's quite annoying. Does anyone know what may be causing this? Is it a hardware issue or something that Linux needs to deal with?

I can't say I know what's causing it but the same thing happened to me, and I fixed it by running (as root): hwclock --hctosys There are actually 2 clocks on your machine; the hardware clock, and the system clock. The time displayed on your desktop is from the system clock, not the hardware clock, and at least on my system, the hardware clock was much more accurate than the system clock. The command I listed simply overwrites the system clock with the hardware clock's time. Do a man hwclock for more info, and if the reverse is true, you can set the hardware clock to the system clock. As for what might contribute to the discrepancy, I don't know. -- J.W.

I don't think that is the problem, since that is what the system tool in SUSE do when you adjust the time via the clock applet.

I'm really beginning to think that, whilst something is slowing it down that I can't put my finger on, the fact that during shutdown the hardware clock is set to the system clock isn't helping. If this didn't happen then I could at least refreh the system clock from the hardware clock on boot.

Here are a list of what I think the possible causes could be:

- Hardware Problem i.e. bios, m/board
- Linux problem i.e. kernel
- KDE problem
- any combination of the above.

Suggestions?