Arch Linux

vids

Member

Registered: 2024-12-19

Posts: 17

Interface LAN Ethernet adapter doesn’t shop up [SOLVED]

Hello. I am relatively new in archlinux.
After boot, LAN (wired connection) works right. But if I unplug the Ethernet cable and plug it back, the Interface Ethernet adapter doesn’t shop up anymore.
“ifplug” is installed.

Before unplug the Ethernet cable I get:

lspci
00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Iris Graphics 6100 (rev 09)
00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03)
00:15.0 DMA controller: Intel Corporation Wildcat Point-LP Serial IO DMA Controller (rev 03)
00:15.4 Serial bus controller: Intel Corporation Wildcat Point-LP Serial IO GSPI Controller #1 (rev 03)
00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03)
00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3)
00:1c.1 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #2 (rev e3)
00:1c.2 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3)
00:1c.4 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #5 (rev e3)
00:1c.5 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #6 (rev e3)
00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
00:1f.6 Signal processing controller: Intel Corporation Wildcat Point-LP Thermal Management Controller (rev 03)
02:00.0 Multimedia controller: Broadcom Inc. and subsidiaries 720p FaceTime HD Camera
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC (rev 01)
04:00.0 SATA controller: Samsung Electronics Co Ltd S4LN058A01[SSUBX] AHCI SSD Controller (Apple slot) (rev 01)
05:00.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
06:00.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
06:03.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
06:04.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
06:05.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
06:06.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
07:00.0 System peripheral: Intel Corporation DSL5520 Thunderbolt 2 NHI [Falcon Ridge 4C 2013]
08:00.0 PCI bridge: Intel Corporation DSL2210 Thunderbolt Controller [Port Ridge 1C 2011]
09:00.0 PCI bridge: Intel Corporation DSL2210 Thunderbolt Controller [Port Ridge 1C 2011]
0a:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM57762 Gigabit Ethernet PCIe

ip link
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: ens9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 49:e7:a0:2c:bc:28 brd ff:ff:ff:ff:ff:ff altname enp10s0 altname enx49e7a02cbc28
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DORMANT group default qlen 1000 link/ether b5:87:62:e3:a7:8f brd ff:ff:ff:ff:ff:ff

After I unplugged and plugged back the Ethernet cable:

00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Iris Graphics 6100 (rev 09)
00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03)
00:15.0 DMA controller: Intel Corporation Wildcat Point-LP Serial IO DMA Controller (rev 03)
00:15.4 Serial bus controller: Intel Corporation Wildcat Point-LP Serial IO GSPI Controller #1 (rev 03)
00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03)
00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3)
00:1c.1 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #2 (rev e3)
00:1c.2 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3)
00:1c.4 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #5 (rev e3)
00:1c.5 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #6 (rev e3)
00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
00:1f.6 Signal processing controller: Intel Corporation Wildcat Point-LP Thermal Management Controller (rev 03)
02:00.0 Multimedia controller: Broadcom Inc. and subsidiaries 720p FaceTime HD Camera
03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC (rev 01)
04:00.0 SATA controller: Samsung Electronics Co Ltd S4LN058A01[SSUBX] AHCI SSD Controller (Apple slot) (rev 01)
05:00.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
06:00.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
06:03.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
06:04.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
06:05.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
06:06.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
07:00.0 System peripheral: Intel Corporation DSL5520 Thunderbolt 2 NHI [Falcon Ridge 4C 2013]

the 3 last lines disappeared...

ip link
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
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DORMANT group default qlen 1000 link/ether b5:87:62:e3:a7:8f brd ff:ff:ff:ff:ff:ff

I just can’t get ens9 Interface Ethernet back! I am working on it since 2 days! Any clue?

Last edited by vids (2024-12-22 07:17:09)

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 8,999

Website

Re: Interface LAN Ethernet adapter doesn’t shop up [SOLVED]

Try unloading the tg3 module and then load it again.

Presumably this is an ifplugd problem. How have you configured that?

---

Jin, Jîyan, Azadî

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 71,651

Re: Interface LAN Ethernet adapter doesn’t shop up [SOLVED]

Please use [code][/code] tags, not "quote" tags. Edit your post in this regard.

You're losing an entire thunderbolt controller - is this some ethernet dongle or is there a dock involved?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

vids

Member

Registered: 2024-12-19

Posts: 17

Re: Interface LAN Ethernet adapter doesn’t shop up [SOLVED]

Head_on_a_Stick: Thank you very much for your answers, they gave me some guidance and understanding  concerning ifplugd.

Seth: Sorry for the "quote" tags, I will use the  tags in the future.
I installed archlinux on an old mac-book (2015) and I use an Ethernet dongle. I was basically unplugging the whole dongle and not only the cable. Obviously, as a matter of fact, I was losing an entire thunderbolt controller…
I can't believe how headless I am!!

Next challenge: try to make the kernel recover the entire thunderbolt controller when plug in. Let’s see if I manage that!

Thanks a lot both

vids

Member

Registered: 2024-12-19

Posts: 17

Re: Interface LAN Ethernet adapter doesn’t shop up [SOLVED]

By the way, I have a Debian 10 system installed on dual boot on this machine. Under Debian, when I unplug and then plug back the Ethernet dongle, Debian recover automatically the entire thunderbolt controller and then ens9 Interface Ethernet back and IP as well.
Would you give me some rough guidance to make it this way on Archlinux? Daemon(s) name, module(s), etc..?

Again, thanks!

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 71,651

Re: Interface LAN Ethernet adapter doesn’t shop up [SOLVED]

Please edit and fix your OP now.
As for the thunderbolt situation, we'll need to see what's going on when you re-plug it (and thus why it doesn't show up)

sudo journalctl -f

yank the dongle, count 5…4…3…2…1 re-plug it and post the output that generates.

You can do the same on the debian system for comparism.
There's only arch and debian, no windows?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

vids

Member

Registered: 2024-12-19

Posts: 17

Re: Interface LAN Ethernet adapter doesn’t shop up [SOLVED]

Thank for helping!

Yes only arch and debian, somethimes some other systems just to have a look at them
I wiped out windows from my life many years ago

What do you mean by “edit and fix your OP now.”?

Below both journals

On debian:

journalctl -f

unplug:

Dec 20 17:21:09 debian kernel: pciehp 0000:06:03.0:pcie204: Slot(3-2): Link Down
Dec 20 17:21:09 debian kernel: thunderbolt 0000:07:00.0: resetting error on 0:1.
Dec 20 17:21:09 debian kernel: thunderbolt 0000:07:00.0: 0:1: unplugged
Dec 20 17:21:10 debian kernel: tg3 0000:0a:00.0: tg3_abort_hw timed out, TX_MODE_ENABLE will not clear MAC_TX_MODE=ffffffff
Dec 20 17:21:10 debian dhclient[913]: receive_packet failed on ens9: Network is down
Dec 20 17:21:10 debian avahi-daemon[571]: Interface ens9.IPv6 no longer relevant for mDNS.
Dec 20 17:21:10 debian avahi-daemon[571]: Leaving mDNS multicast group on interface ens9.IPv6 with address 2a01:cb15:8468:6f00:8501:43cc:735a:d456.
Dec 20 17:21:10 debian avahi-daemon[571]: Interface ens9.IPv4 no longer relevant for mDNS.
Dec 20 17:21:10 debian avahi-daemon[571]: Leaving mDNS multicast group on interface ens9.IPv4 with address 192.168.1.15.
Dec 20 17:21:10 debian avahi-daemon[571]: Withdrawing address record for 2a01:cb15:8468:6f00:8501:43cc:735a:d456 on ens9.
Dec 20 17:21:10 debian avahi-daemon[571]: Withdrawing address record for 192.168.1.15 on ens9.
Dec 20 17:21:10 debian NetworkManager[586]: <info>  [1734711670.7123] device (ens9): state change: activated -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Dec 20 17:21:10 debian kernel: pciehp 0000:09:00.0:pcie204: pcie_do_write_cmd: no response from device
Dec 20 17:21:10 debian NetworkManager[586]: <info>  [1734711670.7450] dhcp4 (ens9): canceled DHCP transaction, DHCP client pid 913
Dec 20 17:21:10 debian NetworkManager[586]: <info>  [1734711670.7451] dhcp4 (ens9): state changed bound -> done
Dec 20 17:21:10 debian NetworkManager[586]: <info>  [1734711670.7458] dhcp6 (ens9): canceled DHCP transaction
Dec 20 17:21:10 debian kernel: pci_bus 0000:0a: busn_res: [bus 0a] is released
Dec 20 17:21:10 debian kernel: pci_bus 0000:09: busn_res: [bus 09-0a] is released
Dec 20 17:21:10 debian kernel: acpiphp: Slot [1] unregistered
Dec 20 17:21:10 debian kernel: acpiphp: Slot [2-1] unregistered
Dec 20 17:21:10 debian kernel: acpiphp: Slot [3-1] unregistered
Dec 20 17:21:10 debian kernel: acpiphp: Slot [4-1] unregistered
Dec 20 17:21:10 debian kernel: acpiphp: Slot [5-1] unregistered
Dec 20 17:21:10 debian NetworkManager[586]: <info>  [1734711670.7768] policy: set 'Livebox-A980' (wlp3s0) as default for IPv4 routing and DNS
Dec 20 17:21:10 debian NetworkManager[586]: <info>  [1734711670.7780] policy: set 'Livebox-A980' (wlp3s0) as default for IPv6 routing and DNS
Dec 20 17:21:10 debian dbus-daemon[581]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=586 comm="/usr/sbin/NetworkManager --no-daemon ")
Dec 20 17:21:10 debian systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec 20 17:21:10 debian dbus-daemon[581]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 20 17:21:10 debian systemd[1]: Started Network Manager Script Dispatcher Service.
Dec 20 17:21:10 debian nm-dispatcher[1939]: req:1 'down' [ens9]: new request (2 scripts)
Dec 20 17:21:10 debian nm-dispatcher[1939]: req:1 'down' [ens9]: start running ordered scripts...
Dec 20 17:21:11 debian clock-applet[1358]: Failed to get METAR data: 308 Permanent Redirect.
Dec 20 17:21:12 debian clock-applet[1358]: Failed to get METAR data: 308 Permanent Redirect.
Dec 20 17:21:12 debian ntpd[722]: Deleting interface #4 ens9, 192.168.1.15#123, interface stats: received=91, sent=100, dropped=2, active_time=130 secs
Dec 20 17:21:12 debian ntpd[722]: 82.65.248.56 local addr 192.168.1.15 -> <null>
Dec 20 17:21:12 debian ntpd[722]: 82.64.100.180 local addr 192.168.1.15 -> <null>
Dec 20 17:21:12 debian ntpd[722]: 5.39.80.51 local addr 192.168.1.15 -> <null>
Dec 20 17:21:12 debian ntpd[722]: 51.68.44.27 local addr 192.168.1.15 -> <null>
Dec 20 17:21:12 debian ntpd[722]: 146.59.30.179 local addr 192.168.1.15 -> <null>
Dec 20 17:21:12 debian ntpd[722]: 82.64.81.218 local addr 192.168.1.15 -> <null>
Dec 20 17:21:12 debian ntpd[722]: 185.123.84.51 local addr 192.168.1.15 -> <null>
Dec 20 17:21:12 debian ntpd[722]: 212.227.232.161 local addr 192.168.1.15 -> <null>
Dec 20 17:21:12 debian ntpd[722]: 91.224.149.41 local addr 192.168.1.15 -> <null>
Dec 20 17:21:12 debian ntpd[722]: 51.75.31.74 local addr 192.168.1.15 -> <null>
Dec 20 17:21:12 debian ntpd[722]: 194.57.169.1 local addr 192.168.1.15 -> <null>
Dec 20 17:21:12 debian ntpd[722]: 54.36.61.42 local addr 192.168.1.15 -> <null>
Dec 20 17:21:12 debian ntpd[722]: 51.195.104.188 local addr 192.168.1.15 -> <null>
Dec 20 17:21:12 debian ntpd[722]: Deleting interface #6 ens9, 2a01:cb15:8468:6f00:8501:43cc:735a:d456#123, interface stats: received=29, sent=31, dropped=0, active_time=130 secs
Dec 20 17:21:12 debian ntpd[722]: 2001:41d0:2:52a7::1:4 local addr 2a01:cb15:8468:6f00:8501:43cc:735a:d456 -> <null>
Dec 20 17:21:12 debian ntpd[722]: 2001:41d0:a:268f::123 local addr 2a01:cb15:8468:6f00:8501:43cc:735a:d456 -> <null>
Dec 20 17:21:12 debian ntpd[722]: 2001:41d0:700:49bc:: local addr 2a01:cb15:8468:6f00:8501:43cc:735a:d456 -> <null>
Dec 20 17:21:12 debian ntpd[722]: 2001:41d0:2:c837::123 local addr 2a01:cb15:8468:6f00:8501:43cc:735a:d456 -> <null>
Dec 20 17:21:12 debian ntpd[722]: Deleting interface #7 ens9, fe80::fec2:b5c3:f1be:c954%2#123, interface stats: received=0, sent=0, dropped=0, active_time=130 secs
Dec 20 17:21:21 debian systemd[1]: NetworkManager-dispatcher.service: Succeeded.

re-plug after 5 seconds

Dec 20 17:22:52 debian kernel: thunderbolt 0000:07:00.0: resetting error on 0:1.
Dec 20 17:22:52 debian kernel: thunderbolt 0000:07:00.0: 0:1: hotplug: scanning
Dec 20 17:22:52 debian kernel: thunderbolt 0000:07:00.0: 0:1: is connected, link is up (state: 2)
Dec 20 17:22:52 debian kernel: thunderbolt 0000:07:00.0: current switch config:
Dec 20 17:22:52 debian kernel: thunderbolt 0000:07:00.0:  Switch: 8086:1549 (Revision: 0, TB Version: 1)
Dec 20 17:22:52 debian kernel: thunderbolt 0000:07:00.0:   Max Port Number: 2
Dec 20 17:22:52 debian kernel: thunderbolt 0000:07:00.0:   Config:
Dec 20 17:22:52 debian kernel: thunderbolt 0000:07:00.0:    Upstream Port Number: 0 Depth: 0 Route String: 0x0 Enabled: 0, PlugEventsDelay: 10ms
Dec 20 17:22:52 debian kernel: thunderbolt 0000:07:00.0:    unknown1: 0x0 unknown4: 0x0
Dec 20 17:22:52 debian kernel: thunderbolt 0000:07:00.0: initializing Switch at 0x1 (depth: 1, up port: 1)
Dec 20 17:22:52 debian kernel: thunderbolt 0000:07:00.0: 1: reading drom (length: 0x7b)
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 1: uid: 0x1000204e9b7a0
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0:  Port 0: 8086:1549 (Revision: 0, TB Version: 1, Type: Port (0x1))
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0:   Max hop id (in/out): 7/7
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0:   Max counters: 8
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0:   NFC Credits: 0x700000
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0:  Port 1: 8086:1549 (Revision: 0, TB Version: 1, Type: Port (0x1))
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0:   Max hop id (in/out): 8/8
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0:   Max counters: 4
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0:   NFC Credits: 0x3c00000
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0:  Port 2: 8086:1549 (Revision: 0, TB Version: 1, Type: PCIe (0x100102))
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0:   Max hop id (in/out): 8/8
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0:   Max counters: 2
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0:   NFC Credits: 0x700000
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 1: hotplug: activating pcie devices
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 0:6 <-> 1:2 (PCI): activating
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: activating path from 0:6 to 1:2
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 1:1: Writing hop 1, index 8
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 1:1:  Hop through port 2 to hop 8 (enabled)
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 1:1:   Weight: 1 Priority: 3 Credits: 16 Drop: 0
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 1:1:    Counter enabled: 0 Counter index: 2047
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 1:1:   Flow Control (In/Eg): 1/0 Shared Buffer (In/Eg): 0/0
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 1:1:   Unknown1: 0x0 Unknown2: 0x0 Unknown3: 0x0
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 0:6: Writing hop 0, index 8
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 0:6:  Hop through port 1 to hop 8 (enabled)
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 0:6:   Weight: 1 Priority: 3 Credits: 7 Drop: 0
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 0:6:    Counter enabled: 0 Counter index: 2047
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 0:6:   Flow Control (In/Eg): 1/1 Shared Buffer (In/Eg): 0/0
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 0:6:   Unknown1: 0x0 Unknown2: 0x0 Unknown3: 0x0
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: path activation complete
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: activating path from 1:2 to 0:6
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 0:1: Writing hop 1, index 8
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 0:1:  Hop through port 6 to hop 8 (enabled)
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 0:1:   Weight: 1 Priority: 3 Credits: 16 Drop: 0
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 0:1:    Counter enabled: 0 Counter index: 2047
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 0:1:   Flow Control (In/Eg): 1/0 Shared Buffer (In/Eg): 0/0
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 0:1:   Unknown1: 0x0 Unknown2: 0x0 Unknown3: 0x0
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 1:2: Writing hop 0, index 8
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 1:2:  Hop through port 1 to hop 8 (enabled)
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 1:2:   Weight: 1 Priority: 3 Credits: 7 Drop: 0
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 1:2:    Counter enabled: 0 Counter index: 2047
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 1:2:   Flow Control (In/Eg): 1/1 Shared Buffer (In/Eg): 0/0
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: 1:2:   Unknown1: 0x0 Unknown2: 0x0 Unknown3: 0x0
Dec 20 17:22:53 debian kernel: thunderbolt 0000:07:00.0: path activation complete
Dec 20 17:22:53 debian kernel: pciehp 0000:06:03.0:pcie204: Slot(3-2): Card present
Dec 20 17:22:53 debian kernel: pcieport 0000:06:03.0: quirk: waiting for Thunderbolt to reestablish PCI tunnels...
Dec 20 17:22:53 debian kernel: pci 0000:08:00.0: [8086:1549] type 01 class 0x060400
Dec 20 17:22:53 debian kernel: pci 0000:08:00.0: enabling Extended Tags
Dec 20 17:22:53 debian kernel: pci 0000:08:00.0: supports D1 D2
Dec 20 17:22:53 debian kernel: pci 0000:08:00.0: PME# supported from D0 D1 D2 D3hot D3cold
Dec 20 17:22:53 debian kernel: pcieport 0000:06:03.0: ASPM: current common clock configuration is broken, reconfiguring
Dec 20 17:22:53 debian kernel: pci 0000:08:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
Dec 20 17:22:53 debian kernel: acpiphp: Slot [1] registered
Dec 20 17:22:53 debian kernel: acpiphp: Slot [2-1] registered
Dec 20 17:22:53 debian kernel: acpiphp: Slot [3-1] registered
Dec 20 17:22:53 debian kernel: acpiphp: Slot [4-1] registered
Dec 20 17:22:53 debian kernel: acpiphp: Slot [5-1] registered
Dec 20 17:22:53 debian kernel: pci 0000:09:00.0: [8086:1549] type 01 class 0x060400
Dec 20 17:22:53 debian kernel: pci 0000:09:00.0: enabling Extended Tags
Dec 20 17:22:53 debian kernel: pci 0000:09:00.0: supports D1 D2
Dec 20 17:22:53 debian kernel: pci 0000:09:00.0: PME# supported from D0 D1 D2 D3hot D3cold
Dec 20 17:22:53 debian kernel: pci 0000:08:00.0: PCI bridge to [bus 09-38]
Dec 20 17:22:53 debian kernel: pci 0000:08:00.0:   bridge window [io  0x0000-0x0fff]
Dec 20 17:22:53 debian kernel: pci 0000:08:00.0:   bridge window [mem 0x00000000-0x000fffff]
Dec 20 17:22:53 debian kernel: pci 0000:08:00.0:   bridge window [mem 0x00000000-0x000fffff 64bit pref]
Dec 20 17:22:53 debian kernel: pci 0000:09:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
Dec 20 17:22:53 debian kernel: pci 0000:0a:00.0: [14e4:1682] type 00 class 0x020000
Dec 20 17:22:53 debian kernel: pci 0000:0a:00.0: reg 0x10: [mem 0x00000000-0x0000ffff 64bit pref]
Dec 20 17:22:53 debian kernel: pci 0000:0a:00.0: reg 0x18: [mem 0x00000000-0x0000ffff 64bit pref]
Dec 20 17:22:53 debian kernel: pci 0000:0a:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Dec 20 17:22:53 debian kernel: pci 0000:0a:00.0: PME# supported from D0 D3hot D3cold
Dec 20 17:22:53 debian kernel: pci 0000:09:00.0: PCI bridge to [bus 0a-38]
Dec 20 17:22:53 debian kernel: pci 0000:09:00.0:   bridge window [io  0x0000-0x0fff]
Dec 20 17:22:53 debian kernel: pci 0000:09:00.0:   bridge window [mem 0x00000000-0x000fffff]
Dec 20 17:22:53 debian kernel: pci 0000:09:00.0:   bridge window [mem 0x00000000-0x000fffff 64bit pref]
Dec 20 17:22:53 debian kernel: pci_bus 0000:0a: busn_res: [bus 0a-38] end is updated to 38
Dec 20 17:22:53 debian kernel: pci_bus 0000:09: busn_res: [bus 09-38] end is updated to 38
Dec 20 17:22:53 debian kernel: pci 0000:09:00.0: bridge window [mem 0x00100000-0x001fffff 64bit pref] to [bus 0a-38] add_size 200000 add_align 100000
Dec 20 17:22:53 debian kernel: pci 0000:09:00.0: bridge window [mem 0x00100000-0x001fffff] to [bus 0a-38] add_size 200000 add_align 100000
Dec 20 17:22:53 debian kernel: pci 0000:08:00.0: bridge window [mem 0x00100000-0x001fffff 64bit pref] to [bus 09-38] add_size 200000 add_align 100000
Dec 20 17:22:53 debian kernel: pci 0000:08:00.0: bridge window [mem 0x00100000-0x001fffff] to [bus 09-38] add_size 200000 add_align 100000
Dec 20 17:22:53 debian kernel: pci 0000:08:00.0: BAR 14: assigned [mem 0xc1a00000-0xc59fffff]
Dec 20 17:22:53 debian kernel: pci 0000:08:00.0: BAR 15: assigned [mem 0xcda00000-0xd1afffff 64bit pref]
Dec 20 17:22:53 debian kernel: pci 0000:08:00.0: BAR 13: assigned [io  0x4000-0x4fff]
Dec 20 17:22:53 debian kernel: pci 0000:09:00.0: BAR 14: assigned [mem 0xc1a00000-0xc59fffff]
Dec 20 17:22:53 debian kernel: pci 0000:09:00.0: BAR 15: assigned [mem 0xcda00000-0xd1afffff 64bit pref]
Dec 20 17:22:53 debian kernel: pci 0000:09:00.0: BAR 13: assigned [io  0x4000-0x4fff]
Dec 20 17:22:53 debian kernel: pci 0000:0a:00.0: BAR 0: assigned [mem 0xcda00000-0xcda0ffff 64bit pref]
Dec 20 17:22:53 debian kernel: pci 0000:0a:00.0: BAR 2: assigned [mem 0xcda10000-0xcda1ffff 64bit pref]
Dec 20 17:22:53 debian kernel: pci 0000:0a:00.0: BAR 6: assigned [mem 0xc1a00000-0xc1a0ffff pref]
Dec 20 17:22:53 debian kernel: pci 0000:09:00.0: PCI bridge to [bus 0a-38]
Dec 20 17:22:53 debian kernel: pci 0000:09:00.0:   bridge window [io  0x4000-0x4fff]
Dec 20 17:22:53 debian kernel: pci 0000:09:00.0:   bridge window [mem 0xc1a00000-0xc59fffff]
Dec 20 17:22:53 debian kernel: pci 0000:09:00.0:   bridge window [mem 0xcda00000-0xd1afffff 64bit pref]
Dec 20 17:22:53 debian kernel: pci 0000:08:00.0: PCI bridge to [bus 09-38]
Dec 20 17:22:53 debian kernel: pci 0000:08:00.0:   bridge window [io  0x4000-0x4fff]
Dec 20 17:22:53 debian kernel: pci 0000:08:00.0:   bridge window [mem 0xc1a00000-0xc59fffff]
Dec 20 17:22:53 debian kernel: pci 0000:08:00.0:   bridge window [mem 0xcda00000-0xd1afffff 64bit pref]
Dec 20 17:22:53 debian kernel: pcieport 0000:06:03.0: PCI bridge to [bus 08-38]
Dec 20 17:22:53 debian kernel: pcieport 0000:06:03.0:   bridge window [io  0x4000-0x4fff]
Dec 20 17:22:53 debian kernel: pcieport 0000:06:03.0:   bridge window [mem 0xc1a00000-0xc59fffff]
Dec 20 17:22:53 debian kernel: pcieport 0000:06:03.0:   bridge window [mem 0xcda00000-0xd1afffff 64bit pref]
Dec 20 17:22:53 debian kernel: pcieport 0000:08:00.0: enabling device (0000 -> 0003)
Dec 20 17:22:53 debian kernel: pcieport 0000:09:00.0: enabling device (0000 -> 0003)
Dec 20 17:22:53 debian kernel: pciehp 0000:09:00.0:pcie204: Slot #9 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl+ LLActRep+ (with Cmd Compl erratum)
Dec 20 17:22:53 debian kernel: tg3 0000:0a:00.0: enabling device (0000 -> 0002)
Dec 20 17:22:53 debian NetworkManager[586]: <info>  [1734711773.3249] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/4)
Dec 20 17:22:53 debian kernel: tg3 0000:0a:00.0 eth0: Tigon3 [partno(BCM957762) rev 57766000] (PCI Express) MAC address 38:c9:86:14:a0:e9
Dec 20 17:22:53 debian kernel: tg3 0000:0a:00.0 eth0: attached PHY is 57765 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
Dec 20 17:22:53 debian kernel: tg3 0000:0a:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
Dec 20 17:22:53 debian kernel: tg3 0000:0a:00.0 eth0: dma_rwctrl[00000001] dma_mask[64-bit]
Dec 20 17:22:53 debian kernel: tg3 0000:0a:00.0 ens9: renamed from eth0
Dec 20 17:22:53 debian systemd-udevd[2012]: Using default interface naming scheme 'v240'.
Dec 20 17:22:53 debian systemd-udevd[2012]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Dec 20 17:22:53 debian NetworkManager[586]: <info>  [1734711773.3549] device (eth0): interface index 4 renamed iface from 'eth0' to 'ens9'
Dec 20 17:22:53 debian NetworkManager[586]: <info>  [1734711773.3787] device (ens9): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Dec 20 17:22:53 debian systemd-udevd[2019]: Using default interface naming scheme 'v240'.
Dec 20 17:22:53 debian kernel: IPv6: ADDRCONF(NETDEV_UP): ens9: link is not ready
Dec 20 17:22:53 debian kernel: IPv6: ADDRCONF(NETDEV_UP): ens9: link is not ready
Dec 20 17:22:55 debian ModemManager[574]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.4/0000:05:00.0/0000:06:03.0/0000:08:00.0/0000:09:00.0/0000:0a:00.0': not supported by any plugin
Dec 20 17:22:56 debian kernel: tg3 0000:0a:00.0 ens9: Link is up at 1000 Mbps, full duplex
Dec 20 17:22:56 debian kernel: tg3 0000:0a:00.0 ens9: Flow control is on for TX and on for RX
Dec 20 17:22:56 debian kernel: tg3 0000:0a:00.0 ens9: EEE is enabled
Dec 20 17:22:56 debian kernel: IPv6: ADDRCONF(NETDEV_CHANGE): ens9: link becomes ready
Dec 20 17:22:56 debian NetworkManager[586]: <info>  [1734711776.3910] device (ens9): carrier: link connected
Dec 20 17:22:56 debian NetworkManager[586]: <info>  [1734711776.3918] device (ens9): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Dec 20 17:22:56 debian NetworkManager[586]: <info>  [1734711776.3949] policy: auto-activating connection 'GRILL wired' (102ca68c-f912-4962-8c1c-68311fafa4bf)
Dec 20 17:22:56 debian NetworkManager[586]: <info>  [1734711776.3970] device (ens9): Activation: starting connection 'GRILL wired' (102ca68c-f912-4962-8c1c-68311fafa4bf)
Dec 20 17:22:56 debian NetworkManager[586]: <info>  [1734711776.3974] device (ens9): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Dec 20 17:22:56 debian kernel: tg3 0000:0a:00.0 ens9: Link is down
Dec 20 17:22:56 debian NetworkManager[586]: <info>  [1734711776.4809] device (ens9): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Dec 20 17:22:56 debian NetworkManager[586]: <info>  [1734711776.4816] device (ens9): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Dec 20 17:22:56 debian NetworkManager[586]: <info>  [1734711776.4821] dhcp4 (ens9): activation: beginning transaction (timeout in 45 seconds)
Dec 20 17:22:56 debian NetworkManager[586]: <info>  [1734711776.4834] dhcp4 (ens9): dhclient started with pid 2025
Dec 20 17:22:56 debian avahi-daemon[571]: Joining mDNS multicast group on interface ens9.IPv6 with address fe80::fec2:b5c3:f1be:c954.
Dec 20 17:22:56 debian avahi-daemon[571]: New relevant interface ens9.IPv6 for mDNS.
Dec 20 17:22:56 debian avahi-daemon[571]: Registering new address record for fe80::fec2:b5c3:f1be:c954 on ens9.*.
Dec 20 17:22:56 debian dhclient[2025]: DHCPREQUEST for 192.168.1.15 on ens9 to 255.255.255.255 port 67
Dec 20 17:22:56 debian clock-applet[1358]: Failed to get METAR data: 308 Permanent Redirect.
Dec 20 17:22:58 debian clock-applet[1358]: Failed to get METAR data: 308 Permanent Redirect.
Dec 20 17:22:58 debian clock-applet[1358]: Failed to get METAR data: 308 Permanent Redirect.
Dec 20 17:23:00 debian clock-applet[1358]: Failed to get METAR data: 308 Permanent Redirect.
Dec 20 17:23:00 debian NetworkManager[586]: <info>  [1734711780.0737] device (ens9): carrier: link connected
Dec 20 17:23:00 debian kernel: tg3 0000:0a:00.0 ens9: Link is up at 1000 Mbps, full duplex
Dec 20 17:23:00 debian kernel: tg3 0000:0a:00.0 ens9: Flow control is on for TX and on for RX
Dec 20 17:23:00 debian kernel: tg3 0000:0a:00.0 ens9: EEE is enabled
Dec 20 17:23:00 debian NetworkManager[586]: <info>  [1734711780.2353] dhcp6 (ens9): activation: beginning transaction (timeout in 45 seconds)
Dec 20 17:23:00 debian NetworkManager[586]: <info>  [1734711780.2385] dhcp6 (ens9): dhclient started with pid 2032
Dec 20 17:23:00 debian avahi-daemon[571]: Leaving mDNS multicast group on interface ens9.IPv6 with address fe80::fec2:b5c3:f1be:c954.
Dec 20 17:23:00 debian avahi-daemon[571]: Joining mDNS multicast group on interface ens9.IPv6 with address 2a01:cb15:8468:6f00:8501:43cc:735a:d456.
Dec 20 17:23:00 debian avahi-daemon[571]: Registering new address record for 2a01:cb15:8468:6f00:8501:43cc:735a:d456 on ens9.*.
Dec 20 17:23:00 debian avahi-daemon[571]: Withdrawing address record for fe80::fec2:b5c3:f1be:c954 on ens9.
Dec 20 17:23:00 debian NetworkManager[586]: <info>  [1734711780.2695] policy: set 'GRILL wired' (ens9) as default for IPv6 routing and DNS
Dec 20 17:23:00 debian dhclient[2032]: XMT: Info-Request on ens9, interval 940ms.
Dec 20 17:23:00 debian dhclient[2032]: RCV: Reply message on ens9 from fe80::3ab5:c9ff:fe34:a980.
Dec 20 17:23:00 debian NetworkManager[586]: <info>  [1734711780.8580] dhcp6 (ens9):   nameserver '2a01:cb15:8468:6f00:3ab5:c9ff:fe34:a980'
Dec 20 17:23:00 debian NetworkManager[586]: <info>  [1734711780.8581] dhcp6 (ens9):   nameserver 'fe80::3ab5:c9ff:fe34:a980'
Dec 20 17:23:00 debian NetworkManager[586]: <info>  [1734711780.8581] dhcp (ens9):   domain search 'home.'
Dec 20 17:23:00 debian NetworkManager[586]: <info>  [1734711780.8582] dhcp6 (ens9): state changed unknown -> bound
Dec 20 17:23:00 debian dbus-daemon[581]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=586 comm="/usr/sbin/NetworkManager --no-daemon ")
Dec 20 17:23:00 debian NetworkManager[586]: <info>  [1734711780.8625] dhcp6 (ens9): client pid 2032 exited with status 0
Dec 20 17:23:00 debian NetworkManager[586]: <info>  [1734711780.8625] dhcp6 (ens9): state changed bound -> done
Dec 20 17:23:00 debian systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec 20 17:23:00 debian dbus-daemon[581]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 20 17:23:00 debian systemd[1]: Started Network Manager Script Dispatcher Service.
Dec 20 17:23:00 debian nm-dispatcher[2037]: req:1 'dhcp6-change' [ens9]: new request (2 scripts)
Dec 20 17:23:00 debian nm-dispatcher[2037]: req:1 'dhcp6-change' [ens9]: start running ordered scripts...
Dec 20 17:23:01 debian clock-applet[1358]: Failed to get METAR data: 308 Permanent Redirect.
Dec 20 17:23:01 debian NetworkManager[586]: <info>  [1734711781.9502] device (ens9): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Dec 20 17:23:01 debian NetworkManager[586]: <info>  [1734711781.9515] device (ens9): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Dec 20 17:23:01 debian NetworkManager[586]: <info>  [1734711781.9520] device (ens9): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Dec 20 17:23:01 debian NetworkManager[586]: <info>  [1734711781.9699] device (ens9): Activation: successful, device activated.
Dec 20 17:23:01 debian nm-dispatcher[2037]: req:2 'up' [ens9]: new request (2 scripts)
Dec 20 17:23:01 debian nm-dispatcher[2037]: req:2 'up' [ens9]: start running ordered scripts...
Dec 20 17:23:01 debian clock-applet[1358]: Failed to get METAR data: 308 Permanent Redirect.
Dec 20 17:23:03 debian clock-applet[1358]: Failed to get METAR data: 308 Permanent Redirect.
Dec 20 17:23:03 debian ntpd[722]: Listen normally on 11 ens9 [2a01:cb15:8468:6f00:8501:43cc:735a:d456]:123
Dec 20 17:23:03 debian ntpd[722]: Listen normally on 12 ens9 [fe80::fec2:b5c3:f1be:c954%4]:123
Dec 20 17:23:03 debian ntpd[722]: new interface(s) found: waking up resolver
Dec 20 17:23:04 debian dhclient[2025]: DHCPREQUEST for 192.168.1.15 on ens9 to 255.255.255.255 port 67
Dec 20 17:23:04 debian dhclient[2025]: DHCPACK of 192.168.1.15 from 192.168.1.1
Dec 20 17:23:04 debian NetworkManager[586]: <info>  [1734711784.2334] dhcp4 (ens9):   address 192.168.1.15
Dec 20 17:23:04 debian NetworkManager[586]: <info>  [1734711784.2335] dhcp4 (ens9):   plen 24 (255.255.255.0)
Dec 20 17:23:04 debian NetworkManager[586]: <info>  [1734711784.2335] dhcp4 (ens9):   gateway 192.168.1.1
Dec 20 17:23:04 debian NetworkManager[586]: <info>  [1734711784.2335] dhcp4 (ens9):   lease time 86400
Dec 20 17:23:04 debian NetworkManager[586]: <info>  [1734711784.2335] dhcp4 (ens9):   nameserver '192.168.1.1'
Dec 20 17:23:04 debian NetworkManager[586]: <info>  [1734711784.2335] dhcp4 (ens9):   domain name 'home'
Dec 20 17:23:04 debian NetworkManager[586]: <info>  [1734711784.2336] dhcp4 (ens9): state changed unknown -> bound
Dec 20 17:23:04 debian NetworkManager[586]: <info>  [1734711784.2361] policy: set 'GRILL wired' (ens9) as default for IPv4 routing and DNS
Dec 20 17:23:04 debian avahi-daemon[571]: Joining mDNS multicast group on interface ens9.IPv4 with address 192.168.1.15.
Dec 20 17:23:04 debian avahi-daemon[571]: New relevant interface ens9.IPv4 for mDNS.
Dec 20 17:23:04 debian avahi-daemon[571]: Registering new address record for 192.168.1.15 on ens9.IPv4.
Dec 20 17:23:04 debian nm-dispatcher[2037]: req:3 'dhcp4-change' [ens9]: new request (2 scripts)
Dec 20 17:23:04 debian nm-dispatcher[2037]: req:3 'dhcp4-change' [ens9]: start running ordered scripts...
Dec 20 17:23:04 debian dhclient[2025]: bound to 192.168.1.15 -- renewal in 41844 seconds.
Dec 20 17:23:04 debian clock-applet[1358]: Failed to get METAR data: 308 Permanent Redirect.
Dec 20 17:23:05 debian clock-applet[1358]: Failed to get METAR data: 308 Permanent Redirect.
Dec 20 17:23:05 debian ntpd[722]: Listen normally on 13 ens9 192.168.1.15:123
Dec 20 17:23:05 debian ntpd[722]: new interface(s) found: waking up resolver
Dec 20 17:23:14 debian systemd[1]: NetworkManager-dispatcher.service: Succeeded.

Then everything is right (ens9 up and got a LAN IP address)

On arch:

journalctl -f

unplug:

Dec 20 18:02:37 archlinux kernel: pcieport 0000:06:03.0: pciehp: Slot(3-2): Link Down
Dec 20 18:02:37 archlinux NetworkManager[444]: <info>  [1734714157.2055] device (ens9): state change: activated -> unmanaged (reason 'unmanaged-link-not-init', managed-type: 'removed')
Dec 20 18:02:37 archlinux NetworkManager[444]: <info>  [1734714157.2056] dhcp4 (ens9): canceled DHCP transaction
Dec 20 18:02:37 archlinux NetworkManager[444]: <info>  [1734714157.2056] dhcp4 (ens9): activation: beginning transaction (timeout in 45 seconds)
Dec 20 18:02:37 archlinux NetworkManager[444]: <info>  [1734714157.2056] dhcp4 (ens9): state changed no lease
Dec 20 18:02:37 archlinux NetworkManager[444]: <warn>  [1734714157.2058] device (ens9): set-link: failure to reset link negotiation
Dec 20 18:02:37 archlinux NetworkManager[444]: <info>  [1734714157.2066] policy: set 'Livebox-A980' (wlan0) as default for IPv4 routing and DNS
Dec 20 18:02:37 archlinux kernel: thunderbolt 0-1: device disconnected
Dec 20 18:02:37 archlinux systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec 20 18:02:37 archlinux kernel: pcieport 0000:09:00.0: Runtime PM usage count underflow!
Dec 20 18:02:37 archlinux kernel: pci_bus 0000:0a: busn_res: [bus 0a] is released
Dec 20 18:02:37 archlinux kernel: pci_bus 0000:09: busn_res: [bus 09-0a] is released
Dec 20 18:02:37 archlinux kernel: acpiphp: Slot [1] unregistered
Dec 20 18:02:37 archlinux kernel: acpiphp: Slot [2-1] unregistered
Dec 20 18:02:37 archlinux kernel: acpiphp: Slot [3-1] unregistered
Dec 20 18:02:37 archlinux kernel: acpiphp: Slot [4-1] unregistered
Dec 20 18:02:37 archlinux kernel: acpiphp: Slot [5-1] unregistered
Dec 20 18:02:37 archlinux systemd[1]: Started Network Manager Script Dispatcher Service.
Dec 20 18:02:47 archlinux systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

After 5 seconds, re-plug:

Dec 20 18:06:44 archlinux kernel: thunderbolt 0-1: new device found, vendor=0x1 device=0x8003
Dec 20 18:06:44 archlinux kernel: thunderbolt 0-1: Apple, Inc. Thunderbolt to Gigabit Ethernet Adapter

... I am trying to understand something ))

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 71,651

Re: Interface LAN Ethernet adapter doesn’t shop up [SOLVED]

https://wiki.archlinux.org/title/Thunde … registered ?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

vids

Member

Registered: 2024-12-19

Posts: 17

Re: Interface LAN Ethernet adapter doesn’t shop up [SOLVED]

Thanks for the link!
Following it, I executed (as root) manually the a PCI rescan:

echo 1 > /sys/bus/pci/rescan

The ouput of

journalctl -f

shows:

Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:00.0: bridge window [io  0x1000-0x0fff] to [bus 07] add_size 1000
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:00.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 07] add_size 200000 add_align 100000
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:04.0: bridge window [io  0x1000-0x0fff] to [bus 39] add_size 1000
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:04.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 39] add_size 200000 add_align 100000
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:04.0: bridge window [mem 0x00100000-0x000fffff] to [bus 39] add_size 200000 add_align 100000
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:06.0: bridge window [io  0x1000-0x0fff] to [bus 6b] add_size 1000
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:06.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 6b] add_size 200000 add_align 100000
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:06.0: bridge window [mem 0x00100000-0x000fffff] to [bus 6b] add_size 200000 add_align 100000
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:00.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:04.0: BAR 14: no space for [mem size 0x00200000]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:04.0: BAR 14: failed to assign [mem size 0x00200000]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:04.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:04.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:06.0: BAR 14: no space for [mem size 0x00200000]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:06.0: BAR 14: failed to assign [mem size 0x00200000]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:06.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:06.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:00.0: BAR 13: no space for [io  size 0x1000]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:00.0: BAR 13: failed to assign [io  size 0x1000]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:04.0: BAR 13: no space for [io  size 0x1000]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:04.0: BAR 13: failed to assign [io  size 0x1000]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:06.0: BAR 13: no space for [io  size 0x1000]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:06.0: BAR 13: failed to assign [io  size 0x1000]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:06.0: BAR 14: no space for [mem size 0x00200000]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:06.0: BAR 14: failed to assign [mem size 0x00200000]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:06.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:06.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:06.0: BAR 13: no space for [io  size 0x1000]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:06.0: BAR 13: failed to assign [io  size 0x1000]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:04.0: BAR 14: no space for [mem size 0x00200000]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:04.0: BAR 14: failed to assign [mem size 0x00200000]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:04.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:04.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:04.0: BAR 13: no space for [io  size 0x1000]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:04.0: BAR 13: failed to assign [io  size 0x1000]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:00.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:00.0: BAR 13: no space for [io  size 0x1000]
Dec 21 14:09:05 archlinux kernel: pcieport 0000:06:00.0: BAR 13: failed to assign [io  size 0x1000]

It looks to me that, as the point 3.2 of the link underline, I need to Increasing hot-plug bus size and memory.
Am I right?

How do I add

pci=hpbussize=0x33,hpmemsize=256M

to kernel command line to manually set the size?

I can’t figure out that? I don’t ask for the full answer, but just a guidance to do so…
Thanks

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 8,999

Website

Re: Interface LAN Ethernet adapter doesn’t shop up [SOLVED]

https://wiki.archlinux.org/title/Kernel_parameters

---

Jin, Jîyan, Azadî

vids

Member

Registered: 2024-12-19

Posts: 17

Re: Interface LAN Ethernet adapter doesn’t shop up [SOLVED]

Thank again for helping.

I have GRUB boot loader / manager.
I went through the link https://wiki.archlinux.org/title/Kernel_parameters#GRUB
and add the two parameters. I could see them

cat /proc/cmdline 
BOOT_IMAGE=/vmlinuz-linux-lts root=UUID=80382ecf-0b43-42cc-9e54-1118b6f324a0 rw loglevel=3 quiet pci=hpbussize=0x33,hpmemsize=256M

The 2 parameters pci=hpbussize=0x33 and hpmemsize=256M were there as suggested.
But still, nothing worked.

Manually I didn’t succeed.
I removed the 2 parameters.

cat /proc/cmdline 
BOOT_IMAGE=/vmlinuz-linux-lts root=UUID=80382ecf-0b43-42cc-9e54-1118b6f324a0 rw loglevel=3 quiet

Automatically, as suggested  https://wiki.archlinux.org/title/Thunde … any_device

I made a file

/etc/udev/rules.d/99-removable.rules

with the content

ACTION=="add", SUBSYSTEM=="thunderbolt", ATTR{authorized}=="0", ATTR{authorized}="1"

then

sudo udevadm control --reload

Everything works. I am still trying to figure out how to make it “by hand” to order to understand what's under the hood

Thank again!

Last edited by vids (2024-12-21 19:06:09)

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 71,651

Re: Interface LAN Ethernet adapter doesn’t shop up [SOLVED]

https://www.kernel.org/doc/html/v5.4/ad … rbolt.html though this is weird wrt both the reconnect (why isn't this initially a problem) as well as the bridge being completely absent instead of just the ethernet device behind it

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc