From mboxrd@z Thu Jan 1 00:00:00 1970 From: greg@kroah.com (Greg KH) Date: Thu, 29 Sep 2016 14:37:03 +0200 Subject: insmod failing to insert a simple module In-Reply-To: References: <20160929112440.GA16400@kroah.com> <20160929121438.GA20712@kroah.com> Message-ID: <20160929123703.GB21716@kroah.com> To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org On Thu, Sep 29, 2016 at 05:57:47PM +0530, Madhu K wrote: > Hi, > > I am runnig 4.0.5_rc7 kernel and I built the module for same kernel. > > uname -a output : > > Linux BLR-PCUB-01141 4.5.0-rc7 #2 SMP Wed Mar 23 15:51:13 IST 2016 x86_64 > x86_64 x86_64 GNU/Linux "4.5.0-rc7" is different han "4.0.5_rc7" :) > > And my modinfo of my module is : > > icense:??????? Dual BSD/GPL > srcversion:???? 1D16256F51E63BC3632B65B > depends:??????? > vermagic:?????? 4.5.0-rc7+ SMP mod_unload modversions 686 That's the issue right there, the module was built for "4.5.0-rc7+" and you are running "4.5.0-rc7". Notice the "+" character? That's the problem here... Run the same kernel version as your module and all should be fine. Note, the "+" means that there are commits past the last tag in your tree (or that it has been modified in some way since that tag). So there is a real difference here, which is why insmod is failing. If you really think you can ignore this, you can always tell insmod to ignore the kernel version check. Read the man page for all of the details there. good luck! greg k-h