kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: leoliang9@gmail.com (leo liang)
To: kernelnewbies@lists.kernelnewbies.org
Subject: initrd insmod: error inserting '/lib/foo.ko' : -1 operation not permitted
Date: Thu, 14 Jun 2012 11:29:20 -0400	[thread overview]
Message-ID: <CAAseYv24AXFNSF=s+2EQ5ZZawrr4qkSJfPsE+=Ty-3wW8z57RQ@mail.gmail.com> (raw)
In-Reply-To: <CADzUK1Lh5DznkCz4wLS0diy7gaGiJPTimqkkSO_NvZMzeBodsQ@mail.gmail.com>

On Thu, Jun 14, 2012 at 11:16 AM, Autif Khan <autif.mlist@gmail.com> wrote:
> On Thu, Jun 14, 2012 at 10:49 AM, leo liang <leoliang9@gmail.com> wrote:
>> Hi,
>>
>> I am trying to add one driver to my kernel.
>>
>> I have the kernel source and use make all build all the modules and bzImage.
>>
>> I already have initrd.img in my machine. I extract it to a tmp folder.
>
> Are bzImage that you compiled and foo.ko from the initrd.img compiled
> at the same time from the same source?

No, the foo.ko is existing module in the initrd image.

Thank you. I think I got the issue.

I should replace all the modules in the initrd.img with the new build.


>
>> Then I copy the driver module into the lib folder. I edited the init
>> file to insert the module when machine boot. After that, I recreated
>> the initrd.img by cpio and gzip.
>>
>> When machine boot, ?I got "insmod: error inserting '/lib/foo.ko' : -1
>> operation not permitted" error.
>>
>> Did I missed any step? What caused the error?
>>
>> Thanks.
>>
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org
>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      reply	other threads:[~2012-06-14 15:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 14:49 initrd insmod: error inserting '/lib/foo.ko' : -1 operation not permitted leo liang
2012-06-14 15:16 ` Autif Khan
2012-06-14 15:29   ` leo liang [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='CAAseYv24AXFNSF=s+2EQ5ZZawrr4qkSJfPsE+=Ty-3wW8z57RQ@mail.gmail.com' \
    --to=leoliang9@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 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).