Hello all, I hope this is the right place to ask this. I'm in the process of
upgrading from kirkstone to scarthgap and everything was going smoothly until I
got to image (genericx86-64 based) creation. I'm creating a self installer
boot image using image-installer.wks.in (more precisely a copy of it) from
meta-intel and it is failing with the following error:
ERROR: _exec_cmd: install -m 0644 -D
/home/mlynch/SGTest/build/SynergyII/Controller/intel/tmp/work/genericx86_64-poky-linux/synergy2-image/1.0/deploy-synergy2-image-image-complete/synergy2-image-genericx86-64.ext4
/home/mlynch/SGTest/build/SynergyII/Controller/intel/tmp/work/genericx86_64-poky-linux/synergy2-image/1.0/tmp-wic/boot.2/rootfs.img
returned '1' instead of 0
output: install: cannot stat
'/home/mlynch/SGTest/build/SynergyII/Controller/intel/tmp/work/genericx86_64-poky-linux/synergy2-image/1.0/deploy-synergy2-image-image-complete/synergy2-image-genericx86-64.ext4':
No such file or directory
When I check, the file it is complaining about does not exist. I've tracked
this down to being caused by the highlighted portion of the line below from
image-installer.wks.in :
part /boot --source bootimg-efi
--sourceparams="loader=${EFI_PROVIDER},title=install,label=install-efi,
*initrd=microcode.cpio;${INITRD_IMAGE_LIVE}-${MACHINE}.${INITRAMFS_FSTYPES}"*
--ondisk sda --label install --active --align 1024 --use-uuid
If I remove either the semicolon *AND* either microcode.cpio or
${INIT_IMAGE_LIVE}-${MACHINE}.${INITRAMGS_FSTYPES} the missing file will get
created and a WIC file is produced (but won't boot). E.G. If I changed the
line in one of the two ways shown below the error does not occur and a WIC file
is produced but it will not boot. As I stated I am upgrading from kirkstone to
scarthgap and the above line works with the kirkstone branch. Note that I am
working from a fresh install of poky (scarthgap) and using the same machine I
use for the kirkstone branch. Given that the image-installer.wks.in file from
meta-intel hasn't really changed but no longer appears to work, I'm assuming
something outside of the layer changed that is responsible for the issue. It
appears that the existence of the semicolon in the initrd= portion of the part
command is causing the issue. With the working version my grub.cfg has a line
that reads " initrd /microcode.cpio
/synergy2-image-initramfs-genericx86-64.cpio.gz " and in the failed case it
does not. Thanks in advance for any guidance anyone can offer even if that's
just pointing me in a direction to look.
part /boot --source bootimg-efi
--sourceparams="loader=${EFI_PROVIDER},title=install,label=install-efi,
*initrd=${INITRD_IMAGE_LIVE}-${MACHINE}.${INITRAMFS_FSTYPES}* " --ondisk sda
--label install --active --align 1024 --use-uuid
part /boot --source bootimg-efi
--sourceparams="loader=${EFI_PROVIDER},title=install,label=install-efi,
*initrd=microcode.cpio* " --ondisk sda --label install --active --align 1024
--use-uuid
-- Mike
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8331):
https://lists.yoctoproject.org/g/meta-intel/message/8331
Mute This Topic: https://lists.yoctoproject.org/mt/106251482/21656
Mute
#kirkstone:https://lists.yoctoproject.org/g/meta-intel/mutehashtag/kirkstone
Mute
#scarthgap:https://lists.yoctoproject.org/g/meta-intel/mutehashtag/scarthgap
Group Owner: meta-intel+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-intel/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
