Pogoplug v2 hosed by installing uboot-env?

Discussion about U-Boot and the kernel.

Re: Pogoplug v2 hosed by installing uboot-env?

Postby fastenova » Mon Sep 30, 2013 11:56 pm

Heh, so on my pogoplug E02 that's working perfectly, from a SSH session, running fw_printenv, I get: "Too few good blocks within range".

Contents of /etc/fw_env.config:

[root@web ~]# cat /etc/fw_env.config
# Configuration file for fw_(printenv/saveenv) utility.
# Up to two entries are valid, in this case the redundand
# environment sector is assumed present.
# MTD device name Device offset Env. size Flash sector size
#/dev/mtd2 0x0000 0x20000 0x20000
# segate dockstar:
# /dev/mtd0 0xc0000 0x20000 0x20000
# iomega iconnect
# /dev/mtd0 0xa0000 0x20000 0x20000
# CuBox
# /dev/mtd0 0xc0000 0x10000 0x10000
/dev/mtd0 0xc0000 0x200000 0x20000


So I can't easily access the environment variables for my working plug to set them in the non-working one. Ideas?

Thanks!


[EDIT]: I corrected the bad value - /dev/mtd0 0xc0000 0x200000 0x20000
fastenova
 
Posts: 13
Joined: Tue Sep 24, 2013 5:29 pm

Re: Pogoplug v2 hosed by installing uboot-env?

Postby fastenova » Tue Oct 01, 2013 12:44 am

I was able to copy the entire environment variable list over and save it, then reset. With no usb drive plugged in it booted to a shell and has the pogoplug hostname so it looks like the factory image is booting. Time to plug into the network and reinstall.

Thanks a million for the help!
fastenova
 
Posts: 13
Joined: Tue Sep 24, 2013 5:29 pm

Re: Pogoplug v2 hosed by installing uboot-env?

Postby grayman4hire » Tue Oct 01, 2013 4:14 pm

That's good news @fastenova.

Any ideas how the uboot env got wiped? It would be nice to know so other users don't accidentally do it themselves.
grayman4hire
 
Posts: 350
Joined: Sat Sep 29, 2012 12:03 am
Location: SF, CA

Re: Pogoplug v2 hosed by installing uboot-env?

Postby fastenova » Tue Oct 01, 2013 4:24 pm

Honestly, I have no clue. The values that were in there were about 10% of what I had to type in, including some that were replaced. Does not make a lot of sense to me. Is there any way that one could run the fw_setenv to reset the environment variables somehow? I know you can use 'setenv variablename' to clear the value assigned to 'variablename' but how it could wipe out everything is beyond me.

Only thing I can think of is if there was some failsafe in the original uBoot image that if it fails, it either boots to another environment or it runs a command to reset the firmware env to defaults... But I wouldn't know anything about that, honest - you guys would know better than I would!

In any case, it's up and running, thanks to you!

Cheers,
Aaron
fastenova
 
Posts: 13
Joined: Tue Sep 24, 2013 5:29 pm

Previous

Return to U-Boot/Kernel

Who is online

Users browsing this forum: No registered users and 8 guests