From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Andrea Galbusera <gizero@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Not booting on BeagleBoard xM 0x2
Date: Wed, 4 Apr 2012 08:50:21 -0400 [thread overview]
Message-ID: <4F7C438D.5020800@windriver.com> (raw)
In-Reply-To: <CAC+thW1Vah3pUPH=CNcQCH=C4QEj2RY17DX+tDHGd_MuCsxViQ@mail.gmail.com>
On 12-04-04 08:04 AM, Andrea Galbusera wrote:
> Hi Tomas,
>
> On Wed, Apr 4, 2012 at 12:14 PM, Tomas Frydrych
> <tf+lists.yocto@r-finger.com> wrote:
>> Hi,
>>
>> I am trying to get Yocto image built from yesterday's master
>> (Linux-3.0.23-yocto-standard) to boot on the NAND-less version of
>> BeagleBoard xM, but the kernel panics with:
>>
>> ----------------- console log start ------------
>>
>> Waiting for root device /dev/mmcblk0p2...
>> mmc0: new SDHC card at address 1234
>> mmcblk0: mmc0:1234 SA04G 3.67 GiB (ro)
>> mmcblk0: p1 p2
>>
>> VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2)
>> Please append a correct "root=" boot option; here are the available
>> partitions:
>>
>> b300 3858432 mmcblk0 driver: mmcblk
>> b301 120456 mmcblk0p1 00000000-0000-0000-0000-000000000mmcblk0p1
>> b302 3445942 mmcblk0p2 00000000-0000-0000-0000-000000000mmcblk0p2
>>
>> VFS: Unable to mount root fs on unknown-block(179,2)
>> User configuration error - no valid root filesystem found
>> Kernel panic - not syncing: Invalid configuration from end user prevents
>> continuing
>>
>> -------------- console log end ------------------------------------
>>
>> My guess would be the problem is the card being detected as 'ro' (line
>> 3), but I do not know why that is (there is no lock switch on mmc cards).
>>
>> The card itself is fine, it's the original card that came with the
>> board, the original Angstrom demo boots fine from it, and yocto kernel
>> 2.6.37 also used to boot.
>>
>> Tomas
>
> Looks related to the comment I wrote here:
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=1892
> I have a slightly different failure with yocto 1.2 beta snapshot (same
> kernel) but seems related. Needs more investigation.
> Anyone else having problem booting on beagleboard xM? Seems something
> wrong happened after 1.1 release...
We are working on several bugs on our reference beagleboard. The problem
is that my beagleboard died (a horrible painful death) and the other boards
that are directly available to are RevC and they are booting. So things
are slowed down a bit .. but we are trying to get to the bottom of it,
as fast as possible.
Cheers,
Bruce
>
> Andrea
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2012-04-04 12:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 10:14 Not booting on BeagleBoard xM 0x2 Tomas Frydrych
2012-04-04 12:04 ` Andrea Galbusera
2012-04-04 12:50 ` Bruce Ashfield [this message]
2012-04-04 14:10 ` Gary Thomas
2012-04-04 14:58 ` Andrea Galbusera
2012-04-04 15:06 ` Gary Thomas
2012-04-04 18:49 ` Robert Berger
2012-04-04 19:11 ` Chris Tapp
2012-04-05 5:31 ` Tomas Frydrych
2012-06-12 23:00 ` Ryan Julian
2012-06-12 23:10 ` Bruce Ashfield
2012-06-12 23:38 ` Ryan Julian
2012-06-13 2:34 ` Bruce Ashfield
2012-06-13 6:46 ` Tomas Frydrych
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=4F7C438D.5020800@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=gizero@gmail.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.