I am on gnome and the stable release of Endeavour. I’ve been using it for a few months and have very few complaints, having tried Mint as soon as I switched from Windows 10 and not liking it. However, there is a recurrent error that has been bugging me. When I plug in my ethernet cable, it seems to work, and I “yay’d” the r8168 driver DKMS, but I get the error “connection failed activation of network connection failed.” Below is the code I found for the NetworkManager session, but I don’t know how to interpret or fix the problem.
$ NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: disabled)
Active: active (running) since Tue 2024-08-06 16:00:32 CDT; 2min 11s ago
Docs: man:NetworkManager(8)
Main PID: 921 (NetworkManager)
Tasks: 4 (limit: 18946)
Memory: 16.3M (peak: 16.9M)
CPU: 333ms
CGroup: /system.slice/NetworkManager.service
└─921 /usr/bin/NetworkManager --no-daemon
Aug 06 16:02:07 kieran-blade NetworkManager[921]: <info> [1722978127.3529] device (enp2s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Aug 06 16:02:07 kieran-blade NetworkManager[921]: <info> [1722978127.3861] dhcp4 (enp2s0): canceled DHCP transaction
Aug 06 16:02:07 kieran-blade NetworkManager[921]: <info> [1722978127.3862] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Aug 06 16:02:07 kieran-blade NetworkManager[921]: <info> [1722978127.3862] dhcp4 (enp2s0): state changed no lease
Aug 06 16:02:07 kieran-blade NetworkManager[921]: <info> [1722978127.3980] policy: auto-activating connection 'Wired connection 1' (872a2858-ff57-373a-9cce-f3840efec153)
Aug 06 16:02:07 kieran-blade NetworkManager[921]: <info> [1722978127.3990] device (enp2s0): Activation: starting connection 'Wired connection 1' (872a2858-ff57-373a-9cce-f3840efec153)
Aug 06 16:02:07 kieran-blade NetworkManager[921]: <info> [1722978127.4000] device (enp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 06 16:02:07 kieran-blade NetworkManager[921]: <info> [1722978127.4007] device (enp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 06 16:02:07 kieran-blade NetworkManager[921]: <info> [1722978127.5242] device (enp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Aug 06 16:02:07 kieran-blade NetworkManager[921]: <info> [1722978127.5249] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
If you have a 8168 compatible ethernet card, most of them work with the driver in kernel. So you wouldn’t need to install any r8168 package from AUR.
If this is the case, uninstall the r8168 package, reboot, and test.
Hello, Thank you for the quick response! This community is part of why I chose EOS!
The same error is occuring, but the wired connection holds on for longer in a buffer state before disconnecting.
In addition, you still have the r8168 driver and not the kernel driver (r8169). Did you try uninstalling r8168 (and reboot)? Not sure based on your posts.
Yeah I was a bit confused about this myself. The r8169 kernel module is mentioned, but the driver is stated as r8168. I wasn’t sure if that was the expected behaviour.
Perhaps share the output of these two command @kieran : (1st shows status of modules in the kernel, 2nd shows installed packages, both filtered for results containing r816)
Blacklisting, in the context of kernel modules, is a mechanism to prevent the kernel module from loading. This could be useful if, for example, … if loading that module causes problems: for instance there may be two kernel modules that try to control the same piece of hardware, and loading them together would result in a conflict.
I’ve not had to blacklist a module before, but if I’ve understood the Wiki’s instructions, you’d create a file under /etc/modprobe.d/ that contains the blacklist command for the module in question.
This will create such a file (including a comment so you can recall what it’s doing):
sudo printf '# Do not load r8169 module on boot\nblacklist r8169' > /etc/modprobe.d/r816.conf
Perhaps verify that it’s made that file by visiting /etc/modprobe.d/ and is in line with the Wiki article. Then reboot and see how you go? After rebooting:
