[Clfs-support] Problem with NFS-root on new kernel

[Ron McDowell]

On 8/7/12 8:15 PM, William Harrington wrote:
> On Tue, 07 Aug 2012 20:00:10 -0500
> Ron McDowell<rcm at fuzzwad.org>  wrote:
>
>> nfs: server 192.168.1.254 not responding, still trying
>> nfs: server 192.168.1.254 not responding, still trying
> What are the logs at that system 192.168.1.254 stating?
>

syslog line from a failed boot with the new kernel:
Aug  7 20:22:17 samsung550 rpc.mountd[1339]: authenticated mount request 
from 192.168.1.1:882 for /NFSRoot (/NFSRoot)

and for a successful boot with the old kernel:
Aug  7 20:14:56 samsung550 rpc.mountd[1339]: authenticated mount request 
from 192.168.1.1:981 for /NFSRoot (/NFSRoot)


...and here's the tail end of the boot messages from a successful boot 
on the old kernel:

NET: Registered protocol family 17
s3c2410-rtc s3c2410-rtc: setting system clock to 2012-08-08 00:43:56 UTC 
(13443)
eth0: link down
IP-Config: Guessing netmask 255.255.255.0
IP-Config: Complete:
      device=eth0, addr=192.168.1.1, mask=255.255.255.0, gw=255.255.255.255,
      host=192.168.1.1, domain=, nis-domain=(none),
      bootserver=255.255.255.255, rootserver=192.168.1.254, rootpath=
Looking up port of RPC 100003/2 on 192.168.1.254
eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
Looking up port of RPC 100005/1 on 192.168.1.254
VFS: Mounted root (nfs filesystem) on device 0:11.
Freeing init memory: 156K
init started: BusyBox v1.20.2 (2012-08-07 18:41:27 CDT)
Starting mdev: OK
Mounting devpts: OK
Enabling swap space: OK
Remounting root rw: OK
Setting hostname: OK
Cleaning up system: OK
Setting up interface lo: OK
Running start scripts.
Starting syslogd: OK
Starting klogd: OK
Setting up interface eth0: OK

mini2440 login:

-- 
Ron McDowell
San Antonio TX