NFS Root with Raspberry Pi (nfs_diskless: no interface)

[Daniel Braniss]

> On 22 Sep 2015, at 08:25, Randy Westlund <rwestlun at gmail.com> wrote:
> 
> I'm trying to boot a Raspberry Pi over the network so I can avoid SD
> card woes, but I'm stuck on something.
> 
> I've taken the FreeBSD RPI-B image and moved the files to an NFS share
> on a server.  Its fstab references the NFS root, but all other files are
> unchanged.
> 
> Thus far, I have the pi loading U-Boot from the SD card and grabbing
> ubldr via TFTP.  Then ubldr successfully connects to the NFS share and
> loads the kernel.
> 
> My problem is when the kernel tries to mount root.  I'm getting this
> error:
> 
>> usbus0: 480Mbps High Speed USB v2.0
>> bcm2835_cpufreq0: ARM 700MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF
>> ugen0.1: <DWCOTG> at usbus0
>> uhub0: <DWCOTG OTG Root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
>> mmcsd0: 4GB <SDHC SU04G 8.0 SN 001FC92A MFG 12/2011 by 3 SD> at mmc0 41.6MHz/4bit/65535-block
>> nfs_diskless: no interface
>> Root mount waiting for: usbus0
>> uhub0: 1 port with 1 removable, self powered
>> ugen0.2: <vendor 0x0424> at usbus0
>> uhub1: <vendor 0x0424 product 0x9512, class 9/0, rev 2.00/2.00, addr 2> on usbus0
>> uhub1: MTT enabled
>> Root mount waiting for: usbus0
>> uhub1: 3 ports with 2 removable, self powered
>> Root mount waiting for: usbus0
>> ugen0.3: <vendor 0x0424> at usbus0
>> smsc0: <vendor 0x0424 product 0xec00, rev 2.00/2.00, addr 3> on usbus0
>> Trying to mount root from nfs:192.168.1.254:/usr/raspi_root [rw]...
>> nfs_diskless: no interface
>> Mounting from nfs:192.168.1.254:/usr/raspi_root failed with error -1.
>> 
> 
> I believe "nfs_diskless: no interface" is the important part.  The
> ethernet port is not ready by the time it tries to mount root.
> 
> The pi uses ethernet over USB and FreeBSD calls the interface ue0.  When
> I boot from the SD card, ethernet works without loading any modules, so
> I believe the kernel should have everything it needs.
> 
> What am I doing wrong?
> 
> Randy

make sure the ue driver is either compiled in or loaded,
you can add
	if_ue_load=“YES”
to /boot/loader.conf

danny