• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1]
1  Hardware and U-Boot firmware / U-Boot stuff / Re: uboot-envtools on: October 08, 2010, 02:23:53 PM
SOLVED "too many errors in block #0 of chunk #0" problem:

as I suspected was mtdpart mapping related:

this was my bootargs setting in uboot
Code:
rootfstype=jffs2 console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) root=/dev/mtdblock1 rw

mtd partition was speficied in uboot and the "u-boot" mtdpart was absent

the solution is to completly remove the mtdparts option from bootargs

IMPORTANT: if you do that you must speficy root=/dev/mtdblock2  because now rootfs is the third part:

Code:
cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00400000 00020000 "uImage"
mtd2: 1fb00000 00020000 "root"
2  Hardware and U-Boot firmware / U-Boot stuff / Re: new uboot version 3.4.25 on: October 08, 2010, 02:12:52 PM
Quote from: pingtoo on January 07, 2010, 09:19:10 PM
There is limit in mmc code. it can only address at most 4GB-something(which I have not exactly figure out) from beginning of a partition. So for example if you have 8GB SD, divide in to 2 partitions each 4GB, then you most likely OK with in u-boot, the mmc command set can address up to 4GB-(1 x ext2 block size) for sure, so unless you happen to have your object in that last block.

However if you divide your partitions to one greater then 4GB and the other one less then 4GB and if you wish use u-boot to access then you better put your object in the smaller partition.

i have a 16Gb SD with a single big partition
a dumb but easy solution I adopted is to copy the uImage in the root dir so a low inode will be assigned and u-boot will correctly load the kernel with:
ext2load mmc 0 0x800000 /uImage
instead of
ext2load mmc 0 0x800000 /boot/uImage
3  Hardware and U-Boot firmware / U-Boot stuff / Re: uboot-envtools on: October 01, 2010, 07:34:57 AM
e-squizo about the "too many errors in block #0 of chunk #0" problem

i think the problem is related to mtdpart mapping

in my system (original sheevaplug with mainline kernel in nand) i've got the same problem

if I do:
Code:
cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00400000 00020000 "uImage"
mtd1: 1fb00000 00020000 "rootfs"

mtd0 should be "uboot" to work, right?

I think my problem is related to "bootargs" parameter in u-boot
Code:
rootfstype=jffs2 console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=192.168.1.9:192.168.1.4:192.168.1.4:255.255.255.0:DB88FXX81:eth0:none

but i must have 3 mtdparts: "uboot", "uImage", "rootfs", right?

any ideas how to correct this? thanks
4  Linux Stuff / Kernel / Re: SD card support on: October 22, 2009, 03:14:31 AM
any news on this topic?
i have a crappy 32Gb no-brand SD with the same problem, recompiled the latest 2.6.31.4 with also this patch
http://plugcomputer.org/plugforum/index.php?topic=352.0
but it didn't work...
should i try opening the plug or it's useless?
5  Linux Stuff / Kernel / Re: 2.6.30.6 new release on: September 10, 2009, 04:00:37 AM
Hi, sorry for this dumb question but I'm a total newbie!
This releases are for "normal" plug, or plug modified with "sheevaplug installer alpha-6"?
thanks
Pages: [1]