Discussing the Linux ARM kernel

satpal parmar | 1 Mar 2007 08:06

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

Thanks for your reply Aras. Yes. I have selected I have compiled kernel with
fileystem support.

Can you suugest any other reson for such kernel behaviour.?

TIA
satpal

On 3/1/07, Aras Vaichas <arasv <at> magtech.com.au> wrote:
>
> satpal parmar wrote:
> ...
> > No filesystem could mount root, tried:  ext2
>
> Have you compiled in support for the filing system used to create the
> initrd?
> e.g. cramfs, squashfs?
>
> Also, I use a 9MB initrd image without any problems.
>
> regards,
>
> Aras Vaichas
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>
-------------------------------------------------------------------

(Continue reading)

headers

satpal parmar | 1 Mar 2007 10:22

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

Hi all

         I am able to solve the problem.It was related to boot parameters.
as we can see from log oneline realted to
I was passing wrong parameters so its was not loooking for initram.Once I
passed right params we got the shell.

Warning: bad configuration page, trying to continue: this give a hint that
some thing is wrong with params or ATAG list.

>> this is not present in my log
 checking if image is initramfs...it isn't (bad gzip magic numbers); looks
like an initrd

>From these two observations we got the solution.

Anyway thanks a lot.
satpal

On 3/1/07, satpal parmar <parmarsatpal <at> gmail.com> wrote:
>
> Thanks for your reply Aras. Yes. I have selected I have compiled kernel
> with fileystem support.
>
> Can you suugest any other reson for such kernel behaviour.?
>
> TIA
> satpal
>
>

(Continue reading)