Proper Use of KERNEL_MODULE_AUTOLOAD variable

Proper Use of KERNEL_MODULE_AUTOLOAD variable

[Ken Sloat]

Hello,

I have an out of tree kernel module which I want autoloaded at startup
on my system. Looking at the Yocto project manual, I see that one way
I can do this is to add the module name to the KERNEL_MODULE_AUTOLOAD
variable within my custom module recipe.

What I have found is that the module-split class is indeed generating
the "/etc/modules-load.d/mymodule.conf" file, however this file is not
actually being installed. To be more precise it is appearing in the
"package" directory (i.e.
tmp/work/**/mymodule/package/etc/modules-load.d/mymodule.conf) but not
within the "image" directory (nor in my final rootfs).

Is there something I'm missing in the usage of KERNEL_MODULE_AUTOLOAD?
Is the intention for this variable I add extra steps to manually
install this file in my recipe? FYI I'm using Morty.

Thanks,
Ken Sloat

Re: Proper Use of KERNEL_MODULE_AUTOLOAD variable

[Bruce Ashfield]

On 2019-02-02 9:59 p.m., Ken Sloat wrote:
> Hello,
> 
> I have an out of tree kernel module which I want autoloaded at startup
> on my system. Looking at the Yocto project manual, I see that one way
> I can do this is to add the module name to the KERNEL_MODULE_AUTOLOAD
> variable within my custom module recipe.
> 
> What I have found is that the module-split class is indeed generating
> the "/etc/modules-load.d/mymodule.conf" file, however this file is not
> actually being installed. To be more precise it is appearing in the
> "package" directory (i.e.
> tmp/work/**/mymodule/package/etc/modules-load.d/mymodule.conf) but not
> within the "image" directory (nor in my final rootfs).
> 
> Is there something I'm missing in the usage of KERNEL_MODULE_AUTOLOAD?
> Is the intention for this variable I add extra steps to manually
> install this file in my recipe? FYI I'm using Morty.

Can you provide your recipe ? It would make suggestions easier. For
example, my first question is: Is the module being installed to your
image via IMAGE_INSTALL, or some other similar variable ?

Bruce

> 
> Thanks,
> Ken Sloat
> 

Re: Proper Use of KERNEL_MODULE_AUTOLOAD variable

[Ken Sloat]

On Sat, Feb 2, 2019 at 10:03 PM Bruce Ashfield
<bruce.ashfield@windriver.com> wrote:
>
> On 2019-02-02 9:59 p.m., Ken Sloat wrote:
> > Hello,
> >
> > I have an out of tree kernel module which I want autoloaded at startup
> > on my system. Looking at the Yocto project manual, I see that one way
> > I can do this is to add the module name to the KERNEL_MODULE_AUTOLOAD
> > variable within my custom module recipe.
> >
> > What I have found is that the module-split class is indeed generating
> > the "/etc/modules-load.d/mymodule.conf" file, however this file is not
> > actually being installed. To be more precise it is appearing in the
> > "package" directory (i.e.
> > tmp/work/**/mymodule/package/etc/modules-load.d/mymodule.conf) but not
> > within the "image" directory (nor in my final rootfs).
> >
> > Is there something I'm missing in the usage of KERNEL_MODULE_AUTOLOAD?
> > Is the intention for this variable I add extra steps to manually
> > install this file in my recipe? FYI I'm using Morty.
>
> Can you provide your recipe ? It would make suggestions easier. For
> example, my first question is: Is the module being installed to your
> image via IMAGE_INSTALL, or some other similar variable ?
>
> Bruce
>
> >
> > Thanks,
> > Ken Sloat
> >
>

Hi Bruce,

Thanks for your quick reply. Yes the module is being installed via
image_install. Module is installed but generated conf file is not. See
recipe below:

require mymodule.inc

inherit module kernel-module-split

DEPENDS = "virtual/kernel"

EXTRA_OEMAKE_append = " \
    KERNELDIR=${STAGING_KERNEL_DIR} \
    "

MAKE_TARGETS = "module"

MODULE_NAME = "mymodule"

PKG_${PN} = "kernel-module-${MODULE_NAME}"

module_do_install() {
    install -d ${D}/lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME}
    install -m 0644 ${MODULE_NAME}.ko \
    ${D}/lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME}/${MODULE_NAME}.ko
}

FILES_${PN} = " \
    /lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME} \
"

KERNEL_MODULE_AUTOLOAD += "${MODULE_NAME}"

Re: Proper Use of KERNEL_MODULE_AUTOLOAD variable

[Bruce Ashfield]

On 2019-02-02 10:16 p.m., Ken Sloat wrote:
> On Sat, Feb 2, 2019 at 10:03 PM Bruce Ashfield
> <bruce.ashfield@windriver.com> wrote:
>>
>> On 2019-02-02 9:59 p.m., Ken Sloat wrote:
>>> Hello,
>>>
>>> I have an out of tree kernel module which I want autoloaded at startup
>>> on my system. Looking at the Yocto project manual, I see that one way
>>> I can do this is to add the module name to the KERNEL_MODULE_AUTOLOAD
>>> variable within my custom module recipe.
>>>
>>> What I have found is that the module-split class is indeed generating
>>> the "/etc/modules-load.d/mymodule.conf" file, however this file is not
>>> actually being installed. To be more precise it is appearing in the
>>> "package" directory (i.e.
>>> tmp/work/**/mymodule/package/etc/modules-load.d/mymodule.conf) but not
>>> within the "image" directory (nor in my final rootfs).
>>>
>>> Is there something I'm missing in the usage of KERNEL_MODULE_AUTOLOAD?
>>> Is the intention for this variable I add extra steps to manually
>>> install this file in my recipe? FYI I'm using Morty.
>>
>> Can you provide your recipe ? It would make suggestions easier. For
>> example, my first question is: Is the module being installed to your
>> image via IMAGE_INSTALL, or some other similar variable ?
>>
>> Bruce
>>
>>>
>>> Thanks,
>>> Ken Sloat
>>>
>>
> 
> Hi Bruce,
> 
> Thanks for your quick reply. Yes the module is being installed via
> image_install. Module is installed but generated conf file is not. See
> recipe below:

Hmm. If you are really installing kernel-module-<your name> to the
image, at a glance, what you have really should be enough.

Can you confirm that you are seeing your .ko on the image, and that
it just isn't being autoloaded ? Are you running an init system that
respects the autoload configuration ?

> 
> require mymodule.inc
> 
> inherit module kernel-module-split

Note that module already inherits kernel-module-split, so you really
shouldn't need to explicitly add that inherit.

Bruce

> 
> DEPENDS = "virtual/kernel"
> 
> EXTRA_OEMAKE_append = " \
>      KERNELDIR=${STAGING_KERNEL_DIR} \
>      "
> 
> MAKE_TARGETS = "module"
> 
> MODULE_NAME = "mymodule"
> 
> PKG_${PN} = "kernel-module-${MODULE_NAME}"
> 
> module_do_install() {
>      install -d ${D}/lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME}
>      install -m 0644 ${MODULE_NAME}.ko \
>      ${D}/lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME}/${MODULE_NAME}.ko
> }
> 
> FILES_${PN} = " \
>      /lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME} \
> "
> 
> KERNEL_MODULE_AUTOLOAD += "${MODULE_NAME}"
> 

Re: Proper Use of KERNEL_MODULE_AUTOLOAD variable

[Ulf Samuelsson]

Den 2019-02-03 kl. 04:16, skrev Ken Sloat:
> On Sat, Feb 2, 2019 at 10:03 PM Bruce Ashfield
> <bruce.ashfield@windriver.com> wrote:
>>
>> On 2019-02-02 9:59 p.m., Ken Sloat wrote:
>>> Hello,
>>>
>>> I have an out of tree kernel module which I want autoloaded at startup
>>> on my system. Looking at the Yocto project manual, I see that one way
>>> I can do this is to add the module name to the KERNEL_MODULE_AUTOLOAD
>>> variable within my custom module recipe.
>>>
>>> What I have found is that the module-split class is indeed generating
>>> the "/etc/modules-load.d/mymodule.conf" file, however this file is not
>>> actually being installed. To be more precise it is appearing in the
>>> "package" directory (i.e.
>>> tmp/work/**/mymodule/package/etc/modules-load.d/mymodule.conf) but not
>>> within the "image" directory (nor in my final rootfs).
>>>
>>> Is there something I'm missing in the usage of KERNEL_MODULE_AUTOLOAD?
>>> Is the intention for this variable I add extra steps to manually
>>> install this file in my recipe? FYI I'm using Morty.
>>
>> Can you provide your recipe ? It would make suggestions easier. For
>> example, my first question is: Is the module being installed to your
>> image via IMAGE_INSTALL, or some other similar variable ?
>>
>> Bruce
>>
>>>
>>> Thanks,
>>> Ken Sloat
>>>
>>
> 
> Hi Bruce,
> 
> Thanks for your quick reply. Yes the module is being installed via
> image_install. Module is installed but generated conf file is not. See
> recipe below:
> 
> require mymodule.inc
> 
> inherit module kernel-module-split
> 
> DEPENDS = "virtual/kernel"
> 
> EXTRA_OEMAKE_append = " \
>      KERNELDIR=${STAGING_KERNEL_DIR} \
>      "
> 
> MAKE_TARGETS = "module"
> 
> MODULE_NAME = "mymodule"
> 
> PKG_${PN} = "kernel-module-${MODULE_NAME}"
> 
> module_do_install() {
>      install -d ${D}/lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME}
>      install -m 0644 ${MODULE_NAME}.ko \
>      ${D}/lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME}/${MODULE_NAME}.ko
> }
> 
> FILES_${PN} = " \
>      /lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME} \
> "
> 
> KERNEL_MODULE_AUTOLOAD += "${MODULE_NAME}"
> 

One would think that the file should be added automatically,
but this might be required, - or a workaround...

FILES_${PN} = " \
       /lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME} \
       ${sysconfdir}/modules-load.d/${MODULE_NAME}.conf \
"


-- 
Best Regards
Ulf Samuelsson

Re: Proper Use of KERNEL_MODULE_AUTOLOAD variable

[Ken Sloat]

On Sun, Feb 3, 2019 at 12:51 AM Ulf Samuelsson <yocto@emagii.com> wrote:
>
> Den 2019-02-03 kl. 04:16, skrev Ken Sloat:
> > On Sat, Feb 2, 2019 at 10:03 PM Bruce Ashfield
> > <bruce.ashfield@windriver.com> wrote:
> >>
> >> On 2019-02-02 9:59 p.m., Ken Sloat wrote:
> >>> Hello,
> >>>
> >>> I have an out of tree kernel module which I want autoloaded at startup
> >>> on my system. Looking at the Yocto project manual, I see that one way
> >>> I can do this is to add the module name to the KERNEL_MODULE_AUTOLOAD
> >>> variable within my custom module recipe.
> >>>
> >>> What I have found is that the module-split class is indeed generating
> >>> the "/etc/modules-load.d/mymodule.conf" file, however this file is not
> >>> actually being installed. To be more precise it is appearing in the
> >>> "package" directory (i.e.
> >>> tmp/work/**/mymodule/package/etc/modules-load.d/mymodule.conf) but not
> >>> within the "image" directory (nor in my final rootfs).
> >>>
> >>> Is there something I'm missing in the usage of KERNEL_MODULE_AUTOLOAD?
> >>> Is the intention for this variable I add extra steps to manually
> >>> install this file in my recipe? FYI I'm using Morty.
> >>
> >> Can you provide your recipe ? It would make suggestions easier. For
> >> example, my first question is: Is the module being installed to your
> >> image via IMAGE_INSTALL, or some other similar variable ?
> >>
> >> Bruce
> >>
> >>>
> >>> Thanks,
> >>> Ken Sloat
> >>>
> >>
> >
> > Hi Bruce,
> >
> > Thanks for your quick reply. Yes the module is being installed via
> > image_install. Module is installed but generated conf file is not. See
> > recipe below:
> >
> > require mymodule.inc
> >
> > inherit module kernel-module-split
> >
> > DEPENDS = "virtual/kernel"
> >
> > EXTRA_OEMAKE_append = " \
> >      KERNELDIR=${STAGING_KERNEL_DIR} \
> >      "
> >
> > MAKE_TARGETS = "module"
> >
> > MODULE_NAME = "mymodule"
> >
> > PKG_${PN} = "kernel-module-${MODULE_NAME}"
> >
> > module_do_install() {
> >      install -d ${D}/lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME}
> >      install -m 0644 ${MODULE_NAME}.ko \
> >      ${D}/lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME}/${MODULE_NAME}.ko
> > }
> >
> > FILES_${PN} = " \
> >      /lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME} \
> > "
> >
> > KERNEL_MODULE_AUTOLOAD += "${MODULE_NAME}"
> >
>
> One would think that the file should be added automatically,
> but this might be required, - or a workaround...
>
> FILES_${PN} = " \
>        /lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME} \
>        ${sysconfdir}/modules-load.d/${MODULE_NAME}.conf \
> "
>
>
> --
> Best Regards
> Ulf Samuelsson
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Hi Ulf,

Yes it seems that this indeed allows it to end up in the final image.

Not sure why it doesn't work without as I see the kernel-module-split
class seems to have statements to do this automatically:

        files = d.getVar('FILES_%s' % pkg, True)
        files = "%s /etc/modules-load.d/%s.conf
/etc/modprobe.d/%s.conf" % (files, basename, basename)
        d.setVar('FILES_%s' % pkg, files)

Maybe there's some type of name mismatch or something in my case?

Thanks,
Ken Sloat

Re: Proper Use of KERNEL_MODULE_AUTOLOAD variable

[Ulf Samuelsson]

> 3 feb. 2019 kl. 20:09 skrev Ken Sloat <ken.sloat@ohmlinx.com>:
> 
>> On Sun, Feb 3, 2019 at 12:51 AM Ulf Samuelsson <yocto@emagii.com> wrote:
>> 
>>> Den 2019-02-03 kl. 04:16, skrev Ken Sloat:
>>> On Sat, Feb 2, 2019 at 10:03 PM Bruce Ashfield
>>> <bruce.ashfield@windriver.com> wrote:
>>>> 
>>>>> On 2019-02-02 9:59 p.m., Ken Sloat wrote:
>>>>> Hello,
>>>>> 
>>>>> I have an out of tree kernel module which I want autoloaded at startup
>>>>> on my system. Looking at the Yocto project manual, I see that one way
>>>>> I can do this is to add the module name to the KERNEL_MODULE_AUTOLOAD
>>>>> variable within my custom module recipe.
>>>>> 
>>>>> What I have found is that the module-split class is indeed generating
>>>>> the "/etc/modules-load.d/mymodule.conf" file, however this file is not
>>>>> actually being installed. To be more precise it is appearing in the
>>>>> "package" directory (i.e.
>>>>> tmp/work/**/mymodule/package/etc/modules-load.d/mymodule.conf) but not
>>>>> within the "image" directory (nor in my final rootfs).
>>>>> 
>>>>> Is there something I'm missing in the usage of KERNEL_MODULE_AUTOLOAD?
>>>>> Is the intention for this variable I add extra steps to manually
>>>>> install this file in my recipe? FYI I'm using Morty.
>>>> 
>>>> Can you provide your recipe ? It would make suggestions easier. For
>>>> example, my first question is: Is the module being installed to your
>>>> image via IMAGE_INSTALL, or some other similar variable ?
>>>> 
>>>> Bruce
>>>> 
>>>>> 
>>>>> Thanks,
>>>>> Ken Sloat
>>>>> 
>>>> 
>>> 
>>> Hi Bruce,
>>> 
>>> Thanks for your quick reply. Yes the module is being installed via
>>> image_install. Module is installed but generated conf file is not. See
>>> recipe below:
>>> 
>>> require mymodule.inc
>>> 
>>> inherit module kernel-module-split
>>> 
>>> DEPENDS = "virtual/kernel"
>>> 
>>> EXTRA_OEMAKE_append = " \
>>>     KERNELDIR=${STAGING_KERNEL_DIR} \
>>>     "
>>> 
>>> MAKE_TARGETS = "module"
>>> 
>>> MODULE_NAME = "mymodule"
>>> 
>>> PKG_${PN} = "kernel-module-${MODULE_NAME}"
>>> 
>>> module_do_install() {
>>>     install -d ${D}/lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME}
>>>     install -m 0644 ${MODULE_NAME}.ko \
>>>     ${D}/lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME}/${MODULE_NAME}.ko
>>> }
>>> 
>>> FILES_${PN} = " \
>>>     /lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME} \
>>> "
>>> 
>>> KERNEL_MODULE_AUTOLOAD += "${MODULE_NAME}"
>>> 
>> 
>> One would think that the file should be added automatically,
>> but this might be required, - or a workaround...
>> 
>> FILES_${PN} = " \
>>       /lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME} \
>>       ${sysconfdir}/modules-load.d/${MODULE_NAME}.conf \
>> "
>> 
>> 
>> --
>> Best Regards
>> Ulf Samuelsson
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
> 
> Hi Ulf,
> 
> Yes it seems that this indeed allows it to end up in the final image.
> 
> Not sure why it doesn't work without as I see the kernel-module-split
> class seems to have statements to do this automatically:
> 
>        files = d.getVar('FILES_%s' % pkg, True)
>        files = "%s /etc/modules-load.d/%s.conf
> /etc/modprobe.d/%s.conf" % (files, basename, basename)
>        d.setVar('FILES_%s' % pkg, files)
> 
> Maybe there's some type of name mismatch or something in my case?
> 
> Thanks,
> Ken Sloat

I would log those statements when building.
Either pkg, or basename has a different value, than what is expected.

Best Regards,
Ulf Samuelsson
+46 722 427 437

Re: Proper Use of KERNEL_MODULE_AUTOLOAD variable

[Robert Berger]

Hi Ken,

Is there any particular reason you don't use the sample[1] for an out of 
tree kernel module?

[1] 
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-skeleton/recipes-kernel/hello-mod

Regards,

Robert

Re: Proper Use of KERNEL_MODULE_AUTOLOAD variable

[Ken Sloat]

On Mon, Feb 4, 2019 at 10:50 AM Robert Berger
<yocto.user.mailinglist@gmail.com> wrote:
>
> Hi Ken,
>
> Is there any particular reason you don't use the sample[1] for an out of
> tree kernel module?
>
> [1]
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-skeleton/recipes-kernel/hello-mod
>
> Regards,
>
> Robert

Hi Robert,

We are running an older version of Yocto (Morty) for a customer. I
redacted the recipe name for the example I posted, but the recipe is
basically an identical copy of another recipe from newer versions of
Poky not present in Morty.

I might try to debug this more at some point, but the FILES statement
seems to make it work. Thanks for all the help everyone, I really
appreciate it.

Re: Proper Use of KERNEL_MODULE_AUTOLOAD variable

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 2719 bytes --]

On Sat, Feb 2, 2019 at 7:17 PM Ken Sloat <ken.sloat@ohmlinxelectronics.com>
wrote:

> On Sat, Feb 2, 2019 at 10:03 PM Bruce Ashfield
> <bruce.ashfield@windriver.com> wrote:
> >
> > On 2019-02-02 9:59 p.m., Ken Sloat wrote:
> > > Hello,
> > >
> > > I have an out of tree kernel module which I want autoloaded at startup
> > > on my system. Looking at the Yocto project manual, I see that one way
> > > I can do this is to add the module name to the KERNEL_MODULE_AUTOLOAD
> > > variable within my custom module recipe.
> > >
> > > What I have found is that the module-split class is indeed generating
> > > the "/etc/modules-load.d/mymodule.conf" file, however this file is not
> > > actually being installed. To be more precise it is appearing in the
> > > "package" directory (i.e.
> > > tmp/work/**/mymodule/package/etc/modules-load.d/mymodule.conf) but not
> > > within the "image" directory (nor in my final rootfs).
> > >
> > > Is there something I'm missing in the usage of KERNEL_MODULE_AUTOLOAD?
> > > Is the intention for this variable I add extra steps to manually
> > > install this file in my recipe? FYI I'm using Morty.
> >
> > Can you provide your recipe ? It would make suggestions easier. For
> > example, my first question is: Is the module being installed to your
> > image via IMAGE_INSTALL, or some other similar variable ?
> >
> > Bruce
> >
> > >
> > > Thanks,
> > > Ken Sloat
> > >
> >
>
> Hi Bruce,
>
> Thanks for your quick reply. Yes the module is being installed via
> image_install. Module is installed but generated conf file is not. See
> recipe below:
>
> require mymodule.inc
>
> inherit module kernel-module-split
>
> DEPENDS = "virtual/kernel"
>
> EXTRA_OEMAKE_append = " \
>     KERNELDIR=${STAGING_KERNEL_DIR} \
>     "
>
> MAKE_TARGETS = "module"
>
> MODULE_NAME = "mymodule"
>
> PKG_${PN} = "kernel-module-${MODULE_NAME}"
>
> module_do_install() {
>     install -d ${D}/lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME}
>     install -m 0644 ${MODULE_NAME}.ko \
>
> ${D}/lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME}/${MODULE_NAME}.ko
> }
>
> FILES_${PN} = " \
>     /lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME} \
> "


Your recipe is overwriting common stuff which otherwise should be provided
by module bbclass
I would suggest that you append to the variables instead of over writing
them above and try to reuse
The primitives from bbclass as much as you can for best results

>
>
> KERNEL_MODULE_AUTOLOAD += "${MODULE_NAME}"
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

[-- Attachment #2: Type: text/html, Size: 3827 bytes --]

Re: Proper Use of KERNEL_MODULE_AUTOLOAD variable

[Ulf Samuelsson]

[-- Attachment #1: Type: text/plain, Size: 3135 bytes --]

Maybe it would be good to have a working example in the tree.

Best Regards,
Ulf Samuelsson

> 6 feb. 2019 kl. 02:22 skrev Khem Raj <raj.khem@gmail.com>:
> 
> 
> 
>> On Sat, Feb 2, 2019 at 7:17 PM Ken Sloat <ken.sloat@ohmlinxelectronics.com> wrote:
>> On Sat, Feb 2, 2019 at 10:03 PM Bruce Ashfield
>> <bruce.ashfield@windriver.com> wrote:
>> >
>> > On 2019-02-02 9:59 p.m., Ken Sloat wrote:
>> > > Hello,
>> > >
>> > > I have an out of tree kernel module which I want autoloaded at startup
>> > > on my system. Looking at the Yocto project manual, I see that one way
>> > > I can do this is to add the module name to the KERNEL_MODULE_AUTOLOAD
>> > > variable within my custom module recipe.
>> > >
>> > > What I have found is that the module-split class is indeed generating
>> > > the "/etc/modules-load.d/mymodule.conf" file, however this file is not
>> > > actually being installed. To be more precise it is appearing in the
>> > > "package" directory (i.e.
>> > > tmp/work/**/mymodule/package/etc/modules-load.d/mymodule.conf) but not
>> > > within the "image" directory (nor in my final rootfs).
>> > >
>> > > Is there something I'm missing in the usage of KERNEL_MODULE_AUTOLOAD?
>> > > Is the intention for this variable I add extra steps to manually
>> > > install this file in my recipe? FYI I'm using Morty.
>> >
>> > Can you provide your recipe ? It would make suggestions easier. For
>> > example, my first question is: Is the module being installed to your
>> > image via IMAGE_INSTALL, or some other similar variable ?
>> >
>> > Bruce
>> >
>> > >
>> > > Thanks,
>> > > Ken Sloat
>> > >
>> >
>> 
>> Hi Bruce,
>> 
>> Thanks for your quick reply. Yes the module is being installed via
>> image_install. Module is installed but generated conf file is not. See
>> recipe below:
>> 
>> require mymodule.inc
>> 
>> inherit module kernel-module-split
>> 
>> DEPENDS = "virtual/kernel"
>> 
>> EXTRA_OEMAKE_append = " \
>>     KERNELDIR=${STAGING_KERNEL_DIR} \
>>     "
>> 
>> MAKE_TARGETS = "module"
>> 
>> MODULE_NAME = "mymodule"
>> 
>> PKG_${PN} = "kernel-module-${MODULE_NAME}"
>> 
>> module_do_install() {
>>     install -d ${D}/lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME}
>>     install -m 0644 ${MODULE_NAME}.ko \
>>     ${D}/lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME}/${MODULE_NAME}.ko
>> }
>> 
>> FILES_${PN} = " \
>>     /lib/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME} \
>> "
> 
> Your recipe is overwriting common stuff which otherwise should be provided by module bbclass 
> I would suggest that you append to the variables instead of over writing them above and try to reuse
> The primitives from bbclass as much as you can for best results 
>> 
>> 
>> KERNEL_MODULE_AUTOLOAD += "${MODULE_NAME}"
>> -- 
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
> -- 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

[-- Attachment #2: Type: text/html, Size: 4559 bytes --]