Welcome! Log In Create A New Profile

Advanced

fail to tftpload Jeff's 2.6.32-5-kirkwood kernel + ramdisk

Posted by Chin 
Forum List Message List New Topic
Chin
fail to tftpload Jeff's 2.6.32-5-kirkwood kernel + ramdisk
August 13, 2011 12:59PM
I tried in vain to tftpload my new compiled 2.6.38 kernel + ramdisk in u-boot.

So I thought testing first tftpload using Jeff's 2.6.32-5-kirkwood kernel + ramdisk which I took from the usb boot-stick created with Jeff's script (using the stick with success for months by now). But this fails too !

In u-boot, i do: 
Marvell>> tftpboot 0x00800000 uImage
Using egiga0 device
TFTP from server 192.168.a.b; our IP address is 192.168.c.d
Filename 'uImage'.
Load address: 0x800000
Loading: #################################################################
        #################################
done
Bytes transferred = 1431848 (15d928 hex)

Marvell>> tftpboot 0x01100000 uInitrd
Using egiga0 device
TFTP from server 192.168.a.b; our IP address is 192.168.c.d
Filename 'uInitrd'.
Load address: 0x1100000
Loading: #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 ##############################################################
done
Bytes transferred = 4714181 (47eec5 hex)
Marvell>>  bootm 0x00800000 0x01100000
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.32-5
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1431784 Bytes = 1.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4714117 Bytes = 4.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

After several minutes, a ping to the dockstar (ping 192.168.c.d) shows no response. What's wrong ?

B.t.w., md5sum:
3703cf3d93eba20151c779a7e5027aaf /var/lib/tftpboot/uImage
efef53223f6b923a5ee8bf6dbbc6005b /var/lib/tftpboot/uInitrd

Any idea ?
Reply Quote
Newer Topic Older Topic
Author:

Your Email:


Subject:
Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: