Forum Post

[OpenArm Troubleshooting] SocketCAN Missing After NetworkManager Update (Beginner)

After a host update, can0 disappeared? Isolate NetworkManager ownership conflicts fast and restore stable OpenArm bringup.

Forum / Posts Index / OpenArm

Post

A very realistic OpenArm host problem appears after a desktop or package update: SocketCAN worked before, but after a NetworkManager or networking stack change the expected interface no longer comes up the same way.

How are you diagnosing OpenArm cases where you cannot find the SocketCAN interface after a NetworkManager update?

Please share how you separate service conflicts from driver problems, which host-side checks reveal who now owns interface setup, and what recovery steps make bringup stable again.

If you reply, include one exact post-update symptom and one exact system check that exposed the cause.

Related troubleshooting path: CAN interface missing after reboot · No such device on can0 after adapter swap

Module: OpenArm · Audience: builders-integrators · Type: question

Tags: openarm, socketcan, networkmanager, interface

Comment 1

Beginner context: Exact symptom here: after update, `ip link` showed only lo and eno1; can0 never appeared, and OpenArm bringup failed in under 5 seconds. Hardware was fine because the same adapter worked from a live USB image.

Comment 2

Beginner context: The check that exposed it was `nmcli dev status` plus `systemctl status systemd-networkd`. NetworkManager started managing the CAN device and overwrote the old startup path. Marking the CAN adapter unmanaged fixed interface creation immediately.

Comment 3

Beginner context: To keep it stable we added a boot check script: fail startup unless `ip -details link show can0` reports UP with expected bitrate. This catches future package updates before operators hit motion commands.

Comment 4

Beginner context follow-up: Follow-up question for beginners: which single command gave you the first reliable signal that NetworkManager was overriding CAN setup, and what output line confirmed it?

Quick Symptom Selector

Pick your closest symptom to follow the right troubleshooting path.

Not selected yet.

Quick FAQ

How can I detect NetworkManager ownership conflicts?

Compare NetworkManager and networkd states right after update and check who owns CAN setup.

nmcli dev status
systemctl status NetworkManager systemd-networkd --no-pager
ip -details link | rg -n "can"
What prevents this from breaking again?

Pin adapter ownership policy and gate bringup on CAN state/bitrate checks.

Can I copy these commands as-is?

Use them as a checklist template first. Confirm interface names, fixture IDs, and safety conditions in your own cell before execution.