Hi, community!
In my situation, the NetworkManager service needs to be restarted to “see” the link connected to the external Type-C Ethernet after the adapter has been connected to the Type-C port. Then it can “see” and use the cable but before that, it shows “no carrier”.
It’s how it works after I physically disconnected the cable and then connected again after a couple of seconds.
┬─[iromanyshyn@iromanyshyn-firefly:~]─[17:56:39]
╰─>$ sudo ip link show 17:56:39
[sudo] password for root:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
link/ether 68:3e:26:73:0e:01 brd ff:ff:ff:ff:ff:ff
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
link/ether 02:42:4e:1b:9d:7c brd ff:ff:ff:ff:ff:ff
5: enp0s13f0u1u1c2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
link/ether 34:29:8f:10:4c:32 brd ff:ff:ff:ff:ff:ff
┬─[iromanyshyn@iromanyshyn-firefly:~]─[17:56:59]
╰─>$ sudo systemctl restart NetworkManager 17:56:59
┬─[iromanyshyn@iromanyshyn-firefly:~]─[17:57:25]
╰─>$ sudo ip link show 17:57:25
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
link/ether 68:3e:26:73:0e:01 brd ff:ff:ff:ff:ff:ff
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
link/ether 02:42:4e:1b:9d:7c brd ff:ff:ff:ff:ff:ff
5: enp0s13f0u1u1c2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 34:29:8f:10:4c:32 brd ff:ff:ff:ff:ff:ff