Welcome! Log In Create A New Profile

Advanced

How do I get out of my Pogoplug Mobile rathole?

Posted by TastesLikeChickN 
How do I get out of my Pogoplug Mobile rathole?
February 26, 2017 07:06PM
I began my journey looking for an inexpensive device to use as a DDNS client. I stumbled on Qui's blog and it sounded like an easy way to go. I bought a Pogoplug Mobile (POGO-V4-A1-01) and away I went.

Things did not start well. After finding out the Qui's files were no longer available, I ended up installing Arch on a USB stick from the Arch site and it sort of worked, but the cheap, trade show USB stick I used had issues. After many failed efforts, my Plug no longer boots and I know that my environment variables are majorly hosed.

I currently have access to my Plug through a soldered cable. It has U-Boot v 2016.05-tld-1 for Pogoplug V4 installed, but will not boot from either my new USB stick (SanDisk 16GB) or my SD Card (SanDisk 16 GB), most likely due in a large part to the environment variables. I have a Raspberry Pi running Arch that I can use to play with my USB stick and SD Card.

Ultimately, I still want to use my Plug as a DDNS client and have it booting from the SD Card. I do have to stay with Arch and will go to Debian or whatever I can get working. I think OpenWrt might suit my needs, but I did not find a lot of information beyond another Qui blog on using it on the version of Plug that I have. Rather than try to troubleshoot the mess I created, I think it may be easier to start over - if some kind soul could point me to some instructions to follow.

Does anyone have any suggestions on where to go from here?

Many thanks in advance!
Re: How do I get out of my Pogoplug Mobile rathole?
February 26, 2017 07:42PM
Let me give me some instructions here and later move this to u-boot thread.

Quote

I currently have access to my Plug through a soldered cable. It has U-Boot v 2016.05-tld-1 for Pogoplug V4 installed, but will not boot from either my new USB stick (SanDisk 16GB) or my SD Card (SanDisk 16 GB), most likely due in a large part to the environment variables. I have a Raspberry Pi running Arch that I can use to play with my USB stick and SD Card.

Plug in your Sandisk USB drive. Power up, interrupt serial console and

printenv
boot

And post the entire serial console log 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



Edited 1 time(s). Last edit at 02/26/2017 07:42PM by bodhi.
Re: How do I get out of my Pogoplug Mobile rathole?
February 26, 2017 07:50PM
Here it is:

U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700)
Pogoplug V4

SoC:   Kirkwood 88F6192_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  128 MiB
MMC:   kwsdio: 0
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Hit any key to stop autoboot:  3  2  0 
Pogov4> printenv
arcNumber=3960
bootargs=root=/dev/nfs nfsroot=192.168.0.220: ip=192.168.0.231:192.168.0.220:::::off
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=3
bootdev=usb
device=0:1
devices=usb mmc ide
disks=0 1 2 3
ethact=egiga0
ethaddr=00:25:31:05:b8:e4
if_netconsole=ping $serverip
ipaddr=192.168.0.231
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
machid=f78
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
serverip=192.168.0.220
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_ready_retry=15

Environment size: 2901/131068 bytes
Pogov4> boot
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found

Reset IDE: ide_preinit failed

Partition Map for USB device 0  --   Partition Type: DOS

Part	Start Sector	Num Sectors	UUID		Type
  1	2048      	30210048  	63754a41-01	83 Boot
  2	30212096  	1048576   	63754a41-02	82
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **

no IDE devices available
running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 134 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
4604848 bytes read in 309 ms (14.2 MiB/s)
loading uInitrd ...
** File not found /boot/uInitrd **
loading DTB ...
** No boot file defined **
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.4.45-1-ARCH
   Created:      2017-01-29   5:31:24 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4604784 Bytes = 4.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
Using machid 0xf78 from environment

Starting 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.45-1-ARCH (builduser@leming) (gcc version 6.3.1 20170109 (GCC) ) #1 PREEMPT Sat Jan 28 22:31:00 MST 2017
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: Pogoplug V4
[    0.000000] Memory policy: Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32480
[    0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 119688K/131072K available (6606K kernel code, 547K rwdata, 1876K rodata, 300K init, 725K bss, 11384K 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 : 0xc8800000 - 0xff800000   ( 880 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc08509e4   (8483 kB)
[    0.000000]       .init : 0xc0851000 - 0xc089c000   ( 300 kB)
[    0.000000]       .data : 0xc089c000 - 0xc0924e6c   ( 548 kB)
[    0.000000]        .bss : 0xc0924e6c - 0xc09da438   ( 726 kB)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] 	Build-time adjustment of leaf fanout to 32.
[    0.000000] NR_IRQS:114
[    0.000021] sched_clock: 32 bits at 166MHz, resolution 6ns, wraps every 12884901885ns
[   24.811464] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 11467562657 ns
[   24.811749] Console: colour dummy device 80x30
[   24.811794] Calibrating delay loop... 795.44 BogoMIPS (lpj=3977216)
[   24.901572] pid_max: default: 32768 minimum: 301
[   24.901711] Security Framework initialized
[   24.901824] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[   24.901853] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[   24.902975] Initializing cgroup subsys io
[   24.903027] Initializing cgroup subsys memory
[   24.903107] Initializing cgroup subsys devices
[   24.903147] Initializing cgroup subsys freezer
[   24.903179] Initializing cgroup subsys net_cls
[   24.903208] Initializing cgroup subsys perf_event
[   24.903243] Initializing cgroup subsys net_prio
[   24.903369] CPU: Testing write buffer coherency: ok
[   24.904057] Setting up static identity map for 0x81e0 - 0x8238
[   24.906998] devtmpfs: initialized
[   24.910601] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[   24.911342] pinctrl core: initialized pinctrl subsystem
[   24.912588] NET: Registered protocol family 16
[   24.913344] DMA: preallocated 256 KiB pool for atomic coherent allocations
[   24.941602] cpuidle: using governor ladder
[   24.971604] cpuidle: using governor menu
[   24.971852] Kirkwood: MV88F6281-A1, TCLK=166666667.
[   24.971890] Feroceon L2: Enabling L2
[   24.971942] Feroceon L2: Cache support initialised.
[   24.975353] Kirkwood PCIe port 0: link down
[   24.975369] PCI: bus0 uses PCIe port 0
[   24.975715] PCI host bridge to bus 0000:00
[   24.975741] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe7ffffff]
[   24.975758] pci_bus 0000:00: root bus resource [io  0x1000-0xffff]
[   24.975774] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[   24.976304] PCI: bus0: Fast back to back transfers disabled
[   25.013755] vgaarb: loaded
[   25.014219] SCSI subsystem initialized
[   25.014948] usbcore: registered new interface driver usbfs
[   25.015061] usbcore: registered new interface driver hub
[   25.015147] usbcore: registered new device driver usb
[   25.015399] pps_core: LinuxPPS API ver. 1 registered
[   25.015412] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[   25.015463] PTP clock support registered
[   25.017067] clocksource: Switched to clocksource orion_clocksource
[   25.074325] FS-Cache: Loaded
[   25.093375] NET: Registered protocol family 2
[   25.094551] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[   25.094590] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[   25.094620] TCP: Hash tables configured (established 1024 bind 1024)
[   25.094727] UDP hash table entries: 256 (order: 0, 4096 bytes)
[   25.094764] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[   25.095037] NET: Registered protocol family 1
[   25.095510] RPC: Registered named UNIX socket transport module.
[   25.095526] RPC: Registered udp transport module.
[   25.095536] RPC: Registered tcp transport module.
[   25.095546] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   25.098586] futex hash table entries: 256 (order: -1, 3072 bytes)
[   25.117715] VFS: Disk quotas dquot_6.6.0
[   25.118115] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[   25.121130] FS-Cache: Netfs 'nfs' registered for caching
[   25.122812] NFS: Registering the id_resolver key type
[   25.122905] Key type id_resolver registered
[   25.122918] Key type id_legacy registered
[   25.123042] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[   25.124991] fuse init (API version 7.23)
[   25.128268] aufs 4.4-20170130
[   25.135844] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[   25.135880] io scheduler noop registered
[   25.135902] io scheduler deadline registered
[   25.136296] io scheduler cfq registered
[   25.136690] io scheduler bfq registered (default)
[   25.136702] BFQ I/O-scheduler: v7r11
[   25.136998] mv_xor mv_xor.0: Marvell shared XOR driver
[   25.179011] mv_xor mv_xor.0: Marvell XOR (Registers Mode): ( xor cpy )
[   25.179369] mv_xor mv_xor.1: Marvell shared XOR driver
[   25.218922] mv_xor mv_xor.1: Marvell XOR (Registers Mode): ( xor cpy )
[   25.227179] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[   25.228738] console [ttyS0] disabled
[   25.248824] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33, base_baud = 10416666) is a 16550A
[   25.837206] console [ttyS0] enabled
[   25.864222] brd: module loaded
[   25.878801] loop: module loaded
[   25.882446] sata_mv sata_mv.0: cannot get optional clkdev
[   25.888013] sata_mv sata_mv.0: slots 32 ports 1
[   25.895015] scsi host0: sata_mv
[   25.898749] ata1: SATA max UDMA/133 irq 21
[   25.903868] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[   25.910395] nand: Hynix H27U1G8F2BTR-BC
[   25.914221] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[   25.921804] Scanning device for bad blocks
[   25.969648] Bad eraseblock 533 at 0x0000042a0000
[   25.989206] Bad eraseblock 716 at 0x000005980000
[   26.018966] 4 cmdlinepart partitions found on MTD device orion_nand
[   26.025207] Creating 4 MTD partitions on "orion_nand":
[   26.030354] 0x000000000000-0x000000100000 : "u-boot"
[   26.036030] 0x000000100000-0x000000500000 : "uImage"
[   26.041669] 0x000000500000-0x000002500000 : "rootfs"
[   26.047366] 0x000002500000-0x000008000000 : "data"
[   26.062657] libphy: orion_mdio_bus: probed
[   26.066901] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[   26.257111] ata1: SATA link down (SStatus 0 SControl F300)
[   27.151511] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:25:31:05:b8:e4
[   27.160450] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   27.166958] ehci-pci: EHCI PCI platform driver
[   27.171521] ehci-orion: EHCI orion driver
[   27.175627] orion-ehci orion-ehci.0: EHCI Host Controller
[   27.181073] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[   27.188845] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[   27.207118] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[   27.214508] hub 1-0:1.0: USB hub found
[   27.218366] hub 1-0:1.0: 1 port detected
[   27.223365] usbcore: registered new interface driver uas
[   27.228924] usbcore: registered new interface driver usb-storage
[   27.234990] usbcore: registered new interface driver ums-alauda
[   27.241021] usbcore: registered new interface driver ums-cypress
[   27.247115] usbcore: registered new interface driver ums-datafab
[   27.253174] usbcore: registered new interface driver ums_eneub6250
[   27.259432] usbcore: registered new interface driver ums-freecom
[   27.265485] usbcore: registered new interface driver ums-isd200
[   27.271482] usbcore: registered new interface driver ums-jumpshot
[   27.277659] usbcore: registered new interface driver ums-karma
[   27.283543] usbcore: registered new interface driver ums-onetouch
[   27.289744] usbcore: registered new interface driver ums-realtek
[   27.295803] usbcore: registered new interface driver ums-sddr09
[   27.301802] usbcore: registered new interface driver ums-sddr55
[   27.307797] usbcore: registered new interface driver ums-usbat
[   27.314239] mousedev: PS/2 mouse device common for all mice
[   27.537107] usb 1-1: new high-speed USB device number 2 using orion-ehci
[   27.689755] usb-storage 1-1:1.0: USB Mass Storage device detected
[   27.696260] scsi host1: usb-storage 1-1:1.0
[   28.327105] rtc-mv rtc-mv: internal RTC not ticking
[   28.332179] i2c /dev entries driver
[   28.336555] sdhci: Secure Digital Host Controller Interface driver
[   28.342750] sdhci: Copyright(c) Pierre Ossman
[   28.387413] sdhci-pltfm: SDHCI platform and OF driver helper
[   28.396925] ledtrig-cpu: registered to indicate activity on CPUs
[   28.403177] usbcore: registered new interface driver r8712u
[   28.409190] gre: GRE over IPv4 demultiplexor driver
[   28.414150] NET: Registered protocol family 17
[   28.418838] Key type dns_resolver registered
[   28.425705] registered taskstats version 1
[   28.432447] Key type encrypted registered
[   28.437399] console [netcon0] enabled
[   28.441055] netconsole: network logging started
[   28.446171] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[   28.453370] hctosys: unable to open rtc device (rtc0)
[   28.463307] Waiting 10 sec before mounting root device...
[   28.698369] scsi 1:0:0:0: Direct-Access     SanDisk  Cruzer Fit       1.00 PQ: 0 ANSI: 6
[   28.708413] sd 1:0:0:0: [sda] 31260672 512-byte logical blocks: (16.0 GB/14.9 GiB)
[   28.716303] sd 1:0:0:0: Attached scsi generic sg0 type 0
[   28.722210] sd 1:0:0:0: [sda] Write Protect is off
[   28.728408] sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[   28.744762]  sda: sda1 sda2
[   28.751773] sd 1:0:0:0: [sda] Attached SCSI removable disk
[   38.477451] VFS: Cannot open root device "LABEL=rootfs" or unknown-block(0,0): error -6
[   38.485427] Please append a correct "root=" boot option; here are the available partitions:
[   38.493864] 0100            8192 ram0  (driver?)
[   38.498542] 0101            8192 ram1  (driver?)
[   38.503152] 0102            8192 ram2  (driver?)
[   38.507812] 0103            8192 ram3  (driver?)
[   38.512423] 0104            8192 ram4  (driver?)
[   38.517027] 0105            8192 ram5  (driver?)
[   38.521688] 0106            8192 ram6  (driver?)
[   38.526298] 0107            8192 ram7  (driver?)
[   38.530932] 0108            8192 ram8  (driver?)
[   38.535543] 0109            8192 ram9  (driver?)
[   38.540168] 010a            8192 ram10  (driver?)
[   38.544866] 010b            8192 ram11  (driver?)
[   38.549577] 010c            8192 ram12  (driver?)
[   38.554275] 010d            8192 ram13  (driver?)
[   38.558993] 010e            8192 ram14  (driver?)
[   38.563692] 010f            8192 ram15  (driver?)
[   38.568408] 0800        15630336 sda  driver: sd
[   38.573015]   0801        15105024 sda1 63754a41-01
[   38.577898]   0802          524288 sda2 63754a41-02
[   38.582761] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[   38.590996] CPU: 0 PID: 1 Comm: swapper Not tainted 4.4.45-1-ARCH #1
[   38.597322] Hardware name: Pogoplug V4
[   38.601094] [<c0010524>] (unwind_backtrace) from [<c000d9d0>] (show_stack+0x10/0x14)
[   38.608820] [<c000d9d0>] (show_stack) from [<c00cda50>] (panic+0x88/0x208)
[   38.615678] [<c00cda50>] (panic) from [<c08522c8>] (mount_block_root+0x1a0/0x260)
[   38.623131] [<c08522c8>] (mount_block_root) from [<c0852578>] (mount_root+0xf4/0x120)
[   38.630931] [<c0852578>] (mount_root) from [<c0852700>] (prepare_namespace+0x15c/0x1bc)
[   38.638906] [<c0852700>] (prepare_namespace) from [<c0851eb4>] (kernel_init_freeable+0x1fc/0x254)
[   38.647756] [<c0851eb4>] (kernel_init_freeable) from [<c0648c7c>] (kernel_init+0x8/0xe8)
[   38.655817] [<c0648c7c>] (kernel_init) from [<c000a4d0>] (ret_from_fork+0x14/0x24)
[   38.663361] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Thanks!

BTW - The SD Card was ejected prior to power on and the Arch installation was done according to the instructions in the Terminally Incoherent blog.



Edited 1 time(s). Last edit at 02/26/2017 07:55PM by TastesLikeChickN.
Re: How do I get out of my Pogoplug Mobile rathole?
February 27, 2017 12:53AM
TastesLikeChickN,

> U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700)
> Pogoplug V4

> [    0.000000] Linux version 4.4.45-1-ARCH (buildu
> ser@leming) (gcc version 6.3.1 20170109 (GCC) ) #1
> PREEMPT Sat Jan 28 22:31:00 MST 2017

> [    0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)

You are booting my u-boot-2016.05-tld-1 image (with the default u-boot envs, and some envs are missing), and trying to boot Arch rootfs. This will not work right away, since the rootfs are slightly different. I have the instruction to boot Arch somewhere, but not written completely and clearly.

So, since you don't care whether it runs Arch or Debian. Here is how to boot Debian rootfs:

1. Create Debian rootfs: http://forum.doozan.com/read.php?2,12096

Scroll down to 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.

Note: Follow the instruction very closely (being root user, create single Ext3 partition). And don't do step 4, since you are booting with the latest u-boot.

2. After creating this rootfs, plug it in the Pogo Mobile and power up, interrutp serial console, and adjust your u-boot env to point to the correct DTB location:

setenv dtb_file '/boot/dts/kirkwood-pogoplug_v4.dtb'

and then
printenv
boot

If not successfully booted into Debian, pls post the entire serial console log here.

If for whatever reason, you'd like to stay with Arch rootfs, I'll need to cleanup some instructions (that I've posted before) for you 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



Edited 2 time(s). Last edit at 02/27/2017 01:01AM by bodhi.
Re: How do I get out of my Pogoplug Mobile rathole?
March 04, 2017 10:22PM
Sorry for the delay in responding. Long week.

I can now reliably boot my 'Plug in Debian. Woo-hoo.

These are some notes on what I did (and didn't) do:
  • I created the Debian rootfs as you stated above. In addition to skipping Step 4, I also skipped Step 3 (Adjust fstab) since I had installed the latest U-Boot for Kirkwood.
  • I also skipped Note2 since I did not have a uEnv.txt file. Instead I created one with the correct dtb_file path:
dtb_file=/boot/dts/kirkwood-pogoplug_v4.dtb
devices=usb
devices=mmc usb ide
disks=0 1 2 3 4 5 6 7
  • I set and additionally saved my dtb_file env var.
  • After booting, I disabled IPv6 using these instructions because my 'Plug will never need it where it is going.
With all that done, I went through the boot console messages and have some questions:
  • Do my env vars look OK? I did some digging and still do not understand what does or does not need to be set and why.
  • Are the "** Bad device mmc # **" errors from the "disks=0 1 2 3 4 5 6 7" line in my uEnv.txt? If so, do I delete this line?
  • Are any of these error-looking messages a concern?
[    0.171429] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[    1.285998] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 36
[    1.286022] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 37
[    1.286040] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 38
[    1.286058] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 39
[    1.286076] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 40
[    1.286093] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 41
[    1.286110] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 42
[    1.286128] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 43
[    1.286145] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 44
[    1.286163] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 45
[    1.286180] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 46
[    1.286198] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 47
[    1.286215] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 48
[    1.286233] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 49
Warning: File system check failed but did not detect errors
[   20.769718] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem
[   20.788923] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
done.
[   24.863264] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
  • Did I somehow screw up the formatting of my USB? I thought it was formatted with a single Ext3 partition, but I have seen Ext2 and Ext4.
root@debian:~# fdisk -l /dev/sda

Disk /dev/sda: 14.9 GiB, 16005464064 bytes, 31260672 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x95537bd3

Device     Boot Start      End  Sectors  Size Id Type
/dev/sda1  *     2048 31260671 31258624 14.9G 83 Linux

root@debian:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
/dev/root      /               ext2    noatime,errors=remount-ro 0 1
tmpfs          /tmp            tmpfs   defaults          0       0
root@debian:~#
A screen capture with my reboot, interupt, print env vars, boot, and login is attached as a file. I think I hit some limit with the size of this post and could not embed it.

Many, many thanks again!
Attachments:
open | download - screenlog.txt (26.8 KB)
Re: How do I get out of my Pogoplug Mobile rathole?
March 04, 2017 11:26PM
TastesLikeChickN,

> I can now reliably boot my 'Plug in Debian. Woo-h
> oo.

Cool :)

> In addition to skipping Step 4, I also skipped
> Step 3 (Adjust fstab) since I had installed the la
> test U-Boot for Kirkwood.

That's fine. But you should check the mount to make sure it looks ok. If rootfs is mounted as ext3 then it is OK.
mount
expected output
/dev/sda1 on / type ext3 (rw,noatime,errors=remount-ro,data=ordered)

> [*] I also skipped Note2 since I did not have a uE
> nv.txt file. Instead I created one with the corre
> ct dtb_file path:

Correct.

> Are the "** Bad device mmc # **" errors from t
> he "disks=0 1 2 3 4 5 6 7" line in my uEnv.txt? I
> f so, do I delete this line?

No, this is because you have no SD card in the slot. If you don't plan to boot with SD card then remove it from the devices env in uEnv.txt to have less noise. But it is just a warning. You can leave it as is.
devices=usb ide

> [ 0.171429] [Firmware Info]: /ocp@f1000000/ethe
> rnet-controller@72000/ethernet0-port@0: local-mac-
> address is not set

This is OK.

> [ 1.285998] kirkwood-pinctrl f1010000.pin-contr
> oller: unknown pinctrl group 36
> ...
> oller: unknown pinctrl group 48
> [ 1.286233] kirkwood-pinctrl f1010000.pin-contr
> oller: unknown pinctrl group 49

This is OK. Just a warning. It has been removed in later kernel version.

> Warning: File system check failed but did not dete
> ct errors
> [ 20.769718] EXT4-fs (sda1): mounting ext3 file
> system using the ext4 subsystem
> [ 20.788923] EXT4-fs (sda1): mounted filesystem
> with ordered data mode. Opts: (null)
> done.

This is a standard kernel message when you use Ext3 nowadays. Not an error.

As I said above, run the mount command to see if everything is OK. If you see something like this then it's working fine:
/dev/sda1 on / type ext3 (rw,noatime,errors=remount-ro,data=ordered)

Congrats :) you got you plug running as it should.

-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
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: