Re: [cobalt-users] qube 2 hardware clock error

[Mike Vanecek <nospam99@xxxxxxxxxxxx>]

On Mon, 26 Jun 2000 17:31:56 -0400, Matthew Williams <williams@xxxxxxxxxxxx>
wrote:

:>We have a qube where the system and hardware clocks can be set
:>(ntp, hwclock --systohc) correctly.  When the machine is rebooted, both
:>clocks come up with the correct time of day but a date of anywhere
:>from 4 to 12 days in the future.  Any suggestions on how to fix
:>this?  Thanks.

What I do on a Qube2 is to set the clock via the GUI time sync dialog. I then
ssh and su to root, type "/sbin/clock -r" and date.  If the two don't match, I
the type "/sbin/clock -w" to force a reset of the CMOS clock. My guess is that
Cobalt isn't updating the CMOS clock, just the system clock (linux sets the
system clock from the CMOS clock at boot and doesn't touch the CMOS clock at
all after that). HTHs.



-- 

  For information on the unofficial qube mailing list, see
  http://majordomo.email-lists.com/qube-users/