Time is going very much off all the time
in [Suse]
|
From: Darrell Stec on 1 Feb 2008 04:04 houghi wrote: > My time is going off all the time since a few weeks. Not sure when it > started, but I now need to do a netdate every 4 hours and the time > difference is between 1 or 2 seconds up to 5 minutes. > > Anybody an idea what might be causing this? > > houghi I had a similar problem. What fixed it was to set the BIOS clock to a slightly different time, boot Linux. Reboot and set the BIOS to the proper time and then use the time feature in OpenSuse to set it to the same time. I don't know why that fixed the problem. If your clock is slow, you might change the backup battery on the motherboard. -- Later, Darrell Stec darstec(a)neo.rr.com Webpage Sorcery http://webpagesorcery.com We Put the Magic in Your Webpages
From: David Wilson Clarke on 1 Feb 2008 05:55 houghi wrote: > My time is going off all the time since a few weeks. Not sure when it > started, but I now need to do a netdate every 4 hours and the time > difference is between 1 or 2 seconds up to 5 minutes. > > Anybody an idea what might be causing this? I've had a similar problem with one of my 10.3 installations. It's a VMware image which I moved from one machine to another, so I assumed it was related to the move, and different processor speeds, or something. I use NTP, so it's correct on startup, but gradually drifts. Is this one of those cases where you delete a file, and it sorts itself out? But not sure which file, maybe '/var/lib/ntp/drift/ntp.drift' but that may just be used to calculate the drift on startup. My problem could be VMWare related. Are you using NTP, houghi? -- David Wilson Clarke
From: russbucket on 1 Feb 2008 10:56 houghi wrote: > Darrell Stec wrote: >>> My time is going off all the time since a few weeks. Not sure when it >>> started, but I now need to do a netdate every 4 hours and the time >>> difference is between 1 or 2 seconds up to 5 minutes. >>> >>> Anybody an idea what might be causing this? >>> >>> houghi >> >> I had a similar problem. What fixed it was to set the BIOS clock to a >> slightly different time, boot Linux. Reboot and set the BIOS to the >> proper time and then use the time feature in OpenSuse to set it to the >> same time. I don't know why that fixed the problem. > > Will try that. > >> If your clock is slow, you might change the backup battery on the >> motherboard. > > The PC is not turned off, so the battery could not be there, for all I > care. > > houghi On modst PC's the battery is used to generate the clock even when the PC is on. If the battery is weak the clock will lose time, at least thats been my experience with bad batteries on my older system. -- Russ Registered Linux user #441463
From: Chris on 1 Feb 2008 12:45 houghi wrote: > David Wilson Clarke wrote: >> Is this one of those cases where you delete a file, and it sorts >> itself out? But not sure which file, >> maybe '/var/lib/ntp/drift/ntp.drift' but that may just be used to >> calculate the drift on startup. > > Mmm. That might point me somewhat in the right direction. > >> My problem could be VMWare related. > > No VMware. 'Normal' PC. > >> Are you using NTP, houghi? > > No, I just run netdate. Might start looking into NTP. > > houghi NTP is easy to setup in Yast (Yast->Network Services->NTP). Then select the option for a random server from ntp.org. That's it. Don't know if that will fix the drifting problem though. -- Chris
From: Darrell Stec on 1 Feb 2008 13:07 houghi wrote: > Darrell Stec wrote: >>> My time is going off all the time since a few weeks. Not sure when it >>> started, but I now need to do a netdate every 4 hours and the time >>> difference is between 1 or 2 seconds up to 5 minutes. >>> >>> Anybody an idea what might be causing this? >>> >>> houghi >> >> I had a similar problem. What fixed it was to set the BIOS clock to a >> slightly different time, boot Linux. Reboot and set the BIOS to the >> proper time and then use the time feature in OpenSuse to set it to the >> same time. I don't know why that fixed the problem. > > Will try that. > >> If your clock is slow, you might change the backup battery on the >> motherboard. > > The PC is not turned off, so the battery could not be there, for all I > care. > > houghi Depending upon the motherboard the battery may run the clock all the time and is continually recharged. But if old enough it takes less and less a charge. Since the charging circuit take a few milli or nanoseconds to recharge the depleting battery you will loose that time. The effect is cumulative so eventually the clock will loose more and more time. On other motherboards the battery only comes into play when the computer loses power or gets below a certain level. Some boards I have seen use the battery in brownout situations where there is enough power to keep all your lights on and the computer on, but it strains the computer to run under those conditions. Sometimes the clock will lose some time. Brown out situations are far more harmful to computers than power surges. You might not notice the effect except with some older monitors the whites suddenly become less white. It might be your battery but it might also be software. -- Later, Darrell Stec darstec(a)neo.rr.com Webpage Sorcery http://webpagesorcery.com We Put the Magic in Your Webpages
|
Next
|
Last
Pages: 1 2 3 4 Prev: Need a translation of an error Next: zd1211 10.3 amd64 ..YetAnotherWifiFubarNoob |