From: "tiejun.chen" <tiejun.chen@windriver.com>
To: Joe Shmo <spamreceptor@yahoo.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC8313erdb uboot1.3.0 kernel2.6.21 dp83848 NFS problem
Date: Thu, 27 Nov 2008 10:58:18 +0800 [thread overview]
Message-ID: <492E0CCA.7020104@windriver.com> (raw)
In-Reply-To: <160205.63568.qm@web30102.mail.mud.yahoo.com>
Joe Shmo wrote:
> I was missing a little bit from my log. Here's the
> NFS failure:
>
> portmap: server 192.168.1.21 not responding, timed out
> Root-NFS: Unable to get nfsd port number from server,
> using default
> Looking up port of RPC 100005/1 on 192.168.1.21
> portmap: server 192.168.1.21 not responding, timed out
> Root-NFS: Unable to get mountd port number from
> server, using default
> mount: server 192.168.1.21 not responding, timed out
> Root-NFS: Server returned error -5 while mounting
> /home/developer/export
> VFS: Unable to mount root fs via NFS, trying floppy.
> VFS: Cannot open root device "nfs" or
> unknown-block(2,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root
> fs on unknown-block(2,0)
> Rebooting in 180 seconds..
>
>
Let us supposed your local network environment configuration is matched and
correct. I think you can boot kernel with Ramdisk firstly. Then under the shell
prompt you up (or mount another fs with NFS) your NIC and you also use the
tcpdump to snoop the detailed network message to track something.
Tiejun
>
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
next prev parent reply other threads:[~2008-11-27 2:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 22:20 MPC8313erdb uboot1.3.0 kernel2.6.21 dp83848 NFS problem Joe Shmo
2008-11-27 2:58 ` tiejun.chen [this message]
[not found] <4937316C.7020903@windriver.com>
2008-12-04 15:17 ` Joe Shmo
-- strict thread matches above, loose matches on Subject: below --
2008-11-26 22:05 Joe Shmo
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=492E0CCA.7020104@windriver.com \
--to=tiejun.chen@windriver.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=spamreceptor@yahoo.com \
/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).