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:14:38 +0200 [thread overview]
Message-ID: <20160929121438.GA20712@kroah.com> (raw)
In-Reply-To: <CAA2oCOnmP2Y8e586m1rtpyJMhaNLRMJ83U5zOcAHRhfDzz0y4Q@mail.gmail.com>
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Thu, Sep 29, 2016 at 05:31:52PM +0530, 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+?
I do not understand these two sentences.
You said you tried to load a module built for the 4.0.5-rc7 kernel tree
(which is a very odd kernel version number, as I don't recall ever
making a -rc7 for 4.0.5, which was released way back in June of 2015,
but that's another issue...) In order to do that properly, you have to
be running that specific kernel version at the same time so this will
work properly.
So, what specific kernel version are you currently running? Does it
match up with the kernel version of the module you are wanting to load?
(exercise for exactly how to determine both of these is left for the
reader...)
thanks,
greg k-h
next prev parent reply other threads:[~2016-09-29 12:14 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 [this message]
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=20160929121438.GA20712@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 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.