[U-Boot] my u-boot freezing at Uncompress Linux...

Hi. dear all
my u-boot-2008.03 use tftp download my kernel ,
but my u-boot was frezzing at Uncompressing Linux ...
and show nothing anymore in my console
i try another way to start my kernel : nfs , but there is the same issue in my u-boot .
//here are is u-boot information in my console
TFTP from server 192.168.1.3; our IP address is 192.168.1.8 Filename 'uImage'. Load address: 0x31000000 Loading: ################################################################# ############################### done Bytes transferred = 1403736 (156b58 hex) ## Booting kernel from Legacy Image at 31000000 ... Image Name: slincearm_bootloader Created: 2009-05-19 5:11:32 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1403672 Bytes = 1.3 MB Load Address: 31000000 Entry Point: 31000040 Verifying Checksum ... OK XIP Kernel Image ... OK OK
Starting kernel ...
Uncompressing Linux.............................................................

Hi SlinceArm,
my u-boot-2008.03 use tftp download my kernel ,
but my u-boot was frezzing at Uncompressing Linux ...
I doubt that. Actually your Linux kernel freezes - U-Boots last message is the "Starting kernel .." message. It's all Linux from there.
So start troubleshooting your kernel. Searching the archieve for this mailing list will probably be a good start point.
Cheers Detlev

I doubt that. Actually your Linux kernel freezes - U-Boots last message is the "Starting kernel .." message. It's all Linux from there. So start troubleshooting your kernel. Searching the archieve for this mailing list will probably be a good start point.
thanks for your reply , Detlev : )
i rebuild a new kernel-2.6.24 and my console freezes at "Starting kernel..." and i will search this issue in forum .
but i still confuse in my case , it mean my u-boot setting is "correct" and my kernel cause this issue ??

Hi SlinceArm,
i rebuild a new kernel-2.6.24 and my console freezes at "Starting kernel..." and i will search this issue in forum .
Good luck.
but i still confuse in my case , it mean my u-boot setting is "correct" and my kernel cause this issue ??
I'm not sure what you mean by "U-Boot settings", but as you can see, U-Boot loads a kernel and transfers control to it, so I don't know what should be wrong in U-Boot _itself_.
Of course on the other hand, U-Boot transfers a commandline (bootargs) and the mystical a-tags to a Linuxkernel which interprets them, so this is also something you should check.
Cheers Detlev
participants (2)
-
Detlev Zundel
-
SlinceArm