[ARMedslack] A few questions on kirkwood initrd

Claudio Cavalera claudio.cavalera at gmail.com
Sun Nov 7 21:44:24 UTC 2010

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

(it's the uboot from doozan: http://jeff.doozan.com/debian/uboot/ )

I've set up a netconsole like suggested here
and it's working so and so.

The problem is that when I load the stuff from the tftpboot, but when
I bootm the last thing I see on my netcat session is:
Starting kernel...
then I would expect my dockstar to be online in order to ssh in it and
run setup, but it does not reply to ping. :-(

I've tried the commands from Stuart as well as the commands from the
original poster:
setenv arcNumber 2097
setenv mainlineLinux yes
usb start
tftpboot 0x1800000 armedslack-13.1/uinitrd-kirkwood.img
tftpboot 0x6000000 armedslack-13.1/uImage-kirkwood
setenv bootargs console=ttyS0,115200 kbd=it nic=auto:eth0:dhcp root=/dev/ram rw
bootm 0x6000000 0x1800000

The original poster also said something about an "uncompressed kernel"
to be used with dockstar.
Could be this the reason of my problem?


On Sun, Nov 7, 2010 at 21:49, Stuart Winter <m-lists at biscuit.org.uk> wrote:
>> setenv bootargs console=ttyS0,115200 nodhcp kbd=uk nic=auto:eth0:dhcp root=/dev/ram rw;bootm 0x00800000 0x01100000;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 0x00800000 0x01100000;reset
> --
> Stuart Winter
> Slackware ARM: www.armedslack.org
> _______________________________________________
> ARMedslack mailing list
> ARMedslack at lists.armedslack.org
> http://lists.armedslack.org/mailman/listinfo/armedslack

More information about the ARMedslack mailing list