MPC8313erdb uboot1.3.0 kernel2.6.21 dp83848 NFS problem

[Joe Shmo]

--- "tiejun.chen" <tiejun.chen at windriver.com> wrote:

> Joe Shmo wrote:
> > That's a good idea.  However, my jtag box is down
> for
> > a few days so we won't be able to flash the file
> > system and RAM isn't big enough.  Any other ideas
> on
> > how to pursue this problem?  
> > 
> 
> I'm confused. You means there is no bootloader on
> your board? If not you can use
> bootloader directly to load ramdisk with appropriate
> commndline such as
> "rd_start=xx rd_size=xx ramdis_size=xx".
I have a uboot flashed, but I need to recompile it to
get the NAND tools and then reflash it.  Our NAND part
is the biggest part on this board and my current
kernel filesystem is huge.  Of couse I will need to
look at paring that down a lot. I might get it to fit
into RAM.   

> > The activity light for the PHY is blinking away
> > normally and you can see that the PHY was
> > reprogrammed.  I also tried the generic PHY and it
> > operates the same. 
> > 
> 
> Can you give me your .config?
I have attached the .config file
 
> > Is there an IP debug flag I can turn on in the
> kernel?
> > I have not found one.
> > 
> 
> I'm not sure this.
> 
> Best Regards
> Tiejun
> 
> > Thanks.
> > 
> > --- "tiejun.chen" <tiejun.chen at windriver.com>
> wrote:
> > 
> >> 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 at ozlabs.org
> >>>
> >
>
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> >>
> > 
> > 
> > 
> >       
> 
> 



      
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: config
URL: <http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20081204/09307b12/attachment-0001.txt>