From: Alex Kost <alezost@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: modprobe on guix
Date: Wed, 25 Mar 2015 21:22:38 +0300 [thread overview]
Message-ID: <87lhilrl75.fsf@gmail.com> (raw)
In-Reply-To: <87lhilp73u.fsf@netris.org> (Mark H. Weaver's message of "Wed, 25 Mar 2015 08:57:41 -0400")
Mark H Weaver (2015-03-25 15:57 +0300) wrote:
> 白い熊@相撲道 <guix-devel_gnu.org@sumou.com> writes:
>> How do I load a kernel module in Guix?
>
> It should just work, assuming that LINUX_MODULE_DIRECTORY is set to
> /run/booted-system/kernel/lib/modules and that you are using 'modprobe'
> from Guix. We set LINUX_MODULE_DIRECTORY in /etc/profile on GuixSD.
>
>> I can insmod the concrete .ko file from the /gnu/store/... kernel
>> directory, however this is impractical for scripts etc, since the
>> directory will change with system reconfigure.
>
> For insmod, use /run/booted-system/kernel/lib/modules.
>
>> However 'sudo modprobe ...' doesn't load the kernel module...
>
> It works for me. Can you try the following command:
>
> sudo bash -c "echo $LINUX_MODULE_DIRECTORY"
>
> and verify that it prints "/run/booted-system/kernel/lib/modules"?
I'm on GuixSD (and LINUX_MODULE_DIRECTORY is set properly) but:
$ sudo modprobe ...
doesn't load a module for me, however when I try it under root:
# modprobe ...
it works. No idea why that happens.
--
Alex
next prev parent reply other threads:[~2015-03-25 18:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 22:39 modprobe on guix 白い熊@相撲道
2015-03-25 12:57 ` Mark H Weaver
2015-03-25 18:22 ` Alex Kost [this message]
2015-03-25 21:01 ` Ludovic Courtès
2015-03-26 13:06 ` Alex Kost
-- strict thread matches above, loose matches on Subject: below --
2015-09-20 18:55 Petter
2015-09-21 16:10 ` Ludovic Courtès
2015-09-22 8:32 Petter
2015-09-22 12:45 ` Ludovic Courtès
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=87lhilrl75.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.