No, it is never the same block failing...
But the good news is that I finally succeed using ubifs on kirkwood: I
had to upgrade uboot
the old uboot was doing some bad init stuff i guess...
I will do more tests in the coming days, and keep you in touch.
Regards,
Romary
Le 24/08/2011 18:43,
Is it always the same blocks failing?
If so, it's more likely to be some error on NAND Level, otherwise it
could also be SPI communication somehow failing or weird bugs in mtd or
ubi...
What NAND chip is used on your board?
I had a SheevaPlug for testing, but the internal power supply died a
w
Hello
I have just tried
LINUX_VERSION:=2.6.39.2
and
LINUX_VERSION:=3.0
Both gave the same result: once you do intensiv i/o on ubifs (like find
//), i get strange message:
> UBI: run torture test for PEB 58 UBI: PEB 58 passed torture test, do
> not mark it as bad UBI error: ubi_io_read: error
Hi Romary,
thank you for testing!
I must admit that I tried only kernel 3.0 and that didn't give me any weird
errors.
It's like it's insiting that PEB 100 must be bad and then repeatingly tortures
it until it will be...
Try changing target/linux/kirkwood/Makefile
-LINUX_VERSION:=2.6.37.6
+LINUX
Hello guys,
I applied the 3 patches about ubifs support on kirkwood successfully.
Many thanks Daniel
I am using linux kernel 2.6.37.6 and mtd-ults 1.4.5.
When erasing, flashing and mounting the first time with mtd-utils from
an initramfs openwrt , it goes well.
After some umount/mount sequences,
Enable ubifs on kirkwood (tested it with SheevaPlug).
Signed-off-by: Daniel Golle
Index: target/linux/kirkwood/image/ubinize.cfg
===
--- target/linux/kirkwood/image/ubinize.cfg (revision 0)
+++ target/linux/kirkwood/image/ubiniz
