kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: me@tobin.cc (Tobin C. Harding)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Invalid module format
Date: Sat, 24 Feb 2018 10:29:33 +1100	[thread overview]
Message-ID: <20180223232933.GB6364@eros> (raw)
In-Reply-To: <CAB3L5ox_R1HQNpgjQXGNoGVq=5WRvKaaiDd_nBRH30sOnBbnWg@mail.gmail.com>

On Thu, Feb 22, 2018 at 02:42:23AM +0530, Srishti Sharma wrote:
> Hello,
> 
> While trying to load a module from the linux-next branch

Do you mean from linux-next tree or from a branch called linux-next in
some other tree?  (Not that it matters that much :)

>, I get the error
> that the module format is invalid, this was because the kernel I compiled
> was different from the kernel I was trying to load the module into, so I
> installed the kernel from the same source as the module, and it booted for
> only once right after the installation. When I try to boot into the same
> kernel, my system reboots. What should I do so that I am able to boot into
> it everytime ?

What are you trying to achieve?  Are you doing testing on linux-next or
do you just want to use the module?  If you just want to use the module
you could build the module for the current running kernel instead of
rebuilding the kernel.  Copy the module someplace and write a new
makefile same as you would if you were developing your own [test]
modules.

(For the record I happened to be trying to learn about linux-next myself
this morning and built a kernel that just goes into a reboot loop
without even getting to the grub menu.  It boots in a VM though so now
I'm playing with the cofig.)

Hope this helps,
Tobin.

  parent reply	other threads:[~2018-02-23 23:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21 21:12 Invalid module format Srishti Sharma
2018-02-21 21:24 ` valdis.kletnieks at vt.edu
     [not found] ` <BY1PR0101MB101393E19DAD4C4C584BD89BCDCE0@BY1PR0101MB1013.prod.exchangelabs.com>
     [not found]   ` <CAB3L5ozA_VUAJiypue2RDN-_kuC7FnS+DaYPO7cOfTKb9dBLAw@mail.gmail.com>
2018-02-21 21:39     ` Alejandro D?az
2018-02-23 23:29 ` Tobin C. Harding [this message]
2018-02-24  3:06   ` valdis.kletnieks at vt.edu
2018-02-25  2:34     ` Tobin C. Harding
2018-02-25  5:04       ` valdis.kletnieks at vt.edu
2018-02-25  7:29         ` Tobin C. Harding
2018-02-24  5:06   ` Srishti Sharma
  -- strict thread matches above, loose matches on Subject: below --
2018-02-24  5:15 Alex Arvelaez
2018-02-24  5:17 ` Srishti Sharma

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=20180223232933.GB6364@eros \
    --to=me@tobin.cc \
    --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).