Hello,
I'm the cause of this thread's revival. I aim to be the first armed
slacker without the serial cable. :-)
I've patched the uboot with these commands on the dockstar:
cd /tmp
wget http://plugapps.com/os/pogoplug/uboot/install_uboot_mtd0.sh
chmod +x install_uboot_mtd0.sh
./install_uboot_mtd0
> setenv bootargs console=ttyS0,115200 nodhcp kbd=uk nic=auto:eth0:dhcp
> root=/dev/ram rw;bootm 0x0080 0x0110;reset
Obviously best to take out "nodhcp", although it still worked with it in:
setenv bootargs console=ttyS0,115200 kbd=uk nic=auto:eth0:dhcp root=/dev/ram
rw;bootm 0x008
[..]
> 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
> sho
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
On 07/28/2010 07:00 PM, Tyler T wrote:
>> By the way, I used the extracted initrd to install Armedslack on my
>> > SD/MMC based system and there was no problem (I extracted initrd to the
>> > MMC card and booted it as my system has to little RAM to use initrd
>> > directly).
> That's clever. If I c
>> 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
> > 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 | cpio -div
>
> Ah, that worked, thank you!
The initrd for kirkwood is in "u-boot" format - it was made with u-boot's
"mkimage".
The s
>> 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 |
>
Hi,
> 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?
>
> Once I can do this, I believe I can repackage it with mkinitrd and go
> from there.
One time I got this instructions from Stuart on how to ext
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
11 matches
Mail list logo
