Coolzero1982 Posted February 9 Posted February 9 Hello, my Cubitruck with Armbian 23.8.1 Bullseye has the false Time and i can't change this. i don't know who is the problem. "date" says me "Mo 9. Feb 19:24:06 CET 2026" but now we have 05:26, when i set date with "sudo date -s "2026-02-09 05:26:00", it looks like it will be override in the next moment, then "date" says sudo date -s "2026-02-09 05:26:00" Mo 9. Feb 05:26:00 CET 2026 root@cubietruck ~ > date Mo 9. Feb 19:26:27 CET 2026 dmesg | grep -i rtc [ 0.000000] Kernel command line: root=UUID=19cf2f1d-1a31-4890-bc04-a2f1c4e4e021 rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 loglevel=1 ubootpart=ba110a34-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u rtc-hctosys=0 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1 [ 0.000000] Unknown kernel command line parameters "ubootpart=ba110a34-01 ubootsource=mmc rtc-hctosys=0 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory", will be passed to user space. [ 1.553534] sun4i-drm display-engine: [drm] Cannot find any crtc or sizes [ 1.555880] sun4i-drm display-engine: [drm] Cannot find any crtc or sizes [ 1.573650] sunxi-rtc 1c20d00.rtc: registered as rtc0 [ 1.573701] sunxi-rtc 1c20d00.rtc: setting system clock to 2026-02-09T18:15:12 UTC (1770660912) [ 1.755046] axp20x-i2c 1-0034: Backup (RTC) battery charging is enabled [ 2.161281] rtc-hctosys=0 sudo systemctl restart chrony chronyc tracking chronyc sources -v Reference ID : 00000000 () Stratum : 0 Ref time (UTC) : Thu Jan 01 00:00:00 1970 System time : 0.000000000 seconds slow of NTP time Last offset : +0.000000000 seconds RMS offset : 0.000000000 seconds Frequency : 6.181 ppm slow Residual freq : +0.000 ppm Skew : 0.000 ppm Root delay : 1.000000000 seconds Root dispersion : 1.000000000 seconds Update interval : 0.0 seconds Leap status : Not synchronised .-- Source mode '^' = server, '=' = peer, '#' = local clock. / .- Source state '*' = current best, '+' = combined, '-' = not combined, | / 'x' = may be in error, '~' = too variable, '?' = unusable. || .- xxxx [ yyyy ] +/- zzzz || Reachability register (octal) -. | xxxx = adjusted offset, || Log2(Polling interval) --. | | yyyy = measured offset, || \ | | zzzz = estimated error. || | | \ MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^? listserver.trexler.at 0 6 0 - +0ns[ +0ns] +/- 0ns ^? time.netzwerge.de 0 6 0 - +0ns[ +0ns] +/- 0ns ^? 2a02:8108:4d82:e400:9677> 0 6 0 - +0ns[ +0ns] +/- 0ns ^? static.179.181.75.5.clie> 0 6 0 - +0ns[ +0ns] +/- 0ns ^? 2a09:e1c1:efc4:1337::123 0 6 0 - +0ns[ +0ns] +/- 0ns ^? 2a01:7e01::f03c:94ff:fee> 2 6 1 0 +50282s[+50282s] +/- 27ms ^? nobody.yourvserver.net 0 6 0 - +0ns[ +0ns] +/- 0ns ^? ctb01.martinmoerch.dk 0 6 0 - +0ns[ +0ns] +/- 0ns ^? fritz.box 0 6 0 - +0ns[ +0ns] +/- 0ns What can be the problem and how can i fix it. Thank you 0 Quote
Coolzero1982 Posted February 10 Author Posted February 10 This morning, the difference is not as big as yesterday, but it is still there. Why isn't it synchronized via NTP? sudo date -s “2026-02-10 04:13:00” Tue, Feb 10, 04:13:00 CET 2026 root@cubietruck ~ > date Tue, Feb 10, 06:11:41 CET 2026 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.