All of lore.kernel.org
 help / color / mirror / Atom feed
From: dhylands@gmail.com (Dave Hylands)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How make modprobe find my kernel module?
Date: Fri, 2 Sep 2011 08:18:59 -0700	[thread overview]
Message-ID: <CABi1daEzP__eLrRWMw+iHZnWPiyruF=xhET+2RYN678jqqq0tg@mail.gmail.com> (raw)
In-Reply-To: <CAOXENUgZ+17oBjAY8DKwx3GDrz06_VVdru8-c4BXpsVR4ND06Q@mail.gmail.com>

Hi Parmenides,

On Fri, Sep 2, 2011 at 8:12 AM, Parmenides <mobile.parmenides@gmail.com> wrote:
> Hi,
>
> ? ?I have write a 'hello, world!' module which is in a directory
> rather than the kernel source tree. I compiled it by:
>
> ? ? ? ? ? ? ? ? ? ? ? make -C /usr/src/linux SUBDIRS=$PWD modules
>
> and installed it by:
>
> ? ? ? ? ? ? ? ? ? ? ? make -C /usr/src/linux SUBDIRS=$PWD modules_install
>
> I find it was installed at /lib/modules/2.6.34/extra. Then, I invoked
>
> ? ? ? ? ? ? ? ? ? ? ? ?modprobe hello.ko
>
> to load this module, but get a message:
>
> ? ? ? ? ? ? ? ? ? ? ? ?FATAL: Module hello.ko not found.
>
> It seems that my module is not in the modprobe's search path. Is that
> true? If so, how can I configure its search path?

modprobe uses modules.dep to translate module names into module
locations. You can either manually add an entry into that file - found
in /lib/modules/$(uname -r)

or you can rerun depmod on your device (if its available).

Alternatively, you can insmod your module bu providing a fully
qualified path to the .ko file. insmod doesn't do any dependancy
checking, so it just fails if you need symbols from some other module
which isn't loaded.

-- 
Dave Hylands
Shuswap, BC, Canada
http://www.davehylands.com

  reply	other threads:[~2011-09-02 15:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-02 15:12 How make modprobe find my kernel module? Parmenides
2011-09-02 15:18 ` Dave Hylands [this message]
2011-09-03  3:33   ` Mulyadi Santosa

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='CABi1daEzP__eLrRWMw+iHZnWPiyruF=xhET+2RYN678jqqq0tg@mail.gmail.com' \
    --to=dhylands@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.