Conversation
Installing KMPs separately from the kernel they are built and using weak-updates for all kernel versions - including the one the module was originally built for. The weak-modules2 script already incorporates logic to create weak updates for only one module version (i.e. the latest one) per kernel version. This way - together with the use of a versioned installation directory using INSTALL_MOD_DIR during module installation it is possible to overcome the one KMP update per kernel version limitation (see discussion in jsc#PED-12049). Signed-off-by: Egbert Eich <eich@suse.com>
e4t
force-pushed
the
sles12-sp7-alternative_kmp_path
branch
from
306a2cc to
89b8779
Compare
|
Why does the /kmp/ need to be added? Shouldn't modules installed in /usr/lib/modules/nvdia-G04-175.25 already get scanned for modules? If not why not? |
|
Duplicate of #123 |
With |
2 participants
This is experimental code that adds /lib/modules/kmp(/) als alternativen module install path. The advantage of this path is that the KMP is not directly installed into the kernel it was built with. Instead weak-updates2 should take care of making this available for this kernel as well.
This ensures there are not multiple versions of the same module available for a single kernel.