Hi Guillaume, Am 17.02.2016 um 11:00 schrieb Guillaume Gardet: > On boot, with latest build (kernel 4.4.0-3-default) I get the following > error: "Initramfs unpacking failed: write error". > Full kernel log (for beaglebone black): > ******************************************************** > Starting kernel ... > > [ 0.000530] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0' > [ 0.000538] This ensures that you still see kernel messages. Please > [ 0.000545] update your kernel commandline. > [ 5.154972] Initramfs unpacking failed: write error [...] > Note that there is no early message (except warning on console, for > which I will send a JeOS SR). > > Any idea what is wrong?
For early messages try adding "earlycon" to the command line. When you need only one console, the most future-proof would be to drop console= if /chosen stdout-path points to something sane in the device tree - Alex reported Kiwi possibly depending on console= parsing, so that may need patches and testing. > Any kernel config update related to initramfs? Not that I'm aware of, no. Alex already pointed to tmpfs vs. ramfs as the most likely cause here; another cause to check for on such errors is whether the load addresses may be wrong - some time ago I ran into such an issue with an Arndale board. With the distro cleanups happening in U-Boot, too many of our JeOS images are still specifying hardcoded addresses in the JeOS scripts rather than using U-Boot-provided $ramdisk_addr_r and friends. I started a cleanup but never finished and don't have access to all boards to check, in particular the Olimex ones. Also once you've successfully installed a JeOS image we provide no package to ever update the boot.scr, so it bitrots and I usually replace it with something simpler on my systems at some point. Another thing to look into is our .kiwi.in template - last time I checked we were always including wildcard drivers such as mmc/* rather than the specific ones needed per board. config.sh should have the list of required drivers for second boot in the dracut snippets. Same comment here, such config files should really go into some board branding package so that users are not left without, e.g., mmc_block after updating the kernel (beaglebone-black-sd-branding-openSUSE?). Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
