From: Heiko Schocher <hs@denx.de>
To: "Bizhan Gholikhamseh (bgholikh)" <bgholikh@cisco.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Failed to mount rootfs
Date: Fri, 25 Jan 2008 08:19:39 +0100 [thread overview]
Message-ID: <47998D8B.8050100@denx.de> (raw)
In-Reply-To: <mailman.1307.1201212280.6908.linuxppc-embedded@ozlabs.org>
Hello Bizhan,
"Bizhan Gholikhamseh (bgholikh)" <bgholikh@cisco.com> wrote:
> Our custom board is leveraged from MPC8541cds from freescale.
> We have been running Linux 2.6.11 on it recently I have tried to boot
> the system with the latest Linux 2.6.22-rc4 from PowerPC git tree.
>
> I did ported the libfdt to our older version of the uboot and were able
> to
Hmm... why you didnt use actual code?
[...]
> chosen {
> linux,stdout-path = "/soc8541@e0000000/serial@4600";
> };
> chosen {
> name = "chosen";
> bootargs = "root=/dev/ram rw console=ttyS1,115200";
> linux,platform = <600>;
> linux,initrd-start = <1ef33000>;
> linux,initrd-end = <1fe190aa>;
> linux,stdout-path = "/soc8541@e0000000/serial@4600";
> };
> };
Here is your problem, you have 2 choosen nodes:
64k data, 108k bss, 116k init) Mount-cache hash table entries: 512
device-tree: Duplicate name in /, renamed to "chosen#1"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-> Linux didnt find your commandline ...
Hmm... do you have CONFIG_OF_FLAT_TREE and CONFIG_OF_LIBFDT defined?
If so, this would explain, why you have 2 choosen nodes.
bye,
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next parent reply other threads:[~2008-01-25 7:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1307.1201212280.6908.linuxppc-embedded@ozlabs.org>
2008-01-25 7:19 ` Heiko Schocher [this message]
2008-01-25 16:47 ` Failed to mount rootfs Bizhan Gholikhamseh (bgholikh)
2008-01-26 7:41 ` Heiko Schocher
2008-01-24 21:53 Bizhan Gholikhamseh (bgholikh)
2008-01-24 22:12 ` Jochen Friedrich
2008-01-24 22:25 ` Bizhan Gholikhamseh (bgholikh)
2008-01-24 23:39 ` Andy Fleming
2008-01-25 0:24 ` Scott Wood
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=47998D8B.8050100@denx.de \
--to=hs@denx.de \
--cc=bgholikh@cisco.com \
--cc=linuxppc-embedded@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).