Just to understand how this work and found out released kmod does not always install in my own build even the kernel version is exact. Just want to know why some of the kernel modules will install, some not ? Can help to kill my curoisity?
show us your kernel+vermagic... and the kernel+vermagic for the official repo... this is no guarantee... but unless you provide proof these match... this discussion is comparing apples with wood.
if you ever verify they match the next step... is to verify your git checkout hash...
prove these match and then your question becomes valid... if they don't match you have your answer... like @eduperez says;
I dont know why you asked me to prove kernel+vermagic when I said kernel version is exact. I missed the fact that there is vermagic which you should have guess this.
vermagic is that 45ed73a630a4bec3328fc33ca1c2e1c2
and is a hash calculated from
all compilation options related to kernel, and
names of all kernel modules enabled in the kernel compilation .config (either =y or =m)
In practice, any change to the config makes the modules officially incompatible.
It is possible to compile individual modules later for a firmware if you have also compiled the static SDK and use that SDK for the kmod compilation (like eduperez does not mwlwifi driver kmods here in the forum)
It is practically impossible to compile a new kernel or full firmware and then try to use older kmods with opkg. The vermagic will differ