Welcome! Log In Create A New Profile

Advanced

trying to upgrade PogoPlug E02

Posted by wooglez 
trying to upgrade PogoPlug E02
November 18, 2019 10:03PM
I was following the UBoot instructions from an older pogoplug I had set up here back in 2014-15, I think the pendrive eventually went bad. I was still able to boot into the stock pogo OS and was following these instructions . I noticed I didn't have an /boot folder towards the end, setup netconsole and rebooted. Below is the output from booting.
Where did I go wrong?

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:13:18 -0700)
Pogo E02
gcc (Debian 6.3.0-18) 6.3.0 20170516
GNU ld (GNU Binutils for Debian) 2.28
Hit any key to stop autoboot:  0 
Initializing devices...
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'
Loading envs from usb 0...
** File not found /boot/uEnv.txt **
Loading envs from usb 1...
** Bad device usb 1 **
Loading envs from usb 2...
** Bad device usb 2 **
Loading envs from usb 3...
** Bad device usb 3 **
Loading envs from ide 0...
** Bad device ide 0 **
Loading envs from ide 1...
** Bad device ide 1 **
Loading envs from ide 2...
** Bad device ide 2 **
Loading envs from ide 3...
** Bad device ide 3 **
Loading envs from mmc 0...
** Bad device mmc 0 **
Loading envs from mmc 1...
** Bad device mmc 1 **
Loading envs from mmc 2...
** Bad device mmc 2 **
Loading envs from mmc 3...
** Bad device mmc 3 **
running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 569 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
1612096 bytes read in 985 ms (1.6 MiB/s)
loading uInitrd ...
7096647 bytes read in 1974 ms (3.4 MiB/s)
loading DTB /boot/dts/kirkwood-pogo_e02.dtb ...
** File not found /boot/dts/kirkwood-pogo_e02.dtb **
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   kernel 3.2.0-4-kirkwood
   Created:      2014-11-07  19:11:20 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1612032 Bytes = 1.5 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   ramdisk 3.2.0-4-kirkwood
   Created:      2014-11-07  19:11:22 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7096583 Bytes = 6.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... Bad Data CRC
Ramdisk image is corrupt or invalid
PogoE02> 

Re: trying to upgrade PogoPlug E02
November 18, 2019 10:27PM
wooglez,

The USB rootfs you are using is not good. The kernel files were not found from that.

Try create a new rootfs using Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 from the release thread:

https://forum.doozan.com/read.php?2,12096

Scroll down to the section

Quote

Updated 25 Aug 2019:

Basic Debian buster Kirkwood rootfs for most Kirwood plugs:

- tarball size: 209M
- install size: 536M
- The init system used in this rootfs is sysvinit . To boot with systemd, see note 2 below.
- Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, dialog, bzip2, nfs server/client, iperf, ethtool, sysvinit-core, sysvinit, sysvinit-utils, u-boot-tools, and mtd-utils.
- see LED controls in /etc/rc.local, and /etc/init.d/halt
- see some useful aliases in /root/.profile
- root password: root

Download at Dropbox:

Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2

md5:
cd8ad170aa1a9fdc2a0a1c43ab1c0721
sha256:
8ccbbced367b4c2bf3728262e882f8232aff0fecd1c0c767219a0cab49a0b9bf


Your u-boot install seems to be OK. So it should boot the new rootfs.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: trying to upgrade PogoPlug E02
November 18, 2019 10:35PM
Hey @bodhi,

Yea I was just coming here to update this post, I decided to follow the rootfs tutorial next and after doing so on my new usb device it booted like a charm.
Would be nice to let new or returning users know what order the process should be for updating devices, UBoot first then rootfs especially since some of the end instructions for Uboot mention modifying (the dtb step) /boot but you don't have that folder until you run through the rootfs install procedure.

anyhow it's booted now!
Re: trying to upgrade PogoPlug E02
November 18, 2019 10:47PM
Hey @bodhi you may want to add a section in the rootfs tutorial about running ntpdate for first login after ssh-keys cuz otherwise apt-get will screw up.
Re: trying to upgrade PogoPlug E02
November 18, 2019 10:51PM
wooglez,

Glad to hear!

I know it is a little bit disjoint when u-boot and Debian roots are in different release threads! It's an internal debate from time to time for me, as how best to go forward.

U-boot can be used in many different distros (Arch, OpenWRt, Ubuntu, Void, Fedora....), not just Debian. So that's why it was separated in the beginning.

-bodhi
===========================
Forum Wiki
bodhi's corner
Author:

Your Email:


Subject:


Spam prevention:
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.
Message: