How to unbrick GoFlex Home?

I have a GoFlex Home that won't boot. I've connected it to a terminal via a USB to UART, but I can't get any output from the device.

(I've tested that the CP2102 interface works, because messing with the TxD and RxD gives me junk values on the screen. Also, all the indicators on my CP2102 interface are active so there's nothing wrong with the physical connection.)

The GoFlex however, just keeps blinking the green light forever, with no output to the serial console. I think my GoFlex is bricked.

What created this problem? Probably when I accidentally typed the commands:

fw_setenv help
fw_setenv -help

Neither of these gave me any output and when I rebooted it just got stuck on the infinite blinking green light.

Is my GoFlex actually bricked?

In reply to https://forum.doozan.com/read.php?3,12381,12381#msg-12381

shayan123,


> I have a GoFlex Home that won't boot. I've
> connected it to a terminal via a USB to UART, but
> I can't get any output from the device.
>
> (I've tested that the CP2102 interface works,
> because messing with the TxD and RxD gives me junk
> values on the screen. Also, all the indicators on
> my CP2102 interface are active so there's nothing
> wrong with the physical connection.)

That's a good first step. You need to know that your serial console works before trying to unbrick this.

>
> The GoFlex however, just keeps blinking the green
> light forever, with no output to the serial
> console. I think my GoFlex is bricked.

When it is blinking, the box might be OK. So I would try to verify that CP2102 works again. Try loop back the TX and RX to see what you type appear on you serial console terminal.

> What created this problem? Probably when I
> accidentally typed the commands:
>

> fw_setenv help
> fw_setenv -help
>

Those were unlikely the problem.

> Is my GoFlex actually bricked?

I don't think it is bricked beyond recovery.

=====

Try to boot with kwboot as described in this post:

https://forum.doozan.com/read.php?3,51739,51919#msg-51919

The example in the link post above was for the Zyxel NSA310S. But it is applicable to the GoFlex Home just the same using a different u-boot image.

Instead of
uboot.2017.07-tld-1.nsa310s.mtd0.kwb

You would use
uboot.2017.07-tld-1.goflexnet.mtd0.kwb

So download that tarball:
uboot.2017.07-tld-1.goflexhome.bodhi.tar

Use the instruction to kwboot your Goflex Home. See if you can do that and we'll continue from there.

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

Okay, obtained the kwb and set up kwboot.
I put in the kwboot command and it says "Please reboot the target into UART boot mode".
How do I do that? I've tried executing the command when the GoFlex is off, on and in recovery. Neither of them work.

Also, correction: serial console doesn't show the Tx or Rx indicator as active. (Previously, the metal plate below the GoFlex board was causing both Tx and Rx to light up simultaneously.) Now just Ground lights up.

shayan123,

>"Please reboot the target into UART boot mode".

Unplug power, start kwboot, and then power on the unit.

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

Havent used your firmware link yet, I was looking at the booting of the current stock firmware via serial console. There is no mention of Kirkwood. It is definitely a Seagate GoFlex Home (REV 01) but U-boot says:

	 -- NAS EXPLORER --
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_ 
| | | |___|  _ \ / _ \ / _ \| __| 
| |_| |___| |_) | (_) | (_) | |_ 
 \___/    |____/ \___/ \___/ \__| 
 ** QSI BOARD: NAS-PLUG LE 

U-Boot 1.1.4 (Sep 26 2011 - 13:01:13) Marvell version: 3.4.27
QSI NAS version: 1.0.6

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6281 A1 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz 

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 128MB 
DRAM Total size 128MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:NAND READID : MID=0x98, DID=0xda
256 MB
*** Warning - bad CRC or NAND, using default environment

Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled 
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  3  2  1  0 
Using egiga0 device
TFTP from server 169.254.254.254; our IP address is 169.254.254.253
Filename 'uImage'.
Load address: 0x2000000
Loading: *T T T T T T T T T T 
Retry count exceeded; starting again
## Booting image at 02000000 ...
Bad Magic Number
Unknown command '<NULL>' - try 'help'
NAS>>

Right there:

CPU : Marvell Feroceon (Rev 1)

Should I just ignore this and assume all Kirkwood related content works with this device? Could using Kirkwood based firmware make things worse?

shayan123,

Quote

Soc: 88F6281 A1 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

Quote

CPU : Marvell Feroceon (Rev 1)

It is a Kirkwood. Either this stock u-boot has been replaced by somebody, or this is some newer version of stock that I vaguely remember seeing somewhere (but not sure).

> Should I just ignore this and assume all Kirkwood
> related content works with this device?

That's what I would do.

> Could using Kirkwood based firmware make things worse?

I'd doubt it will make it worse, it should make it better. But use your own judgement here :) as long as you can kwboot the box with my new u-boot, you are quite safe. Don't flash it yet until you have confidence that it is running OK. You can boot Debian on USB/HDD drive by booting with kwboot.

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

Write allocate disabled

Does this have anything to do with the GoFlex not being able to accept input?
I can see U-boot outputting it’s banners and all, but I can’t send commands to the device.

I assume it’s either the “Write allocate disabled” message during boot or the burnt PCB hole.

shayan123 Wrote:
-------------------------------------------------------
>

> Write allocate disabled
>

>
> Does this have anything to do with the GoFlex not
> being able to accept input?
> I can see U-boot outputting it’s banners and
> all, but I can’t send commands to the device.
>
> I assume it’s either the “Write allocate
> disabled” message during boot or the burnt PCB
> hole.

Please post the entire serial console log here.

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

That is the entire log (4 posts above)
I can’t give any user input so I can’t interrupt the boot. I’m not sure if it’s due to a software side issue or the burnt PCB connector.

From the log above:

...
CPU : Marvell Feroceon (Rev 1)

Streaming disabled 
Write allocate disabled
...

Right there: "Write allocate disabled". Does that have anything to do with this?

shayan123,

> I can’t give any user input so I can’t
> interrupt the boot. I’m not sure if it’s due
> to a software side issue or the burnt PCB
> connector.

Not software.

> Streaming disabled
> Write allocate disabled

No, it is normal to see this output from stock u-boot.

====

Of course, it is impossible to send command to the GF Home if you don't connect its RXD pin. From the pic you posted above, only GND and TX are connected.

If that RX pin was burnt out and cannot be used, then you cannot boot with kwboot. You will need to boot stock u-boot into stock OS or new Debian rootfs, and then flash new u-boot from there. That's what you should do, because with new u-boot you can gain back most input control to the boot process by using netconsole and uEnv.txt.

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

shayan123 Wrote:
-------------------------------------------------------
> I have a GoFlex Home that won't boot. I've
> connected it to a terminal via a USB to UART, but
> I can't get any output from the device.
>
> (I've tested that the CP2102 interface works,
> because messing with the TxD and RxD gives me junk
> values on the screen. Also, all the indicators on
> my CP2102 interface are active so there's nothing
> wrong with the physical connection.)

I have several GoFlex Home units but always struggle getting a good connection with the pins or holes on the base unit. What sort of connector do you use? The Dupont connectors I have are loose and need to held in place - the slightest knock and they fall out... just wondered if the was a specific ten pin connector which would stay firmly in place...

balanga
> What sort of connector
> do you use? The Dupont connectors I have are loose
> and need to held in place - the slightest knock
> and they fall out... just wondered if the was a
> specific ten pin connector which would stay firmly
> in place...

Lol, I really don’t do a lot of this serial console stuff so I don’t even have the right dupont connectors. I had to find a make-shift solution to this problem, so I just use a bunch of paper clips with a bit of excess solder around them to hold them in place. Tilt them at an angle and should be just enough to hold them in place and get a stable connection. You can even use a dab of hot glue if they’re still shaky. (Sorry if this sounds like a really rookie way to do it, It’s the only way I could think of)

But yeah, I’m even I figured there has to be some sort of 10-pin connector that fits into this hassle-free. You could probably check the markets in your city for this stuff, (or maybe AliExpress or something, they seem like they’d have a lot of this stuff)

Wiki thread:
https://forum.doozan.com/read.php?2,23630

Serial Console & JTAG console 

Repair Pogo E02 with Raspberry PI (JTAG) and OpenOCD 
Serial Port connector - what are people using to make it work 
Serial Console hookup - GoFlex Net (external link) 
Serial Console hookup - Pogoplug E02 and Pogoplug Pro V3 (external link) 
OSX Serial/Net Console 
Use Phone Jack - Phone Jack Serial Console Pics 
Adding serial connector to Pogoplug Mobile (external link) 
WD Mycloud EX2100/4100 Serial Console pic1, also pic2, pic3 
Dreamplug Serial Console 
How to unbrick your box using serial console with kwboot

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

shayan123 Wrote:
-------------------------------------------------------
> Lol, I really don’t do a lot of this serial
> console stuff so I don’t even have the right
> dupont connectors. I had to find a make-shift
> solution to this problem, so I just use a bunch of
> paper clips with a bit of excess solder around
> them to hold them in place. Tilt them at an angle
> and should be just enough to hold them in place
> and get a stable connection. You can even use a
> dab of hot glue if they’re still shaky. (Sorry
> if this sounds like a really rookie way to do it,
> It’s the only way I could think of)

I know what you mean by tilting paper clips at an angle but sometimes you need to hold on to them whilst connecting and if you let go you break the connection....

....and sometimes you just can't find the right angle :(...


> But yeah, I’m even I figured there has to be
> some sort of 10-pin connector that fits into this
> hassle-free. You could probably check the markets
> in your city for this stuff, (or maybe AliExpress
> or something, they seem like they’d have a lot
> of this stuff)

Trouble is finding out what such a connector looks like or what it is called.

balanga Wrote:

> I know what you mean by tilting paper clips at an
> angle but sometimes you need to hold on to them
> whilst connecting and if you let go you break the
> connection....
>
> ....and sometimes you just can't find the right
> angle :(...

Like I said, a bit of excessive solder or a dab of hot glue on the tips should help hold it in place. I've tried it and works like a charm.

> Trouble is finding out what such a connector looks
> like or what it is called.

It's the internet mate, everything's there, just takes a bit of searching! Check this one out: 10-pin connector on AliExpress (and its barely a dollar)

shayan123 Wrote:
-------------------------------------------------------
> It's the internet mate, everything's there, just
> takes a bit of searching! Check this one out:
> 10-pin
> connector on AliExpress (and its barely a
> dollar)


Thanks. As I said you need to know what you are looking for...

I don't know the diameter of the pins (or holes) and the spacing between them, or type of connector.

I would probably be able to find someting here:-
http://www.jst.com/home8.html
but it's like looking for a needle in a haystack.


.....

After rummaging about in my old computer cables drawer I found some old cables which happened to have 5x2 connectors which fitted perfectly and created a much more solid connection.



Edited 1 time(s). Last edit at 06/09/2018 12:20PM by balanga.

These connectors are called JST 2.0. The smaller one is called micro JST.

I would recommend you guys read the post and section that I posted above. There are more than enough information in there, no need to search anywhere.

https://forum.doozan.com/read.php?3,60909,61504#msg-61504

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

Also, on the GoFlex Home, if it has the header preistalled (some GFHomes have) you don't need to find the 10 pin header cable, use the CD Audio Blaster cable to connect would be fine.

If your GF Home has only solder holes, then you need to solder the JST header in. If you don't like soldering, then just use 3 male-female test wires (male to the board holes, female to the Serial Module CP2xxx).

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



Edited 2 time(s). Last edit at 06/09/2018 05:02PM by bodhi.

bodhi Wrote:
-------------------------------------------------------

> Of course, it is impossible to send command to the
> GF Home if you don't connect its RXD pin. From the
> pic you posted above, only GND and TX are
> connected.
>
> If that RX pin was burnt out and cannot be used,
> then you cannot boot with kwboot.

Okay, I've managed to fix the burnt out Rx port with a bit of soldering. Ive tested this by interrupting boot on my stock firmware.

However, when I try using kwboot with the following command:

kwboot  -t -B 115200 /dev/tty.SLAB_USBtoUART -b /Volumes/HDD/Users/shayan/Desktop/Projects/GoFlex/UART/uboot.2017.07-tld-1.goflexhome.mtd0.kwb -p

its just an endless "Please reboot the target into UART boot mode..."

Ive tried rebooting into UART as you mentioned above:
>Unplug power, start kwboot, and then power on the unit.

kwboot doesn't do anything when I do this. Am I doing it wrong?

shayan123 Wrote:
-------------------------------------------------------
> bodhi Wrote:
> -------------------------------------------------------
>
> > Of course, it is impossible to send command to
> the
> > GF Home if you don't connect its RXD pin. From
> the
> > pic you posted above, only GND and TX are
> > connected.
> >
> > If that RX pin was burnt out and cannot be
> used,
> > then you cannot boot with kwboot.
>
> Okay, I've managed to fix the burnt out Rx port
> with a bit of soldering. Ive tested this by
> interrupting boot on my stock firmware.

At this point you can run some commands such as printenv at stock u-boot prompt?

>
> However, when I try using kwboot with the
> following command:
>

> kwboot  -t -B 115200 /dev/tty.SLAB_USBtoUART -b
> /Volumes/HDD/Users/shayan/Desktop/Projects/GoFlex/UART/uboot.2017.07-tld-1.goflexhome.mtd0.kwb
> -p
>

> its just an endless "Please reboot the target into
> UART boot mode..."

> kwboot doesn't do anything when I do this. Am I
> doing it wrong?

I'm not sure what you meant here. Is the message above repeated endlessly, or nothing happened?

Please post the log of your kwboot attempt here (copy/paste the entire terminal session).

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

bodhi Wrote:
-------------------------------------------------------

> Please post the log of your kwboot attempt here
> (copy/paste the entire terminal session).

Shayans-MacBook-Air:~ shayan$ kwboot  -t -B 115200 /dev/tty.SLAB_USBtoUART -b /Volumes/HDD/Users/shayan/Desktop/Projects/GoFlex/UART/uboot.2017.07-tld-1.goflexhome.mtd0.kwb -p
Please reboot the target into UART boot mode...\

> I'm not sure what you meant here. Is the message above repeated endlessly, or nothing happened?

Sorry I mean to say "nothing is happening beyond this". It displays the above message and after that nothing happens when I follow this process:
> Unplug power, start kwboot, and then power on the unit.



Edited 1 time(s). Last edit at 07/06/2018 04:32AM by shayan123.

bodhi Wrote:
-------------------------------------------------------
> shayan123 Wrote:
> -------------------------------------------------------
> > bodhi Wrote:
> >
> -------------------------------------------------------
> >
> > > Of course, it is impossible to send command
> to
> > the
> > > GF Home if you don't connect its RXD pin.
> From
> > the
> > > pic you posted above, only GND and TX are
> > > connected.
> > >
> > > If that RX pin was burnt out and cannot be
> > used,
> > > then you cannot boot with kwboot.
> >
> > Okay, I've managed to fix the burnt out Rx port
> > with a bit of soldering. Ive tested this by
> > interrupting boot on my stock firmware.
>
At this point you can run some commands such as
printenv at stock u-boot prompt?

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

bodhi Wrote:

> At this point you can run some commands such
> as
> printenv at stock u-boot prompt?


Yes, I can. But the real issue is, I can't get it to boot successfully, This is what I always get:

-- NAS EXPLORER --
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_ 
| | | |___|  _ \ / _ \ / _ \| __| 
| |_| |___| |_) | (_) | (_) | |_ 
 \___/    |____/ \___/ \___/ \__| 
 ** QSI BOARD: NAS-PLUG LE 

U-Boot 1.1.4 (Sep 26 2011 - 13:01:13) Marvell version: 3.4.27
QSI NAS version: 1.0.6

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6281 A1 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz 

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 128MB 
DRAM Total size 128MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:NAND READID : MID=0x98, DID=0xda
256 MB
*** Warning - bad CRC or NAND, using default environment

Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled 
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  3  2  1  0 
Using egiga0 device
TFTP from server 169.254.254.254; our IP address is 169.254.254.253
Filename 'uImage'.
Load address: 0x2000000
Loading: *T T T T T T T T T T 
Retry count exceeded; starting again
## Booting image at 02000000 ...
Bad Magic Number
Unknown command '<NULL>' - try 'help'
NAS>>

I've tried flashing using the method described on the Seagate website but no luck. This is what happens when I flash using the Seagate method:

<Explorer> Enter USB firmware instllation by RESET IO.
USB:   scanning bus for devices... 2 USB Device(s) found
T Device NOT ready
   Request Sense returned 00 00 00
1 Storage Device(s) found
Device NOT ready
   Request Sense returned 00 00 00
** Can't read from device 0 **

** Unable to use usb 0:1 for fatload **
<Explorer> Firmware installation error(3)!
<Explorer> Please power off system retry again!

I have only one device (with only 1 partition) plugged in but it says 2 USB devices found
Also, I have no idea what Error code 3 means.

What would be the best way to fix this? (I mean, I just need the GoFlex to work like it used to)

BTW, my envs look like this: (See attachment)

shayan123,

> Yes, I can. But the real issue is, I can't get it
> to boot successfully, This is what I always get:

> *** Warning - bad CRC or NAND, using default
> environment

Your envs were corrupted for whatever reason. So you cannot boot to stock OS or any OS. That CRC error means the NAND space (usually 128K) that contains the envs were wiped out, or messed up.

> What would be the best way to fix this? (I mean, I
> just need the GoFlex to work like it used to)

You have only used this box as stock, and never install Debian or Arch on this box?

> BTW, my envs look like this: (See attachment).

I usually need to see them in the post (atachement is not very good way to post envs) to avoid loosing trend of thoughts. So I post them here with MAC address removed

baudrate=115200
loads_echo=0
ipaddr=169.254.254.253
serverip=169.254.254.254
rootpath=/mnt/ARM_FS/
netmask=255.255.0.0
run_diag=yes
stdin=serial
stdout=serial
stderr=serial
console=console=ttyS0,115200
mainlineLinux=no
CASset=min
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
MALLOC_len=1
ethprime=egiga0
netbsd_en=no
vxworks_en=no
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
bootcmd=tftpboot 0x2000000 $(image_name); setenv bootargs $(console) $(bootargs_root) nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvNetConfig) $(mvPhoneConfig);  bootm 0x2000000; 
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
bootdelay=3
disaMvPnp=no
ethaddr=xxxxxxxxxxxxxx
ethmtu=1500
usb0Mode=host
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
enaAutoRecovery=yes
pcieTune=no
ethact=egiga0

The above are default envs inside u-boot (not the correct envs in NAND), so the box always tries to use tftp to load the kernel files. With stock FW, the kernel files are in NAND. That's what this error means

Quote

TFTP from server 169.254.254.254; our IP address is 169.254.254.253
Filename 'uImage'.
Load address: 0x2000000
Loading: *T T T T T T T T T T
Retry count exceeded; starting again
## Booting image at 02000000 ...

If you want to restore the box to stock condifition, you will need to use the reset button approach. As you have tried

Quote

I've tried flashing using the method described on the Seagate website but no luck. This is what happens when I flash using the Seagate method:

======


You have 2 choices:

1. If you want to keep running stok OS. Find somewhere that has the list of the GoFlex Home stock envs and reapply them in serial console at u-boot prompt. And then save them. After that the envs are restored.

2. If you want to run Debian on USB or HDD, try to boot into Debian using a USB drive. This will be a ittle more works, as you have to set the new envs to do that.

Let me know which way you prefer and I might be able find the envs for you. Or someone could.

For choice 1, I don't have this FW version (my GFH boxes are much older so what I have in my old notes might not work).

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

The main reason I started tinkering with my GFH was because I wanted CUPS on it. So I suppose Debian is a better choice.

I'm not sure how to proceed (considering that my envs are currently messed up).
If I decide to install Debian, do I need to fix the envs first?

Also, is it possible to run CUPS and avahi on stock firmware?

If you want to run cups / avahi , better get a Rpi zero W. For $5, you get much better performance, much smaller foot print and less energy...

Goflex home is a good general purpose NAS for home.



Edited 1 time(s). Last edit at 07/11/2018 07:29PM by daviddyer.

shayan123 Wrote:
-------------------------------------------------------
> The main reason I started tinkering with my GFH
> was because I wanted CUPS on it. So I suppose
> Debian is a better choice.

True.

> I'm not sure how to proceed (considering that my
> envs are currently messed up).
> If I decide to install Debian, do I need to fix
> the envs first?

No need to fix them. But you need a few new envs to boot Debian on USB.

> Also, is it possible to run CUPS and avahi on
> stock firmware?

Dont know. It’s been too long ago I can’t remember.

Create the USB rootfs first;
https://forum.doozan.com/read.php?2,12096

After you’ve done with rootfs, I will be back to show you which envs you need.

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

bodhi Wrote:
> Create the USB rootfs first;
> https://forum.doozan.com/read.php?2,12096
>
> After you’ve done with rootfs, I will be back to
> show you which envs you need.

Okay, I have the tarball on a FAT32 (MBR) formatted USB. I assume I can't access the /boot unless I correct my envs?

shayan123,

See this release thread:
https://forum.doozan.com/read.php?2,12096

Quote

Latest released rootfs: Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (24 Jul 2017)

Scroll down to section:

Quote

Updated 24 Jul 2017:

Basic Debian stretch Kirkwood rootfs for most Kirwood plugs:

- tarball size: 188M
- install size: 488M
- The init system used in this rootfs is sysvinit . To boot with systemd, see note 2 below.
- Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, dialog, bzip2, nfs server/client, iperf, ethtool, sysvinit-core, sysvinit, and sysvinit-utils.
- see LED controls in /etc/rc.local, and /etc/init.d/halt
- see some useful aliases in /root/.profile
- root password: root

Download at Dropbox:

Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2

md5:
bf3d29569943875df348fb5ca03b348c
sha256:
4ed5714fdb123cdb40e973f3d0754e91cd199b75a9874018f2b5dc9cfa8ae8bb

Follow the instruction to create this rootfs on USB.

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

The guide here describes how to install Debian over SSH but currently, I can't get SSH to work. I think I need to fix my envs before attempting to install Debian.

bodhi Wrote:
-------------------------------------------------------
> For choice 1, I don't have this FW version (my GFH
> boxes are much older so what I have in my old
> notes might not work).

I wouldn't mind giving these a try. I don't suppose the envs could be that different.