Le 09/10/2012 14:59, Marcus Schäfer a écrit :
Hi,
- MLO is installed by the package u-boot-omap4panda for panda it provides it in /boot when kiwi prepares the boot image. For beagleboard, it is provided by x-loader-omap3beagle, not u-boot. Maybe the problem is here? I just wanted to show an example, because I can easily test with panda I choosed this one. Of course you are right when building for a beagle board x-loader-omap3beagle would be used here. But the process is the same concerning the MLO install
I do not know the kiwi magic, so I suppose it is the same process. ;)
When kiwi creates the initrd cpio archive it moves among other things the MLO to image/loader/MLO because /boot is removed from the initrd after the kernel was extracted. Thus MLO is in the kiwi created initrd at:
gzip -cd /space/mytest/initrd-oemboot-suse-12.2.armv7l-2.7.1.gz |\ cpio -it | grep MLO
==> image/loader/MLO
you should first check if this is the case in your build as well
No. I only have this one: [ 814s] Oct-09 08:54:51 <1> : EXEC [gzip -9 -cd /usr/src/packages/KIWI-oem/oem/initrd-oemboot-suse-12.2.armv7l-2.7.1.gz 2>&1 | cpio -it 2>/dev/null | grep efi_gop.module 2>&1]
You can double check in my full build log (with my patch), here: http://guillaume.gardet.free.fr/openSUSE/patched_JeOS-beagle.log This is nothing you can see in your build log. fetch the created initrd cpio and test if the MLO is inside: I'm pretty sure it's missing because I can't see any MLO reference in your log.
Yes, the command gzip -cd ./build-root/usr/src/packages/KIWI-oem/initrd-oemboot-suse-12.2.armv7l-2.7.1.gz | cpio -it | grep MLO returned only: 129939 blocs
Does x-loader-omap3beagle also provide /boot/MLO in the same way e.g u-boot-omap4panda does ? kiwi atm searches only for boot/MLO
It installs it in /boot/MLO. See: https://build.opensuse.org/package/view_file?file=x-loader-omap3beagle.spec&package=x-loader-omap3beagle&project=openSUSE%3AFactory%3AARM&rev=129826a296d2cbef30e4225a4e1525d9
hardcoding abs paths is not a solution not even a hacky one :) This will cause us more trouble than everything else Ok. So it seems MLO for beagle is not correctly installed in initrd, so it is not available in tmp dir. Any idea how to solve it ? I'm building for beagle now and test if I can reproduce it
Ok. Thanks. Guillaume
Regards, Marcus
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org