From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: insmod failing to insert a simple module
Date: Thu, 29 Sep 2016 14:37:03 +0200 [thread overview]
Message-ID: <20160929123703.GB21716@kroah.com> (raw)
In-Reply-To: <CAA2oCO=Uv9V=4zA057Sjn9wHqQ-Ue4BF-1eac6Hj2BH9=HiPvQ@mail.gmail.com>
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
prev parent reply other threads:[~2016-09-29 12:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 9:56 insmod failing to insert a simple module Madhu K
2016-09-29 10:30 ` Pasquier, Thomas
2016-09-29 10:43 ` Madhu K
2016-09-29 11:24 ` Greg KH
2016-09-29 12:01 ` Madhu K
2016-09-29 12:07 ` Quentin Lambert
2016-09-29 12:10 ` AW:insmod " Johannes Thoma
2016-09-29 12:24 ` insmod " Madhu K
2016-09-29 12:30 ` Alexander Kapshuk
2016-09-29 12:31 ` François
2016-09-29 14:30 ` Valdis.Kletnieks at vt.edu
2016-09-29 12:14 ` Greg KH
2016-09-29 12:27 ` Madhu K
2016-09-29 12:37 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160929123703.GB21716@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).