[opensuse] Re: openSUSE Time Problem
On Thu, 12 Jan 2012 21:02:36 +0100, Swapnil Bhartiya wrote:
On 01/12/2012 08:49 PM, Johannes Weberhofer wrote:
See, if your hardware clock is set to UTC or you local timezone; check if that is refelcted in your timezone-setting (use yast).
That's what it was. The hardware clock set to UTC was selected and it was taking me our our ahead. Time zone was belgium which is correct.
I will report back if the problem persist.
FWIW, I noticed this on two of my 12.1 systems - if I restarted the system the time was off by 7 hours (I'm in Utah). The only way I seemed to be able to fix this was to tell the system the clock was set to UTC. I had tried even forcing the hardware clock to local time after using ntp to set the system time, but after a reboot, the time was still off by 7 hours. Is there anyone using local time on their hardware clock with 12.1 where this is working? (And if you are, which DE are you using - I wonder if this might be a GNOME3-only issue) Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-01-12 21:18, Jim Henderson wrote:
Is there anyone using local time on their hardware clock with 12.1 where this is working? (And if you are, which DE are you using - I wonder if this might be a GNOME3-only issue)
I'll watch my test partition on the laptop. So far I have not seen problems. What I have seen I can blame on double booting Windows on the same machine, which is the reason to have the cmos clock set to local time. And when I see problems, I recommend to ignore the desktop and check the CLI. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk8P+pUACgkQtTMYHG2NR9XhUgCfZ1h8SM5n7WB9FXCvA96kbQb/ UloAnj+W1q149mU6duMTI7HZZtGhTNrs =bkTT -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/13/2012 10:34 AM, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-01-12 21:18, Jim Henderson wrote:
Is there anyone using local time on their hardware clock with 12.1 where this is working? (And if you are, which DE are you using - I wonder if this might be a GNOME3-only issue)
I'll watch my test partition on the laptop. So far I have not seen problems. What I have seen I can blame on double booting Windows on the same machine, which is the reason to have the cmos clock set to local time.
The issue was on KDE and I did not notice it on Gnome. However, when I unckeched the option 'the hardware clock is set to UTC' I have not seen the clock jumping an hour ahead. Swapnil http://www.muktware.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-01-13 10:55, Swapnil Bhartiya wrote:
On 01/13/2012 10:34 AM, Carlos E. R. wrote:
The issue was on KDE and I did not notice it on Gnome. However, when I unckeched the option 'the hardware clock is set to UTC' I have not seen the clock jumping an hour ahead.
That might have been coincidental. You could have instead reset the clock (erase the adjustement file). - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk8QBj8ACgkQtTMYHG2NR9VzdQCfe2EGvkAAwEj03g2DHwqs0jW5 lwoAn2VK9r+DCvJqvL7t7MxW6YT9ZjQ0 =X7Bu -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/13/2012 11:23 AM, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-01-13 10:55, Swapnil Bhartiya wrote:
On 01/13/2012 10:34 AM, Carlos E. R. wrote:
The issue was on KDE and I did not notice it on Gnome. However, when I unckeched the option 'the hardware clock is set to UTC' I have not seen the clock jumping an hour ahead.
That might have been coincidental.
You could have instead reset the clock (erase the adjustement file).
How to reset the clock? Swapnil -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-01-13 11:40, Swapnil Bhartiya wrote:
On 01/13/2012 11:23 AM, Carlos E. R. wrote:
How to reset the clock?
First thing is to ensure that the system clock has the correct time, verifying it on the CLI as root (using "date"). Once that is done, you have to copy that time to the CMOS clock: hwclock --systohc or hwclock --systohc [--utc|--localtime] to be sure. And finally you have to tell the system to forget by which amount was the clock adjusted: rm /etc/adjtime The file will be recreated by the system on the next reboot. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk8Qjj8ACgkQtTMYHG2NR9VpegCeOJTcN7DGpWkzdN7zrT2ukd8F 6WcAn0YICsM08iDK8ZZuHZnqX8i5Lu4B =mcIM -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Is there anyone using local time on their hardware clock with 12.1 where this is working? (And if you are, which DE are you using - I wonder if this might be a GNOME3-only issue) I'll watch my test partition on the laptop. So far I have not seen
On 2012-01-12 21:18, Jim Henderson wrote: problems. What I have seen I can blame on double booting Windows on the same machine, which is the reason to have the cmos clock set to local time.
And when I see problems, I recommend to ignore the desktop and check the CLI.
When I set up dual boot Linux & Windows systems, I configure only Linux for NTP and do not allow Windows to adjust for daylight savings time. On those systems, I also configure Linux to set the hardware clock to local time, rather than UTC. This prevents Windows from messing up the clock. On Linux only systems, I set the hardware clock to UTC. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 13 Jan 2012 10:34:13 +0100, Carlos E. R. wrote:
I'll watch my test partition on the laptop. So far I have not seen problems. What I have seen I can blame on double booting Windows on the same machine, which is the reason to have the cmos clock set to local time.
Yeah, both of my systems I've seen it on are configured for dual boot, though I don't actually boot into Windows. I thought I remembered that Windows wanted/used local time on the HW clock. Once I set everything up for UTC, then I stopped having problems.
And when I see problems, I recommend to ignore the desktop and check the CLI.
Same here. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Carlos E. R. -
James Knott -
Jim Henderson -
Swapnil Bhartiya