Hi Mikko! I found a different approach to resize the ext4 filesystem. Instead of doing this while deploying the .wic image to the SD card, I simply created a small systemd service, which does all the dirty work within the embedded system upon the first boot of the system. This works perfectly and completely independent of my build system.
Nevertheless, thanks for your help! Mit freundlichem Gruß best regards iNOEX GmbH Thore Böckelmann Software Design Mit freundlichen Grüßen / Kind regards i. A. Thore Böckelmann [cid:inoex_logo_4c_982191a2-b996-4578-8ee9-9a0ca87b6136.png]<https://inoex.de> Dipl.-Inform. Thore Böckelmann Software Engineering thore.boeckelm...@inoex.de<mailto:thore.boeckelm...@inoex.de> FON +49 5422 60507-958<callto:+49%205422%2060507-958> | FAX +49 5422 60507-101<callto:+49%205422%2060507-101> A CiTEX Group Company ________________________________ iNOEX GmbH Innovationen und Ausruestungen fuer die Extrusionstechnik Geschaeftsfuehrer / Managing Director: Martin Deters, Jan Lohoff Sitz der Gesellschaft / Headquarter: Maschweg 70, D-49324 Melle Registergericht / Register: Amtsgericht Osnabrück Handelsregisternummer / Registration number: HRB 207338 Bitte beachten Sie die Datenschutzinformationen <https://www.inoex.de/datenschutz/> ________________________________ Von: Mikko Rapeli <mikko.rap...@linaro.org> Gesendet: Mittwoch, 20. November 2024 13:50 An: Böckelmann, Thore <thore.boeckelm...@inoex.de> Cc: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> Betreff: [EXT] Re: AW: [EXT] Re: [yocto] ext4 issues with scarthgap .wic image Diese Nachricht wurde von außerhalb unserer Organisation gesendet. Hi, On Wed, Nov 20, 2024 at 12:42:51PM +0000, Böckelmann, Thore wrote: > Hi Mikko! > > Of course it is always better to move forward instead of backwards. But my > point is that the documented EXTRA_IMAGECMD variable is somehow ignored and > not passed to mkfs.ext4 as it should be. If it isn't to disable a feature the > same issue will arise when I try to pass any other option to mkfs.ext4. This > is what the IMAGE_CMD and EXTRA_IMAGECMD variables were invented for. This could be a bug, or change in image_types.bbclass behaviour. Would be nice if you could debug this a bit further, for example "bitbake -e image" output. At least IMAGE_CMD:ext4 in current poky master image_types.bbclass still has IMAGE_CMD:ext4 = "oe_mkext234fs ext4 ${EXTRA_IMAGECMD}" which would imply that adding command line arguments with EXTRA_IMAGECMD should work. Cheers, -Mikko
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#64323): https://lists.yoctoproject.org/g/yocto/message/64323 Mute This Topic: https://lists.yoctoproject.org/mt/109682386/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
