Hello,
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.
If I run timedatectl, it shows this :-
Local time: Wed 2015-04-29 11:43:59 BST Universal time: Wed 2015-04-29 10:43:59 UTC RTC time: Wed 2015-04-29 10:43:59 Time zone: Europe/London (BST, +0100) NTP enabled: yes NTP synchronized: no RTC in local TZ: no DST active: yes Last DST change: DST began at Sun 2015-03-29 00:59:59 GMT Sun 2015-03-29 02:00:00 BST Next DST change: DST ends (the clock jumps one hour backwards) at Sun 2015-10-25 01:59:59 BST Sun 2015-10-25 01:00:00 GMT
Just before I booted into linux (the machine dual boots between Mageia 5 and Windows 7) I set the time in the BIOS to be 11:43 but I see that it's changed already.
Does anybody have any ideas what's going wrong, and more importantly how to fix it?
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.
If I run timedatectl, it shows this :-
Local time: Wed 2015-04-29 11:43:59 BSTUniversal time: Wed 2015-04-29 10:43:59 UTC RTC time: Wed 2015-04-29 10:43:59 Time zone: Europe/London (BST, +0100) NTP enabled: yes NTP synchronized: no RTC in local TZ: no DST active: yes Last DST change: DST began at Sun 2015-03-29 00:59:59 GMT Sun 2015-03-29 02:00:00 BST Next DST change: DST ends (the clock jumps one hour backwards) at Sun 2015-10-25 01:59:59 BST Sun 2015-10-25 01:00:00 GMT
Just before I booted into linux (the machine dual boots between Mageia 5 and Windows 7) I set the time in the BIOS to be 11:43 but I see that it's changed already.
Does anybody have any ideas what's going wrong, and more importantly how to fix it?
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.
J.
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?
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.
On 29 April 2015 at 12:25, Chris Walker alug_cdw@the-walker-household.co.uk wrote:
I googled "RTC in local TZ" and one link suggested I change timedatectl to 'timedatectl set-local-rtc 1'
I think my preference would be to fix this at the Windows end, not the Linux end.
This looks useful: http://superuser.com/questions/185773/does-windows-7-support-utc-as-bios-tim... .. but I haven't tried it
Having RTC in UTC makes far more sense. Even if both systems understand that it is in local time, you still have the issue that both O/S will likely try to correct the time at BST boundaries, so the clock will go back one hour for each O/S on the system in autumn, and forward one per O/S in spring.
(This is a classic example of Windows assuming it is the only O/S on the system, and it doesn't even play well with multiple Windows versions on the same box.)
On Thu, 30 Apr 2015 17:25:13 +0100 Jonathan McDowell noodles@earth.li wrote:
On Wed, Apr 29, 2015 at 12:25:25PM +0100, Chris Walker wrote:
[snip]
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.
date output :- Thu 30 Apr 18:33:43 BST 2015
On Thu, 30 Apr 2015 17:33:01 +0100 Mark Rogers mark@more-solutions.co.uk wrote:
On 29 April 2015 at 12:25, Chris Walker alug_cdw@the-walker-household.co.uk wrote:
I googled "RTC in local TZ" and one link suggested I change timedatectl to 'timedatectl set-local-rtc 1'
I think my preference would be to fix this at the Windows end, not the Linux end.
This looks useful: http://superuser.com/questions/185773/does-windows-7-support-utc-as-bios-tim... .. but I haven't tried it
Having RTC in UTC makes far more sense. Even if both systems understand that it is in local time, you still have the issue that both O/S will likely try to correct the time at BST boundaries, so the clock will go back one hour for each O/S on the system in autumn, and forward one per O/S in spring.
(This is a classic example of Windows assuming it is the only O/S on the system, and it doesn't even play well with multiple Windows versions on the same box.)
I have now made the change to Windows and set the clock there to the correct time. I then rebooted the box and adjusted the CMOS clock to the correct time but as soon as I boot into Mageia, it sets the CMOS clock back an hour, viz :-
Local time: Fri 2015-05-01 11:33:47 BST Universal time: Fri 2015-05-01 10:33:47 UTC RTC time: Fri 2015-05-01 10:33:47 Time zone: Europe/London (BST, +0100) NTP enabled: yes NTP synchronized: yes RTC in local TZ: no DST active: yes
The desktop clock shows the time as 10:36 when it is in fact 11:36. I can put up with that if things like the times on emails are correct. So I'll check to see what time is displayed on this one when it hits the ALUG list.
I've had a look on the Mageia forum to see if anybody else is having this problem and it appears not. But I might well ask a question there as something else is also not right with the machine. If I right-click on the clock panel, the background disappears as does the taskbar and I get a very small window appear on one desktop. Perhaps it's time to try Mac OS ;-)
On Fri, 1 May 2015 12:56:21 +0100 Chris Walker alug_cdw@the-walker-household.co.uk wrote:
[snip]
So I'll check to see what time is displayed on this one when it hits the ALUG list.
The time on the mail is correct so I'll just ignore the desktop clock!
-
Chris Walker -
Jonathan McDowell -
Mark Rogers