NFS root problems with sheevaplug with current

[kirk russell]

When I tried using a 9.0-CURRENT kernel with my sheevaplug, I was
unable to use a nfs root.  My work-a-round was to change the kernel
config file. I didn't do anymore debugging -- not sure what the
state of NFS is.

This is the work-a-round:
# cvs diff SHEEVAPLUG
Index: SHEEVAPLUG
===================================================================
RCS file: /home/ncvs/src/sys/arm/conf/SHEEVAPLUG,v
retrieving revision 1.3
diff -r1.3 SHEEVAPLUG
20c20
< options 	NFSCLIENT		#Network Filesystem Client
---
> options 	NFSCL			#Network Filesystem Client


Here are the errors I was seeing on the console:
Sending DHCP Request packet from interface mge0 (00:50:43:01:d6:c8)
Received DHCP Ack packet on mge0 from 192.168.1.23 (accepted) (got root path)
mge0 at 192.168.1.79 server 192.168.1.23 boot file node79.bin
subnet mask 255.255.255.0 router 192.168.1.101 root_server
192.168.1.23 rootfs /export/tank/freebsd/arm8le hostname node79
Adjusted interface mge0
Trying to mount root from nfs: []...
Mounting from nfs: failed with error 2: unknown file system.
Trying to mount root from oldnfs: []...
NFS ROOT: 192.168.1.23:/export/tank/freebsd/arm8le
Setting hostuuid: 4e548f07-9f3f-11e0-8815-00504301d6c8.
Setting hostid: 0xb812a530.
Entropy harvesting: interrupts ethernet point_to_point kickstart.
Starting file system checks:
mount: 192.168.1.23:/export/tank/freebsd/arm8le Invalid hostname:
Invalid argument
Mounting root filesystem rw failed, startup aborted
ERROR: ABORTING BOOT (sending SIGTERM to parent)!
Jul 15 17:51:23 init: /bin/sh on /etc/rc terminated abnormally, going
to single user mode
Enter full pathname of shell or RETURN for /bin/sh:
# df
Filesystem                               512-blocks    Used    Avail
Capacity  Mounted on
192.168.1.23:/export/tank/freebsd/arm8le   16777216 2173416 14603800    13%    /



-- 
Kirk Russell            <kirk at ba23.org>           http://www.ba23.org/