[opensuse-factory] weak-update mechanism
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
On Sat, 01 Feb 2020 16:30:00 +0100, Michael Hirmke wrote:
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?
weak-updates2 script works only for KMPs, and ignores the custom installed modules. It's the intentional behavior. Takashi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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?
Takashi
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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
Hi Andrei, [...]
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.
never did that, but if it is not too complicated, I'll try. Any HOWTO or something like that? Thx. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday 2020-02-02 12:41, Michael Hirmke wrote:
You could also build KMP.
never did that, but if it is not too complicated, I'll try. Any HOWTO or something like that?
Existing KMP spec files. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 02/02/2020 12.41, Michael Hirmke wrote:
never did that, but if it is not too complicated, I'll try. Any HOWTO or something like that?
check out https://github.com/bmwiedemann/openSUSE/blob/master/packages/v/vhba-kmp/vhba... not very hard.
Hi Bernhard,
On 02/02/2020 12.41, Michael Hirmke wrote:
never did that, but if it is not too complicated, I'll try. Any HOWTO or something like that?
check out https://github.com/bmwiedemann/openSUSE/blob/master/packages/v/vhba-kmp/vhba... kmp.spec#L36
not very hard.
thx a lot. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Andrei Borzenkov -
Bernhard M. Wiedemann -
Jan Engelhardt -
mh＠mike.franken.de -
Takashi Iwai