mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: CRANESOFT <sailingsmoky@googlemail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: Booting PhyTec PCM043/IMX35  from USB/SD-Card
Date: Thu, 31 May 2012 21:13:07 +0200	[thread overview]
Message-ID: <522FDB4A-4438-4833-A801-D52C53F121D0@crane-soft.de> (raw)
In-Reply-To: <20120531182724.GA30400@pengutronix.de>


Am 31.05.2012 um 20:27 schrieb Sascha Hauer <s.hauer@pengutronix.de>:

> Hi Peter,
> 
> On Fri, May 25, 2012 at 11:35:36AM +0200, Peter Kuennemann@Crane-Soft wrote:
>> 
>> 
>> To have kernel in flash and rootfs on MMC i tried bootargs as:
>> 
>> ... root=/dev/mmcblk0p1 rootfstype=ext2 rootflags=noatime rw noinitrd rootwait ..
>> 
>> and it boots the kernel properly from flash up to:
>> ...
>> mmcblk0: mmc0:a95c SD01G 968 MiB     <== Recognized the sd card
>> mmcblk0: p1                         <== and partion 1
>> ...
>> 1f00             256 mtdblock0 (driver?)
>> 1f01             128 mtdblock1 (driver?)
>> 1f02            2048 mtdblock2 (driver?)
>> 1f03           30336 mtdblock3 (driver?)
>> 1f04         1048576 mtdblock4 (driver?)
>> b300          992000 mmcblk0 driver: mmcblk
>>  b301          991585 mmcblk0p1                    <=== Something missing here?
>> No filesystem could mount root, tried:  ext2        <===
>> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,1) <===
>> 
>> The mmc does contain a ext2 filesystem with the proper rootfs copied from
>> the jffs2.image that I mounted under Ubuntu as loop device. The kernel has ext2 fs
>> support compiled in.
>> 
>> The rootfs on the mmc is properly accessible when booting kernel and flash footfs
>> on the very same platform.
> 
> Has this been solved in the mean time? The above looks correct, I have
> no idea what's wrong.
> 
> Sascha
> 
Sascha,
I am sorry but this issue has not yet been resolved. I am currently out of office but will pick it up after my return. It may well be a Kernel configuration Problem.

Peter
> 
> -- 
> Pengutronix e.K.                           |                             |
> Industrial Linux Solutions                 | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2012-05-31 19:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-23 15:43 Peter Kuennemann@Crane-Soft
2012-05-24 19:55 ` Sascha Hauer
2012-05-25  9:35   ` Peter Kuennemann@Crane-Soft
2012-05-31 18:27     ` Sascha Hauer
2012-05-31 19:13       ` CRANESOFT [this message]
2012-06-28  6:53       ` Peter Kuennemann@Crane-Soft
2012-06-28 10:43         ` Sascha Hauer
2012-06-28 13:36           ` Peter Kuennemann@Crane-Soft
2012-06-28 13:54             ` Sascha Hauer
2012-08-23 17:59           ` Peter
2012-08-24  8:46             ` Jan Lübbe
2012-08-27  7:45               ` Peter

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=522FDB4A-4438-4833-A801-D52C53F121D0@crane-soft.de \
    --to=sailingsmoky@googlemail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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