The simple service unit I posted later in the thread (which invokes
hwclock) works great for me.
On Tue, Mar 31, 2020 at 1:29 PM Michał Zegan wrote:
>
> I have used the embedded term unfortunately, but it seems to affect at
> least some devices like raspberry pi, odroid c2, like sbc's.
>
> W dniu
I have used the embedded term unfortunately, but it seems to affect at
least some devices like raspberry pi, odroid c2, like sbc's.
W dniu 31.03.2020 o 17:57, Lennart Poettering pisze:
> On Di, 31.03.20 17:39, Michał Zegan (webczat_...@poczta.onet.pl) wrote:
>
>> Seems like rtc drivers as module
On Di, 31.03.20 17:39, Michał Zegan (webczat_...@poczta.onet.pl) wrote:
> Seems like rtc drivers as module is quite often a thing for embedded.
> But not sure where this should be solved, maybe at initramfs? If one is
> unwilling to build all rtc drivers into the kernel (the case of generic
> kern
Seems like rtc drivers as module is quite often a thing for embedded.
But not sure where this should be solved, maybe at initramfs? If one is
unwilling to build all rtc drivers into the kernel (the case of generic
kernels where you would have to build all of them in)...
W dniu 31.03.2020 o 16:29,
On Do, 12.03.20 07:13, Kevin P. Fleming (ke...@km6g.us) wrote:
> I've got some Debian Buster systems (so using the Debian systemd
> package 241-7), which have battery-backed RTCs. However the driver for
> these RTCs is loaded as a module, not built into the kernel. As a
> result the kernel's featu
Indeed, I landed there later after my reply. I'm disappointed that it
was never resolved, but I did add a service unit which works
perfectly.
-
[Unit]
Description=Set system clock from hardware clock
After=systemd-modules-load.service
[Service]
Type=oneshot
ExecStart=/sbin/hwclock --hcto
On Thu, 12 Mar 2020 17:35:16 -0400
"Kevin P. Fleming" wrote:
> Thanks, I agree. I could some up with something which ran timedatectl
> to set the system time from the RTC, but the hwclock tool is already
> there for that purpose.
>
> I'll need to investigate why this script exits without making a
Thanks, I agree. I could some up with something which ran timedatectl
to set the system time from the RTC, but the hwclock tool is already
there for that purpose.
I'll need to investigate why this script exits without making any
changes when systemd is running; either the authors expected some par
On Thu, Mar 12, 2020 at 7:13 AM Kevin P. Fleming wrote:
> Prior to systemd, with the 'hwclock' package installed, a udev rule
> would trigger reading of the RTC and setting the system clock when
> /dev/rtc0 appeared. With systemd running, the script run by that udev
> rule is suppressed, it doesn'
