My sheeva starts with system clock set to april 1960...

[hr.punio]

Hi,

The time is in sync within a few minutes (thanks to ntpd I presume).
I was even not aware about the problem;
until I have looked into /var/log/apache/access.log recently

/sbin/hwclock --show
Is not working:
The Hardware Clock registers contain values that are either invalid (e.g. 50th day of month) or beyond the range we can handle (e.g. Year 2095).
And the system installed is Debian Lenny from cyrius.com

I wonder if is this a annoying feature or there is somethig I can do about it?
 

[MarkF]

After ntpd has set the system time, have you done this:

/sbin/hwclock --systohc

To set the hardware clock to the current System Time?

[hr.punio]

Of course not. Thanks Mark

[hargoth]

That gives me:

sheevaplug-debian:~# /sbin/hwclock --systohc
Timed out waiting for time change.

[MarkF]

hargoth - Have you built your own kernel or are you using one of the recent pre-made kernels?

[hargoth]

sheevaplug-debian:~ -> uname -r
2.6.32-00007-g56678ec

This is the kernel installed by Globalscale on the updated Guru Plugs. I received these units in September of 2010.

[MarkF]

Rats!  Everything I found about the "Timed out waiting for time change." message says the Real-Time Clock (RTC) hardware support is not compiled into the kernel, the hardware is toast or there is no battery.

Another idea I had was this might be a symptom of the known problem with kernels before 2.6.32 on newer hardware; but, since you are using a .32 kernel, you should not be experiencing that particular problem.  Just to be sure, could you use the dmesg command and check for a line that contains "Kirkwood: MV88F6281" and make sure it has a valid chip revision value?  While looking at the dmesg output, you could also look at any RTC messages for possible problems.

I'm running out of ideas.