Bug 11712 - poky-tiny core-image-tiny-initramfs WIC image is not built correctly for meta-intel
Summary: poky-tiny core-image-tiny-initramfs WIC image is not built correctly for meta...
Status: RESOLVED NOTABUG
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-intel (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 2.4 M2
Assignee: Alejandro Hernandez
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-06-23 16:39 UTC by Alejandro Hernandez
Modified: 2017-12-06 17:28 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alejandro Hernandez 2017-06-23 16:39:19 UTC
When building poky-tiny (core-image-tiny-initramfs) for an intel MACHINE the resulting WIC image does not boot correctly, it boots up until a login prompt is shown where the user cant login, which is wrong, since core-image-tiny-initramfs should drop to shell way before getting to the login prompt.

MACHINE="intel-corei7-64"
bitbake core-image-tiny-initramfs

The resulting image is about 97M which does not make sense since a correct image should be about ~30M

l tmp/deploy/images/intel-corei7-64/ | grep wic
-rw-r--r-- 2 aehernan aehernan  97M Jun 22 16:06 core-image-tiny-initramfs-intel-corei7-64-20170622210600.rootfs.wic
-rw-r--r-- 2 aehernan aehernan  29M Jun 22 16:11 core-image-tiny-initramfs-intel-corei7-64-20170622211104.rootfs.wic

This is being caused because WIC is using an incorrect WKS file to build the image, when creating the image manually with wic, one can obtain the correct image.
Comment 1 Alejandro Hernandez 2017-06-23 16:56:06 UTC
This is where the issue happens:

# $WKS_FILE [3 operations]#   
set? /home/aehernan/yocto/poky/meta-intel/conf/machine/intel-corei7-64.conf:37
#     "${@bb.utils.contains_any("EFI_PROVIDER", "systemd-boot rmc-boot", "systemd-bootdisk.wks", "mkefidisk.wks", d)}"
#   set /home/aehernan/yocto/poky/meta/classes/image_types_wic.bbclass:8
#     [_defaultval] "${IMAGE_BASENAME}.${MACHINE}.wks"
#   override[poky-tiny]:set? /home/aehernan/yocto/poky/meta-intel/common/recipes-core/images/core-image-tiny-initramfs.bbappend:14
#     "${@wks_intel(d)}"
# pre-expansion value:
#   "${@bb.utils.contains_any("EFI_PROVIDER", "systemd-boot rmc-boot", "systemd-bootdisk.wks", "mkefidisk.wks", d)}"
WKS_FILE="systemd-bootdisk.wks"

This is indicating that WKS_FILE was assigned the value of "systemd-bootdisk.wks"
where it should have been assigned whatever was returned from "${@wks_intel(d)}"

So, for some reason the override[poky-tiny] stopped working.
Comment 2 Alejandro Hernandez 2017-06-30 03:08:20 UTC
The override for poky-tiny is working correctly, it seems that you can't assign DISTRO ?= "poky-tiny", it has to be set as DISTRO = "poky-tiny".

So the DISTRO was being assinged incorrectly, hence why DISTROOVERRIDES wasnt working.