@denexo,

> Is it possible to be able to load
> Jeff''s rescue system at NAND when no other rootfs
> is found? If it helps, i have kept a backup of fw
> boot env config prior installing your U-BOOT. What
> i mostly want to ask if setting the following boot
> envs (as seen at Jeff's script):
>

> fw_setenv rescue_installed 1
> fw_setenv set_bootargs_rescue 'setenv bootargs
> console=$console ubi.mtd=2 root=ubi0:rootfs ro
> rootfstype=ubifs $mtdparts'
> fw_setenv bootcmd_rescue 'run set_bootargs_rescue;
> nand read.e 0x800000 0x100000 0x400000; bootm
> 0x800000'
> fw_setenv bootcmd_pogo 'run bootcmd_rescue'
>

> will make the rescue system working again

Yes it will! My 2014.07 u-boot is a drop-in replacement for the 2011 (davygravy) u-boot. Your current u-boot envs should work exactly the same same way as before.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

@bodhi,

thanks very much for confirming! Will try as soon as i go home and try!
Another quick question: i saw that your U-BOOT supports ext4 rootfs. I preparerd a sata drive with first partition named 'rootfs' and ext4 filesystem, but seeing netconsole messages, i saw error messages that it couldn't find /boot/kernel and /boot/uImage. I didn't have time to dig deeper at the time. I changed accordingly rootfstype to ext4, edited properly /etc/fstab but no luck. I can't recall though seeing the 'usb_root LABEL=rootfs' when doing 'fw_printenv |grep rootfs'. Could this be the case?

denexo,

Not exactly! loading the kernel uImage/uInitrd and mounting rootfs are 2 different phases in booting. Just so happen that the rootfs is on an Ext4 partition (therefore uImage and uInitrd are on /boot of that partition).

1. uImage and uInitrd loading: instead of ex2tload, use ext4load, see if it behaves differently:

ext4load usb 0:1 /boot/uImage
ext4load usb 0:1 /boot/uInitrd

or

ext4load ide 0:1 /boot/uImage
ext4load ide 0:1 /boot/uInitrd

2. rootfs label parameter is relevant only on kernel bootargs (it does not come in to play in loading kernel):

setenv bootagrs .........   root=LABEL=rootfs  ........

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 2 time(s). Last edit at 11/14/2014 04:16AM by bodhi.

bodhi,

it was very explanatory! Will try later on this day. So from what i understand i will have to interrupt the boot and then try the ext4load.

bodhi,

i got a bit lazy and didn't try the ext4load option... I reformatted the disk to ext3 and everything worked fine. I also managed to properly edit the boot envs (by checking the kept backup) and got the nand rescue system working. I might try to check ext4 rootfs loading with a spare hdd i have.

installed the Uboot 2013-10 for Zyxel 325, flashed the envs you provided, restored the envs you say that must be restored, moved the initrd and uimage files in /boot folder. rootfs is ext4.

this is my enviroment (did some changes like making ext4load and changing rootfs partition)

U-Boot 2013.10-tld-1 (Aug 29 2014 - 22:07:26)
ZyXEL NSA325 2-Bay Power Media Server

SoC:   Kirkwood 88F6282_??
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot:  0 
NSA325> printenv
arcNumber=4495
baudrate=115200
bootcmd=run bootcmd_usb; run bootcmd_sata; run bootcmd_mmc; reset
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
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:50:43:00:02:02
if_netconsole=ping $serverip
ipaddr=192.168.0.231
led_error=orange blinking
led_exit=green off
led_init=green blinking
machid=118f
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=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2)
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
rootdelay=10
rootfstype=ext4
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=ext4load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext4load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda2
serverip=192.168.0.220
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

Environment size: 2325/131068 bytes

The rootfs and kernel is Debian 3.16 tld 2.

It does not boot, it just fails and says

Hit any key to stop autoboot:  0 
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 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 occured, error code = 112
ERROR: can't get kernel image!

Reset IDE: Bus 0: OK Bus 1: not available  
  Device 0: Model: FUJITSU MHV2060BH  Firm: 00000025 Ser#: NW79T6327A0V
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 57231.5 MB = 55.8 GB (117210240 x 512)
** Invalid partition 1 **
** Invalid partition 1 **
Wrong Image Format for bootm command
Error occured, error code = 112
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 occured, error code = 112
ERROR: can't get kernel image!
resetting ...

any idea of what I did wrong?

@ bobafetthotmail,

Looks like it failed in loading uImage and uInitrd:

sata_load_uimage=ext4load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext4load ide $device 0x1100000 /boot/uInitrd

To troubleshoot this, at serial console:

NSA325 > ide reset
NSA325> ide info
NSA325> ide part
NSA325> ext4ls ide 0:1 /boot

Please post output of the above commands.

The idea is to see if the hard disk and /boot partition was indeed assigned 0:1. This is because your $device is defined as:

device=0:1

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

ty for the tip. The main partition was dev/sda2 (I just deleted the /dev/sda1), so it was not 0:1.
did some image-repartition-restore and now it is /dev/sda1 and boots debian fine.

It seems it should be able to boot also arch or linux without uInitrd without making modifications, is that correct?

Now I'm just wondering why the nand boot (booting original firmware) fails... saying this

Unknown command 'mmc' - try 'help'
** Bad device mmc 0 **
** Bad device mmc 0 **
Wrong Image Format for bootm command
Error occured, error code = 112
ERROR: can't get kernel image!
resetting ...

bobafetthotmail Wrote:
-------------------------------------------------------
> ty for the tip. The main partition was dev/sda2 (I
> just deleted the /dev/sda1), so it was not 0:1.
> did some image-repartition-restore and now it is
> /dev/sda1 and boots debian fine.
>
> It seems it should be able to boot also arch or
> linux without uInitrd without making
> modifications, is that correct?
>
> Now I'm just wondering why the nand boot (booting
> original firmware) fails... saying this
>
>

Unknown command 'mmc' - try 'help'
> ** Bad device mmc 0 **
> ** Bad device mmc 0 **
> Wrong Image Format for bootm command
> Error occured, error code = 112
> ERROR: can't get kernel image!
> resetting ...
>

The error message above was because of mmc boot, for booting SD card (not NAND boot). You should remove it from the bootcmd. Mmc was included in the default env to cover all possible storage devices. But it is not needed in thix box.

And yes, it should boot Arch fine with the current envs.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 11/19/2014 04:35PM by bodhi.

I've uploaded 2014.07-tld-1 U-Boot image for the Sheevaplug. Please see 1post for download link. Thanks to Wzl, who did all the testing for this Sheevaplug u-boot image!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi,
I have a pogo e02, and wrote image to NAND by following the instruction, ther is no any error during the writting.
I also create Linux Kernel 3.17 (FDT) on a usb flash, and plug to the usb, after reboot, I do not see any message output from netconsole server. The light on pogo plug turns to green, but there is no connection(ip), i can't access the pogo.

I tried to remove usb flash, and restart pogo, the light keeps flashing yellow, and there is no connection.

is it a brick now ?

suo_jian,

> I also create Linux Kernel 3.17 (FDT) on a usb
> flash

Did you upgrade the kernel on an existing rootfs, or create a brand new rootfs?

> and plug to the usb, after reboot, I do not
> see any message output from netconsole server.

serverip=192.168.1.78
ipaddr=192.168.1.76
if_netconsole=ping 192.168.1.78
start_netconsole=setenv ncip 192.168.1.78; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
preboot=run if_netconsole start_netconsole

Your envs for netconsole look OK. How did you run nc server? from a Windows, Mac, or Linux box? the netcat (nc) programs on other OS might be not working properly. You can try different nc versions to see if any behave differently from another.

> usb_init=run usb_scan; setenv usb_root LABEL=ROOTFS rw

You don't need the rw.

> The light on pogo plug turns to green, but there is no
> connection(ip), i can't access the pogo.   
>

It's a very good sign that it turned green.

> I tried to remove usb flash, and restart pogo, the
> light keeps flashing yellow, and there is no
> connection.
> 
> is it a brick now ?

No, it's not bricked.

When the LED is flashing and eventually turns solid green, it means the kernel has been loaded OK. Now the box might get stuck at mounting the roots. Quickest way to trouble shoot is the create a brand new rootfs using Ext3. Download the basic rootfs if you have not done so from the kernel/rootfs thread

Updated 31 Oct 2014: 
Rootfs Debian-3.17.0-kirkwood-tld-1

After booting into Debian, you can then troubleshoot easily from Linux.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

1. Did you upgrade the kernel on an existing rootfs, or create a brand new rootfs?

I create brand new rootfs.

2.Your envs for netconsole look OK. How did you run nc server? from a Windows, Mac, or Linux box? the netcat (nc) programs on other OS might be not working properly. You can try different nc versions to see if any behave differently from another.

I run it on a ubuntu(14.04.1 LTS) vm in a mac os :), the ubuntu vm's ip is 192.168.1.78.
the command i run is nc -l -u -p 6666
The version info is:
This is nc from the netcat-openbsd package. An alternative nc is available
in the netcat-traditional package.

I can apt-get apt-get netcat and have a try.

3. You don't need the rw.
well, I can't connect to pogo box, so no way to change it now.

4. When the LED is flashing and eventually turns solid green, it means the kernel has been loaded OK. Now the box might get stuck at mounting the roots. Quickest way to trouble shoot is the create a brand new rootfs using Ext3. Download the basic rootfs if you have not done so from the kernel/rootfs thread

yes, it's brand new rootfs from Debian-3.17.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 , and I format it by using ext3, it's 8G usb flash, the command i use is mkfs.ext3 /dev/sdb1
Btw, all rootfs/format are done in the ubuntu vm since mac can't write to ext3 easily....

another information, I have archlinux rootfs as well, when I plug it to pogoplug, it turns to solid green as well but without connection.

Oh, i pretty sure the debian rootfs works fine. I have another e02 without 2014.07 U-Boot image flush, it runs archlinux , and I just plugin the debian rootfs usb drive, it can start without any problem.



Edited 1 time(s). Last edit at 12/01/2014 01:54AM by suo_jian.

suo_jian,

> This is nc from the netcat-openbsd package. An
> alternative nc is available
> in the netcat-traditional package.
>

Yes, you need to run netcat-traditional.

> Btw, all rootfs/format are done in the ubuntu vm since mac can't write to ext3 easily....

This is fine, I do exactly this very often on a MacBook Pro.

I'm sure your problem is easy to see once netconsole is working.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi bodhi ,
I run netcat-traditional, and listening at 192.168.1.78, but there is no output.

any other suggestion?

suo_jian Wrote:
-------------------------------------------------------
> Hi bodhi ,
> I run netcat-traditional, and listening at
> 192.168.1.78, but there is no output.
>
> any other suggestion?

Check your nc command. The correct command is:

nc -lup 6666 192.168.1.78 6666

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi bodhi,
Checked with new command, still no message shown, is it possible the nc message is not sent to 192.168.1.78, but somewhere else?

suo_jian Wrote:
-------------------------------------------------------
> Hi bodhi,
> Checked with new command, still no message shown,
> is it possible the nc message is not sent to
> 192.168.1.78, but somewhere else?

Ah! it was reversed in u-boot envs :)

serverip=192.168.1.78
ipaddr=192.168.1.76
if_netconsole=ping 192.168.1.78
start_netconsole=setenv ncip 192.168.1.78; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
preboot=run if_netconsole start_netconsole

serverip is your listening server, ipaddr is your Pogo. So on your listening server (if it is set to 192.168.1.78), then:

nc -lup 6666 192.168.1.76 6666

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 12/02/2014 02:01AM by bodhi.

Tried, nc -lup 6666 192.168.1.76 6666 on 192.168.1.78, still no messages print. It may be the time to order a serial cable.

Good idea, but while you are waiting for serial,
- on server start pinging the pogo
ping 192.168.1.76

- power up the pogo
- if the pogo netconsole is running then you should see it responds to a few pings. If no response then either the network problem, or neconsole is not running at all.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

no response at all, I appreciate your help, will post the result after I get serial .

Hi Bodhi,

just wanted to say thank you because this new uboot has brought a new life to my PP4s.
Now I can reboot consistently (no matter which devices I have plugged in), I have NTP enabled (and services are not starting in 1970 anymore) and I have netconsole working (well, hoping I'll never need it!).

Thanks again!

Hi Bodhi,
I connected a serial-usb adaptor between e02 and ubuntu 14.04

The wire's map is : GND - GND, RXD - TXD, TXD - RXD according to http://blog.qnology.com/2013/10/pogoplug-e02-v2-serial-connection.html

and run
#> screen /dev/tty1

but nothing shows up in the console, am i missing some steps?

The info about adeptor from ubuntu:


#> lsusb
Bus 001 Device 003: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

root@ubuntu64:~# dmesg | grep tty
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=9c0eb3f7-22d4-4252-85bd-ff3096d10068 ro console=tty1 console=ttyS0
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=9c0eb3f7-22d4-4252-85bd-ff3096d10068 ro console=tty1 console=ttyS0
[ 0.000000] console [tty1] enabled
[ 0.000000] console [ttyS0] enabled
[ 0.524491] tty ttyS21: hash matches

suo_jian Wrote:
-------------------------------------------------------
> Hi Bodhi,
> I connected a serial-usb adaptor between e02 and
> ubuntu 14.04
>
> The wire's map is : GND - GND, RXD - TXD, TXD -
> RXD according to
> http://blog.qnology.com/2013/10/pogoplug-e02-v2-se
> rial-connection.html
>
> and run
> #> screen /dev/tty1
>
> but nothing shows up in the console, am i missing
> some steps?
>
> The info about adeptor from ubuntu:
>
>
> #> lsusb
> Bus 001 Device 003: ID 067b:2303 Prolific
> Technology, Inc. PL2303 Serial Port
> Bus 001 Device 001: ID 1d6b:0001 Linux Foundation
> 1.1 root hub
>
> root@ubuntu64:~# dmesg | grep tty
> [ 0.000000] Command line:
> BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic
> root=UUID=9c0eb3f7-22d4-4252-85bd-ff3096d10068 ro
> console=tty1 console=ttyS0
> [ 0.000000] Kernel command line:
> BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic
> root=UUID=9c0eb3f7-22d4-4252-85bd-ff3096d10068 ro
> console=tty1 console=ttyS0
> [ 0.000000] console [tty1] enabled
> [ 0.000000] console [ttyS0] enabled
> [ 0.524491] tty ttyS21: hash matches

It is best to set baud rate, parity,... explicitly. See varkey's setup:
http://varkey.in/seagate-goflex-net-serial-connection/

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Guidobelix Wrote:
-------------------------------------------------------
> Hi Bodhi,
>
> just wanted to say thank you because this new
> uboot has brought a new life to my PP4s.
> Now I can reboot consistently (no matter which
> devices I have plugged in), I have NTP enabled
> (and services are not starting in 1970 anymore)
> and I have netconsole working (well, hoping I'll
> never need it!).
>
> Thanks again!

Cool! Glad it works well for you!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi Bodhi,

I've flashed uboot with your uboot file for my pogoplug e02. I did until step A and rebooted.
After that, I can't connect my pogoplug via SSH. I tried to boot with USB which contains Debian linux (I used it with older uboot by Doozan), but it failed.

Followings are my netconsole dialog when pogoplug is booted with USB.

U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:29:52)
Pogo E02
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Hit any key to stop autoboot:  0
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
** File not found /rescueme **
** Unrecognized filesystem type **
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=3"
UBI: MTD device size:            91 MiB
UBI: number of good PEBs:        728
UBI: number of bad PEBs:         0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     0
UBI: available PEBs:             717
UBI: total number of reserved PEBs: 11
UBI: number of PEBs reserved for bad PEB handling: 7
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "rootfs", error -22
UBIFS error (pid 0): ubifs_mount: Error reading superblock on volume 'rootfs' errno=-22!

ubifsmount - mount UBIFS volume

Usage:
ubifsmount <volume-name>
    - mount 'volume-name' volume
1 bytes read in 252 ms (0 Bytes/s)
Found bootable drive on usb 0:1
1435696 bytes read in 324 ms (4.2 MiB/s)
4682500 bytes read in 461 ms (9.7 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.32-5-kirkwood
   Created:      2000-01-01   4:40:48 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1435632 Bytes = 1.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-2.6.32-5-kirkwood
   Created:      2000-01-01   4:40:50 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4682436 Bytes = 4.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK


Starting kernel ...

Alos, followings are my environment. I checked this is equal to my old environment.

arcNumber=2097
baudrate=115200
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
bootdelay=10
console=ttyS0,115200
ethact=egiga0
ethaddr=00:25:31:02:24:CA
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
if_netconsole=ping $serverip
ipaddr=192.168.1.11
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
ncip=192.168.1.42
partition=nand0,2
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
preboot=run if_netconsole start_netconsole
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
serverip=192.168.1.42
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_device=0:1
usb_init=run usb_scan
usb_root=/dev/sda1
usb_rootdelay=10
usb_rootfstype=ext2
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_scan_list=1 2 3 4
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params

Environment size: 2598/131068 bytes

Thank you.

gunjaekoo,

Does the LED lit solid green? do you use static IP address? netconsole only shows that much, nothing more, unless you set it up further. All I can suggest is:

- Take the USB to another box and do fsck to make sure there is no file system error.

- If there was no error, perhaps try rootfs label approach:

1. Take the USB to another Linux box, mount it and label the rootfs (if it is mounted as /media/sdb1):

tune2fs -L rootfs /media/sdb1
sync

Then, umount the USB drive.

2. Plug in the USB to the Pogo. Boot up, interrupt netconsole, and:

setenv usb_init "run usb_scan; setenv usb_root LABEL=rootfs" 
boot

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 12/04/2014 09:15PM by bodhi.

Hi Bodhi,

Thank you for your reply. (I'm gunjaekoo...)
I tried to set label and also change environment for usb_init. But, pogoplug doesn't work eigher.
Yes. The light is green consistantly.

BTW, when I checked bad blocks,

root@debian:~# dmesg | grep -i 'bad'
[    9.336843] Scanning device for bad blocks
[    9.345723] Bad eraseblock 45 at 0x0000005a0000

But, I believe it is out of 1M area for uboot. Right?

gunjae,

> But, I believe it is out of 1M area for uboot.
> Right?

Right, it is way out, higher than 1M. Besides, your u-boot in NAND has booted until after the kernel was loaded successfully, and solid green LED means kernel was loaded and starting. So it is not u-boot. The remaining possible problems are bootargs and rootfs mounting. And your bootargs look OK. So for whatever reason, the rootfs mounting could have been unsuccessful.

If you have another USB drive, try download the latest rootfs and format the drive as ext2 or ext3 (does not matter), and boot with it (this is to verify that your u-boot is working OK):

Rootfs Debian-3.17.0-kirkwood-tld-1 (Updated 31 Oct 2014)

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi bodhi,

I booted the pogoplug successfully with new rootfs of 3.14 linux kernel after I wrote a new fresh image on another thumb drive. Strangely, I failed to boot with the same image which I tested on the old u-boot environment but I succeeded with the new fresh image. I don't know why.

I really appreciate your help.

Gunjae



Edited 1 time(s). Last edit at 12/05/2014 02:28AM by gunjae.