System clock does not seem to get correct time from the ntp [SOLVED]

[jarkky]

Using the MX Date & Time -> Network Time -> Update Now results into:
200 OK
try: 1, refid: 00000000, correction: 0.000000001, skew: 0.000
try: 2, refid: 00000000, correction: 0.000000001, skew: 0.000
try: 3, refid: 00000000, correction: 0.000000001, skew: 0.000
try: 4, refid: 00000000, correction: 0.000000001, skew: 0.000
try: 5, refid: 00000000, correction: 0.000000001, skew: 0.000
try: 6, refid: 00000000, correction: 0.000000001, skew: 0.000
try: 7, refid: 00000000, correction: 0.000000001, skew: 0.000
try: 8, refid: 00000000, correction: 0.000000001, skew: 0.000
try: 9, refid: 00000000, correction: 0.000000001, skew: 0.000
try: 10, refid: 00000000, correction: 0.000000001, skew: 0.000
Can this be caused by failed CMOS battery?
In the Windows11 mode time seem to be correct.

Code: Select all

System:
  Kernel: 6.5.0-1mx-ahs-amd64 [6.5.3-1~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/vmlinuz-6.5.0-1mx-ahs-amd64 root=UUID=<filter> ro quiet splash
    init=/lib/systemd/systemd
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.3_ahs_x64 Libretto October 15  2023 base: Debian GNU/Linux
    12 (bookworm)
Machine:
  Type: Laptop System: HP product: HP ENVY Laptop 17-ce0xxx v: Type1ProductConfigId
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: HP model: 85E5 v: 30.32 serial: <superuser required> UEFI: Insyde v: F.18
    date: 08/14/2023
Battery:
  ID-1: BAT0 charge: 45.1 Wh (100.0%) condition: 45.1/45.1 Wh (100.0%) volts: 12.9 min: 11.6
    model: 333-54-2C-A LK03055XL type: Li-ion serial: <filter> status: full
CPU:
  Info: model: Intel Core i7-8565U bits: 64 type: MT MCP arch: Comet/Whiskey Lake note: check
    gen: core 8 level: v3 note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x8E (142)
    stepping: 0xC (12) microcode: 0xFA
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 2400 high: 2401 min/max: 400/4600 scaling: driver: intel_pstate
    governor: powersave cores: 1: 2400 2: 2400 3: 2400 4: 2400 5: 2400 6: 2401 7: 2400 8: 2400
    bogomips: 31999
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: Enhanced IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS, IBPB: conditional, RSB filling,
    PBRSB-eIBRS: SW sequence
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel WhiskeyLake-U GT2 [UHD Graphics 620] vendor: Hewlett-Packard driver: i915
    v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: eDP-1
    empty: DP-1,DP-2,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:3ea0 class-ID: 0300
  Device-2: NVIDIA GP108M [GeForce MX250] vendor: Hewlett-Packard driver: N/A alternate: nouveau
    non-free: 530.xx+ status: current (as of 2023-03) arch: Pascal code: GP10x process: TSMC 16nm
    built: 2016-21 pcie: speed: Unknown lanes: 63 link-max: gen: 6 speed: 64 GT/s bus-ID: 02:00.0
    chip-ID: 10de:1d13 class-ID: 0302
  Device-3: Cheng Uei Precision Industry (Foxlink) HP Wide Vision HD Camera type: USB
    driver: uvcvideo bus-ID: 1-4:3 chip-ID: 05c8:03d3 class-ID: 0e02
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: eDP-1 model: BOE Display 0x0825 built: 2018 res: 1920x1080 hz: 60 dpi: 128
    gamma: 1.2 size: 382x215mm (15.04x8.46") diag: 438mm (17.3") ratio: 16:9 modes: 1920x1080
  API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: Mesa Intel UHD Graphics 620 (WHL GT2)
    direct-render: Yes
Audio:
  Device-1: Intel Cannon Point-LP High Definition Audio vendor: Hewlett-Packard
    driver: sof-audio-pci-intel-cnl alternate: snd_hda_intel, snd_soc_skl, snd_sof_pci_intel_cnl
    bus-ID: 00:1f.3 chip-ID: 8086:9dc8 class-ID: 0401
  API: ALSA v: k6.5.0-1mx-ahs-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Cannon Point-LP CNVi [Wireless-AC] driver: iwlwifi v: kernel modules: wl
    bus-ID: 00:14.3 chip-ID: 8086:9df0 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 03:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) type: USB driver: btusb v: 0.8
    bus-ID: 1-10:6 chip-ID: 8087:0aaa class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 3.0 lmp-v: 5.1
    sub-v: 100 hci-v: 5.1 rev: 100
  Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
    service-classes: rendering, capturing, audio, telephony
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 port: 5060
    bus-ID: 00:17.0 chip-ID: 8086:282a rev: N/A class-ID: 0104
Drives:
  Local Storage: total: 1.14 TiB used: 228.31 GiB (19.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: PC SN520 SDAPNUW-256G-1006
    size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 15.8 Gb/s lanes: 2 type: SSD
    serial: <filter> rev: 20110006 temp: 42.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000LM048-2E7172 size: 931.51 GiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: 0001 scheme: MBR
Partition:
  ID-1: / raw-size: 47.6 GiB size: 46.55 GiB (97.80%) used: 16.31 GiB (35.0%) fs: ext4
    dev: /dev/nvme0n1p9 maj-min: 259:9
  ID-2: /boot raw-size: 1024 MiB size: 989.4 MiB (96.62%) used: 111.6 MiB (11.3%) fs: ext4
    dev: /dev/nvme0n1p8 maj-min: 259:8
  ID-3: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%) used: 112.2 MiB (43.8%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-4: /home raw-size: 465.76 GiB size: 457.38 GiB (98.20%) used: 211.77 GiB (46.3%) fs: ext4
    dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 76.0 C pch: 66.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2352 pm: dpkg pkgs: 2344 libs: 1220 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0 pm: snap pkgs: 8
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/expressvpn.list
    1: deb [signed-by=/usr/share/keyrings/expressvpn.asc] mirror+file: /usr/lib/expressvpn/repo_mirror.list any-version main
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
    1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/microsoft-edge.list
    1: deb [arch=amd64] https://packages.microsoft.com/repos/edge/ stable main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb https://mirrors.tuna.tsinghua.edu.cn/mxlinux/mx/repo/ bookworm main non-free
    2: deb https://mirrors.tuna.tsinghua.edu.cn/mxlinux/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/teams.list
    1: deb [arch=amd64] https://packages.microsoft.com/repos/ms-teams stable main
Info:
  Processes: 298 Uptime: 13m wakeups: 11601 Memory: 15.35 GiB used: 4.12 GiB (26.8%) Init: systemd
  v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

[j2mcgreg]

You need to configure Windows 11 to use Local Time. Otherwise, in a dual boot situation. it will override the time settings you make in Linux.

[jarkky]

This problem did not seem to occur before this week and I was using this system as it is above a year.
Do you think the Windows11 updates have altered its operations recently (so that its time setting will affect linux now on)?

[FullScale4Me]

3.9 Incorrect Windows Time In Dual Boot and turn on Time Sync

Windows assumes Local Time and Linux expects UTC. Making Linux use local time the same way Windows does is a good option. There are two ways to address this time difference.

Do NOT do both!!!

1) LINUX: Change the time setting for Linux: https://mxlinux.org/wiki/help-files/date-time/


2) WINDOWS: perform the following steps (may cause issues with some 3rd party apps):

• Open Regedit on Windows and navigate to:

• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation\.

• Right-click the “TimeZoneInformation” key.

• Select "New" => DWORD (32-bit) Value. (or QWORD on 64-bit systems).

• Name your new value RealTimeIsUniversal.

• Double-click the RealTimeIsUniversal value you've just created, set its value to 1.

• Click “OK” to exit Regedit.

Right click time.

Left click Adjust date/time.

Turn OFF "Set Time Automatically".

[jarkky]

Screenshot_2024-07-31_23-18-46.png

[DukeComposed]

The errors says, it can not update the time&date.

OK, do the details say anything interesting? QSI shows you're running systemd, and you haven't specified if you've historically run your MX system with systemd or svsvinit. If you continue to run your machine with systemd as init, I imagine you'll have to figure out how to troubleshoot the systemd-timesyncd service. Good luck. If you start your machine with sysvinit, it will most likely try to sync the system with a serious piece of software like ntpd or chronyd.

[jarkky]

I'm not sure why this happens. Maybe actually this machine does not have separate RTC CMOS battery at all and there is something else wrong now.
As I said it worked earlier for a year and more and started to give this problem just few days ago.

[FullScale4Me]

The issue could be, if on MX 23 and your [Uncomplicated] Firewall is enabled. It is by default on MX 23 installation. A firewall on your PC could be blocking ports or your ISP router may be doing blocking.

Chrony is the NTP time source in use from MX 23 onward.

What is the default port for chronyd and how to change the port? https://access.redhat.com/solutions/5716751

"There are two ports for chronyd one is udp 323 another is udp 123. (Jun 13, 2024)"

[jarkky]

Even firewall disabled for the test, the system time did not update

Screenshot_2024-08-02_00-07-1.png

I am starting to think that there was lightning strike or something that has damaged the RTC.

[jarkky]

But it could be possible that it didn't work in foreign country, why?
This laptop was set to SouthKorea and it stopped working in Philippines.
And when returned to Korea it started to work again.
Maybe it is caused by some internet conditions there in the Philippines.