02.02.2020 12:47, Michael Hirmke пишет:
Hi Takashi,
[...]
After installing a new kernel with the same flavour:
- create /lib/modules/<kver2>/weak-updates/ - link /lib/modules/<kver>/updates/<mpath>/ to /lib/modules/<kver2>/weak-updates/ - run depmod -a
So one doesn't have to recompile the module, if the second kernel's flavour matches the flavour of the first one, which is the case for most of the openSUSE Leap kernel updates within a given Leap version.
This works as expected, when doing it manually.
What I don't understand:
As far as I've read, it shouldn't be necessary to do the second part manually - it should happen automagically when installing a new kernel, if part one has been executed properly. But this doesn't happen here. It has to be done manually. Running the script weak-updates2 from the suse-module-tools also doesn't seem to work - otherwise I don't understand the purpose and/or the parameters correctly.
What am I missing here?
weak-updates2 script works only for KMPs, and ignores the custom installed modules. It's the intentional behavior.
Thx for your answer. So doing it manually is the correct/only way to create the appropriate weak-updates links for my self compiled modules? Not automatism?
You could also build KMP. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org