Without saying much to that effect, U-Boot as installed this week per http://archlinuxarm.org/platforms/armv5 ... 2-pinkgray (unlike earlier versions, also Jeff Doozan's for Debian) does not boot from NAND anymore if no readable USB media is found.
With #/etc/init.d/hbmgr.sh start commented out in /etc/init.d/rcS, the stock OS can prove invaluable as an emergency partition though, when (rather than if) the USB stick fails.
How do I re-enable this very useful fallback from within a current, working Arch (after pacman -S uboot-env mtd-utils) ?
$this->bbcode_second_pass_code('', '# uname -a
Linux alarm 3.19.1-2-ARCH #1 PREEMPT Mon Mar 16 05:48:43 MDT 2015 armv5tel GNU/Linux
# dmesg
[ 14.618675] nand: Could not find valid ONFI parameter page; aborting
[ 14.625121] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[ 14.631502] nand: Hynix NAND 128MiB 3,3V 8-bit
[ 14.635984] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 14.643598] Scanning device for bad blocks
[ 14.725395] 2 cmdlinepart partitions found on MTD device orion_nand
[ 14.731686] Creating 2 MTD partitions on "orion_nand":
[ 14.736870] 0x000000000000-0x000000100000 : "u-boot"
[ 14.742326] 0x000000100000-0x000008000000 : "rootfs"')
Moreover, is there a way to give it the ability to boot bodhi's Debian jessie http://forum.doozan.com/read.php?2,1209 ... #msg-12096 (FDT rootfs) as well?
P.S.: The above NAND partitioning (2 rather than 4, apparently set by http://os.archlinuxarm.org/os/armv5te/b ... go_e02.env) seems to contradict what http://archlinuxarm.org/os/armv5te/boot ... ogo_e02.sh saw according to its preserved log (and there's no valid line in /etc/fw_env.config either) - shouldn't this be fixed, and if so, how?$this->bbcode_second_pass_code('', 'erasing U-Boot NAND [OK]
erasing environment [OK]
writing U-Boot [OK]
writing environment [OK]
Validating..
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x000c0000 and ending at 0x000e0000...')