[U-Boot-Users] bootm problem

T Michael Turney tmike at recipes4linux.com
Mon Sep 6 15:35:42 CEST 2004


> Kernel command line: root=/dev/nfs rw
> nfsroot=192.168.1.245:/opt/eldk/ppc_8xx
> ip=192.168.1.248:192.168.1.245:192.168.1.1:255.255.255.0

...

> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP
> IP: routing cache hash table of 512 buckets, 4Kbytes
> TCP: Hash tables configured (established 2048 bind
> 4096)
> IP-Config: Complete:
>       device=eth0, addr=192.168.1.248,
> mask=255.255.255.0, gw=192.168.1.1,
>      host=192.168.1.248, domain=, nis-domain=(none),
>      bootserver=192.168.1.245,
> rootserver=192.168.1.245, rootpath=
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> Looking up port of RPC 100003/2 on 192.168.1.245
>
>
>
>  And it hang not continue.
>

I would bet that NFS is not running on 192.168.1.248.
Your kernel command line is trying to point the newly
booted kernel to access its root filesystem through an
NFS mount point on 192.168.1.248, specifically,
th directory: /opt/eldk/ppc_8xx.

1) make sure NFS is running,
   on RHL, try, e.g., '/etc/init.d/nfs status'
2) make sure you have a well-formed /etc/exports file
   try, e.g.,  '/opt/eldk/ppc_8xx *(rw,no_root_squash,no_all_squash)'
3) make sure the mount point '/opt/eldk/ppc_8xx' exists and
   contains an image of the ELDK PPC/8xx root filesystem
4) run 'exportfs -ra' after starting NFS the first time, to synchronize info
5) boot your target again

Cheers,
T.mike





More information about the U-Boot mailing list