On Wed, Apr 29, 2015 at 12:25:25PM +0100, Chris Walker wrote:
On Wed, 29 Apr 2015 12:04:53 +0100 Jonathan McDowell noodles@earth.li wrote:
On Wed, Apr 29, 2015 at 11:48:43AM +0100, Chris Walker wrote:
My machine seems to be having problems with its clock. Linux keeps resetting the RTC to minus one hour. The desktop is currently showing the time as 10:46 for example.
[snip]
It's been a while since I dual booted anything but last I checked Windows stores the RTC in local time and Linux uses UTC (see "RTC in local TZ" in your timedatectl output). You need to tell Mageia that the RTC is in local time so it doesn't reset it on you.
I googled "RTC in local TZ" and one link suggested I change timedatectl to 'timedatectl set-local-rtc 1'
I've done that but I now get this warning (and the desktop clock hasn't changed even though I've just rebooted).
Warning: The system is configured to read the RTC time in the local time zone. This mode can not be fully supported. It will create various problems with time zone changes and daylight saving time adjustments. The RTC time is never updated, it relies on external facilities to maintain it. If at all possible, use RTC in UTC by calling 'timedatectl set-local-rtc 0'.
Here's the timedatectl output now Local time: Wed 2015-04-29 12:21:45 BST Universal time: Wed 2015-04-29 11:21:45 UTC RTC time: Wed 2015-04-29 12:21:45 Time zone: Europe/London (BST, +0100) NTP enabled: yes NTP synchronized: no RTC in local TZ: yes DST active: yes
So is the time correct as far the computer is concerned and the only 'real' problems is that the desktop display is awry for some reason? Or is there still a basic problem with clock settings?
No idea. Does "date" at a command line give the expected timezone and time? It looks like systemd at least knows the correct time details now.
J.