You are not logged in.
Today after full system upgrade via pacman -Syu and rebooting my ethernet has stopped working. After some investigation I figured out that ip link doesn't show en... interface like before. Accordingly dmesg says that dhcpcd cannot load interfaces. I've used expac to see which packages were updated and have guessed that the problem is caused by the new kernel version which doesn't load my ethernet module. I've downgraded linux-5.1.6.arch1-1-x86_64.pkg.tar.xz to linux-5.1.5.arch1-2-x86_64.pkg.tar.xz and virtualbox-host-modules-arch-6.0.8-8-x86_64.pkg.tar.xz to virtualbox-host-modules-arch-6.0.8-7-x86_64.pkg.tar.xz. After reboot the problem has gone. Now ip link shows UP enp0s20u1 interface. So the question is... is it a kernel bug and should I ignore this version in pacman.conf?
Last edited by Arthas (2019-06-03 10:18:40)
Offline
Before assuming a kernel bug, verify that you are actually loading the updated kernel, outputs of
pacman -Q linux
uname -a
should match, if they don't you should ensure that your boot partition/ESP is mounted when the kernel runs an update/mkinitcpio is ran. If that isn't it, you might want to post the output of
dmesg
as that might provide a pointer as to where the failure is.
Offline
I have just verified that both pacman -Q linux and uname -a after full system upgrade show 5.1.6.arch1-1. After downgrading -- 5.1.5.arch1-2. Exact error message of dmesg when trying to run dhcpcd is "no interfaces have a carrier".
Last edited by Arthas (2019-06-03 13:07:34)
Offline
Offline
It looks relevant. Thanks.
Offline
The issue has gone with linux 5.1.7.arch1-1 and virtualbox-host-modules-arch 6.0.8-9. Thanks for the answers.
Last edited by Arthas (2019-06-05 09:32:33)
Offline
Glad to hear, please mark as [SOLVED] by editing and appending to the title in your first post.
Offline