I moved from older release (2.6.34 kernel) to latest one with 2.6.36. And UBIFS seems not to work anymore. I flash my NAND and I can mount UBIFS partitions and access files. Trying to boot from NAND fails. Both kernels has save UBIFS config options enabled with identical values. Everything is set up exactly as in old version. Any ideas what's getting wrong here? Modifications for u-boot env:
setenv nandroot 'ubi0:overo-rootfs ubi.mtd=4,512'
setenv nandrootfstype ubifs
OR
setenv nandroot 'ubi0:overo-rootfs ubi.mtd=4'
setenv nandrootfstype ubifs
UBIFS error (pid 1): ubifs_get_sb: cannot open "ubi0:overo-rootfs", error -19
twl_rtc twl_rtc: setting system clock to 2000-01-01 00:03:05 UTC (946684985)
VFS: Cannot open root device "ubi0:overo-rootfs" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00             512 mtdblock0 (driver?)
1f01            1792 mtdblock1 (driver?)
1f02             256 mtdblock2 (driver?)
1f03            4096 mtdblock3 (driver?)
1f04          255488 mtdblock4 (driver?)
1f05          248598 mtdblock5 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Also UBIFS seem to work:
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB 1,8V 16-bit)
cmdlinepart partition parsing not available
Creating 5 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000080000 : "xloader"
0x000000080000-0x000000240000 : "uboot"
0x000000240000-0x000000280000 : "uboot environment"
0x000000280000-0x000000680000 : "linux"
0x000000680000-0x000010000000 : "rootfs"
UBI: attaching mtd4 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: max. sequence number:       2
UBI: attached mtd4 to ubi0
UBI: MTD device name:            "rootfs"
UBI: MTD device size:            249 MiB
UBI: number of good PEBs:        1996
UBI: number of bad PEBs:         0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 1996
UBI: number of PEBs reserved for bad PEB handling: 19
UBI: max/mean erase counter: 5/2
UBI: image sequence number:  1902834807
UBI: background thread "ubi_bgt0d" started, PID 47


View this message in context: UBIFS boot fails to work on latest release
Sent from the Gumstix mailing list archive at Nabble.com.