Hi *, can anyone please explain, how one can use the automatic weak-update mechanism for installing extra modules? What I understood so far (if this is correct): - compile your module - create /lib/modules/<kver>/updates/<mpath> - copy your module to /lib/modules/<kver>/updates/<mpath>/ - run depmod -a 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? TIA. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org