From owner-freebsd-arm@FreeBSD.ORG Fri Jul 15 19:06:10 2011 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02A02106566B for ; Fri, 15 Jul 2011 19:06:10 +0000 (UTC) (envelope-from kirk.j.russell@gmail.com) Received: from mail-pz0-f49.google.com (mail-pz0-f49.google.com [209.85.210.49]) by mx1.freebsd.org (Postfix) with ESMTP id D33BD8FC1B for ; Fri, 15 Jul 2011 19:06:09 +0000 (UTC) Received: by pzk33 with SMTP id 33so2457396pzk.8 for ; Fri, 15 Jul 2011 12:06:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:reply-to:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type:content-transfer-encoding; bh=IKuKH/9l9ULwOBX72US3meh/A/IjX1fJYOqx5URuZBE=; b=uOAmY+ICXNBpPxpHkmrvIW1RmFwRtjk5laIk+3qc89P8Q8uO5lCYjGf911pyLY0Vet Q+bspm/XdIzOv1C5hGE7C4H+hbHScgVeQMW13den+T8SkxCNzftZvZLKxOGu6lOKetWp jUjEfNSqGn2moQJsLoTWJQ8QuxwzxSG16wkgA= MIME-Version: 1.0 Received: by 10.142.62.29 with SMTP id k29mr1596357wfa.253.1310755462341; Fri, 15 Jul 2011 11:44:22 -0700 (PDT) Sender: kirk.j.russell@gmail.com Received: by 10.142.185.18 with HTTP; Fri, 15 Jul 2011 11:44:22 -0700 (PDT) Date: Fri, 15 Jul 2011 19:44:22 +0100 X-Google-Sender-Auth: AmwN9XlP3eut2z_iUbW9s9ns-DE Message-ID: From: kirk russell To: freebsd-arm@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: NFS root problems with sheevaplug with current X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kirk@ba23.org List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2011 19:06:10 -0000 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 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 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 pat= h) 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%= / --=20 Kirk Russell =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 htt= p://www.ba23.org/