David List said: > Does anyone here know a solution for this problem?
recompile your kernel and include RTC support ? sparky:~# ntpdate time.nist.gov 6 Jun 12:18:45 ntpdate[17615]: step time server 192.43.244.18 offset 13.699978 sec sparky:~# hwclock --debug --systohc hwclock 2.4c/util-linux-2.11n Using /dev/rtc interface to clock. Last drift adjustment done at 1054834353 seconds after 1969 Last calibration done at 1054834353 seconds after 1969 Hardware clock is on local time Assuming hardware clock is kept in local time. Waiting for clock tick... /dev/rtc does not have interrupt functions. Waiting in loop for time from /dev/rtc to change ...got clock tick Time read from Hardware Clock: 2003/06/06 12:18:52 Hw clock time : 2003/06/06 12:18:52 = 1054927132 seconds since 1969 Time elapsed since reference time has been 0.535764 seconds. Delaying further to reach the next full second. Setting Hardware Clock to 12:18:54 = 1054927134 seconds since 1969 ioctl(RTCSET) was successful. Clock drifted 1 seconds in the past 92779 seconds in spite of a drift factor of 40.773487 seconds/day. Adjusting drift factor by 0.931245 seconds/day sparky:~# uname -a Linux sparky 2.4.18 #1 Thu May 29 20:31:23 PDT 2003 sparc64 unknown sparky:~# grep -i rtc /boot/config-2.4.18 CONFIG_SUN_MOSTEK_RTC=y (machine is an Ultra 1 Creator3D) maybe the debian folks left out RTC support for a good reason I always compile my own kernels out of habbit. nate
