Forum Post

[OpenArm Troubleshooting] "No Such Device" on can0 After USB-CAN Adapter Swap (Beginner)

Adapter swap done but can0 no longer exists? Confirm interface mapping and udev naming before changing OpenArm configs.

Forum / Posts Index / OpenArm

Post

A very common OpenArm host-side error appears after changing a USB CAN adapter: old setup commands still refer to can0, but the new adapter binds differently or does not create the expected interface at all.

How are you diagnosing OpenArm cases where the system reports 'No such device' on can0 after a USB CAN adapter swap?

Please share how you verify adapter detection, interface creation, and naming assumptions, and what checks help you distinguish host configuration mistakes from actual CAN hardware faults.

If you reply, include one exact error symptom and one exact interface or adapter check that exposed the cause.

Related troubleshooting path: SocketCAN missing after NetworkManager update · CAN interface missing after reboot

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

Tags: openarm, can0, usb-can, no-such-device

Comment 1

Beginner context: After swapping adapters we got `candump can0: No such device` every time, but `lsusb` still showed the dongle. So the hardware was seen, just not bound to the expected interface name.

Comment 2

Beginner context: The decisive check was `dmesg | rg -i can` plus `ip -details link`. The new adapter came up as can1 because another virtual CAN was created first. Old scripts hardcoded can0, so bringup failed.

Comment 3

Beginner context: We fixed it with a udev rule pinned to adapter serial and updated startup to resolve interface by rule name. Since then swaps are plug-and-play without rewriting launch scripts.

Comment 4

Beginner context follow-up: Follow-up question for beginners: after adapter swap, which command do you run first to map physical adapter serial to interface name before bringup?

Quick Symptom Selector

Pick your closest symptom to follow the right troubleshooting path.

Not selected yet.

Quick FAQ

What usually causes "No such device on can0" after adapter swap?

Most often interface renaming or binding differences, not hardware failure.

lsusb
dmesg | rg -i "can|usb"
ip -details link | rg -n "can"
How do I keep future swaps plug-and-play?

Pin adapter identity with udev and resolve interface by stable name in startup scripts.

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.