William
Yes I did start with your guide, but could not make it work, then I noticed 
that the addresses in the uEnv.txt that come with the standard distro did 
not match the ones in your guide and I'm using the standard kernel, uBoot 
etc. so I got suspicious and I started looking elsewhere and hacking around.
I've now changed mmcargs to netargs and still no joy. I'm going to mess 
with the ipaddr bit when I get home from work tonight since currently I'm 
doing a bit more than you with 
${ipaddr}:${serverip}:${gateway}:${netmask}:${hostname}:${nfsdevice} 
instead of just ${ipaddr}.
I also noticed in the standard distro it has ${cape_disable} ${cape_enable} 
${kms_force_mode} in the mmcargs line, I'm not sure if you also need them 
when using netargs with this version.

Giles

On Wednesday, 30 July 2014 01:41:08 UTC+1, William Hermans wrote:
>
> Giles, what your your fstab look like on the beaglebone black ?  Also I'm 
> not 100% sure about this but for consistancy you should not use mmcargs, 
> but instead use netargs
>
> This is what my own netargs line looks like:
>
>> *netargs=setenv bootargs console=${console} ${optargs} root=/dev/nfs 
>>> nfsroot=${serverip}:${rootpath},vers=3 rw ip=${ipaddr}*
>>
>>
> NFS version 3 works fine on Debian, perhaps Ubuntu is different ? I know 
> you've read other guides but perhaps reading my guild to double check what 
> you've done is complete. My guide: 
> http://www.embeddedhobbyist.com/debian-tips/beaglebone-black/beaglebone-black-nfs-root/
>  
>
> scroll down to *Configuring the NFS server *and read down to see if you 
> perhaps missed something. Also keep in mind that Although Ubuntu is based 
> on Debian, package names can be different, and not everything is done the 
> same way.
>
>
> On Tue, Jul 29, 2014 at 3:49 PM, Giles Godart-Brown <[email protected] 
> <javascript:>> wrote:
>
>> Thanks for the quick reply, the serial port log reveals that it does not 
>> like vers=3, nor nfsvers=3 in the nfsopts variable, after removing them it 
>> gets a little further, but still does not boot. The full serial log has 
>> been posted here <http://pastebin.com/8E0XRu57>
>>
>> Giles
>>
>> On Tuesday, 29 July 2014 22:26:06 UTC+1, Giles Godart-Brown wrote:
>>>
>>> I've seen many posts about how to boot a Beaglebone black via an NFS 
>>> mounted root partition, but none seem to work with the latest version.
>>> I started by creating an NFS mount on my Ubuntu PC and successfully 
>>> mounting it from the Beaglebone when booted from an SD image of the latest 
>>> version dated 2013.06.20 
>>> <https://s3.amazonaws.com/angstrom/demo/beaglebone/Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.06.20.img.xz>
>>>  from 
>>> the Beaglebone site. All the commands below were done as root.;
>>> uname -a
>>> Linux beaglebone 3.8.13-bone50 ....
>>> Then test the mount with;
>>> mount -o nfsvers=3 192.168.10.118:/home/bone /mnt/nfs
>>> Next I copied the entire filesystem to the nfs mount with
>>> cp -axv /. /mnt/nfs/.
>>> I've edited the fstab on the nfs (/home/bone/etc/fstab) to add
>>> /dev/nfs / nfs defaults 0  0
>>> and correctly edited /home/bone/etc/network/interface to reflect the 
>>> correct IP address etc.
>>> Next I edited the uEnv.txt on the SD card to add 
>>> serverip=192.168.10.118
>>> ipaddr=192.168.10.47
>>> hostname=MH_bbb
>>> netmask=255.255.255.0
>>> gateway=192.168.10.1
>>> nfsdevice=eth0:off
>>> nfsopts=vers=3
>>> rootpath=/home/bone
>>> and changed the mmcargs line to;
>>> mcargs=setenv bootargs console=tty0 console=${console} ${optargs} 
>>> ${cape_disable} ${cape_enable} ${kms_force_mode} ip=${ipaddr}:${serverip}:${
>>> gateway}:${netmask}:${hostname}:${nfsdevice} root=/dev/nfs rw 
>>> nfsroot=${serverip}:${rootpath},${nfsopts}  ${systemd}
>>> The Bone starts to boot and I can ping it on the correct IP address, but 
>>> the display never shows anything and it doesn't let me ssh to it.
>>> Can anyone let me know what I've missed?
>>> Thanks
>>>
>>>
>>>  -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to