Welcome! Log In Create A New Profile

Advanced

[SOLVED] Help unbricking Pogo E02

Posted by ueghio 
[SOLVED] Help unbricking Pogo E02
February 17, 2017 05:29AM
Hello guys.. I managed to restore uboot image after a wrong installation in a Pogoplug e02. I have serial access and this is part of the output of printenv:
PogoE02> printenv
arcNumber=3960
baudrate=115200
bootcmd=run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; run bootcmd_pogo; reset
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
bootcmd_pogo=if ubi part root 2048 && ubifsmount ubi:rootfs && ubifsload 0x800000 uboot.mtd0.dockstar.original.kwb ; then go 0x800200; fi
bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot;
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
device=0:1
ethact=egiga0
ethaddr=00:25:31:00:5d:10
if_netconsole=ping $serverip
ipaddr=192.168.1.10
led_error=orange blinking
led_exit=green off
led_init=green blinking
machid=F78
mainlineLinux=yes
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
mmc_init=mmc rescan
mmc_load_uimage=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
partition=nand0,2
preboot=run if_netconsole start_netconsole
preboot_nc=run if_netconsole start_netconsole
rootdelay=10
rootfstype=ext3
sata_boot=mw 0x800000 0 1; run sata_load_uimage; if run sata_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_init=ide reset
sata_load_uimage=ext2load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext2load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
serverip=192.168.1.100
set_bootargs_mmc=setenv bootargs console=$console root=$mmc_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_sata=setenv bootargs console=$console root=$sata_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
usb_boot=mw 0x800000 0 1; run usb_load_uimage; if run usb_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_init=usb start
usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd
usb_root=/dev/sda1
usb_rootfstype=ext3

Environment size: 2459/131068 bytes
Is possible to install debian 8 from this startpoint or do I miss something? thank you in advance. Marco



Edited 2 time(s). Last edit at 02/24/2017 09:08AM by ueghio.
Re: Help unbricking Pogo E02
February 17, 2017 02:52PM
Marco,

Yes it is possible to boot Debian jessie on USB with your u-boot. See the rootfs release thread.

However, your u-boot was not restored correctly. Your envs are not for the Pogo E02. It is for Pogo V4. Also, the envs are for an older u-boot version than the latest u-boot.

Please post the whole serial console log (from the banner until you interrupt it, and printenv). I need to see u-boot version to help you further.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Help unbricking Pogo E02
February 18, 2017 03:50AM
Hi Bodhi thank you for your answer. This is the booting log
U-Boot 2015.10-tld-1 (Nov 06 2015 - 15:46:25 -0800)
Pogo E02

SoC:   Kirkwood 88F6281_A0
DRAM:  256 MiB (ECC not enabled)
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
No link on egiga0
ping failed; host 192.168.1.100 is not alive
Hit any key to stop autoboot:  0
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Unknown command 'mmc' - try 'help'
** Bad device mmc 0 **
** Bad device mmc 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Unknown command 'ide' - try 'help'
** Bad device ide 0 **
** Bad device ide 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
UBI: attaching mtd1 to ubi0
UBI: scanning is finished
UBI init error 22
resetting ...




U-Boot 2015.10-tld-1 (Nov 06 2015 - 15:46:25 -0800)
Pogo E02

SoC:   Kirkwood 88F6281_A0
DRAM:  256 MiB (ECC not enabled)
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
No link on egiga0
ping failed; host 192.168.1.100 is not alive
Hit any key to stop autoboot:  0
PogoE02>
And this is printenv
PogoE02> printenv
arcNumber=3960
baudrate=115200
bootcmd=run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; run bootcmd_pogo; reset
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
bootcmd_pogo=if ubi part root 2048 && ubifsmount ubi:rootfs && ubifsload 0x800000 uboot.mtd0.dockstar.original.kwb ; then go 0x800200; fi
bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot;
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
device=0:1
ethact=egiga0
ethaddr=00:25:31:00:5d:10
if_netconsole=ping $serverip
ipaddr=192.168.1.10
led_error=orange blinking
led_exit=green off
led_init=green blinking
machid=F78
mainlineLinux=yes
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
mmc_init=mmc rescan
mmc_load_uimage=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
partition=nand0,2
preboot=run if_netconsole start_netconsole
preboot_nc=run if_netconsole start_netconsole
rootdelay=10
rootfstype=ext3
sata_boot=mw 0x800000 0 1; run sata_load_uimage; if run sata_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_init=ide reset
sata_load_uimage=ext2load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext2load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
serverip=192.168.1.100
set_bootargs_mmc=setenv bootargs console=$console root=$mmc_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_sata=setenv bootargs console=$console root=$sata_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
usb_boot=mw 0x800000 0 1; run usb_load_uimage; if run usb_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_init=usb start
usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd
usb_root=/dev/sda1
usb_rootfstype=ext3

Environment size: 2459/131068 bytes
PogoE02>
I used this tutorial to recover uboot after a bad flash. I installed this uboot.2015.10-tld-1.pogo_e02.bodhi.tar

I tried to follow this guide but i'm stuck at point 3.
I formatted a usb pendrive in ext3 through my linux pc, created a boot folder in the root of the pendrive, extracted linux-4.8.0-kirkwood-tld-1-bodhi.tar.bz2. But I think I miss something..



Edited 3 time(s). Last edit at 02/18/2017 04:04AM by ueghio.
Re: Help unbricking Pogo E02
February 18, 2017 05:11AM
Marco,

> U-Boot 2015.10-tld-1 (Nov 06 2015 - 15:46:25 -0800)
> Pogo E02

Your envs are not correct, so we will need to put the envs in the /boot folder of the rootfs to recover. Your installed u-boot is relative new. So that will make it easier.


> I formatted a usb pendrive in ext3 through my linu
> x pc, created a boot folder in the root of the pen
> drive, extracted linux-4.8.0-kirkwood-tld-1-bodhi.
> tar.bz2. But I think I miss something..

This is not correct. You dont need to install the kernel. The released rootfs is ready to be used. You can upgrade the kernel after booting into Debian.

=============


Here is what you need to do:

1. Create the Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 rootfs on USB using the instruction in the rootfs release thread. See section:

Quote

Updated 20 Feb 2016:

This Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 is to keep in sync with kernel Linux-4.4.0-kirkwood-tld-1.

2. Download the script uboot.2016.05-tld-1.environment.scr that I've attached to this post (this is the default envs text in script format).

3. Mount the USB rootfs on another Linux box (and assuming it is mounted as /media/sdb1), copy the script to /boot folder
cp -a uboot.2016.05-tld-1.environment.scr /media/sdb1/boot/
sync

4. Plug this rootfs to the Pogo E02 and power up, interrupt serial console and execute commands:

usb start
ext2load usb 0:1 0x800000 /boot/uboot.2016.05-tld-1.environment.scr
source 0x800000


and then boot

boot

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Attachments:
open | download - uboot.2016.05-tld-1.environment.scr (3.2 KB)
Re: Help unbricking Pogo E02
February 19, 2017 04:33AM
Hi bodhi I followed your suggestions. I can now boot the rootfs and I'm trying to sync with kernel Linux-4.4.0-kirkwood-tld-1
following steps updated on 30 June 2015 in this thread.
but I'm stuck at point 3.

Quote
3. And install it with dpkg. If you encounter error with flash-kernel when running dpkg, then remove flash-kernel first to avoid potential problem (It is much better to generate uImage and uInitrd manually anyway):

I cannot execute dpkg commands neither from my ubuntu box (different architecture error) nor from from the rootfs prompt (because I cannot see /boot folder)

I find these folder when I boot:
(initramfs) ls
bin      dev      init     proc     run      scripts  tmp
conf     etc      lib      root     sbin     sys      var


What am I missing?
Re: Help unbricking Pogo E02
February 19, 2017 02:57PM
ueghio,

You have not booted into Debian. When you see the initramfs prompt, it means that the rootfs has not been mounted successfully, so the kernel exited and you are in the temporary rootfs (i.e. the one provided by initramfs).

I think your rootfs creation was not done properly. During rootfs creation, you must follow the instruction very closely (thing like being root user, and label the partition rootfs are important). If you missed any step, the rootfs will not work. dpkg is not needed at all during rootfs creation (only use this to upgrade the kernel after you have booted into Debian successfully with kernel 4.4 inside the rootfs).

Please post the entire bootlog (from the u-boot banner until the initrmfs prompt). And if you'd like me to check, post the entire log of what you did during rootfs creation here.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Help unbricking Pogo E02
February 21, 2017 06:23AM
Thank you bodhi, i apologize for being a newbe..i missed the step of label rootfs. Now I can boot into debian
root@debian:~# uname -a
Linux debian 4.4.0-kirkwood-tld-1 #1 PREEMPT Mon Jan 25 20:35:24 PST 2016 armv5tel GNU/Linux
root@debian:~# cat /etc/debian_version
8.3
When I booted after this step
usb start
ext2load usb 0:1 0x800000 /boot/uboot.2016.05-tld-1.environment.scr
source 0x800000
I encountered a kernel panic but now I think everything should be right.
In your opinion would be convenient to install the last
u-boot and kernel image?



Edited 3 time(s). Last edit at 02/22/2017 12:24AM by ueghio.
Re: Help unbricking Pogo E02
February 21, 2017 11:49PM
ueghio,

You need to boot using these commands in serial console for a few times
usb start
ext2load usb 0:1 0x800000 /boot/uboot.2016.05-tld-1.environment.scr
source 0x800000

to confirm that you can boot Debian:
root@debian:~# uname -a
Linux debian 4.4.0-kirkwood-tld-1 #1 PREEMPT Mon Jan 25 20:35:24 PST 2016 armv5tel GNU/Linux

And then at the next boot, save it permanently
usb start
ext2load usb 0:1 0x800000 /boot/uboot.2016.05-tld-1.environment.scr
source 0x800000
saveenv
and
boot


After that, shudown the box, backup your rootfs using this instruction (remember you have to be root user for this to work):
http://forum.doozan.com/read.php?2,12096,24034#msg-24034

And the proceed to install the latest kernel.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Help unbricking Pogo E02
February 22, 2017 05:52AM
Hello Bodhi this is the log when I try to boot using those commands in serial console
 Data Size:    7179871 Bytes = 6.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
   Booting using the fdt blob at 0x1c00000
   Loading Kernel Image ... OK
   Loading Ramdisk to 0f440000, end 0fb18e5f ... OK
   Loading Device Tree to 0f43a000, end 0f43f8cd ... OK
Using machid 0x831 from environment

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.4.0-kirkwood-tld-1 (root@tldDebian) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 PREEMPT Mon Jan 25 20:35:24 PST 2016
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine model: CloudEngines Pogoplug E02
[    0.000000] bootconsole [earlycon0] enabled
[    0.000000] Memory policy: Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
[    0.000000] Kernel command line: console=ttyS0,115200n8 earlyprintk root=/dev/sda1 rootdelay=10
[    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Memory: 250592K/262144K available (6007K kernel code, 573K rwdata, 1992K rodata, 296K init, 312K bss, 11552K reserved, 0K cma-reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xd0800000 - 0xff800000   ( 752 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc07d7ef4   (8000 kB)
[    0.000000]       .init : 0xc07d8000 - 0xc0822000   ( 296 kB)
[    0.000000]       .data : 0xc0822000 - 0xc08b169c   ( 574 kB)
[    0.000000]        .bss : 0xc08b169c - 0xc08ff9d0   ( 313 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]  Build-time adjustment of leaf fanout to 32.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[    0.000009] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[    0.008270] Console: colour dummy device 80x30
[    0.012836] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
[    0.100932] pid_max: default: 32768 minimum: 301
[    0.105753] Security Framework initialized
[    0.110070] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.116816] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.124809] Initializing cgroup subsys io
[    0.128993] Initializing cgroup subsys devices
[    0.133564] Initializing cgroup subsys freezer
[    0.138181] Initializing cgroup subsys net_cls
[    0.142808] CPU: Testing write buffer coherency: ok
[    0.148317] Setting up static identity map for 0x8200 - 0x8258
[    0.154554] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x2
[    0.163626] devtmpfs: initialized
[    0.171697] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.182176] prandom: seed boundary self test passed
[    0.190992] prandom: 100 self tests passed
[    0.195224] pinctrl core: initialized pinctrl subsystem
[    0.202006] NET: Registered protocol family 16
[    0.207002] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.238053] cpuidle: using governor ladder
[    0.268049] cpuidle: using governor menu
[    0.272484] Feroceon L2: Enabling L2
[    0.276195] Feroceon L2: Cache support initialised.
[    0.281602] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[    0.297079] No ATAGs?
[    0.329557] vgaarb: loaded
[    0.332990] usbcore: registered new interface driver usbfs
[    0.338717] usbcore: registered new interface driver hub
[    0.344210] usbcore: registered new device driver usb
[    0.350492] clocksource: Switched to clocksource orion_clocksource
[    0.412563] NET: Registered protocol family 2
[    0.417827] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[    0.425067] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[    0.431585] TCP: Hash tables configured (established 2048 bind 2048)
[    0.438115] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.444097] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.450698] NET: Registered protocol family 1
[    0.455517] RPC: Registered named UNIX socket transport module.
[    0.461604] RPC: Registered udp transport module.
[    0.466417] RPC: Registered tcp transport module.
[    0.471243] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.478178] NetWinder Floating Point Emulator V0.97 (double precision)
[    0.485904] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.492248] audit: initializing netlink subsys (disabled)
[    0.497794] audit: type=2000 audit(0.480:1): initialized
[    0.503633] Initialise system trusted keyring
[    0.508435] zbud: loaded
[    0.511389] VFS: Disk quotas dquot_6.6.0
[    0.515469] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.523151] NFS: Registering the id_resolver key type
[    0.528341] Key type id_resolver registered
[    0.532680] Key type id_legacy registered
[    0.536822] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.543671] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    0.550357] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    0.558065] Key type big_key registered
[    0.573435] Key type asymmetric registered
[    0.577650] Asymmetric key parser 'x509' registered
[    0.582815] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    0.590340] io scheduler noop registered
[    0.594556] io scheduler deadline registered
[    0.598994] io scheduler cfq registered (default)
[    0.605202] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[    0.613405] irq: Cannot allocate irq_descs @ IRQ32, assuming pre-allocated
[    0.620839] irq: Cannot allocate irq_descs @ IRQ64, assuming pre-allocated
[    0.628362] mv_xor f1060800.xor: Marvell shared XOR driver
[    0.671183] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    0.678837] mv_xor f1060900.xor: Marvell shared XOR driver
[    0.721182] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    0.729095] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    0.737014] console [ttyS0] disabled
[    0.740811] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 25, base_baud = 12500000) is a 16550A
[    0.749934] console [ttyS0] enabled
[    0.749934] console [ttyS0] enabled
[    0.757071] bootconsole [earlycon0] disabled
[    0.757071] bootconsole [earlycon0] disabled
[    0.767152] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[    0.773576] nand: Hynix NAND 128MiB 3,3V 8-bit
[    0.778039] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    0.785670] Scanning device for bad blocks
[    0.901335] libphy: Fixed MDIO Bus: probed
[    0.905786] libphy: orion_mdio_bus: probed
[    0.910678] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    1.991142] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:25:31:00:5d:10
[    2.000022] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.006639] ehci-pci: EHCI PCI platform driver
[    2.011201] ehci-orion: EHCI orion driver
[    2.015404] orion-ehci f1050000.ehci: EHCI Host Controller
[    2.020973] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[    2.028825] orion-ehci f1050000.ehci: irq 29, io mem 0xf1050000
[    2.050582] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[    2.056848] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.063703] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.070982] usb usb1: Product: EHCI Host Controller
[    2.075881] usb usb1: Manufacturer: Linux 4.4.0-kirkwood-tld-1 ehci_hcd
[    2.082544] usb usb1: SerialNumber: f1050000.ehci
[    2.088005] hub 1-0:1.0: USB hub found
[    2.091871] hub 1-0:1.0: 1 port detected
[    2.096789] mousedev: PS/2 mouse device common for all mice
[    2.410526] usb 1-1: new high-speed USB device number 2 using orion-ehci
[    2.562083] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[    2.568832] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    2.576034] usb 1-1: Product: USB2.0 Hub
[    2.580944] hub 1-1:1.0: USB hub found
[    2.585083] hub 1-1:1.0: 4 ports detected
[    2.870520] usb 1-1.3: new high-speed USB device number 3 using orion-ehci
[    2.981457] usb 1-1.3: New USB device found, idVendor=0781, idProduct=5571
[    2.988381] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.995763] usb 1-1.3: Product: Cruzer Fit
[    2.999878] usb 1-1.3: Manufacturer: SanDisk
[    3.004188] usb 1-1.3: SerialNumber: 4C530201270404115231
[    3.110523] rtc-mv f1010300.rtc: internal RTC not ticking
[    3.116155] i2c /dev entries driver
[    3.120986] hidraw: raw HID events driver (C) Jiri Kosina
[    3.126826] drop_monitor: Initializing network drop monitor service
[    3.133412] NET: Registered protocol family 17
[    3.138147] Key type dns_resolver registered
[    3.143346] registered taskstats version 1
[    3.147507] Loading compiled-in X.509 certificates
[    3.152417] zswap: loaded using pool lzo/zbud
[    3.157898] Key type encrypted registered
[    3.162498] hctosys: unable to open rtc device (rtc0)
[    3.169021] Waiting 10 sec before mounting root device...
[   13.180752] VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6
[   13.188098] Please append a correct "root=" boot option; here are the available partitions:
[   13.196547] 1f00          131072 mtdblock0  (driver?)
[   13.201680] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[   13.209980] CPU: 0 PID: 1 Comm: swapper Not tainted 4.4.0-kirkwood-tld-1 #1
[   13.216969] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[   13.223296] [<c0016784>] (unwind_backtrace) from [<c00129f8>] (show_stack+0x10/0x14)
[   13.231080] [<c00129f8>] (show_stack) from [<c00c2200>] (panic+0x80/0x214)
[   13.237995] [<c00c2200>] (panic) from [<c07d9280>] (mount_block_root+0x204/0x24c)
[   13.245517] [<c07d9280>] (mount_block_root) from [<c07d93b4>] (mount_root+0xec/0x118)
[   13.253391] [<c07d93b4>] (mount_root) from [<c07d9504>] (prepare_namespace+0x124/0x184)
[   13.261431] [<c07d9504>] (prepare_namespace) from [<c07d8e9c>] (kernel_init_freeable+0x208/0x258)
[   13.270349] [<c07d8e9c>] (kernel_init_freeable) from [<c05b16b4>] (kernel_init+0x8/0xe4)
[   13.278481] [<c05b16b4>] (kernel_init) from [<c000f090>] (ret_from_fork+0x14/0x24)
[   13.286092] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)



Edited 2 time(s). Last edit at 02/22/2017 08:05AM by ueghio.
Re: Help unbricking Pogo E02
February 22, 2017 04:24PM
ueghio,

You need to post the entire serial boot log doing this:

usb start
ext2load usb 0:1 0x800000 /boot/uboot.2016.05-tld-1.environment.scr
source 0x800000
printenv
and then
boot

Without the entire log, I can only guess the problem, but will not able to determine for sure what it was.

-------

However, from the partial log above, I can tell that your rootfs was not created correctly. You should not do step 4.

Quote

4. Create uImage with embedded DTB for booting with older u-boots (2012 or earlier). Skip this step if you have installed the latest U-Boot for Kirkwood (or are installing this u-boot at the same time).

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Help unbricking Pogo E02
February 23, 2017 05:05PM
Bodhi, your assumption was right. I didn't skip point 4. Now booting process ends without errors and I can log in. I'm going to update the kernel in the next days. Tank you for your help. Marco
Re: Help unbricking Pogo E02
February 23, 2017 08:57PM
ueghio Wrote:
-------------------------------------------------------
> Bodhi, your assumption was right. I didn't skip po
> int 4. Now booting process ends without errors and
> I can log in. I'm going to update the kernel in th
> e next days. Tank you for your help. Marco

Cool! Glad everything is working now!

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Help unbricking Pogo E02
February 24, 2017 08:15AM
Hi Bodhi, Kernel updated successfully following your guide! Thank you again for your hard work and for your support, everything is working flawlessly now! Kind regards, Marco



Edited 2 time(s). Last edit at 02/24/2017 09:09AM by ueghio.
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: