Am 17.02.2016 um 15:47 schrieb Andreas Färber:
> I started
> a cleanup but never finished and don't have access to all boards to
> check, in particular the Olimex ones.
I can do that tests. While testing
openSUSE-Tumbleweed-ARM-E20-olinuxinolime2.armv7l-1.12.1-Build377.1.raw.xz
I faced some issues (I removed "quiet splash=silent" from the kernel
command line to get some output to serial console):
The first boot end with:
<snip>
+ echo '[1455926389.155528] Checking ext4 filesystem on /dev/mmcblk0p2...'
+ '[' 0 = 0 ']'
+ set +x
+ checkFilesystem
+ local device=
+ local FSTYPE_SAVE=
+ '[' -z ext4 ']'
+ '[' ext4 = reiserfs ']'
+ '[' ext4 = ext2 ']'
+ '[' ext4 = ext3 ']'
+ '[' ext4 = ext4 ']'
+ e2fsck -p -f
Usage: e2fsck [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device
Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j external_journal Set location of the external journal
-l bad_blocks_file Add to badblocks list
-L bad_blocks_file Set badblocks list
+ FSTYPE=
+ Echo 'Resizing filesystem on /dev/mmcblk0p2...'
+ local 'IFS=
'
+ '[' 0 = 0 ']'
+ set +x
+ echo '[1455926389.184328] Resizing filesystem on /dev/mmcblk0p2...'
+ '[' 0 = 0 ']'
+ set +x
+ eval resize2fs -f -F -p /dev/mmcblk0p2
++ resize2fs -f -F -p /dev/mmcblk0p2
resize2fs 1.42.13 (17-May-2015)
resize2fs: Unknown code ____ 255 while trying to flush /dev/mmcblk0p2
+ '[' '!' 1 = 0 ']'
+ systemException 'Failed to resize/check filesystem' reboot
+ local 'IFS=
'
+ set +x
+ echo -e '[1455926389.338469] Failed to resize/check filesystem'
+ '[' 0 = 0 ']'
+ set +x
+ case "$what" in
+ cat /var/log/boot.kiwi
[1455926395.681619] rebootException: reboot in 120 sec...
[ 152.968761] reboot: Restarting system
[ 153.972608] Reboot failed -- System halted
<snap>
after reset the board /boot/zImage points to zImage-4.4.1-1-default
which is not there. So uboot fails at that point.
/boot/dtb points to dtb-4.4.0-1 which indicates that the dtb version is
different from the kernel version. This was already problem in the past
where outdated dtb versions were used in images.
Br,
Frank
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
