From: Darren Hart <dvhart@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: poky <poky@yoctoproject.org>
Subject: Re: load kernel module at startup
Date: Wed, 20 Apr 2011 08:49:35 -0700 [thread overview]
Message-ID: <4DAF008F.70706@linux.intel.com> (raw)
In-Reply-To: <20110420153153.GK5675@jama.jama.net>
On 04/20/2011 08:31 AM, Martin Jansa wrote:
> On Wed, Apr 20, 2011 at 08:25:38AM -0700, Darren Hart wrote:
>>
>>
>> On 04/11/2011 02:38 AM, Gerard van den Bosch wrote:
>>> Hello,
>>>
>>> I would like to modprobe my wireless driver kernel module at startup
>>> automatically.
>>>
>>> This works when I generate a rootfs and then boot up the first time so
>>> the modules file gets generated and then I can manually add the kernel
>>> module in that file and then reboot.
>>>
>>> When I look in the manpage of update-modules it states that a config
>>> file should be added in /etc/modutils but that directory is not in my
>>> rootfs.
>>>
>>> So I was wondering what I have to do to get /etc/modutils directory or
>>> an other way to get the kernel module loaded at startup.
>>>
>>> I am using the Poky 4.0 Laverne release.
>>
>> I believe you can just add the name of the module to:
>>
>> /etc/modules
>>
>> Can you try that?
>
> module_autoload_module_name to do that, is not supported in Poky?
I am not familiar with this technique.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-04-20 15:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 9:38 load kernel module at startup Gerard van den Bosch
2011-04-20 15:25 ` Darren Hart
2011-04-20 15:31 ` Martin Jansa
2011-04-20 15:49 ` Darren Hart [this message]
2011-04-21 6:27 ` Martin Jansa
2011-04-21 9:23 ` Gerard van den Bosch
2011-04-21 22:02 ` Darren Hart
2011-04-22 6:19 ` Gerard van den Bosch
2011-04-21 6:14 ` Gerard van den Bosch
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=4DAF008F.70706@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=martin.jansa@gmail.com \
--cc=poky@yoctoproject.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