From: Wolfgang Denk <wd@denx.de>
To: brian.auld@adic.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: I can smell it ... I'm almost there
Date: Mon, 03 Feb 2003 23:38:40 +0100 [thread overview]
Message-ID: <20030203223845.75F74C608E@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 03 Feb 2003 11:31:20 PST." <995FF289C9D69747A09E42992644595405B23645@penguin.adic.com>
In message <995FF289C9D69747A09E42992644595405B23645@penguin.adic.com> you wrote:
>
> I'm almost there. As you can see from the attachment below, linux gets
> loaded, the root filesystem gets mounted via nfs, and then I get some error
> messages. Maybe I could get on the right track if someone would be kind
> enough to given me a hint on the following:
>
> (1) modprobe. The kernel I built is 2.4.20 and the directory in
> {/opt/eldk/ppc_4xx)/lib/modules is 2.4.4 .... hence the modprobe errors.
> Do I have to get this squared away before I get to a bash prompt, and if
> yes, how would I go about it?
> - Is there a "make modules, make modules install" step that I have to
> take ... similar to workstation (non-embedded) kernel re-builds.
Ignore this for now, it is not relevant here.
> (2) There is no {/opt/eldk/ppc_4xx}/etc/fstab file which seems to cause
> several errors towards the bottom of my boot log. Is there information
> somewhere on how '{/opt/eldk/ppc_4xx}/etc/fstab' is supposed to be
> setup, if at all?
The main problem is that your root filesystem is mounted read-only. All other problems are just results from this.
> Kernel command line: ip=on
In here is the cause of your problem: you are passing insufficient
boot parameters; the boot options required for root filesystem over
NFS include "root=/dev/nfs rw" - and it's especially the "rw" part
that is missing in your case.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
I must follow the people. Am I not their leader? - Benjamin Disraeli
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-02-03 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-03 19:31 I can smell it ... I'm almost there brian.auld
2003-02-03 22:38 ` Wolfgang Denk [this message]
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=20030203223845.75F74C608E@atlas.denx.de \
--to=wd@denx.de \
--cc=brian.auld@adic.com \
--cc=linuxppc-embedded@lists.linuxppc.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).