(In reply to Stefan Dirsch from comment #12) > The reason the issue doesn't show up on Leap 42.3 is, because there we are > kABI compatible. And without using the fixed tree weak-updates mechanism > wouldn't work. > On TW we're no longer kABI compatible. Ah! Then you wouldn't use/need it in TW at all... > Anyway, I've changed this now. But I haven't done any testing yet. > > Mon Feb 26 16:22:07 UTC 2018 - sndirsch@suse.com > > - rebuilded kernel modules in %trigger of TW packages should go to > the tree against which the kernel module gets builded, not the > hardcoded one during build of the package; introduced > kmp-trigger.sh/kmp-trigger-old.sh script snippets for this based > on kmp-post.sh/kmp-post-old.sh (boo#1082704) > > --> obs://X11:Drivers:Video/nvidia-gfxG04 > > You can do a manually build, if you want (check the README file). I had a look at the kmp.post.sh, looks fine to me. I had just manually compiled the 4.15.2-1-default version of the modules, based on the old TW script, changing $kver and the related directory names (linux-obj -> linux-${kver%$flavor}obj). Went fine, depmod $kver doesn't give errors. Thanks!