have persistent problem that hwclock of my diskless MD was 1 hour back (when booted as Pluto's MD time is right, when powered off it goes back 1 hour - I know cause it displays it on small LCD screen).
Now since we changed our time in Europe this lag is two hours. Have played with hwclock utility but no success. I also spot same behaviour if I boot my win laptop as MD, after that time is 2 hours back as it was before (in windows).
I'm attaching my discussion with Radu - maybe someone will have idea how to fix this problem.
Rob.
Rob (3/30/2006 11:42:58 AM): I'm still bugging with that 2 hour lag on my diskless MD - Digimatrix - it shows hardware clock on LCD screen
Rob (3/30/2006 11:43:17 AM): when it's powered on as Pluto MD, it show right time, after shutdown it goes 2 hours behind...
radu_c_public (3/30/2006 11:43:40 AM): it was 1 hours; now it's 2? did DST come into effect in your country too?
Rob (3/30/2006 11:43:48 AM): yeap...
Rob (3/30/2006 11:44:05 AM): and same happens with my laptop if I boot it as Pluto MD....
Rob (3/30/2006 11:44:19 AM): I've asked on forums, and they lead me to hwclock utility...
Rob (3/30/2006 11:44:45 AM): but I'm now checking hwclock --show with Digimatrix MD and it shows correct time.....
Rob (3/30/2006 11:45:34 AM): why it goes to some other time on shutdown - un fortunately we cannot check hardware clock when powered off?
radu_c_public (3/30/2006 11:47:25 AM): on our build server just now: pluto-devel:~# date Thu Mar 30 12:46:41 EEST 2006 pluto-devel:~# hwclock --show Thu Mar 30 11:47:09 2006 -1.937256 seconds
radu_c_public (3/30/2006 11:47:55 AM): the system clock was set using ntpdate
radu_c_public (3/30/2006 11:48:29 AM): I bet that if I power it off forcefully (like with a power outage), the time will be off by one hour at boot
radu_c_public (3/30/2006 11:49:17 AM): I also did a search today, remembering that the time was off by one hour when DST came into effect here, and found this:
http://www.linux.com/howtos/Clock-2.shtmlradu_c_public (3/30/2006 11:50:24 AM): I guess a "hwclock --systohc" is needed to program the clock into the BIOS
Rob (3/30/2006 11:54:34 AM): I did this and powered off - it went 2 hours back....
Rob (3/30/2006 11:54:50 AM): Reading this doc I'm confused....
Rob (3/30/2006 11:55:55 AM): I thought I understand time, zones and DST....
Rob (3/30/2006 12:04:09 PM): hmm, I 've tried both hwclock --utc and hwclock --localtime - but both went 2 hours back. I have a feeling that on powerdown Sarge somewhere calls hwclock on its own.....
radu_c_public (3/30/2006 12:05:08 PM): try a "hardware" poweroff
Rob (3/30/2006 12:07:09 PM): you mean between settings ?
radu_c_public (3/30/2006 12:07:54 PM): I mean, after hwclock --systohc, just press the power button
Rob (3/30/2006 12:08:45 PM): poweroff and then press power button - or button imediately ?
Rob (3/30/2006 12:09:02 PM): hwclock ---systohc will write to bios ?
Rob (3/30/2006 12:09:08 PM): is that what you meant ?
Rob (3/30/2006 12:10:05 PM): I guess it will work once... but not permanently....
Rob (3/30/2006 12:10:21 PM): I have win32 laptop. if I work in windows all the time, time is ok.
Rob (3/30/2006 12:10:47 PM): when I boot it as diskless MD and get back to windows time is 1 hour behind - that means that sarge somehow influences my hw clock...
Rob (3/30/2006 12:12:56 PM): ok, I did hwclock --systohc and pressed power button - it went off but 2 hours back....
