Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 09 Jul 2013 10:05:04 +0200
From:      "Ronald Klop" <ronald-freebsd8@klop.yi.org>
To:        "John-Mark Gurney" <jmg@funkthat.com>, "Oleksandr Tymoshenko" <gonzo@bluezbox.com>, "Douglas Beattie" <beattidp@ieee.org>
Cc:        freebsd-arm@freebsd.org
Subject:   Re: NFS root on BeagleBone Black
Message-ID:  <op.wzx3eqt68527sy@ronaldradial.versatec.local>
In-Reply-To: <E02E111C-DC63-490B-AA5D-B397152686F2@ieee.org>
References:  <0D94186F-F592-44C4-9F76-9E4B4B487468@ieee.org> <20130708054342.GB26412@funkthat.com> <E02E111C-DC63-490B-AA5D-B397152686F2@ieee.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 08 Jul 2013 19:37:21 +0200, Douglas Beattie <beattidp@ieee.org>  
wrote:

> On Jul 7, 2013, at 11:43 PM, John-Mark Gurney wrote:
>
>> Douglas Beattie wrote this message on Sun, Jul 07, 2013 at 23:06 -0600:
>>>
>>> options         NFS_ROOT                #NFS usable as /, requires  
>>> NFSCL
>>> options          
>>> ROOTDEVNAME=\"nfs:192.168.0.198:/opt/tftpboot/beaglebone\"
>>
>> Do you have:
>> options 	BOOTP
>>
>> in your kernel to give the interface an ip address?  I don't see
>> anything in your dmesg about the kernel trying to get an ip address
>> before it tries to nfs mount root.
>>
>> There isn't any communication from U-Boot to the kernel on what the ip
>> address is suppose to be...  The kernel needs to rediscover it itself.
>
>
>
> I tried enabling 'BOOTP' and related options at first, but reverted to
> only 'NFS_ROOT', since I don't have a BOOTP service.

Isn't BOOTP about the same protocol as DHCP?
Oh no, wait.
http://en.wikipedia.org/wiki/Bootstrap_Protocol
'Most DHCP servers also function as BOOTP servers.'

Maybe you can just hardcode its IP.

Ronald.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.wzx3eqt68527sy>