U-Boot w/ MMC/SD-card booting for Pogoplug Series 4

nguyen Wrote:
-------------------------------------------------------
> Have anyone able to boot original Pogoplug Linux
> using this uBoot?

I never really try to do that. But it would be very doable. Just remember to save your orginal uBoot envs to a text file. And then later set them back to boot the correct mtdparts. Installing this uBoot image using Linux command only overwrites mtd0 (so all other mtd parts, where pogo OS is, will remain intact).

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

I've followed bodhi's instruction, it was really friendly to understand.
I think that sd slot of my v4 has defect, because all of my sd cards has shown same messages.
is there anyone who have same problem like me? I couldn't find on google.


Pogov4> mmc init
mmc init
SD found. Card desciption is:
Manufacturer: 0x00, OEM "\x00\x00"
Product name: "SMI ", revision 1.0
Serial number: 10145
Manufacturing date: 8/2006
CRC: 0x00, b0 = 0
mmc block read error
mmc1 is available

Kernel is not starting.
I've finally found the sd card whch doesn't show "block read error". However after loading two kinds of images, it's hang with "Starting Kernel...".

I know that message doesn't mean it's not working. I already have a working usb stick with that message. so I've tried to duplicate "dd if=/dev/working-usb of=/dev/found-sd", but SD card didn't work. I checked DHCP/static ip on my router table.

Do I have to use serial cable for figuring out what's going on? Unfortunately, initramfs net console didn't worked also. Is there any workaround?



Edited 5 time(s). Last edit at 07/21/2013 10:51PM by yoonbae81.

yoonbae81 Wrote:
-------------------------------------------------------
> Kernel is not starting.
> I've finally found the sd card whch doesn't show
> "block read error". However after loading two
> kinds of images, it's hang with "Starting
> Kernel...".
>
> I know that message doesn't mean it's not working.
> I already have a working usb stick with that
> message. so I've tried to duplicate "dd
> if=/dev/working-usb of=/dev/found-sd", but SD card
> didn't work. I checked DHCP/static ip on my router
> table.
>

> Do I have to use serial cable for figuring out
> what's going on? Unfortunately, initramfs net
> console didn't worked also. Is there any
> workaround?

What I would do is: format the SD card to have the same type of file system as the USB (ie. ext2 or ext3), and then copy the rootfs:

- log in to another Linux box as root, mount both (assuming USB is sdb1 and SDD is sdc1, mounted under /media)
cp -aR /media/sdb1/* /media/sdc1/
sync
- unmount SDD and boot with it.

Try this first, if it does not work then next step is making sure persistent net rules are either commented out of removed:

cat /etc/udev/rules.d/70-persistent-net.rules

# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# Unknown net device (/devices/platform/mv643xx_eth_port.0/net/eth0) (mv643xx_eth_port)
#SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:10:75:xx:xx:xx", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

cat /lib/udev/rules.d/75-persistent-net-generator.rules

# device name whitelist
KERNEL!="Eth*|ath*|Wlan*[0-9]|msh*|ra*|sta*|ctc*|lcs*|hsi*", \
					GOTO="persistent_net_generator_end"

- If that does not help, then you'll need serial console.

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

Hello All - I bricked my Pogoplug Mobile V4 A1-04

I currently have a UART hooked up and was successful at loading the latest U-Boot in nand that can boot through SD.
I have tried loading the latest version Arch Linux as well as the latest version of Debian shown in this long and winding post.
I have tried various settings of setenv's and it always results in a hang.
All of the original Nand got trashed so all I have flash'ed is the boot that seems to work (?).
Attached is the printenv followed by the boot results ending in the 'hang'

If anyone can provide some insight into getting this going I would be grateful.
George



U-Boot 2011.12 (Apr 08 2012 - 19:03:41)
Cloud Engines-Pogoplug v4/Mobile:MMC version

SoC: Kirkwood 88F6281_A1
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
Hit any key to stop autoboot: 0
Pogov4> ?
? - alias for 'help'
base - print or set address offset
bdinfo - print Board Info structure
boot - boot default, i.e., run 'bootcmd'
bootd - boot default, i.e., run 'bootcmd'
bootm - boot application image from memory
bootp - boot image via network using BOOTP/TFTP protocol
chpart - change active partition
cmp - memory compare
coninfo - print console devices and information
cp - memory copy
crc32 - checksum calculation
dhcp - boot image via network using DHCP/TFTP protocol
echo - echo args to console
editenv - edit environment variable
env - environment handling commands
exit - exit script
ext2load- load binary file from a Ext2 filesystem
ext2ls - list files in a directory (default /)
false - do nothing, unsuccessfully
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls - list files in a directory (default /)
fsinfo - print information about filesystems
fsload - load binary file from a filesystem image
go - start application at address 'addr'
help - print command description/usage
iminfo - print header information for application image
imxtract- extract a part of a multi-image
itest - return true/false on integer compare
loadb - load binary file over serial line (kermit mode)
loads - load S-Record file over serial line
loady - load binary file over serial line (ymodem mode)
loop - infinite loop on address range
ls - list files in a directory (default /)
md - memory display
mii - MII utility commands
mm - memory modify (auto-incrementing address)
mmc - MMC sub-system
mtdparts- define flash/nand partitions
mtest - simple RAM read/write test
mw - memory write (fill)
nand - NAND sub-system
nboot - boot from NAND device
nfs - boot image via network using NFS protocol
nm - memory modify (constant address)
ping - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
reset - Perform RESET of the CPU
run - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv - set environment variables
showvar - print local hushshell variables
sleep - delay execution for some time
source - run script from memory
test - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protocol
true - do nothing, successfully
ubi - ubi commands
ubifsload- load file from an UBIFS filesystem
ubifsls - list files in a directory
ubifsmount- mount UBIFS volume
ubifsumount- unmount UBIFS volume
usb - USB sub-system
usbboot - boot from USB device
version - print monitor, compiler and linker version
Pogov4> printenv
alarm_args=setenv $boot_args_console root /dev/mmcblk0p1 rootwait rootfstype ext3
alarm_boot=ide reset
alarm_mmc=mmc init; mmc init; ext2load mmc 0:1 0x800000 /boot/uImage; ext2load mmc 0:1 0x1100000 /boot/uInitrd; setenv device /dev/mmcblk0p1; run alarm_args; bootm 0x800000 0x1100000
arcNumber=2097
baudrate=115200
bootargs=$(bootargs_console)
bootargs_console=console=ttyS0,115200
bootcmd=setenv bootargs $(bootargs_console); run bootcmd_mmc; bootm 0x00800000 0x01100000
bootcmd_mmc=mmc init; mmc init; ext2load mmc 0:1 0x00800000 boot/uImage; ext2load mmc 0:1 0x01100000 boot/uInitrd
bootcmd_usb=usb start; ext2load usb 0:1 0x00800000 /uImage; ext2load usb 0:1 0x01100000 /uInitrd
bootdelay=3
device=/dev/mmcblk0p1
ethact=egiga0
ethaddr=02:50:43:73:5d:82
filesize=2C16B8
ipaddr=192.168.1.50
isDisk=no
led_error=orange blinking
led_exit=green off
led_init=green blinking
loads_echo=1
mainlineLinux=no
mtddevname=u-boot
mtddevnum=0
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
partition=nand0,0
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
root=/dev/mmcblk0p1 rootwait rootfstype ext3
rootpath=/mnt/ARM_FS/
serverip=192.168.1.16
stderr=serial
stdin=serial
stdout=serial
ubifs_mtd=3
ubifs_set_bootargs=etenv bootargs console= ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)

Environment size: 1514/131068 bytes


Pogov4> boot
No MMC card found
SDHC found. Card desciption is:
Manufacturer: 0x03, OEM "SD"
Product name: "SU04G", revision 8.0
Serial number: 834365051
Manufacturing date: 5/2010
CRC: 0x00, b0 = 0
mmc1 is available
Loading file "boot/uImage" from mmc device 0:1 (xxa1)
2261056 bytes read
Loading file "boot/uInitrd" from mmc device 0:1 (xxa1)
6565586 bytes read
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.12.0-kirkwood-tld-1
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2260992 Bytes = 2.2 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-3.12.0-kirkwood-tld-1
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 6565522 Bytes = 6.3 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

GeorgeRosar,

Your uBoot envs for bootargs were not setup correctly.

alarm_args=setenv $boot_args_console root /dev/mmcblk0p1 rootwait rootfstype ext3 
alarm_boot=ide reset 
alarm_mmc=mmc init; mmc init; ext2load mmc 0:1 0x800000 /boot/uImage; ext2load mmc 0:1 0x1100000 /boot/uInitrd; setenv device /dev/mmcblk0p1; run alarm_args; bootm 0x800000 0x1100000 
arcNumber=2097 
baudrate=115200 
bootargs=$(bootargs_console) 
bootargs_console=console=ttyS0,115200 
bootcmd=setenv bootargs $(bootargs_console); run bootcmd_mmc; bootm 0x00800000 0x01100000 
bootcmd_mmc=mmc init; mmc init; ext2load mmc 0:1 0x00800000 boot/uImage; ext2load mmc 0:1 0x01100000 boot/uInitrd

- Should be something similar to this:

debian_set_bootargs=setenv bootargs console=$bootargs_console root=/dev/mmcblk0p1  rootdelay=10 rootfstype=ext3 $mtdparts 
bootcmd=run debian_set_bootargs; run bootcmd_mmc; bootm 0x00800000 0x01100000

See this thread for info:
http://forum.doozan.com/read.php?2,11663

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

Thanks -- I just got it working ! You are the best !

bohdi,
I currently am able to successfully boot and run Debian from a 4G SD card. However when I changed to a 16GB Lexar SD card I get intermittent results. Mostly not-good.
I ususally get "mmc block read error" when I try and boot the kernel and or ramdisk.
I created the file system as one large primary partition using > mke2fs -j /dev/sdc1
I've done diagnostics using fsck on my desktop ubuntu system and it appears everything is OK.

Here is what I see from an mmc init:
Pogov4> mmc init
SDHC found. Card desciption is:
Manufacturer: 0x28, OEM "BE"
Product name: " ", revision 1.0
Serial number: 2974000583
Manufacturing date: 8/2013
CRC: 0x00, b0 = 0
mmc1 is available

Once I boot into linux kernel I am able to successfully update, upgrade and load packages with apt-get.

Any help or suggestions would be appreciated.

- Geo

Geo,

Quote
boot the kernel and or ramdisk.

The MMC driver in uBoot seems to have problem with some SD cards. Might be the timing setings was too short and it's timed out too quickly.

Exactly what point did the block read error occurred? Did you mean during loading either one of the images? But once both were loaded, then it is OK? Do you still have the log or can recreate it?

I'll need to rebuild Davy's uBoot image if we want to make it more resilient. So far I've built a version with his USB patch only and it worked fine. I have not tried to add MMC yet.

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

I was not able to recreate the exact scenario but it seems if the hardware is off overnight (i.e cold) it can reboot.
Today I was able to boot from a 4Gi and then swap cards after it loaded uImage and uInitrd so that is the log file I attached.

I waited for a couple of hours and it booted good. I will attach that file as well.



Edited 1 time(s). Last edit at 11/30/2013 09:14AM by GeorgeRosar.

Geo,

I did not see anything peculiar other than the read errors. Have you tried to reformat the 16GB card? (ie. on Windows or Mac).

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

@Geo,

I'm also having problem with a Sandisk microSDHC 16GB (with Sandisk adapter). It was not recognized by this uBoot. Debian was fine with it after boot.

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

I wanted to thank people on this discussion board for the amazing help provided to hack up the Debian PogoPlug. Bodhi - u da man!

Here's a bit of a contribution in return :

I've had some issues with uboot not recognizing some SD cards and mysteriously working on others. Others online seem to have this problem often as well. I might have located the cause (and fix) for this - apparently some platforms dont read SD cards whose sizes are not a multiple of the cylinder count. Luckily there is a free SD Formatter (https://www.sdcard.org/downloads/formatter_4/) that does this for you.

1) Download and install the formatter
2) Enable Format Size Adjustment ON and Full Erase/Overwrite. Start the format.
3) Let it complete (takes a while). It makes a single large fat32 partition on the card.
4) Boot into a Linux system (including the pogoplug) and just mkfs.ext2 -L rootfs over the same fat partition to replace it with an ext2.
5) Extract the rootfs (http://forum.doozan.com/read.php?2,12096)
6) sync and reboot.

I had a 4G SanDisk SD card that refused to work before I did this. Now its running perfectly.

Vulcan, thanks for the tips!

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

Hi Bodhi,
Sorry for not getting back to this sooner ..... my desktop linux box was returned for service... long story. Now I'm back to looking at this pogoplug issue.

My 4GB card that works is a class 2 (2MBy/s) and my 16GB is class 6 (12MBy/s).

I'm not convinced that it is a cylinder size issue, because the pogoplug worked intermittently. If I let it sit for a while it works and if I try rebooting immediately it doesn't. What class/speed was your Sandisk card you tried?

I am going to try making a smaller partition for boot. Perhaps that will work.

Happy Holidays,
George

George,

Try this to see if it helps:
http://forum.doozan.com/read.php?3,14575

My card is microSDHC Sandisk Ultra 16GB, don't remember exactly but I think it is class 6. I could do mmc init twice and uBoot would recognize the card, but can not find the kernel on it. It is kind of flaky. I don't intend to use it for rootfs, though.

I don't have plan to play with CE Pogo V4 uBoot. (I've shelved it for another day, because the code is too old, very hard to read).

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

Could anyone please confirm that Bodhi procedure sketched above leaves booting
from a USB stick in tact. I am fine booting using an SD card, but can't get USB to work.
With netconsole I can see the USB device and even ext2ls files on the first (/dev/sda1)
partition. Running the usb_boot finds the kernel (ArchLinux latest) and starts it up;
and that's all I see. Can't ping the device, don't see it on my network, can't ssh into it.
Any ideas?

Thanks!

Geert Wrote:
-------------------------------------------------------
> Could anyone please confirm that Bodhi procedure
> sketched above leaves booting
> from a USB stick in tact. I am fine booting using
> an SD card, but can't get USB to work.
> With netconsole I can see the USB device and even
> ext2ls files on the first (/dev/sda1)
> partition. Running the usb_boot finds the kernel
> (ArchLinux latest) and starts it up;
> and that's all I see. Can't ping the device, don't
> see it on my network, can't ssh into it.
> Any ideas?
>
> Thanks!

Geert, which procedure?

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

Dear Bodhi,

All I wanted to know is whether DavyGravy's U-Boot on a Pogoplug Mobile V4-A1-01
still allows for booting from a USB stick. The "procedure" is your write-up on how
to flash the above U-Boot and set some env variables. So with this in place, I am fine
booting ArchLinux from an SD card. But I simply can't get the exact same image (of
rootfs) copied over to a USB stick to work. I even tried sticking the SD card in a USB
card reader and booting that, again no success. Of course once booted, any USB drive
attached to the Pogoplug will show up in ArchLinux and can be mounted etc.

Another question: there are several references on this and other forums about booting
back into the original Pogoplug OS. I have all that stuff in tact on my plug in the various
mtd partition. Can this be done with DavyGravy's U-Boot and how? It seems that I can get
the original kernel going using:

From a netconsole I do the setenvs:
load_nand=nboot 0x800000 0 0x200000
load_nand2=nboot 0x800000 0 0x500000
boot=bootm 0x800000
boot_nand=run load_nand boot || run load_nand2 boot

Pogov4> run boot_nand

Loading from nand0, offset 0x200000
Image Name: Linux-2.6.31.8
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2080956 Bytes = 2 MiB
Load Address: 00008000
Entry Point: 00008000
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-2.6.31.8
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2080956 Bytes = 2 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Using machid 0xf78 from environment

Starting kernel ...

But the device does not show up on the network.
What am I missing? I tried setting pogo_root to /dev/mtdblock4 to no avail.
I also dropped arcNumber and machid settings, no change.

Thanks.

Geert,

Booting ArchLinux is differrent from Debian. Arch does not use uInitrd, Debian does. Look at you uBoot env bootcmd. The procedure set this env to boot Debian, so uBoot will look for uInitrd. To boot Arch, bootcmd must be set to look for uImage only.

It should boot either USB or SD card. You could get a listing of your uBoot envs and post here.

- in Linux command line:
fw_printenv
- or in console
printenv

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



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

If the uInitrd does not exist, of course it will also simply be bypassed.

Thanks for the replies guys.
Now at least I know that USB booting is supposed to work with Davy's U-boot.
I am pretty sure I have all the env vars set up correctly.
I will have to do some debugging with my serial cable.

I am still curious to learn if anybody ever got booting into the original Pogoplug OS
going from Davy's U-boot on the Mobile A1. Or is this smply impossible and we need
to restore the original U-boot?

By the way, how come nobody mentions that the mtd4 partitition which holds the
root file system is using ubifs? Are there any successes of trying to mount a nanddump
of mtd4 via mtdram or a loop device?

Here are brief instructions to mount the NAND root partition holding the original Pogoplug
root file system. On Mobile and Series 4 this is no longer jffs2 but ubifs.

I did this on a Mobile V4-A1-01 running the latest ArchLinux (ALARM).
Make sure you have the mtd-utils package installed.

Attach the mtd partition holding the ubi file system (this should be mtd4):
(Mind the -O 2048; without it you will get errors)

[root@alarm ~]# ubiattach -O 2048 -p /dev/mtd4
UBI device number 0, total 894 LEBs (113516544 bytes, 108.3 MiB), available 0 L\
EBs (0 bytes), LEB size 126976 bytes (124.0 KiB)

This causes a /dev/ubi0_0 device to be created:

[root@alarm ~]# ls -l /dev/ubi*
crw------- 1 root root 248,  0 Jan  2 21:18 /dev/ubi0
crw------- 1 root root 248,  1 Jan  2 21:18 /dev/ubi0_0
crw------- 1 root root  10, 59 Dec 31  1969 /dev/ubi_ctrl

This you can immediately mount:
(Assume you created mkdir /mnt/disk ahead of time)

[root@alarm ~]# mount /dev/ubi0_0 /mnt/disk

Here is the proof. Showing the root directory:

[root@alarm ~]# ls -la /mnt/disk
total 4
drwxr-xr-x 14 root root  1064 Dec 28 13:59 .
drwxr-xr-x  3 root root  4096 Dec 29 21:33 ..
drwxr-xr-x  2 root root  4344 Aug 23  2011 bin
drwxr-xr-x  5 root root 19088 Dec 28 11:05 dev
drwxr-xr-x  5 root root  1304 Dec 28 14:11 etc
drwxr-xr-x  3 root root  2448 Dec 28 14:36 lib
drwx------  2 root root   160 Aug 23  2011 lost+found
drwxr-xr-x  2 root root   160 Jun 10  2010 mnt
lrwxrwxrwx  1 root root    17 Dec 28 13:59 opt -> /tmp/mnt_opt/.opt
drwxr-xr-x  2 root root   160 Jun  8  2010 proc
drwxr-xr-x  3 root root   224 Dec 28 14:20 root
drwxr-xr-x  2 root root  2784 Aug 23  2011 sbin
drwxr-xr-x  2 root root   160 Jun  8  2010 sys
drwxr-xr-x  2 root root   160 Jun 10  2010 tmp
drwxr-xr-x  8 root root   544 Dec 28 14:17 usr
lrwxrwxrwx  1 root root     8 Aug 23  2011 var -> /tmp/var

To undo the above actions, first unmount, then detach:

[root@alarm ~]# umount /mnt/disk
[root@alarm ~]# ubidetach -p /dev/mtd4

Be careful when modifying the mounted file system.

Quote
Geert
I am still curious to learn if anybody ever got booting into the original Pogoplug OS going from Davy's U-boot on the Mobile A1

Not too many people are interested in doing this, I think.

Quote
WarheadsSE
If the uInitrd does not exist, of course it will also simply be bypassed

Thanks, I've recalled incorrectly that my abbreviated instruction did not account for this, and let it up to the users to figure it out. But upon checking, it did :)
http://forum.doozan.com/read.php?2,11663

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

Bodhi ( & Geert)

On my second debian pogoplug installation, using a Pogoplug 'non' mobile Pogoplug series V4, I am having difficulty booting from a USB (the one on the top) - it hangs with: "Uncompressing Linux... done, booting the kernel"

For another clue, I set machid=FFFF and the kernel, I presume, complained, listing all of the available machid's.

I tried various combinations of root and rootpath variables such as:

root=dev/sda1 then root=/dev/usbda1, then root= "LABEL=ROOTFS rw"
and rootpath=/mnt/ARM_FS/ then rootpath= // empty

Any suggestions?


On a different thread - I looked further into SD cards that were class 6 and several of them did not work in the mobile V4 and a second class 2 8MB worked) Seems like the problems were due to speed. I also tried the SD-formatter fix described above [see 'VulcanTheTerrible' - Dec 24,2013] and that did not fix my problem . I am at this point just using 4GB SD cards speed 2.


George

GeorgeRosar,

> On my second debian pogoplug installation, using
> a Pogoplug 'non' mobile Pogoplug series V4, I am
> having difficulty booting from a USB (the one on
> the top) - it hangs with: "Uncompressing
> Linux... done, booting the kernel"

Pogo V4 USB 2.0 (top port) booting is very reliable with Davy's uBoot. Please post your console output and console printenv.

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

bodhi,
The last set of environments and output is attached- thanks in advance.
Geo-

Geo,

Your uBoot envs and boot log look good so far. The one thing I would do is temporarily stop netconsole

Boot with your working SD card into Debian and

fw_setenv preboot
fw_setenv preboot_nc 'run if_netconsole start_netconsole'

This way your UART booting will show the entire USB boot process, and hopefully we can see what went wrong.

Later, after everything is working, if you want to enable netconsole then add this uBoot env back:
fw_setenv preboot 'run preboot_nc'

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

I hooked up a serial cable and was finally able to debug why my Pogoplug Mobile would
not boot up from a USB stick (it works fine from an SD card). The cause was the USB stick
itself, a ADATA 8GB one. Although everything looked good when inspected and e2fck-ed
on my laptop, the stick refused to properly work in the Mobile; it booted and started ArchLinux
and then caused a load of I/O errors etc.

I took a fresh PNY 32GB stick and tried again. This one works flawlessly.
All right. Problem solved.

Anyone knows if it possible that this uBoot version can't transfer coherent_pool boot parameter to Linux ? (tried with Pogoplug Mobile)
I've no issue like this with Arch Linux uBoot on Pogoplug eSata.

Due to some kernel regression I need to manually set the coherent_pool to 1M so the firmware of my DVB device will load correctly.

I only made a quick test and even didn't looked at the uBoot's output it but I'm pretty sure my uBoot params are set right so I tends to blame uBoot.

I probably will end with patching the kernel as it seems much quicker than to fiddled around the uBoot sources.