[yocto] [meta-raspberrypi] core-image-minimal for raspberrypi3-64 manifest/sdimg contains no kernel modules

[Andre McCurdy]

On Wed, Aug 15, 2018 at 12:08 PM, Max Krummenacher <max.oss.09 at gmail.com> wrote:
> Hi
>
> Am Mittwoch, den 15.08.2018, 02:47 -0400 schrieb Steve Pavao:
>> There seems to be a problem with the core-image-minimal bitbake for raspberrypi3-64 target at head
>> of sumo in all repos.  I wonder if it’s also a problem for the raspberrypi3 target.
>>
>> No kernel modules appear in the .manifest, and no kernel modules are put into the sdimg.  It’s
>> hard to believe it’s true, but that’s what I'm seeing.
>>
>> The problem does NOT occur for the rpi-hwup-image bitbake, which is actually deprecated in poky
>> 2.5/sumo.
>>
>> Before you retire the rpi-hwup-image bitbake target, will you please make sure that the kernel
>> modules from the core-image-minimal build make it into the .manifest and therefore into the sdimg?
>>
>> Please let me know where to log this issue, so I can send you the .manifest diffs, some ls command
>> output showing the large size difference between the core-image-minimal and rpi-hwup-image sdimg
>> files for identical builds, and perhaps some file listings to show that one of the builds contains
>> kernel modules (rpi-hwup-image) and the other does not (core-image-minimal).
>>
>> Steve Pavao
>> Korg R&D
>>
>
> Note that the 'kernel-modules' package is one of the packages built by a kernel recipe.
> It is a meta package which RDEPENDS on all kernel module packages built by your kernel
> configuration. So adding that package to your image should do the trick.

To understand what's happening it's worth also reading the SUMMARY for
core-image-minimal:

  SUMMARY = "A small image just capable of allowing a device to boot"

and comparing to core-image-base:

  SUMMARY = "A console-only image that fully supports the target
device hardware"

ie the fact that core-image-minimal doesn't contain any kernel modules
is a feature, not a bug.