• Time is never right

    From TimW@timw@nomailta.co.uk to alt.os.linux.mint on Thu Oct 29 10:59:28 2026
    From Newsgroup: alt.os.linux.mint

    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
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From TimW@timw@nomailta.co.uk to alt.os.linux.mint on Thu Oct 29 15:48:29 2026
    From Newsgroup: alt.os.linux.mint

    On 29/10/2026 10:59, 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

    I put it right this morning and it has gone an hour ahead again now.
    TW
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.os.linux.mint on Thu Oct 29 11:03:12 2026
    From Newsgroup: alt.os.linux.mint

    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
    Print the current time zone only timedatectl show --property=Timezone --value
    List all time zones timedatectl list-timezones
    Set time zone sudo timedatectl set-timezone America/New_York
    Reset to UTC sudo timedatectl set-timezone Etc/UTC Enable NTP sync sudo timedatectl set-ntp true
    Set without systemd sudo ln -sf /usr/share/zoneinfo/Region/City /etc/localtime


    Debian and Ubuntu Alternative: tzdata

    On Debian and Ubuntu systems, you can also use the tzdata package
    to change the time zone through an interactive menu:

    sudo dpkg-reconfigure tzdata

    Select a geographic area and then a city or region. The command updates /etc/localtime
    and prints the resulting local and universal times.

    ***************

    I think in the past, the tzdata definition is what controlled daylight savings dates. When regions of the world change their definitions on a frequent basis, this wreaks havoc on the tzdata. Changes should be pushed out promptly when governments make decisions. I don't know if there is a central registry
    for such changes (government applies to have their definition updates)
    or how that works.

    You would find, on say an old Win2K OS installation, the TZDATA has probably changed three or four times since changes were regularly pushed out, and you had to use a utility yourself and update the details.

    I'm not a Time Lord, and those are just the barest details in that article.
    But I have seen the kind of time errors you're seeing, and I cannot always trace them to anything meaningful.

    When you set NTP synchronization, that's to prevent drift of the local clock. That can use "pool", which is 800 nodes all deriving their time from
    atomic clocks (stratum). You can also select organizational NTP sites,
    which are also atomic, but have been known to have gross errors on occasion. The largest reference clock error I've seen is 20 minutes... which is not good really.

    You can synchronize to GPS, but that's not particularly a good idea any more. There is too much farting with GPS, to rely on it as in another era. GPS
    is atomic as well, it's the time average of a pool of atomic clocks. You can get a quite accurate UTC that way.

    Paul
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan K.@alan@invalid.com to alt.os.linux.mint on Thu Oct 29 11:13:25 2026
    From Newsgroup: alt.os.linux.mint

    On 10/29/26 11:48 AM, TimW wrote:
    On 29/10/2026 10:59, 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

    I put it right this morning and it has gone an hour ahead again now.
    TW
    how did you put it right.
    PS. I have no issues with Mint 22.3 Cinnamon.

    Also I bounce between windows and Linux. My issue is windows won't set right. But
    that's nothing you're probably fighting.
    --
    Mint 22.3, Thunderbird 153.5.1esr, Firefox 158.0.1
    Alan K.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.os.linux.mint on Thu Oct 29 12:47:09 2026
    From Newsgroup: alt.os.linux.mint

    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:
    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
    how did you put it right.
    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

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Dan Purgert@dan@djph.net to alt.os.linux.mint on Thu Oct 29 16:47:58 2026
    From Newsgroup: alt.os.linux.mint

    On 2026-10-29, 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

    What timezone is the machine configured for?
    Are you dual-booting with Windows?

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From TimW@timw@nomailta.co.uk to alt.os.linux.mint on Thu Oct 29 18:12:39 2026
    From Newsgroup: alt.os.linux.mint

    On 29/10/2026 15:03, Paul wrote:
    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
    [...]

    I got a warning! and followed the advice.
    Hopefully that's fixeed it. thanks


    RTC time: Thu 2026-10-29 19:02:00
    Time zone: Europe/London (GMT, +0000)
    System clock synchronized: yes
    NTP service: active
    RTC in local TZ: yes

    Warning: The system is configured to read the RTC time in the local time
    zone.
    This mode cannot 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'.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan K.@alan@invalid.com to alt.os.linux.mint on Thu Oct 29 15:08:23 2026
    From Newsgroup: alt.os.linux.mint

    On 10/29/26 12:47 PM, Paul wrote:
    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:
    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
    how did you put it right.
    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

    I got my info from a How-To Geek article. https://www.howtogeek.com/323390/how-to-fix-windows-and-linux-showing-different-times-when-dual-booting/
    Seems to be working for me.
    Only issue is when I ventoy into a new linux system to test and it's not set and messes
    with everything. (lol). But it's temp.
    --
    Mint 22.3, Thunderbird 153.5.1esr, Firefox 158.0.1
    Alan K.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to alt.os.linux.mint on Thu Oct 29 23:14:21 2026
    From Newsgroup: alt.os.linux.mint

    On Thu, 29 Oct 2026 10:59:28 +0000, TimW wrote:

    always an hour out.

    Does

    TZ=UTC date

    show the right time in UTC? Conversely, does

    TZ=-2local time zone-+ date

    show something close to your local clock time? Suitable values for
    -2local time zone-+ are the names of files in /usr/share/zoneinfo
    (without that base directory prefix).

    What is your rCLTZrCY variable set to?

    Note that the concept of rCLlocalrCY time on *nix is process-specific.
    There isnrCOt really much (if any) concept of a rCLsystemwiderCY local time. --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to alt.os.linux.mint on Thu Oct 29 23:17:26 2026
    From Newsgroup: alt.os.linux.mint

    On Thu, 29 Oct 2026 12:47:09 -0400, Paul wrote:

    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.

    Note that Linux system time is always UTC. That flag controls the
    Linux systemsrCOs treatment of the hardware clock. Obviously if you
    dual-boot frequently between Linux and some proprietary OS that
    insists on treating the hardware clock as local time, it is best if
    Linux does the same.

    It was claimed at one time, there was a downside to using that flag,
    which you would have to research.

    It is prone to getting the calculation of the daylight-saving
    transition wrong. Like forgetting it has already turned on
    daylight-saving and then doing it again, ending up two hours ahead of
    winter time instead of one.

    It just makes more sense to have an underlying time reference that
    doesnrCOt keep flipping back and forth.
    --- Synchronet 3.22a-Linux NewsLink 1.2