But tbh I'm not sure whether I want to support this device officially
(in-tree) because the RPi doesn't support initrds which means potentially
a big change to how I build the kernels and modules packages;
In my experiments with ARMedSlack on a Seagate DockStar, I remember
using a mkboot
what CPU/RAM/flash does the Seagate Dockstar have?
1.2GHz ARMv5TE (Kirkwood), 128MB DDR RAM, 256MB flash.
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
Now I wonder if I should buy an IGEPv2 board. It seems very promising. This
indeed would be a nice thing to start a Salix port. Does anybody have
experience with this one?
Don't know anything about that but here's a forum posting about cheap
ARM devices:
I have a Dockstar coming directly from Seagate ($39 USD) and would like to
run ARMedslack on it. Is there a single site that provides instructions on
how I would go about this?
http://jeff.doozan.com/debian/uboot/ has the basic procedure. Rather
than run the script, I just ran the important
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
