Re: [Gumstix-users] What is mtdblock0 on the overo earthlinux-omap3-2.6.29 build

[Steve S. <sa...@gm...>]

On Wed, Apr 22, 2009 at 9:31 AM, Victor Andres <vi...@cy...> wrote:
> Hi Elvis,
>
> I really don't know what could be the problem, but when I start my Overo I
> get the following mtdblock0 errors (using the prebuilding Image v0.92
> http://www.gumstix.net/overo-gm-images/v0.92/)
>
> ....
> Freeing init memory: 940K
> mmc1: mmc_rescan - card ocr from io_op=0x00000000, err = -110
> INIT: version 2.86 booting
> Starting udevend_request: I/O error, dev mtdblock0, sector 0
> Buffer I/O error on device mtdblock0, logical block 0
> uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector 8
> Buffer I/O error on device mtdblock0, logical block 1
> uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector 16
> Buffer I/O error on device mtdblock0, logical block 2
> end_request: I/O error, dev mtdblock0, sector 24
> Buffer I/O error on device mtdblock0, logical block 3
> end_request: I/O error, dev mtdblock0, sector 0
> Buffer I/O error on device mtdblock0, logical block 0
> ads7846 spi1.0: touchscreen, irq 274
> ads7846 spi1.0: no device detected, test read result was 0x00000000
> ...

These messages are normal and are due to the fact that the x-load
partition is written using hwecc, rather than the swecc that linux
expects.

hwecc is a requirement of the OMAP3 bootloader so there is no
workaround for this, you just have to live with the messages :-)

Steve