From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ralph Siemsen <rsiemsen@rossvideo.com>
Date: Wed, 28 Jul 2004 14:34:41 -0400
Subject: [U-Boot-Users] Flawed ATAG passing
In-Reply-To: <20040728164601.GA19459@stud4.tuwien.ac.at>
References: <20040728164601.GA19459@stud4.tuwien.ac.at>
Message-ID: <4107F1C1.8090308@rossvideo.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Christian Kapeller wrote:

> Machine: Intel DBPXA250 Development Platform (aka Lubbock)
> parse_tags number of tags: 5
> parsing tag: 0x54410001
> parse_tag: tag 0x54410001 
> parse_tag_core
> parsing tag: 0x54410002
> parse_tag: tag 0x54410002 
> parse_tag_mem32 start 0xa0000000 size 0x01000000

So your bootloader is passing fine the tags to kernel.

> Kernel command line: root=/dev/ram console=ttyS0,115200

Here you are telling it to boot from ramdisk (maj 1, minor 0)

> Kernel panic: VFS: Unable to mount root fs on unknown-block(1,0)

Your kernel fails to mount the ramdisk, since you have RAMDISK driver 
etc, then the next most likely reason is you are missing the filesystem 
support in your kernel.  For exampel if your ramdisk in in ext2 format 
then make sure your kernel has ext2 support compiled in (not as a module).

-R