docs(MAINTAINING): note timesyncd vs networkd/NetworkManager conflict - #4
Merged
Merged
Conversation
The base Arch Linux ARM (rpi) tarball ships systemd-networkd enabled while customize.sh also enables NetworkManager, so both run at once. networkd claims the unplugged wired end0 and writes ONLINE_STATE=offline, which makes systemd-timesyncd never send an NTP packet. Combined with the uConsole having no RTC, the clock ends up badly off after boot. Document the symptom, root cause, the on-device permanent fix (disable/mask networkd, drop stale netif state, pin JP NTP servers), and a TODO to fix it at image-build time in customize.sh. Added to both EN and JA docs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
On the running uConsole,
systemd-timesyncdwasactivebut never synced (PacketCount=0, emptyServerName), leaving the clock badly off — even thoughping/ manual UDP 123 queries worked.Root cause is two-fold and both layers originate from what this image ships:
RTC time: n/a) → the clock drifts on every boot, so network sync is effectively mandatory.systemd-networkdenabled, whilescripts/customize.shadditionally enables NetworkManager → both run at once. The real link (wlan0) is on NetworkManager, but networkd claims the unplugged wiredend0, staysconfiguring, and writesONLINE_STATE=offlineinto/run/systemd/netif/state.timesyncdreads that networkd-provided state and never starts syncing.Changes
### Time sync … networkd / NetworkManager conflictsubsection under Arch-specific operations in bothMAINTAINING.mdandMAINTAINING.ja.md(EN/JA parity), documenting:netifstate, pin JP NTP servers),scripts/customize.sh.Docs-only; no build behavior changes in this PR.
🤖 Generated with Claude Code