On Tue, Nov 9, 2010 at 5:12 PM, john stultz johnstul@us.ibm.com wrote:
So I know its not on the testing list, but the qemu instructions on the wiki page fail, as they don't include an omap3 hwpack.
Feel free to update the wiki :)
Further, after providing an omap3 hwpack to build the image, the resulting image seems to have partition table issues when booted with qemu:
[ 24.961090] EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. fsck from util-linux-ng 2.17.2 rootfs: The filesystem size (according to the superblock) is 1030168 blocks The physical size of the device is 1030118 blocks Either the superblock or the partition table is likely to be corrupt!
rootfs: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) mountall: fsck / [224] terminated with status 4 mountall: Filesystem has errors: / Errors were found while checking the disk drive for / Press F to attempt to fix the errors, I to ignore, S to skip mounting or M for manual recovery
That bug *should* be fixed as of a few weeks ago:
------------------------------------------------------------ revno: 141 fixes bug(s): https://launchpad.net/bugs/658511 committer: matt.waddel@linaro.org branch nick: align-image timestamp: Wed 2010-10-13 12:35:44 -0600 message: Round the size of the raw disk image up to a multiple of 256K so it is an exact number of SD card erase blocks in length. Otherwise Linux under qemu cannot access the last part of the card and is likely to complain that the last partition on the disk has been truncated. ------------------------------------------------------------ Is your branch up to date? If so, what are the command line options you are using to create the image?
Thanks, Paul Larson