Why do I need to specify kernel-modules in local.conf if I did bitbake menuconfig?

Why do I need to specify kernel-modules in local.conf if I did bitbake menuconfig?

[Victor Rodriguez]

Hi team

The other day I enable a module ( USB WEB CAM ) in my
core-image-minimal-xfce but I could find the module once it booted
until someone really kind toll me that you need to add the kernel
modules:

IMAGE_INSTALL_append = " kernel-modules"

Is not the expected that if you do bitbake menuconfig then enable the
module you want save it .. the module be there .. I mean thats the
reason why you did the menuconfig right ?

Is this an expected behaivor for Yocto ?

Best regards

Victor Rodriguez

Re: Why do I need to specify kernel-modules in local.conf if I did bitbake menuconfig?

[Gary Thomas]

On 2015-07-21 09:30, Victor Rodriguez wrote:
> Hi team
>
> The other day I enable a module ( USB WEB CAM ) in my
> core-image-minimal-xfce but I could find the module once it booted
> until someone really kind toll me that you need to add the kernel
> modules:
>
> IMAGE_INSTALL_append = " kernel-modules"
>
> Is not the expected that if you do bitbake menuconfig then enable the
> module you want save it .. the module be there .. I mean thats the
> reason why you did the menuconfig right ?
>
> Is this an expected behaivor for Yocto ?

Enabling the module(s) via menuconfig and what gets installed in
your image are separate.  Just because you've built the modules
does not imply that they should be installed.  Indeed, using
the 'kernel-modules' package is telling bitbake that you want
all possible modules installed in your image.  Often this is
not needed nor desirable and only a [limited] set of kernel
modules will be installed.

So, yes, this is the expected behaviour.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------