Subject: Re: MPC8313erdb uboot1.3.0 kernel2.6.21 dp83848 NFS problem

From: "tiejun.chen" <[email-masked]>
Date: Thu, 27 Nov 2008 10:58:18 +0800

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
> [email-masked]
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>