From: Mirek23 <miroslaw.dach@psi.ch>
To: linuxppc-embedded@ozlabs.org
Subject: RE: zImage.elf loads but does not start
Date: Tue, 15 May 2007 05:08:41 -0700 (PDT) [thread overview]
Message-ID: <10621564.post@talk.nabble.com> (raw)
In-Reply-To: <10429898.post@talk.nabble.com>
>It seems to be that the console works fine and the root file system is
mounted properly via NFS.
>I do not however understand why eldk4.1 init does not work.
I have done some more investigations. My observation is as following:
The eldk4.1/ppc_4xx root file system has the init which is not statically
built. When I removed the lib directory on the
NFS server:/opt/eldk4.1/ppc_4xx/lib the kernel has booted up to the point:
[ 9.302101] VFS: Mounted root (nfs filesystem).
[ 9.357642] Freeing unused kernel memory: 96k init
[ 9.481509] Kernel panic - not syncing: No init found. Try passing init=
option to kernel.
When the lib directory was present the last printed message was:
[ 9.357642] Freeing unused kernel memory: 96k init
I have observed the same behaviour with busybox accessed via NFS.
I have compiled busybox with crosstool-0.43 (gcc-4.0.2 glibc-2.3.2) because
eldk4.1 crosscompilers failed to compile busybox. When using busybox mounted
via NFS I copied the lib directory from crosstool.
Unfortunately also this time the system hanged at init.
My own version of init which uses printf just to print the string to the
screen runs however fine.
Would somebody have some suggestion what might cause the problem to properly
launch the init command.
Best Regards
Mirek
--
View this message in context: http://www.nabble.com/zImage.elf-loads-but-not-starts-tf3607582.html#a10621564
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
next prev parent reply other threads:[~2007-05-15 12:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 15:10 zImage.elf loads but not starts Mirek23
2007-04-23 15:12 ` zImage.elf loads but does not start Mirek23
2007-04-23 16:11 ` Leonid
2007-04-24 16:55 ` Mirek23
2007-04-24 17:11 ` Andrei Konovalov
2007-05-04 15:04 ` Mirek23
2007-05-04 15:41 ` Andrei Konovalov
2007-05-08 9:46 ` Mirek23
2007-05-08 21:46 ` Leonid
2007-05-08 21:50 ` Adrian Craine
2007-05-09 15:02 ` Charles Krinke
2007-05-10 8:45 ` Mirek23
2007-05-10 16:05 ` Mead, Joseph
2007-05-11 11:21 ` Mirek23
2007-05-15 12:08 ` Mirek23 [this message]
2007-05-15 12:29 ` Andrei Konovalov
2007-05-15 12:45 ` Miroslaw Dach
2007-05-15 18:07 ` Andrei Konovalov
2007-05-15 18:49 ` Miroslaw Dach
2007-05-18 12:43 ` Mirek23
2007-05-25 12:24 ` Mirek23
2007-05-25 13:16 ` Andrei Konovalov
2007-05-25 15:23 ` Mirek23
2007-05-25 16:56 ` Advice needed Charles Krinke
2007-05-15 13:12 ` zImage.elf loads but does not start Mead, Joseph
2007-05-18 13:28 ` Mirek23
2007-04-23 16:24 ` Andrei Konovalov
2007-04-23 17:35 ` Grant Likely
2007-04-24 13:42 ` Mirek23
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=10621564.post@talk.nabble.com \
--to=miroslaw.dach@psi.ch \
--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).