From: Georg Schardt <g.schardt@fz-juelich.de>
To: linuxppc-embedded@ozlabs.org
Subject: JFFS2 root-fs
Date: Mon, 31 Mar 2008 16:33:42 +0200 [thread overview]
Message-ID: <47F0F646.30002@fz-juelich.de> (raw)
In-Reply-To: <16306218.post@talk.nabble.com>
Hi all,
i ask this questions a few months ago but i still have no solution for
my problem :(
i try to boot linux with a root-fs from flash. i create a jffs2-image,
download it to flash and
the u-boot "ls" shows me all my files, so i think all is right with the
image.
BUT, the kernel hangs after mounting the rootfs:
[ 0.572527] physmap platform flash device: 00400000 at 04000000
[ 0.579205] physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
[ 0.586062] Amd/Fujitsu Extended Query Table at 0x0041
[ 0.591456] number of CFI chips: 1
[ 0.594973] cfi_cmdset_0002: Disabling erase-suspend-program due to
code brokenness.
[ 0.602916] 4 cmdlinepart partitions found on MTD device physmap-flash.0
[ 0.609759] Creating 4 MTD partitions on "physmap-flash.0":
[ 0.615454] 0x00000000-0x00010000 : "env"
[ 0.619599] mtd: Giving out device 0 to env
[ 0.628166] 0x00010000-0x00030000 : "uboot"
[ 0.632563] mtd: Giving out device 1 to uboot
[ 0.641172] 0x00030000-0x00160000 : "kernel"
[ 0.645744] mtd: Giving out device 2 to kernel
[ 0.654372] 0x00160000-0x00400000 : "fs"
[ 0.658604] mtd: Giving out device 3 to fs
[ 0.666992] block2mtd: version $Revision: 1.30 $
[ 0.673341] mice: PS/2 mouse device common for all mice
[ 0.679193] TCP cubic registered
[ 0.683016] NET: Registered protocol family 1
[ 0.687619] NET: Registered protocol family 17
[ 0.696556] MTDSB: dev_name "/dev/root"
[ 0.700723] MTDSB: path_lookup() returned 0, inode c02ec290
[ 0.706515] MTDSB: New superblock for device 3 ("fs")
[ 2.386543] VFS: Mounted root (jffs2 filesystem).
[ 2.392022] Freeing unused kernel memory: 76k init
[ 2.397182] Warning: unable to open an initial console.
[ 2.416877] Kernel panic - not syncing: No init found. Try passing
init= option to kernel.
[ 2.427312] Rebooting in 180 seconds..
It seems to me, that the kernel does not find ANY file. because the
/dev/console file is in the image, but the initial console is not found too
any ideas and hints are appreciated
regars
georg
-------------------------------------------------------------------
-------------------------------------------------------------------
Forschungszentrum Jülich GmbH
52425 Jülich
Sitz der Gesellschaft: Jülich
Eingetragen im Handelsregister des Amtsgerichts Düren Nr. HR B 3498
Vorsitzende des Aufsichtsrats: MinDir'in Bärbel Brumme-Bothe
Geschäftsführung: Prof. Dr. Achim Bachem (Vorsitzender),
Dr. Ulrich Krafft (stellv. Vorsitzender), Prof. Dr. Harald Bolt,
Dr. Sebastian M. Schmidt
-------------------------------------------------------------------
-------------------------------------------------------------------
next prev parent reply other threads:[~2008-03-31 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 17:02 Xilin Temac Timer ? khollan
2008-03-26 19:48 ` Xilinx " John Linn
2008-03-27 19:31 ` khollan
2008-03-31 14:33 ` Georg Schardt [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-31 17:23 JFFS2 root-fs Sugathan, Rupesh
2008-04-01 6:07 ` Georg Schardt
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=47F0F646.30002@fz-juelich.de \
--to=g.schardt@fz-juelich.de \
--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).