Hello Sluggers,
Am still fighting my time problem. Am also subscribed to the SuSE
mailing list and have posted to that list several times regards this
problem. No luck. Others have this same problem. Nobody seems to have
the answer. Been doing some analysis and record keeping on what is
happening. Figured I would give the Sluggers another shot at it with
a little more information. Following is a copy of a post that I made to
the Suse list.
Re: [SLE] Time display
From: Bob Stia <rnr@sanctum.com>
To: suse-linux-e@suse.com
Date: Sat, 20 Oct 2001 21:30:03 -0400
On Saturday 20 October 2001 03:12 pm, you wrote:
> Although there has been plenty of discussion concerning the clock time
> in recent weeks, I must admit I've paid it NO attention as my clock has
> been as solid as granit, that is until 3 days ago. Now suddenly it can't
> seemingly be displayed correctly from boot to boot. For the 4+ monthis
> I've been using SuSE 7.1 it boots to the correct time display EVERY
> time, until mid last week, now it roughly 4 hours +/_ on each boot.
>
> what have I missed in the discussion that will fix the problem?
Dave,
You haven't missed anything. Nobody has been able to come up
with an answer for this. I also am having the same problem as are
at least 2 or 3 others whom are running 7.1. It is driving me crazy.
I have an A15VG+ motherboard, AMD K6-2 processor - running
the 2.4.7 Mantel kernel, and of course SuSE 7.1 This problem also
exists with the original 2,4,0 kernel, And, please don't ask if I changed
the bios battery. Did that twice.
I am running a dual boot system and the time is being changed
in the bios by hwclock. I can set the clock accurately from either
windoze or 7.1. I have been keeping accurate records at boot
in both systems for several days now. As long as I only boot
windoze the time will remain accurate. As soon as I boot 7.1
the time changes. Now get this, the system time will be set
back 4 hours, but, hwclock can be some other weird time that
may or may not coincide with the system time. Whatever time
it sets itself to is changed in the bios and from that time on
it will be the time set for windoze also.
The procedure I am following to try and figure this out is this:
Boot to bios - check time - boot to win - check time - shut down-
boot to bios - check time - boot to suse - check time - check
hwclock - shut down - boot to bios - check time - boot to win -etc. etc.
Here is just an example of what I have found - After resetting time
System Display time Actual time Difference
Oct. 16, 2001 - Server time reset
hwclock - set 11:34 11:34 0
bios 11:35 11:35 0
win 11:38 11:38 0
bios 11:51 11:51 0
Shut down an boot up
suse 7:55 11:55 - 4 hrs.
hwclock 12:23 11:39 + 24 minutes
After midnight - Oct. 17, 2001
bios 12:51 12:27 + 24 minutes
win 12:53 12:29 + 24 minutes
Shut down and boot up
bios 12:54 12:30 + 24 minutes
suse 6:41 10:17 - 3 hrs. 36 minutes
hwclock 10:21 12:33 - 2 hrs. 12 minutes
bios 10:23 12:35 - 2 hrs. 12 minutes
Oct. 17, 2001- Server time reset
bios 9:34 9:34 0
win 9:36 9:36 0
Shut down and boot up
bios 9:39 9:39 0
suse 5:40 9:40 - 4 hrs.
hwclock 9:18 9:41 - 23 minutes
Shut down and boot up
bios 10:53 11:16 - 23 minutes
win 10:56 11:19 - 23 minutes
After Midnight - Oct. 18, 2001
bios 1:02 1:25 - 23 minutes
suse 9:39 1:30 - 3 hrs. 51 minutes
hwclock 5:39 1:30 - 7 hrs. 51 minutes
Shut down and boot up
bios 5:41 1:32 - 7 hrs. 51 minutes
Right now - No resets in two days - Oct. 21, 2001 - Several reboots
suse 12:14 - 10/20 12:05 - 10/21 - 23 hrs. 51 minutes
hwclock 3:16 - 10/19 12:07 -10/21 - 32 hrs. 51 minutes
The problem appears to be with hwclock. It can be set and then system
time set to it. Upon reboot it will knock the system clock back by exactly
4 hours, but if you do a -r and check the time it will be some other
arbitrary time - which resets the bios to whatever that was. On the next
boot to suse it will add or subtract that hwclock time to the -4 hour time
that was previoulsy set and reflects that error in the system time. I just
don't know. Is the hwclock setting random on each reboot ?? Maybe some
of the mathematicians out there can figure this out.
Keep an eye on hwclock. Check the time for accuracy when you power
down. Check it again after you boot up and compare it to your system
time. If you don't know how to check or reset hwclock take a look at
" man 8 hwclock". Let us or me personally know what you come up with.
Bob
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 15:42:56 EDT