Hello all
I´ve been trying lately to fix a problem with my company´s computer server, unfortunately with no success. I am not a computer specialist, and after several failed attempts to fix it, I don´t know what else I may try.

Well, this server runs with Debian GNU/Linux 4.0 (Etch) , and kernel version 2.6.18-4-k7.
No dual boot with Windows.
The problem is related with the HW clock. It seems that it is not working properly.
Every time I reboot the computer, the system keeps always the same date, that is, the last one I introduced from the BIOS menu.
So, the problem is: when I modify the HW clock from the BIOS using the real time, the system will copy it to the system clock and keeps that date with every reboot!!

Any attempt to change the HW clock from the command line using commands like hwclock is unsuccessful. Neither, the system replies nor changes are made whatsoever.
I am going to explain every step I've tried so far to fix the problem:

1) Change the BIOS battery.

It seems logical that, since there is no response from the HW clock, the problem must be related with the battery of the BIOS. Alas, I have changed it twice and it didn´t change anything.

2) Use the hwclock and date commands

When typing the command:

hwclock –show

the system returns the following message:

“ Select() to /dev/rtc to wait or clock tick timed out”

I´ve read in several forums that the solution is to remove the rtc module.
I did it using the following commands:

rmmod rtc
echo “blacklist rtc” >> /etc/modprobe.d/own-blacklist.conf

Then I rebooted the computer and typed the command:

hwclock --debug

With the following answer:

Hwclock: Open of /dev/rtc failed, errno=2: No such file or directory.
Using direct I/O instructions to ISA clock.
Last drift adjustment done at xxxx seconds after 1969.
Last calibration done at yyyy seconds after 1969.
Hardware clock is on local time.
Assuming hardware clock is kept in local time.
Waiting for clock tick…
… got clock tick


It seems that the hwclock is "working", but that is just an illusion, because typing afterwards the commands:

hwclock --show, hwclock –-systohc or hwclock –-hctosys

No replies, no changes, nothing comes from the computer. In fact since the hwclock command does not give any reply, I have no means to guess what the problem is.
On the other hand, the command date works fine, and allows me to change the system time although at this moment it is useless to me.

3) Other modules.

No success using other modules like:

modprobe genrtc
hwclock –show
rmmod genrtc
modprobe rtc
hwclock –show
rmmod rtc

4) NTP time update service.
My server uses the ntp service but it does not update the system time because it is behind a proxy.

I checked it typing the command:

ntpq -p

It detects that the server is connected to my company service provider. Using the ntptrace command, it returns a message saying that there is synchronization with the server but also indicating stratum 16. I think it means: "This server is not considered a time provider".
I believe that, as the server is behind a proxy, I cannot update the time using external servers as pool.ntp.org, right?

And that´s all.

I haven´t found any clue, and after Googling a lot, I just can find some BIOS battery related issues. I discarded them after replacing it twice, so now I have no idea how to fix the problem.. ???

I would appreciate any help / idea / clue which could shed some light to find the solution before getting mad!!
Thanks in advance

The presence of the 1969 date would imply that the hwclock is stuck at zero (00:00:00 January 1, 1970 UTC as I recall).

I was going to suggest changing the cmos battery, but I see you did that.

After re-reading your post I suspect the hardware itself might be bad - the silicon. If so there is probably not much you can with it other than set the system time after reboot and let the kernel and NTP keep it good until power off - then reset it on reboot.

1 members found this post helpful.

um, hate to ask, but did you update your BIOS time after you replaced the battery?

Depends on how old this server is. Some RTC's are a module that might be possible to change.

I assume you put the new battery in correctly. You may have to remove battery, power to system and press power button a few times. Then replace battery and then power it back up.

Newer clock's have an oscillator that might have gone bad. Maybe even a jumper on the board to enable it.

It may be possible to enable ntp on a router or modem or other computer within the lan.

1 members found this post helpful.

Thank you for your support!
As it seems that I have a Hardware problem with the server, I am going to switch the damaged board for a spare one.
I will tell you soon if that is the key to solve my problem!!

Also, most computers these days are set up to obtain their time from a network time-server, which in turn obtains its time-reference from nist.gov or somesuch. Usually, you want every computer on the local network to have an exactly-synchronized clock.

Finally It was a hardware problem. I changed the main board and everything went fine.
Thanks to everybody for the support.

Glad you got it going, glad to help!