Dnia 2010-06-25, pią o godzinie 15:28 +0800, Sylvia Liu pisze: > Backup your meego_qemu_nand.img, and try this command: > qflasher -v -m rx51 -r my_rootfs.ubiimg -y r -o meego_qemu_nand.img > > But make sure your ubiimg is not too big, less than 200M is enough. > If it is too big, you can change your .ks file in the %post part, > release some memories.
Thanks for the hint. But even with: wrote rootfs (181MB, 93056 pages) in blocks 38-1491 i still have a kernel panic on rootfs. I have the following error before, while initializing MTD [ 1.576507] OneNAND driver initializing [ 1.582366] omap2-onenand omap2-onenand: initializing on CS0, phys base 0x04000000, virtual base d0880000 [ 1.583618] Muxed OneNAND 256MB 1.8V 16-bit (0x40) [ 1.584075] OneNAND version = 0x0121 [ 1.602752] Scanning device for bad blocks [ 1.648620] Creating 6 MTD partitions on "omap2-onenand": [ 1.649414] 0x00000000-0x00020000 : "bootloader" [ 1.650848] 0x00020000-0x00080000 : "config" [ 1.651733] 0x00080000-0x000c0000 : "log" [ 1.653839] mtdoops: Attached to MTD device 2 [ 1.654296] 0x000c0000-0x002c0000 : "kernel" [ 1.655273] 0x002c0000-0x004c0000 : "initfs" [ 1.656311] 0x004c0000-0x10000000 : "rootfs" [ 1.663635] UBI: attaching mtd5 to ubi0 [ 1.664337] UBI: physical eraseblock size: 131072 bytes (128 KiB) [ 1.665008] UBI: logical eraseblock size: 129024 bytes [ 1.665588] UBI: smallest flash I/O unit: 2048 [ 1.666046] UBI: sub-page size: 512 [ 1.666534] UBI: VID header offset: 512 (aligned 512) [ 1.667083] UBI: data offset: 2048 [ 1.794311] UBI error: vtbl_check: volume table check failed: record 0, error 9 [ 1.797698] UBI error: ubi_init: cannot attach mtd5 [ 1.798797] UBI error: ubi_init: UBI error: cannot initialize UBI, error -22 _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
