always an hour out. I have to turn off 'use network time' and turn it on again to make it show the right time. It is wrong on GMT now it's Winter
and it was wrong in the Summer on BST as well.
I a hoping this is a common fault with a simple fix. This is mint 21.3
Tim W
always an hour out. I have to turn off 'use network time' and turn it on again to make it show the right time. It is wrong on GMT now it's Winter and it was wrong in the Summer on BST as well.
I a hoping this is a common fault with a simple fix. This is mint 21.3
Tim W
On 29/10/2026 10:59, TimW wrote:how did you put it right.
always an hour out. I have to turn off 'use network time' and turn it on
again to make it show the right time. It is wrong on GMT now it's Winter
and it was wrong in the Summer on BST as well.
I a hoping this is a common fault with a simple fix. This is mint 21.3
Tim W
I put it right this morning and it has gone an hour ahead again now.
TW
On 10/29/26 11:48 AM, TimW wrote:
On 29/10/2026 10:59, TimW wrote:how did you put it right.
always an hour out. I have to turn off 'use network time' and turn it on >>> again to make it show the right time. It is wrong on GMT now it's Winter >>> and it was wrong in the Summer on BST as well.
I a hoping this is a common fault with a simple fix. This is mint 21.3
Tim W
I put it right this morning and it has gone an hour ahead again now.
TW
PS.-a I have no issues with Mint 22.3 Cinnamon.
Also I bounce between windows and Linux.-a-a My issue is windows won't set right.-a But that's nothing you're probably fighting.
always an hour out. I have to turn off 'use network time' and turn it on again to make it show the right time. It is wrong on GMT now it's Winter
and it was wrong in the Summer on BST as well.
I a hoping this is a common fault with a simple fix. This is mint 21.3
On Thu, 10/29/2026 6:59 AM, TimW wrote:
always an hour out. I have to turn off 'use network time' and turn it on again to make it show the right time. It is wrong on GMT now it's Winter and it was wrong in the Summer on BST as well.
I a hoping this is a common fault with a simple fix. This is mint 21.3
Tim W
https://linuxize.com/post/how-to-set-or-change-timezone-in-linux/
Show complete time status timedatectl
[...]
On Thu, 10/29/2026 11:13 AM, Alan K. wrote:
On 10/29/26 11:48 AM, TimW wrote:
On 29/10/2026 10:59, TimW wrote:how did you put it right.
always an hour out. I have to turn off 'use network time' and turn it on >>>> again to make it show the right time. It is wrong on GMT now it's Winter >>>> and it was wrong in the Summer on BST as well.
I a hoping this is a common fault with a simple fix. This is mint 21.3 >>>>
Tim W
I put it right this morning and it has gone an hour ahead again now.
TW
PS.-a I have no issues with Mint 22.3 Cinnamon.
Also I bounce between windows and Linux.-a-a My issue is windows won't set right.-a But that's nothing you're probably fighting.
By default, one uses UTC and one uses local time.
But there is a flag, to make them both the same,
such that you can boot back and forth and the
hour will be correct. It was claimed at one time,
there was a downside to using that flag, which
you would have to research.
The time is maintained by two crystals on the computer.
When the computer is off, the 32768Hz quartz cylinder
provides the ticks the RTC uses to track the time.
At boot, the RTC time (a forty year old Motorola
CMOS gate level implementation, emulated in Intel
silicon) is transferred to the software clock.
The software clock (if using a tick-based OS
design instead of tickless), it advances based on
a high level interrupt. When your NVidia card
changes from 2D to 3D mode, it is possible for a tick
to get lost (because some weird things happen when
the Ring0 driver is screwing around). If you played
enough games, entering and exiting, that might
contribute to the software clock drifting a bit.
It is expected, due to clock handling, that some
tiny error could accumulate from all the booting
and shutting down.
That likely pales in comparison to the stability
of the actual BCLK used while the system is running.
BCLK is what the software clock would be traceable to.
It's probably 50PPM or so, but could be worse than that.
*******
https://dev.to/hopsayer/fix-time-jumps-between-linux-and-windows-dual-boot-3omc
"This happens because both systems read the same hardware clock
but interpret it differently: Windows treats it as local time,
while Linux treats it as UTC."
"Use UTC for both systems (recommended):
On Linux:
timedatectl set-local-rtc 0 --adjust-system-clock
It's not necessary because Linux uses UTC by default, but this explicitly ensures the setting.
On Windows: [admin terminal]
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation" /v RealTimeIsUniversal /t reg_dword /d 1 /f
It will add a registry key to treat the hardware clock as UTC.
"
That's an example of keeping the peace.
The article has a second option.
If you used the second option, then setting the clock at
the BIOS level, from your wristwatch, is going to make
more sense :-)
Paul
always an hour out.
By default, one uses UTC and one uses local time. But there is a
flag, to make them both the same, such that you can boot back and
forth and the hour will be correct.
It was claimed at one time, there was a downside to using that flag,
which you would have to research.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:30:54 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,563 |