http://bugzilla.opensuse.org/show_bug.cgi?id=1082704 http://bugzilla.opensuse.org/show_bug.cgi?id=1082704#c17 --- Comment #17 from Peter Sütterlin <P.Suetterlin@royac.iac.es> --- Puh, took a while to master obs... So I built a package now, nvidia-gfxG04-kmp-default-390.25_k4.15.5_1-0.x86_64.rpm I installed it on my system, which still runs 4.15.4-1, and it correctly compiled the modules for this kernel and installed them in /lib/modules/4.15.4-1-default/updates/. No error from depmod. So far, so good! However, it looks like the weak-updates script has messed up things with the older kernel that is still installed (4.15.2-1). That one did have (proper) modules in /lib/modules/4.15.2-1-default/updates/. After installing the new package, this directory had been deleted, and instead a weak-updates/updates directory had been created, with links to /lib/modules/4.15.5-1-default/updates/ (i.e., the ones that came with the rpm). Furthermore, those modules have been deleted, too (don't know whether by the install, or by the weak-update script - probably the latter), so the links go to nowhere :( As you mentioned yourself, the weak-updates mechanism relies on kABI stability, which is not given for Tumbleweed. It probably should not be used at all? (and while at it - would there be a reason not to use a 'make -j ' for compiling the modules in the trigger script?) -- You are receiving this mail because: You are on the CC list for the bug.