[Solved] Failed wired connection after system update

LyCC · 2020-10-21 20:14:57

Hi guys,

I just updated my Arch installation, and I no longer have an ipv4 address. dhcpcd failed to acquire ipv4, so I changed to dhclint but this doesn't work
either. I have a wireless USB stick, which fortunately works.

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether b4:2e:99:92:e1:67 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::f4a1:9b38:3a48:fe22/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: wlp2s0f0u10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 38:6b:1c:82:62:4b brd ff:ff:ff:ff:ff:ff
    inet6 fe80::b534:64f9:be13:bd4c/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

Oct 21 23:19:10 ArchPC NetworkManager[602]: <info>  [1603311550.8795] device (wlp2s0f0u10): supplicant interface state: interface_disabled -> disconnected
Oct 21 23:19:25 ArchPC NetworkManager[602]: <info>  [1603311565.1092] device (enp5s0): Activation: starting connection 'Wired connection 1' (05e6b43d-750f-3339-895e-4611d8680693)
Oct 21 23:19:25 ArchPC NetworkManager[602]: <info>  [1603311565.1093] audit: op="connection-activate" uuid="05e6b43d-750f-3339-895e-4611d8680693" name="Wired connection 1" pid=969 uid=1000 result="success"
Oct 21 23:19:25 ArchPC NetworkManager[602]: <info>  [1603311565.1094] device (enp5s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 21 23:19:25 ArchPC NetworkManager[602]: <info>  [1603311565.1100] manager: NetworkManager state is now CONNECTING
Oct 21 23:19:25 ArchPC NetworkManager[602]: <info>  [1603311565.1103] device (enp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 21 23:19:25 ArchPC NetworkManager[602]: <info>  [1603311565.1108] device (enp5s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 21 23:19:25 ArchPC NetworkManager[602]: <info>  [1603311565.1112] dhcp4 (enp5s0): activation: beginning transaction (timeout in 45 seconds)
Oct 21 23:20:10 ArchPC NetworkManager[602]: <warn>  [1603311610.8426] dhcp4 (enp5s0): request timed out
Oct 21 23:20:10 ArchPC NetworkManager[602]: <info>  [1603311610.8427] dhcp4 (enp5s0): state changed unknown -> timeout
Oct 21 23:20:10 ArchPC NetworkManager[602]: <info>  [1603311610.8427] device (enp5s0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Oct 21 23:20:10 ArchPC NetworkManager[602]: <info>  [1603311610.8433] manager: NetworkManager state is now DISCONNECTED
Oct 21 23:20:10 ArchPC NetworkManager[602]: <warn>  [1603311610.8443] device (enp5s0): Activation: failed for connection 'Wired connection 1'
Oct 21 23:20:10 ArchPC NetworkManager[602]: <info>  [1603311610.8447] device (enp5s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 21 23:20:13 ArchPC NetworkManager[602]: <info>  [1603311613.9760] dhcp4 (enp5s0): canceled DHCP transaction
Oct 21 23:20:13 ArchPC NetworkManager[602]: <info>  [1603311613.9760] dhcp4 (enp5s0): state changed timeout -> done

Where do I start troubleshooting in such case?

Thank you.

Last edited by LyCC (2020-10-21 23:55:45)

seth · 2020-10-21 21:06:16

The log shows an attempt by the internal NM dhcp client.
What's the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

and also see https://wiki.archlinux.org/index.php/Ne … HCP_client

LyCC · 2020-10-21 21:13:22

Thank you for your answer, here's the output

dbus-org.freedesktop.NetworkManager.service | system
dbus-org.freedesktop.nm-dispatcher.service | system
dirmngr.socket                           | sockets.target.wants
display-manager.service                  | system
getty@tty1.service                       | getty.target.wants
gpg-agent-browser.socket                 | sockets.target.wants
gpg-agent-extra.socket                   | sockets.target.wants
gpg-agent.socket                         | sockets.target.wants
gpg-agent-ssh.socket                     | sockets.target.wants
httpd.service                            | multi-user.target.wants
libvirtd.service                         | multi-user.target.wants
lm_sensors.service                       | multi-user.target.wants
NetworkManager.service                   | multi-user.target.wants
nmb.service                              | multi-user.target.wants
ntpd.service                             | multi-user.target.wants
org.cups.cupsd.path                      | multi-user.target.wants
org.cups.cupsd.service                   | printer.target.wants
org.cups.cupsd.socket                    | sockets.target.wants
p11-kit-server.socket                    | sockets.target.wants
php-fpm.service                          | multi-user.target.wants
pipewire.socket                          | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
rc-local.service                         | multi-user.target.wants
remote-fs.target                         | multi-user.target.wants
smb.service                              | multi-user.target.wants
sshd.service                             | multi-user.target.wants
virtlockd.socket                         | sockets.target.wants
virtlogd.socket                          | sockets.target.wants
xdg-user-dirs-update.service             | default.target.wants

Edit: Tried it with a static IP, it doesn't work either.

Last edited by LyCC (2020-10-21 21:25:59)

seth · 2020-10-21 21:27:28

Neither dhcpcd nor dhclient are enabled, but NM is - in case you did: do not try to run dhcpcd/dhclient or a manual static assignment next to NM. The various network configuring approaches are all mutually exclusive.

Stop the NetworkManager.service and try to connect w/

dhclient -4 -v -d enp5s0

(dhclient will not fork this way)
If this fails, post the output of dhclient and a complete system journal of the current boot (please do not use the "-x" option, no matter what wiki or manpage say - it's just meaningless clutter)

LyCC · 2020-10-21 22:03:38

Stopped NM, and it failed ...

Listening on LPF/enp5s0/b4:2e:99:92:e1:67
Sending on   LPF/enp5s0/b4:2e:99:92:e1:67
Sending on   Socket/fallback
DHCPDISCOVER on enp5s0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on enp5s0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on enp5s0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on enp5s0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on enp5s0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on enp5s0 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

The boot log is 153k (after a reboot), I am cutting the network related lines only (The full log is here: https://paste.ubuntu.com/p/QvGmmYKzJ8/ (expires in 1 week))

Oct 22 00:54:18 ArchPC kernel: libphy: r8169: probed
Oct 22 00:54:18 ArchPC kernel: r8169 0000:05:00.0 eth0: RTL8168g/8111g, b4:2e:99:92:e1:67, XID 4c0, IRQ 78
Oct 22 00:54:18 ArchPC kernel: r8169 0000:05:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
Oct 22 00:54:19 ArchPC kernel: r8169 0000:05:00.0 enp5s0: renamed from eth0
Oct 22 00:54:20 ArchPC NetworkManager[596]: <info>  [1603317260.6092] manager: (enp5s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Oct 22 00:54:20 ArchPC NetworkManager[596]: <info>  [1603317260.6098] device (enp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct 22 00:54:20 ArchPC kernel: Generic FE-GE Realtek PHY r8169-500:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-500:00, irq=IGNORE)
Oct 22 00:54:20 ArchPC kernel: r8169 0000:05:00.0 enp5s0: Link is Down
Oct 22 00:54:23 ArchPC kernel: r8169 0000:05:00.0 enp5s0: Link is Up - 1Gbps/Full - flow control off
Oct 22 00:54:35 ArchPC kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp5s0: link becomes ready
Oct 22 00:54:35 ArchPC NetworkManager[596]: <info>  [1603317275.2187] device (enp5s0): carrier: link connected
Oct 22 00:54:35 ArchPC NetworkManager[596]: <info>  [1603317275.2195] device (enp5s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Oct 22 00:54:35 ArchPC NetworkManager[596]: <info>  [1603317275.2212] device (enp5s0): Activation: starting connection 'Wired connection 1' (05e6b43d-750f-3339-895e-4611d8680693)
Oct 22 00:54:35 ArchPC NetworkManager[596]: <info>  [1603317275.2214] device (enp5s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 22 00:54:35 ArchPC NetworkManager[596]: <info>  [1603317275.2221] device (enp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 22 00:54:35 ArchPC NetworkManager[596]: <info>  [1603317275.2225] device (enp5s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 22 00:54:35 ArchPC NetworkManager[596]: <info>  [1603317275.2228] dhcp4 (enp5s0): activation: beginning transaction (timeout in 45 seconds)
Oct 22 00:54:37 ArchPC ntpd[614]: unable to create socket on enp5s0 (4) for fe80::b62e:99ff:fe92:e167%2#123
Oct 22 00:54:40 ArchPC ntpd[614]: Listen normally on 5 enp5s0 [fe80::b62e:99ff:fe92:e167%2]:123
Oct 22 00:54:40 ArchPC kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
Oct 22 00:54:40 ArchPC kernel: Modules linked in: tun bridge stp llc eeprom nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) snd_hda_codec_realtek jfs fuse snd_hda_codec_generic r8188eu(C) snd_hda_codec_hdmi ledtrig_audio edac_mce_amd lib80211 snd_hda_intel snd_intel_dspcfg kvm_amd snd_hda_codec wmi_bmof kvm cfg80211 snd_hda_core drm_kms_helper irqbypass snd_hwdep snd_pcm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cec aesni_intel r8169 rc_core realtek snd_timer crypto_simd mdio_devres syscopyarea of_mdio ccp cryptd snd sysfillrect fixed_phy sp5100_tco glue_helper sysimgblt joydev input_leds mousedev rfkill rapl pcspkr k10temp i2c_piix4 fb_sys_fops rng_core libphy soundcore wmi pinctrl_amd gpio_amdpt evdev mac_hid acpi_cpufreq vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) drm sg crypto_user agpgart ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 hid_generic usbhid hid uas usb_storage crc32c_intel xhci_pci xhci_pci_renesas sr_mod cdrom xhci_hcd
Oct 22 00:54:40 ArchPC kernel: r8169 0000:05:00.0 enp5s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).

Thank you again.

Edit: this may be related?

Oct 22 00:54:40 ArchPC kernel: ------------[ cut here ]------------
Oct 22 00:54:40 ArchPC kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
Oct 22 00:54:40 ArchPC kernel: WARNING: CPU: 4 PID: 0 at net/sched/sch_generic.c:442 dev_watchdog+0x26d/0x280
Oct 22 00:54:40 ArchPC kernel: Modules linked in: tun bridge stp llc eeprom nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) snd_hda_codec_realtek jfs fuse snd_hda_codec_generic r8188eu(C) snd_hda_codec_hdmi ledtrig_audio edac_mce_amd lib80211 snd_hda_intel snd_intel_dspcfg kvm_amd snd_hda_codec wmi_bmof kvm cfg80211 snd_hda_core drm_kms_helper irqbypass snd_hwdep snd_pcm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cec aesni_intel r8169 rc_core realtek snd_timer crypto_simd mdio_devres syscopyarea of_mdio ccp cryptd snd sysfillrect fixed_phy sp5100_tco glue_helper sysimgblt joydev input_leds mousedev rfkill rapl pcspkr k10temp i2c_piix4 fb_sys_fops rng_core libphy soundcore wmi pinctrl_amd gpio_amdpt evdev mac_hid acpi_cpufreq vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) drm sg crypto_user agpgart ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 hid_generic usbhid hid uas usb_storage crc32c_intel xhci_pci xhci_pci_renesas sr_mod cdrom xhci_hcd
Oct 22 00:54:40 ArchPC kernel: CPU: 4 PID: 0 Comm: swapper/4 Tainted: P         C OE     5.9.1-arch1-1 #1
Oct 22 00:54:40 ArchPC kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F50 11/27/2019
Oct 22 00:54:40 ArchPC kernel: RIP: 0010:dev_watchdog+0x26d/0x280
Oct 22 00:54:40 ArchPC kernel: Code: 08 47 74 ff eb 85 4c 89 f7 c6 05 fd 34 08 01 01 e8 38 9a fa ff 44 89 e9 4c 89 f6 48 c7 c7 68 05 a0 96 48 89 c2 e8 29 23 7d ff <0f> 0b e9 63 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 90 0f 1f 44
Oct 22 00:54:40 ArchPC kernel: RSP: 0018:ffffb03000330e90 EFLAGS: 00010286
Oct 22 00:54:40 ArchPC kernel: RAX: 0000000000000000 RBX: ffff985d86cb4400 RCX: 0000000000000000
Oct 22 00:54:40 ArchPC kernel: RDX: 0000000000000103 RSI: ffffffff96953f7f RDI: 00000000ffffffff
Oct 22 00:54:40 ArchPC kernel: RBP: ffff985d85c883dc R08: 0000000000000431 R09: 0000000000000001
Oct 22 00:54:40 ArchPC kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff985d85c88480
Oct 22 00:54:40 ArchPC kernel: R13: 0000000000000000 R14: ffff985d85c88000 R15: ffff985d86cb4480
Oct 22 00:54:40 ArchPC kernel: FS:  0000000000000000(0000) GS:ffff985d8e900000(0000) knlGS:0000000000000000
Oct 22 00:54:40 ArchPC kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 22 00:54:40 ArchPC kernel: CR2: 000055ae16430000 CR3: 00000003ef016000 CR4: 00000000003506e0
Oct 22 00:54:40 ArchPC kernel: Call Trace:
Oct 22 00:54:40 ArchPC kernel:  <IRQ>
Oct 22 00:54:40 ArchPC kernel:  ? pfifo_fast_init+0x110/0x110
Oct 22 00:54:40 ArchPC kernel:  ? pfifo_fast_init+0x110/0x110
Oct 22 00:54:40 ArchPC kernel:  call_timer_fn+0x2d/0x160
Oct 22 00:54:40 ArchPC kernel:  ? pfifo_fast_init+0x110/0x110
Oct 22 00:54:40 ArchPC kernel:  __run_timers+0x1ec/0x280
Oct 22 00:54:40 ArchPC kernel:  run_timer_softirq+0x2b/0x50
Oct 22 00:54:40 ArchPC kernel:  __do_softirq+0xff/0x344
Oct 22 00:54:40 ArchPC kernel:  asm_call_irq_on_stack+0xf/0x20
Oct 22 00:54:40 ArchPC kernel:  </IRQ>
Oct 22 00:54:40 ArchPC kernel:  do_softirq_own_stack+0x5d/0x80
Oct 22 00:54:40 ArchPC kernel:  irq_exit_rcu+0xd8/0x120
Oct 22 00:54:40 ArchPC kernel:  sysvec_apic_timer_interrupt+0x47/0xe0
Oct 22 00:54:40 ArchPC kernel:  asm_sysvec_apic_timer_interrupt+0x12/0x20
Oct 22 00:54:40 ArchPC kernel: RIP: 0010:cpuidle_enter_state+0xcc/0x3c0
Oct 22 00:54:40 ArchPC kernel: Code: 8a d8 20 6a e8 15 9b 8c ff 49 89 c7 0f 1f 44 00 00 31 ff e8 56 a9 8c ff 80 7c 24 0f 00 0f 85 11 02 00 00 fb 66 0f 1f 44 00 00 <45> 85 e4 0f 88 53 01 00 00 49 63 d4 4c 2b 3c 24 48 8d 04 52 48 8d
Oct 22 00:54:40 ArchPC kernel: RSP: 0018:ffffb0300015fea0 EFLAGS: 00000246
Oct 22 00:54:40 ArchPC kernel: RAX: ffff985d8e900000 RBX: ffff985d8c30d400 RCX: 000000000000001f
Oct 22 00:54:40 ArchPC kernel: RDX: 0000000000000000 RSI: ffffffff96953f7f RDI: ffffffff9695e5c9
Oct 22 00:54:40 ArchPC kernel: RBP: ffffffff96ed8f80 R08: 000000065d007133 R09: 0000000000000018
Oct 22 00:54:40 ArchPC kernel: R10: 000000000001c0ae R11: 000000000000ebd1 R12: 0000000000000002
Oct 22 00:54:40 ArchPC kernel: R13: ffffffff96ed9068 R14: 0000000000000002 R15: 000000065d007133
Oct 22 00:54:40 ArchPC kernel:  cpuidle_enter+0x29/0x40
Oct 22 00:54:40 ArchPC kernel:  do_idle+0x1ed/0x280
Oct 22 00:54:40 ArchPC kernel:  cpu_startup_entry+0x19/0x20
Oct 22 00:54:40 ArchPC kernel:  secondary_startup_64+0xb6/0xc0
Oct 22 00:54:40 ArchPC kernel: ---[ end trace b383d907fdd3bccc ]---
Oct 22 00:54:40 ArchPC kernel: r8169 0000:05:00.0 enp5s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).

Last edited by LyCC (2020-10-21 22:14:24)

Zod · 2020-10-21 22:10:58

Do you have jumbo frames enabled?

If so, how long?

LyCC · 2020-10-21 22:19:47

Zod wrote:

Do you have jumbo frames enabled?
If so, how long?

You mean for how long did I have it enabled? I think I installed this OS somewhere in 2011 (power of rolling release) ... I really haven't touched the network config since (or maybe
when I switched to systemd). It pretty much worked since, this is the 3rd PC and the 4th HDD under it (I just copied the system to the next one and went on).

If you are asking it's size, it autoconfigures to :

eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]

Last edited by LyCC (2020-10-21 22:20:59)

seth · 2020-10-21 22:21:16

Try https://www.archlinux.org/packages/comm … _64/r8168/

As for jumbo frames, according to the OP, the MTU is at the default of 1500 (so "no")

LyCC · 2020-10-21 22:33:07

Thanks for the r8168 idea, unfortunately no change.

ethtool -i enp5s0

driver: r8168
version: 8.048.03-NAPI
firmware-version: 
expansion-rom-version: 
bus-info: 0000:05:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no

Last edited by LyCC (2020-10-21 22:37:43)

Zod · 2020-10-21 22:35:16

Yeah, I see that now, it seems the realtek drivers announce it as a possible feature.

eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]

LyCC · 2020-10-21 23:17:14

... I installed the LTS kernel (also uninstalled the r8168 package), boot it, and still the same, this means it's not a driver issue?

Linux ArchPC 5.4.72-1-lts #1 SMP Sat, 17 Oct 2020 13:30:57 +0000 x86_64 GNU/Linux

LyCC · 2020-10-21 23:43:16

Ok, so, If i unplug the PC, wait the famous 10 seconds, boot, it's working. However, it is working only until restart, then it stops working again, same issue.
PS: if it's not working, it doesn't work under Windows either, until I hit "Diagnose", which resets the card (and ladies and gentlemen, we made history here - for the first time in my life, I seen something actually being fixed by the MS troubleshooter)
Differential diagnosis:
Restarting windows a couple of times -> adapter still works.
Restarting linux with LTS kernel a couple of times, adapter still works.
Booting with the new kernel, restart -> adapter doesn't work any more (not with the LTS kernel, not in windows), until PC unplug (this will be very annoying).

I am buying a beer for anyone who can give a logical explanation for this...

Edit: solved. I reinstalled the r8168, powered off the PC, not it seems to be ok, 3 restarts and the adapter still works (great 6 hours spent).

driver: r8168
version: 8.048.03-NAPI

Thank you seth for you help!

Btw, the kernel driver,

firmware-version: rtl8168g-2_0.0.1 02/06/13

, is this real? from 2013?

Last edited by LyCC (2020-10-22 00:01:51)

solskog · 2020-10-22 00:09:20

LyCC journal wrote:

Oct 22 00:54:18 ArchPC kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=c886e2d0-109f-41b3-b813-694d5c7feba7 rw loglevel=3 quiet mitigations=off
...
Oct 22 00:54:18 ArchPC kernel: pci 0000:00:00.2: AMD-Vi: IOMMU performance counters supported
Oct 22 00:54:18 ArchPC kernel: pci 0000:00:01.0: Adding to iommu group 0
Oct 22 00:54:18 ArchPC kernel: pci 0000:00:01.1: Adding to iommu group 0
...
Oct 22 00:54:18 ArchPC systemd[1]: Created slice Virtual Machine and Container Slice.
...
Oct 22 00:54:20 ArchPC systemd[1]: Starting Virtual Machine and Container Registration Service...

Looks like you have AMD Virtualization enabled but without kernel parameter been set? amd_iommu=on
Maybe also iommu=pt parameter. This will prevent Linux from touching devices which cannot be passed through.
This maybe not related, but is this really safe on a VM host? "mitigations=off"

Oct 22 00:54:35 ArchPC libvirtd[713]: direct firewall backend requested, but /usr/bin/ebtables is not available: No such file or directory
Oct 22 00:54:35 ArchPC libvirtd[713]: internal error: Failed to initialize a valid firewall backendOct 22 00:54:35 ArchPC audit: ANOM_PROMISCUOUS dev=virbr0-nic prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
Oct 22 00:54:35 ArchPC kernel: virbr0: port 1(virbr0-nic) entered blocking state
Oct 22 00:54:35 ArchPC kernel: virbr0: port 1(virbr0-nic) entered disabled state
Oct 22 00:54:35 ArchPC kernel: device virbr0-nic entered promiscuous mode
Oct 22 00:54:35 ArchPC audit: ANOM_PROMISCUOUS dev=virbr0-nic prom=0 old_prom=256 auid=4294967295 uid=0 gid=0 ses=4294967295
Oct 22 00:54:35 ArchPC kernel: device virbr0-nic left promiscuous mode
Oct 22 00:54:35 ArchPC kernel: virbr0: port 1(virbr0-nic) entered disabled state
Oct 22 00:54:35 ArchPC systemd-udevd[836]: virbr0-nic: Failed to get link config: No such device

If libvirt also involved in network assignment/bridge? Because this actually failed before NetworkManager reaching out.

Use archiso liveUSB is a better way to test if your network is working or not, change kernel or OS is not necessary.

Last edited by solskog (2020-10-22 00:43:17)

LyCC · 2020-10-22 12:33:20

Thank you for your answer, I will test this issue with an USB installation when I will have some free time.

Arch Linux

#1 2020-10-21 20:14:57

[Solved] Failed wired connection after system update

#2 2020-10-21 21:06:16

Re: [Solved] Failed wired connection after system update

#3 2020-10-21 21:13:22

Re: [Solved] Failed wired connection after system update

#4 2020-10-21 21:27:28

Re: [Solved] Failed wired connection after system update

#5 2020-10-21 22:03:38

Re: [Solved] Failed wired connection after system update

#6 2020-10-21 22:10:58

Re: [Solved] Failed wired connection after system update

#7 2020-10-21 22:19:47

Re: [Solved] Failed wired connection after system update

#8 2020-10-21 22:21:16

Re: [Solved] Failed wired connection after system update

#9 2020-10-21 22:33:07

Re: [Solved] Failed wired connection after system update

#10 2020-10-21 22:35:16

Re: [Solved] Failed wired connection after system update

#11 2020-10-21 23:17:14

Re: [Solved] Failed wired connection after system update

#12 2020-10-21 23:43:16

Re: [Solved] Failed wired connection after system update

#13 2020-10-22 00:09:20

Re: [Solved] Failed wired connection after system update

#14 2020-10-22 12:33:20

Re: [Solved] Failed wired connection after system update

Board footer