Constant time adjustment [Still Happening]

[ohjrson]

Ok N4RPS
  I have made a discovery of sorts I guess. I recently looked at my time on my Linux lite OS and it was off quite a bit. So as normal I went to the command prompt and did an update and low an behold it updated to the right time. SO..... the Bios is keeping the right time but the OS LL 1.08 is dropping off slowly for some reason. Now I still have the LL 1.08 on my laptop and it has no problem keeping time. So any idea's as to what may not be set right in the OS?

Thanks.

[rokytnji]

https://help.ubuntu.com/community/UbuntuTime

Code:

sudo dpkg-reconfigure tzdata

Follow the directions in the terminal.

[gold_finger]

ohjrson,

See if anything here helps:  http://forums.linuxmint.com/viewtopic.ph...46#p806451

[ajoseph]

Good day,

Had a similar problem with my laptop after installing LL 2.0. Having tried online remedies to try to change system admin time (and restarting the machine many times) to no avail, I turned to synaptic. Found a prog called "gnome-time-admin". I set my time and date in there and have had no problems since.

Note: Only experienced this issue with the Laptop. Desktop kept Time and Date perfectly after LL 2.0 installation.

[ohjrson]

I seem to be having the same issue I was having with LL 1.08 regarding losing time with LL 2.0 or Beryl.

I have done a hardware update with the NTP server and the time is correct now. I used what rokytnjl suggested on the code and it showed my hardware time was out of sync so with that synced up now I am hoping it will stay. I was hoping that I would not have this issue with LL 2.0 or Beryl. and the odd thing is I did the install for Beryl on my laptop and it seems fine. So go figure.

[Scott(0)]

Hi Ohjrson,

Does this laptop sometimes boot to Windows? I know one cause for out of sync time is booting between an OS on local time (usually Windows) and an OS on universal time (usually Linux).

~Scott

[ohjrson]

Hi Ohjrson,

Does this laptop sometimes boot to Windows? I know one cause for out of sync time is booting between an OS on local time (usually Windows) and an OS on universal time (usually Linux).

~Scott

No it is exclusively LL 2.0 or Beryl.
Oddly enough now my laptop is having wireless issues... Go figure.
update: That issue was resolved and should be correctly marked.

As far as the time. I have left the computer on and it looks like I have lost 4 minutes since Monday.

[ohjrson]

Update:
Well it seems that the time is anywhere from 2 minutes to 13 minutes off. However it seems to reset itself periodically.

Is there a program I can put in to help keep this as close to the right time as possible?

Update: Just did a reboot to my system because the time was off by 10 minutes.
Had let the system run for 4 days. Lost the time over that many days.

Update: as of today the time is now 22 minutes ahead of what it is supposed to be and the computer has been running for 5d 3:21
Why is this happening?
Thanks
ohjrson

[ohjrson]

Anybody?

[bitsnpcs]

Hello Ohjrson,

I found this website http://linux.die.net/man/8/hwclock

It states "You can also run hwclock periodically to insert or remove time from the Hardware Clock to compensate for systematic drift (where the clock consistently gains or loses time at a certain rate if left to run)."

Systemic drift sounds like/similar to what you have described.

In the options area of the page it covers

Code:

-u
--utc
--localtime

and states -
"If you specify the wrong one of these options (or specify neither and take a wrong default), both setting and querying of the Hardware Clock will be messed up. "

It may be worth looking into these on the link in more detail and altering these settings to see if any of these options solve the issue.

Reading a little more on this I notice -
"It works like this: hwclock keeps a file, /etc/adjtime, that keeps some historical information. This is called the adjtime file. "

So if this file is absent or not working for some reason then the hwclock will not check the current time and adjust the clock correctly, I am unsure how to test the adjtime file.
Finding this out would probably be better to test first before altering any of the options for hwclock.