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

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

Joe Shmo wrote:

quoted

That's a good idea.  However, my jtag box is down

for

quoted

a few days so we won't be able to flash the file
system and RAM isn't big enough.  Any other ideas

on

quoted

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.   

quoted

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
 

quoted

Is there an IP debug flag I can turn on in the

kernel?

quoted

I have not found one.

I'm not sure this.

Best Regards
Tiejun

quoted

Thanks.

--- "tiejun.chen" <tiejun.chen@windriver.com>

wrote:

quoted

quoted

Joe Shmo wrote:

quoted

I was missing a little bit from my log.  Here's

the

quoted

NFS failure:

portmap: server 192.168.1.21 not responding,

timed

quoted

quoted

out

quoted

Root-NFS: Unable to get nfsd port number from

server,

quoted

using default
Looking up port of RPC 100005/1 on 192.168.1.21
portmap: server 192.168.1.21 not responding,

timed

quoted

quoted

out

quoted

Root-NFS: Unable to get mountd port number from
server, using default
mount: server 192.168.1.21 not responding, timed

out

quoted

Root-NFS: Server returned error -5 while

mounting

quoted

quoted

quoted

/home/developer/export
VFS: Unable to mount root fs via NFS, trying

floppy.

quoted

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

quoted

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

quoted

      
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org

https://ozlabs.org/mailman/listinfo/linuxppc-embedded

quoted

quoted