Hello. I'm new to this forum, and fairly new with the Pogoplug, but experienced with Unix/Linux.
I bought a Pogoplug V4-A3-01 that was configured by the previous owner to boot Arch Linux from USB drive. I'm booting debian from SD on my other Pogoplugs, which is what I'd like to do on this one.
I'm not able to see it on my network when I boot to the original Cloud Engines OS, so I booted to Arch Linux, and ran uboot.sh (pulled from http://ssl.pepas.com/pogo/uboot.sh). It says MD5 sums of /bin/busybox and /proc/version don't match, which of course they wouldn't since I'm not running the original OS.
But, I'm thinking it should be safe to do the override of that MD5 check ("export BRICK_MY_POGO=1") and let it do the U-boot update since it IS the correct hardware, but not sure if there are going to be any gotchas since I'm running it under Arch Linux rather than the orig. OS. I did comment out the /sbin/poweroff at the bottom of uboot.sh so I can try to recover while it's still up in case there are any errors running the script.
Do you agree that this should work? This is what I see for current U-Boot version.
[root@alarm ~]# grep -a --null-data U-Boot /dev/mtd0ro
U-Boot 1.1.4 (Oct 1 2011 - 12:06:06) Cloud Engines 1.1.2 (3.4.27) PHYADDR=0If U-Boot Endiannes is going to change (LE->BE or BE->LE), Then Env parameters should be overriden..
U-Boot
** Invalid partition type "%.32s" (expect "U-Boot")
U-Boot code: %08lX -> %08lX BSS: -> %08lX
Addresses %dM - 0M are saved for the U-Boot usage.
U-Boot BUG at %s:%d!
U-Boot 1.1.4 (Jan 13 2012 - 22:33:21) Arch Linux ARM (PPV4 r1) PHYADDR=0If U-Boot Endiannes is going to change (LE->BE or BE->LE), Then Env parameters should be overriden..
U-Boot
** Invalid partition type "%.32s" (expect "U-Boot")
U-Boot code: %08lX -> %08lX BSS: -> %08lX
Addresses %dM - 0M are saved for the U-Boot usage.
U-Boot BUG at %s:%d!
Is this telling me there are two on /dev/mtd0? Will uboot.sh replace them both with just U-Boot 2014.07-tld-1?
Any/all help and suggestions appreciated!
rsantag
I bought a Pogoplug V4-A3-01 that was configured by the previous owner to boot Arch Linux from USB drive. I'm booting debian from SD on my other Pogoplugs, which is what I'd like to do on this one.
I'm not able to see it on my network when I boot to the original Cloud Engines OS, so I booted to Arch Linux, and ran uboot.sh (pulled from http://ssl.pepas.com/pogo/uboot.sh). It says MD5 sums of /bin/busybox and /proc/version don't match, which of course they wouldn't since I'm not running the original OS.
But, I'm thinking it should be safe to do the override of that MD5 check ("export BRICK_MY_POGO=1") and let it do the U-boot update since it IS the correct hardware, but not sure if there are going to be any gotchas since I'm running it under Arch Linux rather than the orig. OS. I did comment out the /sbin/poweroff at the bottom of uboot.sh so I can try to recover while it's still up in case there are any errors running the script.
Do you agree that this should work? This is what I see for current U-Boot version.
[root@alarm ~]# grep -a --null-data U-Boot /dev/mtd0ro
U-Boot 1.1.4 (Oct 1 2011 - 12:06:06) Cloud Engines 1.1.2 (3.4.27) PHYADDR=0If U-Boot Endiannes is going to change (LE->BE or BE->LE), Then Env parameters should be overriden..
U-Boot
** Invalid partition type "%.32s" (expect "U-Boot")
U-Boot code: %08lX -> %08lX BSS: -> %08lX
Addresses %dM - 0M are saved for the U-Boot usage.
U-Boot BUG at %s:%d!
U-Boot 1.1.4 (Jan 13 2012 - 22:33:21) Arch Linux ARM (PPV4 r1) PHYADDR=0If U-Boot Endiannes is going to change (LE->BE or BE->LE), Then Env parameters should be overriden..
U-Boot
** Invalid partition type "%.32s" (expect "U-Boot")
U-Boot code: %08lX -> %08lX BSS: -> %08lX
Addresses %dM - 0M are saved for the U-Boot usage.
U-Boot BUG at %s:%d!
Is this telling me there are two on /dev/mtd0? Will uboot.sh replace them both with just U-Boot 2014.07-tld-1?
Any/all help and suggestions appreciated!
rsantag