Custom Kernel module: the old version keeps getting called

[JCOneTwoThree]

I loaded a kernel module from the official Linux Github repo, compiled and placed it within /lib/modules/.........

 

Now if I make changes to this kernel module, and recompile it and reboot, the old one still gets called.

 

If I rmmod and modprobe however, the new module gets loaded.

 

The module I'm talking about is qcaspi.

 

This issue doesn't occur on RPi so I'm thinking it could be an Armbian issue or an oversight by me.

 

Any help please?

[Igor]

49 minutes ago, JCOneTwoThree said:

I loaded a kernel module from the official Linux Github repo, compiled and placed it within /lib/modules/.........

 

Now if I make changes to this kernel module, and recompile it and reboot, the old one still gets called.

 

Did you tell kernel to use this module you added by hand? Not sure why Armbian kernel would act differently? Perhaps we have better security enabled by default ... not sure, would need to investigate, but that is not possible just like that. Use official build method https://docs.armbian.com/Developer-Guide_Build-Preparation/

 

49 minutes ago, JCOneTwoThree said:

Any help please?

Your turn.

https://forum.armbian.com/forum/54-help-wanted/

 

[JCOneTwoThree]

Thanks Igor.

 

I managed to find this command which basically solved this issue:

 

update-initramfs -v -u

 

It seems that for debian based OS the modules get stored in archive. The above basically updates the archive.

 

20 hours ago, Igor said:

 

Did you tell kernel to use this module you added by hand? Not sure why Armbian kernel would act differently? Perhaps we have better security enabled by default ... not sure, would need to investigate, but that is not possible just like that. Use official build method https://docs.armbian.com/Developer-Guide_Build-Preparation/

 

Your turn.

https://forum.armbian.com/forum/54-help-wanted/