Problem booting Pogo v4 (2 replies)

Hey Bodhi,

I recently found my lost Pogoplug 4 and managed to mess up upgrading it from 3.18.5 to the latest 4.8. I tried to roll back my changes but booting is stuck at starting the kernel regardless of which one I try to use.

U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700)
Pogoplug V4
gcc (Debian 4.9.2-10) 4.9.2
GNU ld (GNU Binutils for Debian) 2.25
Hit any key to stop autoboot:  0

MMC rescan: current device # 0 initialized OK
3229040 bytes read in 1508 ms (2 MiB/s)
6533854 bytes read in 1915 ms (3.3 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.8.0-kirkwood-tld-1
   Created:      2016-12-14  21:13:04 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3228976 Bytes = 3.1 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.8.0-kirkwood-tld-1
   Created:      2016-12-14  21:13:15 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6533790 Bytes = 6.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK


Starting kernel ...

I've upgraded uboot during my troubleshooting and noticed that my /proc/mtd has two uImage lines. I'm not sure if this is the problem but I also don't know how to remove the uImage2 line to actually troubleshoot it.

~ # cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00200000 00020000 "u-boot"
mtd1: 00300000 00020000 "uImage"
mtd2: 00300000 00020000 "uImage2"
mtd3: 00800000 00020000 "failsafe"
mtd4: 07000000 00020000 "root"

Any insights as to why my Pogoplug is getting stuck starting the kernel will be appreciated.

Thanks,
Strix