Hi there,
I come from here https://www.toradex.com/community/questions/17258/problem-with-usb-wifi-ambicom-wl250n-usb.html?childToView=17266#comment-17266.
I have some confusion regarding modules against modified, “dirty” kernel. In essence, my kernel image has changed and therefore the preloaded modules do not work. Even depmod doesn’t work because ‘uname -r’ now it’s “dirty” which is different from the original version (after copying the /lib/modules4.4… with -dirty, depmod worked with our “dirty” compiled own modules).
My question(s) is: Having only the kernel changed does break the image in certain forms since modules won’t work because kernel versions differ?
Please note, that this is a practical question to avoid Yocto rebuild, we are just looking for a quick way of modifying kernel config (ie. adding a new module) with the original uploaded image.
In this specific case, I’m refering to:
- Some custom modules which we have it’s source code (and therefore easily compiled against any kernel)
- Backtraced modules where its regeneration is not trivial.
- Already installed modules in the image (that, again, should not work with a dirty image?).
Thanks, Álvaro.