[..]
Though I am using a serial cable, it's theoretically possible to do
this without the serial cable by using the fw_envset commands to alter
the mtd3 u-Boot from within the DockStar' stock Linux install in NAND.
Though the armedslack installer initrd startup scripts look like they
should
If any of you wanted a happy ending, or at least closure, here it is:
My serial cable finally arrived but I still could not get the kernel
to boot. My first false start was loading the kernel to the same
location as on the SheevaPlug, 0x800, which put the kernel beyond
the DockStar's 128MB
I've tried to extract the initrd with gunzip and cpio; no
luck. What format is the Armedslack installer initrd in, and how do I
extract it?
One time I got this instructions from Stuart on how to extract initrd:
dd if=armedslack-current/isolinux/uinitrd-kirkwood.img bs=64 skip=1 |
gzip -dc
Unfortunately, the Dockstar won't finish booting the resulting image
It could be because the installer image is too large to fit in RAM, or
into the addresses into which you're loading it.
I think you're right. We're getting into stuff I don't know much about, but:
# mkimage -l
