All of lore.kernel.org
 help / color / mirror / Atom feed
From: lambert.quentin@gmail.com (Quentin Lambert)
To: kernelnewbies@lists.kernelnewbies.org
Subject: insmod failing to insert a simple module
Date: Thu, 29 Sep 2016 14:07:25 +0200	[thread overview]
Message-ID: <7580c01d-91a7-7fa0-5112-112f54ebf56b@gmail.com> (raw)
In-Reply-To: <CAA2oCOnmP2Y8e586m1rtpyJMhaNLRMJ83U5zOcAHRhfDzz0y4Q@mail.gmail.com>



On 29/09/2016 14:01, Madhu K wrote:
> No it is not the requirement, when I downloaded the source 
> "4.0.5-rc7+" was latest. Is there any problem with 4.0.5-rc7+?
What Greg is telling you is that for you to be able to insmod a module 
you need to be running the same kernel version as the source code 
against which you have compiled your module.

If you are running kernel 4.0.0, you won't be able to insmod your module 
that has been compiled using the "4.0.5-rc7+" source code.

Quentin
>
> Thanks,
> Madhu
>
> On Thu, Sep 29, 2016 at 4:54 PM, Greg KH <greg@kroah.com 
> <mailto:greg@kroah.com>> wrote:
>
>     On Thu, Sep 29, 2016 at 03:26:49PM +0530, Madhu K wrote:
>     > Hi All,
>     >
>     > While inserting a kernel module, insmod is failing with
>     following error.
>     >
>     >
>     > insmod: error inserting 'page_walk.ko': Invalid module format.
>     >
>     > I verified the modinfo of "page_walk.ko" it is showing version
>     magic as : 4.0.5_rc7+ SMP mod_unload modversions 686
>
>     Is the kernel version that you are currently running also 4.0.5-rc7+?
>     That is a requirement :)
>
>     > what does "mod_unload" mean here?
>
>     You have enabled the ability to unload modules.
>
>     Also look in your kernel log for any specific error messages when
>     trying
>     to load a module, it usually will be more verbous than the insmod
>     program itself.
>
>     good luck,
>
>     greg k-h
>
>
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2016-09-29 12:07 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 [this message]
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

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=7580c01d-91a7-7fa0-5112-112f54ebf56b@gmail.com \
    --to=lambert.quentin@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.