Debian on Netgear Stora

with stock U-Boot I had some problems getting debian running on this box.
so I tried to cleaning out the U-Boot env but this results in an env overflow

I tested and flashend the newest U-Boot and it's running fine

U-Boot 2014.07-tld-2 (Sep 20 2014 - 01:22:13)
Netgear-MS2110

SoC:   Kirkwood 88F6281_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
PHY reset timed out
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0

but I noticed that with stock and this U-Boot the kernel recognizes more bad blocks as it should .. there are only two.

I had this erlier with some other box but I didn't remember how I fixed it.
I also found an older thread with the same issue:

http://forum.doozan.com/read.php?3,6910,7752

its a "MS2000-100PES" and I think that I use the right DTB (kirkwood-netgear_stora_ms2000.dtb)

any hints?

pengu Wrote:
-------------------------------------------------------
> with stock U-Boot I had some problems getting
> debian running on this box.
> so I tried to cleaning out the U-Boot env but this
> results in an env overflow
>
> I tested and flashend the newest U-Boot and it's
> running fine
>
>

> U-Boot 2014.07-tld-2 (Sep 20 2014 - 01:22:13)
> Netgear-MS2110
> 
> SoC:   Kirkwood 88F6281_A1
> DRAM:  128 MiB
> WARNING: Caches not enabled
> NAND:  256 MiB
> In:    serial
> Out:   serial
> Err:   serial
> Net:   egiga0
> PHY reset timed out
> 88E1116 Initialized on egiga0
> Hit any key to stop autoboot:  0 
>

>
> but I noticed that with stock and this U-Boot the
> kernel recognizes more bad blocks as it should ..
> there are only two.
>
> I had this erlier with some other box but I didn't
> remember how I fixed it.
> I also found an older thread with the same issue:
>
> http://forum.doozan.com/read.php?3,6910,7752
>
> its a "MS2000-100PES" and I think that I use the
> right DTB (kirkwood-netgear_stora_ms2000.dtb)
>
> any hints?

What the error message look like? Did it say "too many bad blocks/ too few good blocks" or did it show individual bocks?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 09/02/2015 04:53PM by bodhi.

that's what I get when I try to read the env (fw_printenv)

>
> What the error message look like? Did it say "too
> many bad blocks/ too few good blocks" or did it
> show individual bocks?

before that, it seems that all blocks on nand were bad blocks:

...

[   11.535624] Bad eraseblock 2037 at 0x00000fea0000
[   11.540388] Bad eraseblock 2038 at 0x00000fec0000
[   11.545172] Bad eraseblock 2039 at 0x00000fee0000
[   11.549936] Bad eraseblock 2040 at 0x00000ff00000
[   11.554720] Bad eraseblock 2041 at 0x00000ff20000
[   11.559484] Bad eraseblock 2042 at 0x00000ff40000
[   11.564269] Bad eraseblock 2043 at 0x00000ff60000
[   11.569033] Bad eraseblock 2044 at 0x00000ff80000
[   11.573794] Bad eraseblock 2045 at 0x00000ffa0000
[   11.578578] Bad eraseblock 2046 at 0x00000ffc0000
[   11.583343] Bad eraseblock 2047 at 0x00000ffe0000
[   11.588109] 2 cmdlinepart partitions found on MTD device orion_nand
[   11.594428] Creating 2 MTD partitions on "orion_nand":

This problem with "too few good blocks within range" has been solved for other Kirkwood boxes. But perhaps I missed it in the Stora! Will take a look.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

@pengu,

Try booting with this DTB.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

booted with new DTB:

[    1.884855] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xda
[    1.891247] nand: Samsung NAND 256MiB 3,3V 8-bit
[    1.895926] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    1.903550] Scanning device for bad blocks
[    1.988351] Bad eraseblock 751 at 0x000005de0000
[    2.022252] Bad eraseblock 1024 at 0x000008000000
[    2.136915] 2 cmdlinepart partitions found on MTD device orion_nand
[    2.143213] Creating 2 MTD partitions on "orion_nand":

thanks a lot bodhi ;-))


the U-Boot env is also readable via fw_printenv but write isn't possible:

Read error on /dev/mtd1: Success
Error: can't write fw_env to flash

I saw the same error an the new arrived NSA320



Edited 1 time(s). Last edit at 09/04/2015 06:16AM by pengu.

pengu,

> the U-Boot env is also readable via fw_printenv
> but write isn't possible:
>
>

> Read error on /dev/mtd1: Success
> Error: can't write fw_env to flash
>

>
> I saw the same error an the new arrived NSA320

The kernel might have set the default access for mtd0 to RO. I'll check.

Yes, it did for the Stora. But the NSA320 should be OK.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 09/04/2015 01:57PM by bodhi.

Here is another DTB version. Pls try. u-boot envs should be writeable now.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

sorry I'll test it later.
the write problem exists on other boxes so I'll first fix this there.

Edit
ok ..looks like an error in the fw_env.config
now writing is possible on the Stora

seems that the first modification which let's the 2047 bad blocks gone awas is enough, but I can test the second one too

Edit 2

the last modification is also working ;-)



Edited 4 time(s). Last edit at 09/05/2015 09:14AM by pengu.

pengu,

> the write problem exists on other boxes so I'll
> first fix this there.

Other boxes should have mtd0 writeable already.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)