linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "somshekar chandrashekar kadam" <som_kadam1@rediffmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: denx 3.1.1 eldk ramdisk_image
Date: 16 Oct 2005 12:53:38 -0000	[thread overview]
Message-ID: <20051016125338.12386.qmail@webmail50.rediffmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]


Hi ,

  thanks Wlofgang Denk for the answer we can use ramdisk image used for other kernel version , 
now i am using ELDK 3.1.1 , and also using the ramdisk image provided by the ELDK ramdisk_image.gz , 
and in kernel i have configured for intial ramdisk support with size 4096 and for ext2 file system , 
it gives the message 

VFS kernel panic unable to mount root fs 01:00 

i tried both options 
first one making a multi image 
using mkimage clubbing it into one image FI64_fresh , with vmlinux.gz and ramdisk_image.gz 

./mkimage -A ppc -O linux -T multi -C gzip -a 0 -e 0 -n FI64_fresh -d vmlinux.gz:ramdisk_image.gz FI64_fresh
  
i download FI64_fresh at 0x500000 using tftpboot 

use bootm 0x500000 to boot the kernel i get the above message .

second option 

at 0x500000 in ram i download uImage of the linux-2.4.25 .
at 0x600000 i download ramdisk_image.gz 

and use the command 
bootm 0x500000 0x600000 
 i get the same message as above 

i do intial check using imi command it says images are fine after veryfing checksum 

is it i am missing somethoing else please let me know or is there any other way to check this 


Thanks In Advance 
Neelu 

[-- Attachment #2: Type: text/html, Size: 1681 bytes --]

             reply	other threads:[~2005-10-16 13:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-16 12:53 somshekar chandrashekar kadam [this message]
2005-10-16 22:34 ` denx 3.1.1 eldk ramdisk_image Wolfgang Denk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051016125338.12386.qmail@webmail50.rediffmail.com \
    --to=som_kadam1@rediffmail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).