You are not logged in.

#1 2022-05-21 19:23:49

god-anpu
Member
Registered: 2022-05-17
Posts: 3

r8168 fails to properly "migrate" to new kernel version

Hi everyone,

tl;dr
Is it intentional that one should manually reinstall r8168 after kernel upgrade (which was not necessary before)?

pkg versions:
r8168-8.050.00-7
linux-5.17.9-arch1-1 (or linux-5.17.8-arch1-1), but probably not specific to the kernel version

I just had the weirdest problem fixing networking on two of my computers: Both have on board NICs that run with the r8168 module (and did so for years), kernel upgrades were never a problem.

Anyways when upgrading the kernel to linux-5.17.9-arch1-1 or linux-5.17.8-arch1 and rebooting the network was down. To be more exact no /dev/eth0 was created and "dmesg | grep r8168" showed no module was loaded. After searching around a bit it became apparent that /usr/lib/modules/5.17.7-arch2-1/extramodules/r8168.ko.xz existed (owned by r8168), but apparently was not in a path where the new kernel would find it. Either copying the file to /usr/lib/modules/5.17.9-arch1-1/extramodules/r8168.ko.xz or reinstalling r8168 (which automatically puts the file in the directory tree of  the currently installed kernel version) fixed the issue.

So is that intended behaviour? Am I missing something - like adding a hook to mkinitcpio or whatnot? How would one go best about reinstalling a package after upgrading another one (other than some hacked together script)?

Last edited by god-anpu (2022-05-21 19:38:19)

Offline

#2 2022-05-21 19:50:09

seth
Member
Registered: 2012-09-03
Posts: 50,016

Re: r8168 fails to properly "migrate" to new kernel version

Is it intentional that one should manually reinstall r8168 after kernel upgrade

If you just updated the kernel instead of running a complete system udpate: yes - for all out-of-tree modules.

If you ran into this after an "pacman -Syu" and a subsequent "pacman -Sy r8168" fixed it, chances are that you were using an out of sync mirror, try https://archlinux.org/packages/community/any/reflector/ and/or where super-unlucky to otherwise receive the new kernel but not the r8168 module (which was updated 1 minute later)

Check your pacman log on what happened.

Online

#3 2022-05-21 20:21:05

god-anpu
Member
Registered: 2022-05-17
Posts: 3

Re: r8168 fails to properly "migrate" to new kernel version

seth wrote:

Is it intentional that one should manually reinstall r8168 after kernel upgrade

If you just updated the kernel instead of running a complete system udpate: yes - for all out-of-tree modules.

I was not aware of that.

seth wrote:

If you ran into this after an "pacman -Syu" and a subsequent "pacman -Sy r8168" fixed it, chances are that you were using an out of sync mirror, try https://archlinux.org/packages/community/any/reflector/ and/or where super-unlucky to otherwise receive the new kernel but not the r8168 module (which was updated 1 minute later)

The issue seems to be something else because I ran into this problem after "pacman -Syu" (technically a "paru -Syu" but that should not change anything), but a "pacman -S r8168" (again technically used paru) fixed it - please note the missing "y", so without any updating of the repositories. On a side note: the r8168 version still has not changed.

Offline

#4 2022-05-21 20:26:05

seth
Member
Registered: 2012-09-03
Posts: 50,016

Re: r8168 fails to properly "migrate" to new kernel version

Then there would have been some issue during the update.
I'll just blame paru tongue  but you may check the pacman log whether you missed some errors from the "paru -Syu"

Online

Board footer

Powered by FluxBB