systemd adjusts hardware/kernel clock to be at least when systemd was last released (ie. sometime in 2020). It does that very early during init. And since initrd's init is systemd, the equivalent functionality is already there.
Do you have any symptoms that indicate that above is not working? I.e. do you see system clock coming up as before than 2020? any tls / gpg verification failures (i.e. errors like CA certificate expired, or start date in the future)
No, we do not need fixrtc script.
kernel cmdline must _not_ specify 'fixrtc'
systemd adjusts hardware/kernel clock to be at least when systemd was last released (ie. sometime in 2020). It does that very early during init. And since initrd's init is systemd, the equivalent functionality is already there.
Do you have any symptoms that indicate that above is not working? I.e. do you see system clock coming up as before than 2020? any tls / gpg verification failures (i.e. errors like CA certificate expired, or start date in the future)