You are not logged in.
Pages: 1
My system time is out. How do I fix that? hwclock, timedatectl, and ntp aren't available.
Last edited by safari (2026-07-02 14:33:03)
Offline
sudo apt install ntpsec-ntpdate
is valid for devuan 6.0
sudo ntpdate-debian2026-07-02 16:39:31.356971 (+0200) +0.170255 +/- 0.010254 0.debian.pool.ntp.org 37.247.53.178 s2 no-leapbut with dual-boot windows + linux there is still woes, at least on computers that i use.
Offline
Thanks, that worked. Do you know if that sets OS time only, or hardware time too?
Last edited by safari (2026-07-02 15:03:15)
Offline
would have to guess, but apparently i am able to mess up the time every other time i boot into windows and back , or so ~
there have been kind peopel on this forum who told me how to fix time with windows tricks ]
but those have tricks not lasted that long also use several computer , and what function on one, seem not always stable on another. . it has probably to do aswell with the computers itself; and maybe also language, regional settings may interfere?
maybe some day we can get to to the bottom of it.
Offline
i think the confusion stems also from the fact that during installation i set "language: englsish"
but i live somehwere else, and i am however constrained to select a region that has "english mapping" and hence everything goes tupsy turvy;
this is probably a limitating on the lclassic debian-inux installer.
Offline
Do you know if that sets OS time only, or hardware time too?
ntp sets the HW clock. The rest is job of the operating system.
In Linux its standard to set the HW re. the bios clock to UTC. During installation you configure your location and timezone, and the OS then generates the local time from that.
Windows per default is running on local time, i.e. the bios clock is set to local time. This creates 2h time shifts on a Linux/Windows dual boot system. The best fix is to set Windows to UTC.
Online
ntp sets the HW clock.
As fas as I know it doesn't. (And I'm not sure, if this was changed with ntpsec?)
NTP sets the systemtime only ...
If NTP would be depending on the HW-clock, how should it work with devices (e.g. singleborad-computers) without any such?
Best Regards, FM81
Last edited by FM81 (2026-07-03 04:20:39)
The most brilliant role in comedy is that of a fool, he must not be in order to make it seem. (Miguel de Cervantes)
Offline
would have to guess, but apparently i am able to mess up the time every other time i boot into windows and back , or so ~
there have been kind peopel on this forum who told me how to fix time with windows tricks ]
but those have tricks not lasted that long also use several computer , and what function on one, seem not always stable on another. . it has probably to do aswell with the computers itself; and maybe also language, regional settings may interfere?
maybe some day we can get to to the bottom of it.
It has to do with windows always setting the system clock to local time. Most Linux installs default to Universal Time, the UTC method o doing it. A .reg file download to make the required change.
https://www.howtogeek.com/wp-content/up … C-Time.zip
From this page.
Offline
As fas as I know it doesn't. (And I'm not sure, if this was changed with ntpsec?)
I does indirectly. When I shut down my PC the HW clock is updated. ntp and ntpsec are the same.
If NTP would be depending on the HW-clock, how should it work with devices (e.g. singleborad-computers) without any such?
I am pretty sure any device supporting a clock has a RTC on board.
Online
I does indirectly. When I shut down my PC the HW clock is updated.
In SYSVINIT this is done by /etc/init.d/hwclock.sh for example. But it works independent of what your systemtime was set.
It does it's job too, if there is no NTP or if you've changed your systemtime manually.
I am pretty sure any device supporting a clock has a RTC on board.
For example, Raspberry, at least up to models 4 (didn't know about 5) doesn't have a RTC. ("fake-hwclock" here is not the same)
But independent from all said before, you can go the way "vice versa" and set some type of hardware-vlock (for example DCF77, GPS or what ever) as source for NTP.
Greetings, FM81
Last edited by FM81 (2026-07-03 12:15:42)
The most brilliant role in comedy is that of a fool, he must not be in order to make it seem. (Miguel de Cervantes)
Offline
To maintain accuracy of your system's clock you can use "chrony". It will enable also a dedicated service.
If you run only Devuan is enough to install the "chrony" package.
If you are dual-boot with Windows it's recommended to have both system set to UTC time. Windows does not use UTC by default, and if you are dual-booting, this will conflict with Devuan. That's why the installer will see that you have Windows installed and will set the time as Windows to local time.
To make the system time to UTC in Windows just download and run the registry file that RedGreen925 suggested.
In Devuan do this:
Check if the system time is set to UTC or not:
$ cat /etc/adjtime
Marks the hardware clock standard as UTC in Devuan and verify
$ sudo hwclock --systohc --utc
$ cat /etc/adjtime
Force chrony to re-sync:
sudo chronyc makestep
Last edited by ovi (Yesterday 21:39:51)
Offline
The kernel will set the hwclock itself if a time-keeper is running successfully.
All you needed to do was install ntpsec.
ntpsec-ntpdate is for single-shot use: that was wrong advice.
Yes, chrony will also work, but you don't need to switch software family to get this behaviour.
Offline
Pages: 1