davygravy Wrote:
> Your host that you were booted into is called
> "rescue". Is this a NAND rescue that you were
> booted into, or a USB rescue? (flashing your NAND
> while booted from NAND usually doesn't work)

And is it possible for you to upload that environment, where you've compiled all that stuff (openvpn, busybox, e.t.c.), because I've tried to copy some programs from USB with debian, it seems to be OK if I will copy some libraries as well, but libraries on USB debian installation are newer and bigger, therefore it takes much more space, so I would like to compile some programs myself but I would need the same libraries you have used for rescue image.

How did you make udhcpc do its stuff before ntpdate? I'm having a hard time figuring out how to make ntpd run before udhcpc? I tried adding delay but the kernel always waits for ntpd to come up before executing udhcpc. Any ideas?

Have a couple of questions:
1. Can it be installed from u-boot with tftp? I'm having problem starting Debian on USB.
2. Once inside the rescue system, is it possible to install Debian on USB using http://projects.doozan.com/debian/?

Quotedavygravy
kk, thank you for the offer for the patch... actually, 30 minutes and some testing seems to have done it (just took the ALARM support patch and pulled out the two Pogo sections, added/modified two lines or so in each)... I now have a version 2.8.1 that extends arcNumber support for the Pogo_e02 and pogoplugv4 by their given arcNumbers...

I tested it in the PogoE02 and it works fine - setting arcNumber to 3542 enables proper LED behavior. I haven't tested it on the mtd function w/ this patch, but it shouldn't have changed anything wrt mtd.

hi all,
I successfully installed rescue system v2.8.1 on my PogoE02 (pink), and also Debian Wheezy on USB device.
They both work, but LED configuration is not fine.
In fact, in

/sys/class/leds

I only have:

plug:green:health

and

plug:red:misc

I can just switching on/off the led with orange color changing (echo..) trigger value of plug:green:health to default-on/none.
This behaviour both occur on rescue system (installed from archive at first post RescueV2.8.1-05282012.tar.gz), whose kernel is:

hi all,
here are further steps I made, about issue of LED not properly set on Pogoplug E02, using rescue.

Please consider I'm quite a noob at these things, so forgive me if what I write here is not correct.

Having a look at content of rescue source file referenced at first post (custom-RescueV2.8.1.tar.gz), whitin the config file of buildroot (buildroot-config) it's also se the kernel config to be used:

#
# Kernel
#
BR2_LINUX_KERNEL=y
# BR2_LINUX_KERNEL_2_6_34 is not set
# BR2_LINUX_KERNEL_SAME_AS_HEADERS is not set
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
# BR2_LINUX_KERNEL_CUSTOM_TARBALL is not set
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="3.3.2"
BR2_LINUX_KERNEL_VERSION="3.3.2"
BR2_LINUX_KERNEL_PATCH="custom/linux-3.3.2-wide"
# BR2_LINUX_KERNEL_USE_DEFCONFIG is not set
BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="custom/linux-3.3.2-config"
BR2_LINUX_KERNEL_UIMAGE=y
# BR2_LINUX_KERNEL_BZIMAGE is not set
# BR2_LINUX_KERNEL_ZIMAGE is not set
# BR2_LINUX_KERNEL_VMLINUX is not set

In turn, having a look in the kernel config file refernced there (custom/linux-3.3.2-config), I see that the POGO E02 arch (CONFIG_MACH_POGO_E02) is missing:

Anyway, after discovering this, I tried to recompile the 3.3.2 kernel, using instructions found in the kernle 3.3.2 thread (I resumed the procedure I followed in the file attached to this post). Of course, during the menuconfig I enabled the POGO_E02 machine, in this case. The compilation and the install of the kernel was ok, and I was able to start the pogo with my kernel (confirmed by output of "uname -a").

But, apparently the machine arch is not recognized correctly, and the led configuration is the Sheevaplug one (arc=2097).

My fw_env seems to be setted correctly, infact:

root@debian:/var/log# fw_printenv | grep arc
arcNumber=3542

(on the previous post, there is the compite fw_printev output)
But, in my dmseg output, running my custom build kernel, it seems that the wrong machine number is taken into account:

Setting the "machid" variable makes the led behave correctly, both on rescue system (i.e. with the kernel provided by you in the first post) and on my debian install on usb hdd (i.e. with the kernel I rebuilt).
Therefore, the led support was already there, but for some reasons I don't know setting the variable "arcNumber" in uBoot is not effective: the variable that is indeed considered is "machid". The only caveat is that "machid" wants the hex value of the architecture number. In my case (POGO_E02), the corresponding value for arcNumber=3542 is machid=dd6.
Therefore, the only thing to do to enable correct led behaviour was:

/usr/sbin/fw_setenv machid dd6

Maybe this may help also in other cases.

Thanks for your help.

PS: as a side note, while trying setting "machid", the first try I did was to set value 3542, and of course the kernel didn't boot. So I needed to access netconsole to change the value of machid. Being on a windows box, I downloaded the windows port of nc suggested in the netconsole tutorial by Jeff (link), and in fact as explained it worked only in read-only mode. But I found another port of nc that worked interactively even on windows (link; actually not a great discover, being the first result on google for "netcat on windows"!). Maybe this info could be useful to others, too.

The UBoot that I uploaded for Jeff to distribute to the community is a completely functional/tested/working kwb image - save for one detail : the arcNumber setup is not correctly implemented (this is my oversight, not Jeff's).

Edited: I found a USB disk which has ext2+swap partitions on it. I plugged it in the Dockstar, and it booted up with 3.3.3-dockstar-shyd. The USB must have been a backup disk I made more than a year ago.

What should I do now to "Reverse" these commands that I did while booting with the Dockstar's internal boot partition please ?
flash_eraseall /dev/mtd7
nandwrite /dev/mtd7 uImage-mtd1.img
flash_eraseall /dev/mtd8

Thank you everyone for helping me ressucitate my Dockstar .

(I do see it gets assigned IP from the router. But other than that, I can't even ssh/winScp to it if booting with a blank ext2+swap usb key). :( :(

i wanna say thanks your your work, but i had a lot of questions. I have got a Pogo E02 with the Rescue System v2 on it, latest uboot installed trough the sh script and Debian on a USB Stick. Now i want to update to the latest 2.8.2 Rescue System but im not sure if i am right and before i brick my Pogo i want to her if my steps were ok.

No, this is not necessary, since flash_erase and nandwrite are already available
>
... snip ...
>
> So the next steps, after flashing those both
> images i boot into Rescue Mode and enter
>
> run bootcmd_rescue

No, you are way past this point once the rescue system is booted up ...
>
> And the last problem, i got on my pc ubuntu as os,
> but i didnt found anything about the netconsole
> how to use it on thos forum. whalt should i
> exactly do to use it?

Look here and maybe here also
>
> I know, a lot of quesions, ive rtfm but i want to
> be on the right side.
>
> thx

unbelievable, but in spite of the red alert text in the first post, i managed to erase mtd1 and mtd2 on one of my Zyxel NSA320s when trying to install the rescue system (wanted to do everything quickly, since I need to go out for a while in a minute and copy and pasted the wrong commands ...).

Now the machine is still running and I have others with which I could try to remedy the situation if I only knew enough to do so. Therefore, here is what I believe to be the case:

a) mtd1 = uboot_env and mtd2 = key_store (from looking at fw_printenv)
b) uBoot is still there as it is in mtd0

fw_printenv still gives me the values I expect to see, but maybe it does not read directly from /dev/mtd1? What is/dev/mtd2 used for (key_store)? Can I reboot with it overwritten?

If not, will the following help:

1. Extract images of /dev/mtd1 and /dev/mtd2 from another NSA320 (will be a challenge, but google will be my friend ...)
2. Flash those images to the one currently under re-construction

Please, enter the code that you see below in the input field.
This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right.
If you enter the wrong code, a new image is created and you get
another chance to enter it right.