public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Xu Yang <risingsunxy@googlemail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: ramdisk
Date: Mon, 03 Sep 2007 11:03:04 -0400	[thread overview]
Message-ID: <46DC2228.7080503@tmr.com> (raw)
In-Reply-To: <ab40e9c0709030604u5fecf34dr945ece01b95e622d@mail.gmail.com>

Xu Yang wrote:
> Hi everyone,
> 
> I want to use ramdisk to boot my filesystem, as I can't use NFS and harddisk.
> 
> I have load the ramdisk into the ram memory (start address :0x4000000)
> 
> and in the boot options I specified : root =dev/ram0 initrd=0x4000000
> 
> but the kernel said it can not find any file system on it.
> 
Looking at the information below, did the program which loaded the 
filesystem into RAM decompress it? It noted that it was compressed so I 
would assume so, but I am unfamiliar with ARM tools, so I ask the 
question. Also, should the boot device be "/dev/ram0" rather than 
"dev/ram0" or is that correct for your system?

> Here is the information I can supply :
> U-Boot 1.2.0 (Aug 31 2007 - 20:54:55)
> 
> ***  Auto-detects ethernet chip ***
> 
> 
> 
> DRAM:   0 kB
> ## Unknown FLASH on Bank 1 - Size = 0x00000000 = 0 MB
> Flash:  0 kB
> *** Warning - bad CRC, using default environment
> 
> In:    serial
> Out:   serial
> Err:   serial
> 
> Hit any key to stop autoboot:  0
> ## Booting image at 00007fc0 ...
>    Image Name:   Linux-2.6.19-arm2
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    740372 Bytes = 723 kB
>    Load Address: 00008000
>    Entry Point:  00008000
> OK
> 
> 
> ## Loading Ramdisk Image at 04000000 ...
>    Image Name:   ramdisc
>    Image Type:   ARM Linux RAMDisk Image (gzip compressed)
>    Data Size:    12582962 Bytes = 12 MB
>    Load Address: 04000000
>    Entry Point:  04000000
> 
> Starting kernel ...
> 
> 
> .........................................................................................
> 
> RAMDISK driver initialized: 16 RAM disks of 10240K size 1024 blocksize
> <6>loop: loaded (max 8 devices)
> <6>mice: PS/2 mouse device common for all mice
> <6>VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 3
> No filesystem could mount root, tried:  ext2 cramfs vfat
> <0>Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(1,0)
> 
> 
> Who can give me some hints ? or point me some direction to handle this.
> 
> I appreciate this very much.
> 
> regards,
> 
> Yang


-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

  reply	other threads:[~2007-09-03 15:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-03 13:04 ramdisk Xu Yang
2007-09-03 15:03 ` Bill Davidsen [this message]
2007-09-03 17:03   ` ramdisk Xu Yang
2007-09-03 23:21     ` ramdisk Bill Davidsen
2007-09-04  8:52       ` ramdisk Xu Yang
2007-09-04 15:04 ` ramdisk linux-os (Dick Johnson)
2007-09-04 21:37   ` ramdisk Xu Yang
2007-09-04 22:43     ` ramdisk linux-os (Dick Johnson)
2007-09-05  8:07   ` ramdisk Uli Luckas
2007-09-05 11:22     ` ramdisk Xu Yang
2007-09-05 11:35       ` ramdisk Xu Yang
2007-09-19 17:14         ` ramdisk Midhun A

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=46DC2228.7080503@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=risingsunxy@googlemail.com \
    /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