pogoplug login after uboot

Hi, all:

Am trying to install ALARM on a pogo v2. uboot installed fine but I had to close putty ssh connection, now cannot log back on. The previous password is no longer valid, but don't know what to use now. I opted to save pogo's original software during uboot installation -- do I unplug hard drive and start over or what?

Thanx -- flyyboyy

flyyboyy Wrote:
-------------------------------------------------------
> Hi, all:
>
> Am trying to install ALARM on a pogo v2. uboot
> installed fine but I had to close putty ssh
> connection, now cannot log back on. The previous
> password is no longer valid, but don't know what
> to use now. I opted to save pogo's original
> software during uboot installation -- do I unplug
> hard drive and start over or what?
>
> Thanx -- flyyboyy

flyyboyy,

No enough information to help you.

How far did you get? completed Arch rootfs installation? which u-boot are you running? did you reboot?

If you have a log of of what you did then pls post here.

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

Hi, thanks for the reply;
Absolute noob with linux, but doing a lot of reading, trying to learn. . .
Was following step-by-step for getting an E02 set up as a micro nas / media server. Didn't get very far:

killall hbwd
#Install UBoot
cd /tmp
wget http://jeff.doozan.com/debian/uboot/install_uboot_mtd0.sh
chmod +x install_uboot_mtd0.sh
./install_uboot_mtd0.sh

#Would you like to disable the Pogoplug services? [Y/n]
#n - to keep original Pogoplug software
#when booting without USB drives attached
#y - if you're not planning on ever using the stock
#Pogoplug software again
N

[Plugged in and partitioned USB hard drive]
/sbin/fdisk /dev/sda

# Type in the following commands to erase
# and re-partition USB flash/hard drive
#(WARNING - FLASH/HARD DRIVE WILL BE COMPLETELY WIPED):
#
# p # list current partitions
# o # to delete all partitions
# n # new partition
# p # primary partition
# 1 (one) # first partition
# <enter> # default start block
# <enter> # default end block (to use the whole drive)
# w # write new partition to disk

[Tried to install http://archlinuxarm.org/os/pogoplug/mke2fs]
cd /tmp
wget http://archlinuxarm.org/os/pogoplug/mke2fs

[The install failed, I get:]
Connecting to archlinuxarm.org (50.116.36.110:80)
[then]
wget: not an http or ftp url: https://archlinuxarm.org/os/pogoplug/mke2fs

After several hours of dinking with wget, had to move on to other things (real life) and closed my putty session. Now cannot log back on to continue / try again.

I did not save the ssh session, and did not reboot.

__________

Thanks for your input and help!

flyyboyy,

> killall hbwd
> #Install UBoot
> cd /tmp
> wget
> http://jeff.doozan.com/debian/uboot/install_uboot_
> mtd0.sh
> chmod +x install_uboot_mtd0.sh
> ./install_uboot_mtd0.sh

At this point you have installed Jeff/davygravy u-boot.

> closed my
> putty session

Bad idea :) and I don't know what other things went on, since you don't have a log. So the best advice: if you have another Linux box, create a new rootfs on USB. This rootfs can be either Arch or Debian. And it has to be older then the current release because this u-boot is quite old and does not support FDT kernel.

The u-boot you have installed will work with Debian 3.16 rootfs. See the same recommendation here:
http://forum.doozan.com/read.php?3,25511,25515#msg-25515

Once you can boot with this rootfs, you then can go back to Arch installation and continue with the latest release at Arch site. Don't use any link that from any other site, you apparently did and end up installing with a very out-of -date procedure!

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

flyyboyy Wrote:
-------------------------------------------------------
> Hi, all:
>
> Am trying to install ALARM on a pogo v2. uboot
> installed fine but I had to close putty ssh
> connection, now cannot log back on.

Can you try to establish a connection through a serial/console cable?

I think this may be of relevance

[Tried to install http://archlinuxarm.org/os/pogoplug/mke2fs]
cd /tmp
wget http://archlinuxarm.org/os/pogoplug/mke2fs

[The install failed, I get:]
Connecting to archlinuxarm.org (50.116.36.110:80)
[then]
wget: not an http or ftp url: https://archlinuxarm.org/os/pogoplug/mke2fs

After several hours of dinking with wget, had to move on to other things (real life) and closed my putty session. Now cannot log back on to continue / try again.

I did not save the ssh session, and did not reboot.

I dont think the device is bricked - from what i read you are trying to download the tools to do the jobs and you are not able to with the wget built into Busybox. what is the light sequence on your unit. i think you have just rebooted the unit and lost console access. if you can ping the box all is not lost

Hello, GR;

Thanks for the reply. Yes, I can still ping the E02, it still shows up in my DHCP list, and I can communicate with it up to the point where it wants login credentials. I did NOT reboot it (not sure if I would lose any further contact with it), it's been sitting idling while I read/learn more. The front LED remains steady green.

I was in the process of following bodhi's instructions for creating a USB stick with Debian 3.16.0 but still don't know enough about Linux yet to make it happen -- still studying while the Pogo sits patiently.

Have not yet made serial cable (per habibie), but should be no problem other than I don't have a TTL converter on hand.

It sounds like (per bodhi) that I was following ancient instructions -- 2014-ish, and that there is much more recent info though I have not been able to find it. I see Archlinux has a way, but it doesn't maintain pogo's original software. And regarding that, I had thought that disconnecting the USB HD would allow pogo to boot back into its native software and that I should be able to start the process over. Since that has not been suggested, I assume (again) that I'm mistaken. . .

Sooooo, if it isn't yet bricked, do you recommend I follow bodhi's suggestion? Or do you have another?

Sorry for being so noobish, and thanks for your reply!

Hi, habibie:

Thanks for the suggestion, have no problem with building a serial cable though I don't have a TTL converter on hand. I probably ought to pick one up, may have other use for it sometime.

And, I'm all ears for any other suggestion.

bodhi:

> Bad idea :)

Yup, of course it was! Hindsight is WONDERFUL!

Trying to put your Debian 3.16.0 onto thumb drive -- getting closer but still doing something wrong; don't know enough yet apparently, and feeling pretty stupid. . . Gonna play with it again later tonight.

You indicate that I was following an old procedure to install ALARM. It's kinda funny, because in preparing to do it, I came across and studied MANY sites/pages that all follow pretty much the same procedure, using the same file downloads, and all from about the same time (2014 or so). I assumed that these were still valid since I had not seen anything "newer". So would appreciate if you would point me in a better direction once I get logged back into pogo.

I have purposely NOT rebooted pogo, fearing making things worse. Right / wrong / doesn't matter at this point? And, I thought the "benefit" of using Jeff/davygravy u-boot was that IT would maintain the original pogo functionality and could disconnect the USB HD (thus being able to "start over.") Since that hasn't been suggested, I assume I assumed wrong.

Still reading/studying.Thanks again, and will gladly accept all the hand-holding I can get.

flyy

flyyboyy,

> You indicate that I was following an old procedure
> to install ALARM. It's kinda funny, because in
> preparing to do it, I came across and studied MANY
> sites/pages that all follow pretty much the same
> procedure, using the same file downloads, and all
> from about the same time (2014 or so). I assumed
> that these were still valid since I had not seen
> anything "newer". So would appreciate if you would
> point me in a better direction once I get logged
> back into pogo.

ALARM has moved to their own new u-boot. So the installation that has Jeff's script is no longer supported by them:
https://archlinuxarm.org/platforms/armv5/pogoplug-v2-pinkgray

But if you intend to run Debian with my u-boot build or keep Jeff/davygravy u-boot, then it is easier for me to help. BTW, davygravy's u-boot image that you have installed will work fine for non-FDT kernel. The FDT kernel will need some repackaging (embedded DTB) to be able to boot with it. That's why I suggested using my Debian 3.16 rootfs.

> Since that hasn't been suggested, I assume
> I assumed wrong.
>

No, you are not wrong! that's exactly correct. The easiest way to keep Pogo OS is using Jeff's installation. The only caveat is that if you're not using Arch latest installation procedure, it's difficult to get help at Arch site when you have Arch-specific problems.

If this is what you intend to do, i.e. keeping this 2012 u-boot, I will help you get it working. I don't think it matters which system you are using, Arch or Debian, we are having fun hacking embedded Linux :)

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

@ flyyboyy

At this point you have 3 steps to try. If one fails try the next.

1. Try to get back in with SSH.
2. Prepare the Debian 3.16 rootfs on USB and reboot with it.
3. Connect serial console.

If you decide on serial console then do that and not worrying about 1 or 2.

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

Hi, bodhi, et al:

Back to the project tonight.

I installed Debian 3.16.0 rootfs on a USB stick and looks (visually) like Pogo boots with it -- see the thumb drive LED flash, then few seconds later Pogo's front LED flashes and then turns solid green. I can ping it and can ssh into it, but still can't get past login request; root/root does not work. Yes, I had removed USB HD so nothing other than the stick was attached.

I also tried booting with no external storage attached (attempting to access it with Pogo's native OS); same as above, appears to boot, can ping it, can ssh to it, but it won't accept any login credentials including the pw set at my.pogoplug.com for ssh access.

So, what do I need to do to get past the ssh login? -- still don't have a working user/password combo.

And again, big thanks! -- flyyboyy

flyyboyy,

> I installed Debian 3.16.0 rootfs on a USB stick

It's root/root. If you can't get in, then prepare the rootfs again. Remember to follow the instruction very closely.

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

this might be an off the wall suggestion - but its a mistake i commonly make - you havent set the password with CAPS lock on have you?

if you still cant get in with your password combo, wait until you have your TTL connector working.

with a printout of the uboot envs, we should be able to see where you need modifications and you will also be able to change the password from there if necessary.

bodhi: OK, will try redoing rootfs again

Gravelrash: No on CapLock. Yup, looks like serial cable gonna get its day in the sun.

Thanks to both!

Also forgot to mention that based on this statement (in Debian 3.16.0 rootfs instructions):

> (If unsure how to set this u-boot env on the installation target, then don't worry, it can be safely skipped. . .

I skipped them.


So is it okay to skip them? If I need to set them, I'm not sure how.

flyyboyy Wrote:
-------------------------------------------------------
> Also forgot to mention that based on this
> statement (in Debian 3.16.0 rootfs instructions):
>
> > (If unsure how to set this u-boot env on the
> installation target, then don't worry, it can be
> safely skipped. . .
>
> I skipped them.
>
>
> So is it okay to skip them? If I need to set them,
> I'm not sure how.

Yes, basically if you use Ext3 rootfs then no need to worry about what u-boot env for rootfs type is.

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

Hi, All

Been unable to do any more til just today. Anyhoo, remembered I had an old laptop with a real db9 serial port. Fired it up with serial cable (only Rx, Tx and Gnd) and they appear to communicate. Using 115200-8-1-N-N, and UTF-8 but it spits out garbage.

Tried a couple of other bps settings, still nothing useful.

Ideas?

Thanks

flyyboyy Wrote:
-------------------------------------------------------
> Hi, All
>
> Been unable to do any more til just today. Anyhoo,
> remembered I had an old laptop with a real db9
> serial port. Fired it up with serial cable (only
> Rx, Tx and Gnd) and they appear to communicate.
> Using 115200-8-1-N-N, and UTF-8 but it spits out
> garbage.
>
> Tried a couple of other bps settings, still
> nothing useful.
>
> Ideas?
>
> Thanks

I don't think it will work. You need a converter:
http://forum.doozan.com/read.php?8,13263

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

flyyboyy Wrote:
-------------------------------------------------------
> Hi, All
>
> Been unable to do any more til just today. Anyhoo,
> remembered I had an old laptop with a real db9
> serial port. Fired it up with serial cable (only
> Rx, Tx and Gnd) and they appear to communicate.
> Using 115200-8-1-N-N, and UTF-8 but it spits out
> garbage.
>
> Tried a couple of other bps settings, still
> nothing useful.
>
> Ideas?
>
> Thanks

Do yourself a big favor, get either this PL2303 or this inexpensive CH340 USB To RS232 TTL converter.