Pogoplug v2 hosed by installing uboot-env?

[fastenova]

Well, the problem is that I can't SSH into the device after attempting to boot without the USB stick... So it seems like something in flash is not right...?

I can see that it grabs an IP from my router, but I am not able to SSH into it. I CAN ping it successfully. It does NOT show up on the pogoplug.com website (phone-home) so I can't tell it to enable SSH...

[fastenova]

OK ordered a cable from here: http://www.adafruit.com/products/954

Since it worked before I started messing with it, I will try clearing the machid value first and see if it boots cleanly. If not I'll look into setting the other values (usb_rootfstype, ethaddr)

If that fails, I will post the results of the boot here and ask for more assistance.

Thanks for all your help!

[grayman4hire]

I don't think you're issue has anything to do with installing uboot-env or setting the machid or usb_rootfstype (did you messed with the ethaddr?).

[Edtit] - Clarification. machid definitely shouldn't effect anything. usb_rootfstype would matter if you formatted your drive as ext2 and then went ahead and told uboot to mount as ext3. I'm going to assume you followed the tutorial and formatted the usb flash drive as ext3, hence why I don't think this is related to your issue.

Typically SSH is enabled by default on the Pogoplug out of the box. If you register the device on my.pogoplug.com, I believe ssh is then disabled, unless you re-enable it via the my.pogoplug.com web interface.

How did you go about setting up your pogoplug? Did you register it first or did you attempt to install ALARM right out of the box?

Also note that during the uboot installation, the script ask you if you want to disable the pogoplug service.

If you followed my tutorial, my recommendation is to select 'y' (maybe I should change that).
$this->bbcode_second_pass_code('', '#Would you like to disable the pogoplug services? [Y/n]
#y - don't look back')

If you selected y, this would explain why you're not seeing it on the my.pogoplug.com website.

Saying that...all is not lost. Just setup your USB Flash drive on a linux machine or use a linux live CD. Make sure its formatted as ext3 and extract the alarm tarball onto it.

[fastenova]

Hey guys,

So got my ttl cable working. Here's my printenv:

u-boot>> printenv
baudrate=115200
bootargs=root=/dev/nfs nfsroot=: ip=::::::off
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=5
ethact=egiga0
ethaddr=02:50:43:b2:70:b1
machid=dd6
stderr=serial
stdin=serial
stdout=serial

I know that the ethaddr is incorrect, but not sure what my next step here is - should I try to correct these to match the settings on my other working E02 or...?

Many thanks!

[WarheadsSE]

Yes, make them match your other one, to the T, minus the ethernet address.

[fastenova]

Awesome, thanks again for your assistance. I'll try this tonight after work. I'll set the ethaddr to match the MAC printed on the bottom of the unit.

[grayman4hire]

why is the ethernet address "incorrect"? Did you change it?

[fastenova]

I definitely did NOT change it. I have no idea why it's incorrect. The only flag I set was the machid flag (to dd6).

It's "incorrect" because it's not the same as the hardware MAC (presuming that the assigned MAC on the bottom is the correct one). Pretty sure they need to match in order for the OS to correctly process packets destined for the NIC...

Only guess is some weird default from the original uboot script that is not overridden by the Arch install since it's not booting to Arch, just to uboot.

[WarheadsSE]

Yup, something has reset your environment to compile-time scratch. It nuked it.

[grayman4hire]

@WarheadsSE, do you know how something like that could happen?