Re: strange time problem with bullseye
On Wednesday 06 March 2024 12:37:09 am Teemu Likonen wrote:
> * 2024-03-06 02:47:06+0800, hlyg wrote:
>
> > my newly-installed deb11 for amd64 shows wrong time, it lags behind
> > correct time by 8 hours though difference between universal and local
> > is ok.
>
> It seems that you have solved the problem but here is another hint.
> "timedatectl" is a good high-level tool for querying and adjusting time
> settings. Without command-line arguments it prints a lot of useful info:
>
> $ timedatectl
> Local time: ke 2024-03-06 07:33:00 EET
> Universal time: ke 2024-03-06 05:33:00 UTC
> RTC time: ke 2024-03-06 05:33:00
> Time zone: Europe/Helsinki (EET, +0200)
> System clock synchronized: yes
> NTP service: active
> RTC in local TZ: no
>
> See "timedatectl -h" or manual page for more info.
>
Mine shows:
Local time: Wed 2024-03-06 12:09:44 EST
Universal time: Wed 2024-03-06 17:09:44 UTC
RTC time: Wed 2024-03-06 17:20:53
Time zone: America/New_York (EST, -0500)
Network time on: yes
NTP synchronized: no
RTC in local TZ: no
How do I get the RTC to agree with the right time? I don't reboot this often, but when I do the time displayed on the onscreen clock is typically off by several minutes.
--
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space, a critter that can
be killed but can't be tamed. --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James
M Dakin
Reply to: