Le 04/04/2018 à 09:32, Guillaume Gardet a écrit :
Hi Marcus, openSUSE:Factory:ARM switched to new kiwi to build images. But we have still a number of images requiring firmware=custom option to build with u-boot. But this leads to the following error: ********************************************************************** [ 45s] running kiwi system build for oem... [ 45s] cd /usr/src/packages/SOURCES && rm -rf /usr/src/packages/KIWI-oem && LANG=en_US.UTF-8 /usr/bin/kiwi --debug system build --description /usr/src/packages/SOURCES --target-dir /usr/src/packages/KIWI-oem --ignore-repos-used-for-build --add-repo dir://./repos/openSUSE:Factory:ARM/standard,rpm-md,,99 [ 47s] [ DEBUG ]: 07:30:09 | EXEC: [mkdir -p /usr/src/packages/KIWI-oem/build] [ 47s] [ INFO ]: 07:30:10 | Loading XML description [ 48s] [ DEBUG ]: 07:30:10 | EXEC: [jing /usr/lib/python3.6/site-packages/kiwi/schema/kiwi.rng /tmp/tmpcw837wx_] [ 49s] [ INFO ]: 07:30:12 | RelaxNG validation failed. See jing report: [ 49s] [ INFO ]: 07:30:12 | --> /tmp/tmpcw837wx_:10:395: error: value of attribute "firmware" is invalid; must be equal to "bios", "ec2", "efi", "ofw", "opal" or "uefi" [ 49s] [ 49s] [ ERROR ]: 07:30:12 | KiwiDescriptionInvalid: Schema validation for /usr/src/packages/SOURCES/config.xml failed ********************************************************************** Does new kiwi support firmware=custom? Otherwise, what would be the solution?
If I remove the firmware=custom, I finally get this error: ******************************************************************************** [ 349s] [ DEBUG ]: 07:54:47 | --------------err stop-------------- [ 349s] [ DEBUG ]: 07:54:47 | EXEC: [ln /usr/src/packages/KIWI-oem/kiwi_boot_root.2ggl7lso/linuxrc /usr/src/packages/KIWI-oem/kiwi_boot_root.2ggl7lso/init] [ 349s] [ INFO ]: 07:54:47 | Precalculating required disk size [ 349s] [ DEBUG ]: 07:54:47 | EXEC: [du -s --apparent-size --block-size 1 /usr/src/packages/KIWI-oem/build/image-root] [ 349s] [ DEBUG ]: 07:54:47 | EXEC: [bash -c find /usr/src/packages/KIWI-oem/build/image-root | wc -l] [ 350s] [ INFO ]: 07:54:48 | --> system data with filesystem overhead needs 1452 MB [ 350s] [ INFO ]: 07:54:48 | --> spare partition adding 8 MB [ 350s] [ INFO ]: 07:54:48 | --> EFI partition adding 20 MB [ 350s] [ INFO ]: 07:54:48 | Using calculated disk size: 1480 MB [ 350s] [ INFO ]: 07:54:48 | Creating raw disk image /usr/src/packages/KIWI-oem/openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2018.04.03.raw [ 350s] [ DEBUG ]: 07:54:48 | EXEC: [qemu-img create /usr/src/packages/KIWI-oem/openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2018.04.03.raw 1480M] [ 350s] [ DEBUG ]: 07:54:48 | EXEC: [losetup -f --show /usr/src/packages/KIWI-oem/openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2018.04.03.raw] [ 350s] [ DEBUG ]: 07:54:48 | "grub2-install": in paths "/usr/src/packages/KIWI-oem/build/image-root/usr/sbin" exists: "False" mode match: not checked [ 350s] [ ERROR ]: 07:54:48 | KiwiBootLoaderConfigSetupError: Support for custom bootloader config not implemented [ 350s] [ INFO ]: 07:54:48 | Cleaning up BootImageKiwi instance [ 350s] [ DEBUG ]: 07:54:48 | EXEC: [rm -r -f /usr/src/packages/KIWI-oem/kiwi_boot_root.2ggl7lso] [ 350s] [ INFO ]: 07:54:48 | Cleaning up LoopDevice instance [ 350s] [ DEBUG ]: 07:54:48 | EXEC: [losetup -d /dev/loop0] [ 350s] [ INFO ]: 07:54:48 | Cleaning up BootImageKiwi instance [ 350s] [ DEBUG ]: 07:54:48 | EXEC: [rm -r -f /usr/src/packages/KIWI-oem/kiwi_boot_root.e99c_8_l] ******************************************************************************** It seems that new kiwi does not support u-boot (non EFI/Grub2) images? Is there a solution/workaround? Guillaume -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
