**** BEGIN LOGGING AT Mon Oct 19 02:59:57 2020 **** BEGIN LOGGING AT Mon Oct 19 02:54:02 2020 **** ENDING LOGGING AT Mon Oct 19 02:59:57 2020 **** BEGIN LOGGING AT Mon Oct 19 02:59:57 2020 Oct 19 04:07:54 @zmatt, we had a chat some days ago regarding CBB-Serial cape - fyi - "disable generic-board-startup.service if you don't need usb networking" will also disable automatic configuration of the cape (ip link won't show can0 and can1) Oct 19 04:10:46 sudo sed -i "/##USB_NETWORK_DISABLED/{s/^##//}" /etc/default/bb-boot # shall do the trick Oct 19 04:13:39 I don't see how that could possibly affect that, are you sure you didn't change something else at the same time? Whether or not the can interfaces appear in "ip link" is not up to userspace software, it only depends on whether the kernel has detected the hardware (i.e. the interfaces are enabled in DT) and loaded the driver for it Oct 19 04:15:07 is it possible that can0 and can1 show up only after _some time_ after ssh login has passed? Oct 19 04:15:13 (checking on that atm) Oct 19 04:15:56 i expected can0 and can1 to be visible around the same time eth0 is shown in ip link# Oct 19 04:17:06 it shows up later - I was wrong. Oct 19 04:17:13 Sorry Oct 19 04:17:19 huh, that seems very odd Oct 19 04:17:44 the can interfaces appear so late that you're able to login via ssh and use "ip link" before they show up? Oct 19 04:19:01 I even typed in ip link 7 times (1-2 secs inbetween) before it showed up Oct 19 04:20:10 wtf Oct 19 04:20:32 Where is That From? :D Oct 19 04:20:36 :P Oct 19 04:21:04 (Linux bb-rt-0 5.4.66-ti-rt-r18 #1buster SMP PREEMPT_RT) Oct 19 04:21:05 huh, what Oct 19 04:22:25 journalctl -o short-monotonic -b | grep can shows the devices are registered by the kernel in the first second of boot, yet the network interface appear (as reported by connman) like 20 seconds after boot Oct 19 04:22:29 bizarre Oct 19 04:22:30 anyway, bbl **** ENDING LOGGING AT Mon Oct 19 04:25:06 2020