OPENsuse Tumbleweed: Clock two hours off - have to update it at every login

English Hardware
#1

Hi everybody,

I am on an old HP pavilion laptop, with OPensuse Tumbleweed, KDE 4.8.5. I’m having a problem with my system clock:

The clock is two hours late with respect to my time zone (e.g 10.00 am instead of 8.00), even if I’m using the “set time automatically” option. The only way i found to change the time is to repeatedly check and uncheck the “set time automatically” option. Even so, at every login the time is again two hours off.

My sysconfig options are set to: hardware clock accessible, and systohc (system to hardware clock) to “yes” at shutdown.

Any ideas?

Thanks,
federico

#2

The following steps should resolve your problem.

  1. Start Yast → Network Services → NTP Configuration
  2. Choose Synchronize without Daemon
  3. Click on the “Add” button - Under “Type” choose Server
  4. Click on the “Next” button then Select Public NTP Server
  5. Choose your country and Public NTP Server nearest your area
  6. Once the server has been selected, click on the “Test” button to confirm the server has received your ping
  7. Click on the OK buttons to confirm your selections

That’s it. You may have to restart KDE.

#3

Thanks! That indeed did the trick. So, just for my knowledge, the problem was that there is a time-setting demon in OPENsuse and that daemon was not working properly?

Thanks again!

#4

Nope. You forgot to set the clock to UTC (or you did and dual boot with Windows) and adjust it once. NTP is not on by default. It gets the time from a timeserver on the web, so it won’t work on, for example, laptops that connect to the web only when the desktop is loaded. If you’re on a wired connection NTP is the option to go for.

#5

Thanks! That indeed did the trick. So, just for my knowledge, the problem was that there is a time-setting demon in OPENsuse and that daemon was not working properly?

Thanks again!

Nope. It pulls it from a web server without the need of a daemon. I like to use this setting as it doesn’t require a daemon.

#6

Thanks for the explanation (and apologies for the belated reply).

My clock is still working fine, but … I am slightly confused …

I AM indeed on a dual boot system with windows (Vista) - that means that Vista resets the hardware clock every time it loads???

I am on a laptop, and it connects to the internet via our wireless home network – how come NTP works in my case?

Thanks again!

#7

I phrased wrongly. If you’re sure you have an internet connection all the time, it’s OK on a laptop. But, it won’t work if you don’t have an internetconnection available.

I don’t know the details about time setting, just know the phenomenon

#8

On 2012-10-30 19:26, reducto wrote:
>
> Thanks for the explanation (and apologies for the belated reply).

As long as we remember the issue - I don’t :stuck_out_tongue:

> My clock is still working fine, but … I am slightly confused …
>
> Knurpht;2498083 Wrote:
>> Nope. You forgot to set the clock to UTC (or you did and dual boot with
>> Windows) and adjust it once.
>
> I AM indeed on a dual boot system with windows (Vista) - that means
> that Vista resets the hardware clock every time it loads???

Windows writes the CMOS clock to whatever is the local time on Windows
every time it runs. If Windows is configured to check the time in
Internet, then the CMOS will be correct. If the Internet check doesn’t
work, then the time may be incorrect.

As to NTP, you clock should run correct without NTP. NTP may correct it
when it runs, but the clock would be wrong for some processes before NTP
runs. So I prefer to disable it and find out the problem.

Notice that there is a published correction to make Windows 7 use UTC
time for the CMOS clock, and it is said that Vista has it too.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))