On 02.02.2012, at 10:35, Marcus Schäfer <ms@suse.de> wrote:
Hi,
Feb-02 03:10:53 <1> : Set boot space to: 64M
Our /boot is 64MB (I think that was one of the odd constraints we had from omap)
yes do you remember our session with Dirk :) 64M seems to be a must have. If you like to give it a test with another size check the code in
/usr/share/kiwi/modules/KIWIBoot.pm:__getBootSize
... # on arm it's required to have a maximum of 64MB for the boot part if ($arch =~ /arm/) { $gotMB = 64; }
I would love to get rid of this but so far it seems required
cp: writing `/tmp/kiwiloop.4KkehU/boot/boot.scr': No space left on device cp: failed to extend `/tmp/kiwiloop.4KkehU/boot/boot.scr': No space left on device cp: writing `/tmp/kiwiloop.4KkehU/boot/linux.vmx': No space left on device
*urks*
-rw-r--r-- 1 root root 33M Feb 2 04:10 initrd-vmxboot-suse-SLES12.armv7l-2.7.1.gz
This beast is already 33MB.
So by keeping it in /boot twice, we exceed the 64MB we have available. Any ideas? In the long run, we should definitely redesign the whole bootstrapping process. Having FAT partitions is just insane.
I added a patch to kiwi which only leaves the uboot variant on /boot commit: 0387c5660cf82d734d6650475bec19e681142e81 from master
I bumped it to 128MB last night too see if it'd break somewhere else later and that gave me a successful build! Woot :) Adrian, in obs the build is failing due to: Feb-02 11:03:10 <3> : Failed to mount /dev/mapper/loop0p1 to: /tmp/kiwiloop.teKAej: Unsupported ioctl: cmd=0x5331 (0) mount: unknown filesystem type 'vfat' [80C[10D[1;31mfailed [mFeb-02 11:03:10 <1> : EXEC [sync] failed Feb-02 11:03:11 <3> : Couldn't mount image boot device: /dev/mapper/loop0p1 failed Any idea how to fix this? Apparently the kernel doesn't include vfat support without y module. But we can't use the arm modules here either. Marcus, could we have a flag that tells kiwi to create an ext3 partition for /boot instead of vfat? The efikas can already boot off that and I would like to get MLO to understand ext2 too, so we can just use that instead of vfat. We will have to create a different boot.scr depending on the choice though. Also, I just played a bit with efi on x86. There we create a mount point /boot/efi which contains elilo and the currently used kernels. Maybe that would be the way to go for arm too for now? Have a /boot/uboot directory that is our first partition and have perl-bootloader copy / mkuimage ther kernel / initrd over to that partition from /boot. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org