[poky] load kernel module at startup

[Gerard van den Bosch]

On 04/21/2011 08:27 AM, Martin Jansa wrote:
> On Wed, Apr 20, 2011 at 08:49:35AM -0700, Darren Hart wrote:
>>
>> 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.
> I've checked Poky 5.0 and according to git log it was there from the
> beginning, so also in Poky 4.0. And also it's inherited by
> linux-yocto(-stable).
>
> if you read classes/kernel.bbclass you'll notice ie:
> module_autoload_ipv6 = "ipv6"
>
> which adds postinst to kernel-module-ipv6 package to "modprobe ipv6" and
> also creates /etc/modutils/ipv6 file with "ipv6" in it to autoload ipv6
> module after reboot.
>
Added the following line to class/kernel.bbclass:
module_autoload_libertas-sdio = "libertas-sdio"
After that I rebuilded the kernel and generated the image but didn't get the modutils file and it didn't autoload either.

Also tried adding the line inside my kernel recipe after "inherit kernel" but that also didn't work.

> similar
> module_conf_bluez = "alias net-pf-31 bluez"
> creates
> /etc/modprobe.d/bluez.conf (or /etc/modutils/bluez.conf for 2.4 kernel)
> with "alias net-pf-31 bluez"
>
> and those files are added to kernel-module-something FILES, so removing
> module removes autoload and config with it properly.
>
> Regards,
This part I don't understand, how can I figure out what to alias?
With some googling I came across some list where it's major number related, but there is no difference between /proc/devices when I have the module loaded or not.

Regards,
Gerard