[    9.005000] EXT2-fs: mmcblk0p2: couldn't mount because of unsupported optional features (4).
The problem can be corrected by using a microSD card reader on another computer to mount the ext2 partition. After unmounting the partition and inserting it into the FreeRunner?, the operating system boots without issue.
This shows that 007a8000, the first line of the above diff, is at the start of mmcblk0p2 (280*28672 = 7a8000). Unfortunately, I don't understand the ext2/3 filesystem headers so I'm not sure what this diff means. It should prove useful to someone that knows a bit more about it, though.
I can provide additional information about the before_mount and after_mount images if you need them.
Presumably the issue is with the Openmoko kernel. It is unable to mount the partition even though another Linux kernel can mount it (the one on the computer with the attached microSD reader). The differences in the ext2/3 filesystem header appear to be causing the problem. Either the filesystem header is being left in an invalid state on a hard shutdown or the kernel is unable to read the valid filesystem header that is present after a hard shutdown. In any case, the kernel should be able to correct the issue at boot time and proceed.
This issue can be reproduced by modifying the filesystem header as described in the above diff. It can also be reproduced by doing a hard shutdown on an Om2008.8 system booted from the 512MB microSD card shipped with the FreeRunner?, although it only occurs sometimes.
printk("EXT2-fs: %s: couldn't mount because of "
Don't really know what it means, but I never saw it myself and Google is pretty quiet about it, usually a sign it is the outcome of somthing funny.
Note the desktop box is doing a mount from userspace, so it's quite possible it can try multiple times or take corrective action if it sees insanity: we are having one go entirely from kernel so we might be a little more fragile.
Check we are not somehow mixing up rootfstype= between ext2 and ext3, on kernel commandline or in /etc/fstab in the root filesystem for example.
Another angle, IIRC Debian for example has initscript to remount the rootfs rw, it is happy to have ro rootfs initially. I noticed in the ext2 code there are different rules for what it doesn't like if you mount ro. So you might mask this behaviour if you add "ro" to your kernel commandline to get the rootfs mounted read only initially.
Kamagra Safe Kamagra 100mg Wirkung Buy Overnight Direct Zentel Tab Amex Fedex C.O.D.