oh, and if there is any doubt . . . l*ogin as: root* > *Debian GNU/Linux 7* > > *BeagleBoard.org BeagleBone Debian Image 2014-08-19* > > *Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian > <http://elinux.org/Beagleboard:BeagleBoneBlack_Debian>* > *root@beaglebone:~# passwd* > *Enter new UNIX password:* > *Retype new UNIX password:* > *passwd: password updated successfully* > *root@beaglebone:~# df -h /* > *Filesystem Size Used Avail Use% > Mounted on* > *192.168.xxx.xxx:/home/william/rootfs-testing 136G 3.9G 125G 3% /* > *root@beaglebone:~# uname -r* > *3.8.13-bone63* > *root@beaglebone:~#* >
Yes, I sanitized the ip address . . . On Mon, Aug 25, 2014 at 3:34 AM, William Hermans <[email protected]> wrote: > > > On Tuesday, August 12, 2014 9:19:51 AM UTC-7, Brian Anderson wrote: >> >> I am attempting to setup a BBB to boot via TFTP and mount a rootfs via >> NFS. >> >> I am using Robert Nelson's 2014-08-05 Debian lxde release image. I've >> examined the nfs-uEnv.txt in the boot partition and had a brief look at how >> the various environment variables interact with the default uboot setup. >> With the latest BBB uboot setup, it appears that TFTP boot and NFS rootfs >> functionality are now "packaged" together. >> >> I've also read William Herman's guides to setting up to boot via TFTP and >> mount the rootfs using NFS. Whilst helpful, these guides are now a bit >> dated (published June 2013) with respect to the latest uboot default setup. >> > > >> Brian, >> > > My NFS rootfs instructions work *EXACTLY* the same as they did last year > when I wrote the that post. I did too much thinking and confused myself > with the new example nfs-uEnv.txt file. This mean that what Robert has > setup can be overridden this means that > https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-DealingwitholdBootloaderineMMC > modified by commenting out mmcargs > > #mmcargs=setenv bootargs console=tty0 console=${console} ${optargs} > ${cape_disable} ${cape_enable} root=${mmcroot} rootfstype=${mmcrootfstype} > ${cmdline} > then adding: > netargs=setenv bootargs console=${console} ${optargs} root=/dev/nfs > nfsroot=${serverip}:${rootpath},vers=3 rw ip=${static_ip} > and editing: > uenvcmd=run loadall; run mmcargs; bootz ${loadaddr} - ${fdtaddr}; > to: > uenvcmd=setenv autoload no; run loadall; run netargs; bootz ${loadaddr} - > ${fdtaddr} > > Works exactly the same as it did before. There are some diffferences, but > if you take the time to understand how this all works it should be no > problem setting up. Of course the rest of the instruction on my blog post > are necessary too. ipaddr / serverip, etc etc. The reason why this is > important to me is that I have no use at the moment for using TFTP for > loading the kernel via network. However, im nearly 100% sure this aspect > could be overridden as well. As it is, Robert has made this really simple . > . . but those who do not understand how it works will still have problems. > > Robert, sorry for popping off on you about this, you did an excellent job. > I was just confused, with little time to think / work on this last week. > > > -- > 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. > -- 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.
