Le 19/11/2012 12:15, Marcus Schäfer a écrit :
Hi,
I am trying to build an armv5 image for Raspberry Pi with a FAT32 boot partition but the partition flag is wrong. It is 83 (Linux) instead of 0C (FAT32 LBA). Any idea why?
The boot partition flag problem also occur on a local build, so this is not related to a kernel problem but seems to be a kiwi one. Using fdisk, I can change the flag from 83 (Linux) to 0C (FAT32) and then, board boots on it, without reformating. Where kiwi set the partition type flag?
Moreover, in OBS JeOS image build, FAT32 partition cannot be mounted. Error log: ********************************************************************************
[ 2030s] Nov-19 10:54:35 <1> : EXEC [mkdosfs -F 32 -n 'BOOT' /dev/mapper/loop0p1 2>&1] [ 2030s] Nov-19 10:54:35 <1> : Copying boot image to disk [ 2030s] Nov-19 10:54:35 <1> : EXEC [blkid /dev/mapper/loop0p1 2>&1] [ 2030s] Nov-19 10:54:35 <1> : EXEC [pvs --noheadings -o vg_name /dev/mapper/loop0p1 2>/dev/null] [ 2031s] Nov-19 10:54:36 <1> : EXEC [blkid -o value -s TYPE /dev/mapper/loop0p1] [ 2031s] Nov-19 10:54:36 <1> : EXEC [dd if=/dev/mapper/loop0p1 bs=128k count=1 2>/dev/null | grep -qi CLIC] [ 2031s] Nov-19 10:54:36 <1> : EXEC [mount /dev/mapper/loop0p1 /tmp/kiwiloop.awflR6 2>&1] [ 2031s] [ 2002.933444] FAT-fs (dm-0): codepage cp437 not found
no code page support in this kernel for the generated fat filesystem Does the kernel provide:
kernel/fs/nls/nls_cp437.ko
?
so you can create the filesystem but you can't use it within the buildservice it could also be an emulation problem because I think you are not running on real hardware
We are using qemu for ARM build in OBS. Not sure which kernel (or kernel config) is used. On a local build (osc build on my computer) does not show up this problem, but I have nls_cp437 module loaded on my system. Adrian, Alex, any idea? Guillaume
Regards, Marcus
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org