unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Hebi Li <lihebi.com@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: Looking for Guix alternative to /lib/modules/$(uname -r)/build
Date: Wed, 11 Sep 2019 22:21:14 -0500	[thread overview]
Message-ID: <CAKOCGPWmLSG=v3fnG=gpyY3WYAsGiuEeBXmHHq9KPQAHT_CFfw@mail.gmail.com> (raw)
In-Reply-To: <87y2yvpbd5.fsf@elephly.net>

Thanks, I've managed to use linux-module-build-system to build the
module, and I got the output
/gnu/store/...my-module-0.0.1/extra/xxx.ko. I can load the module via
insmod with the full path.

Now I want to load the module via modprobe, instead of specifying the
full path. For that, I need to place the .ko file in the modprobe
search directory. I notice that in
gnu/packages/patches/kmod-module-directory.patch, the modprobe is
modified to honor the LINUX_MODULE_DIRECTORY env variable, which is
set to /run/booted-system/kernel/lib/modules. However,
/run/booted-system/kernel/ is symlink to
/gnu/store/9rq5y83c9y1kplv6r7a2vksswyjzs57k-linux-libre-5.2.13, which
is read-only.

Further, it seems that modprobe can only scan exactly *one* directory,
be it from the LINUX_MODULE_DIRECTORY env variable, or the original
hard coded "/lib/modules/"

So my question is, is it possible to let modprobe be aware of my
external module?

Hebi

      reply	other threads:[~2019-09-12  3:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-11  6:25 Looking for Guix alternative to /lib/modules/$(uname -r)/build Hebi Li
2019-09-11  6:59 ` Ricardo Wurmus
2019-09-12  3:21   ` Hebi Li [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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKOCGPWmLSG=v3fnG=gpyY3WYAsGiuEeBXmHHq9KPQAHT_CFfw@mail.gmail.com' \
    --to=lihebi.com@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=rekado@elephly.net \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).