The Dockstar has an identical processor ("Kirkwood") to the
SheevaPlug, which is supported.
It takes some extra effort to "hack" the bootloader on the Dockstar,
but once I had that sorted, running Slackware on my Dockstar was no
problem.
On Tue, Jul 10, 2012 at 12:58 PM, Gregg Levine wrote:
> He
> 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 uti
Sounds great!
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
> Unless there's some way of
> installing via an alternative route, e.g. usb or sd?
See below. I used an SD card to assist with the process, but I believe
uBoot is reliable enough now you could just put /boot directly on the
USB hard drive and skip the SD card entirely.
Reprinted from
http://plu
> PS: Could the 128 MB RAM on my Dockstar be a problem, even if I use distcc?
I compiled MythTV on my DockStar using distcc so my SheevaPlug could
do all the grunt work (not cross-compiling in my case). RAM and CPU
consumption on the 'Star were very very low except linking; I had to
add 32MB of sw
> 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
> 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
> 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: http://plugapps.com/forum/viewtopic.p
Hello and welcome! There doesn't seem to be a lot of traffic on this
list, I guess because Armedslack "just works". Salix looks perfect for
netbooks, maybe an ARM port of it is in order. ;)
___
/yler
___
ARMedslack mailing list
ARMedslack@lists.armedslac
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 of
Update: the 'mtd3' chained-bootloader that I'm using is from
http://www.plugapps.com/index.php5?title=PlugApps:Pogoplug_Setboot so
I examined the kernel it ships with using 'mkimage -l' and it's Load
Address is the same as Armedslack's, 8000. This works because upon
closer examination, the stoc
>> 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 uImageIns
>> 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 |
>
I've been enjoying Armedslack on my Sheeva for a while so I've decided
to put it on my Seagate Dockstar (a stripped down Sheeva) too. This
presents a few challenges that I think I can overcome with a little
help:
DockStar's u-Boot is crippled, so I use it to chainload a better
u-Boot which I have
14 matches
Mail list logo
