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
