Ack, It's definitely getting late( 3:50am ) I keep slipping up and forgetting to add information.
Moscowbob, here i a blog post I wrote up on the subject last year. http://www.embeddedhobbyist.com/debian-tips/beaglebone-black/beaglebone-black-nfs-root/ I also wrote another post on how to boot via a USB hard drive here too. http://www.embeddedhobbyist.com/debian-tips/beaglebone-black/beaglebone-black-usb-boot/ The information is written in a way to make it more concise, but the information is also different. Since we're "booting" from a different device. There is also another post I wrote on loading the kernel over the network via tftp. If you can wrap your brain around these 3 different posts well enough you should have a better understanding of how all this works On Mon, Sep 8, 2014 at 3:43 AM, William Hermans <yyrk...@gmail.com> wrote: > Yeah i made another minor mistake, it's getting late for me. > > root@arm:~# cat /media/boot/uEnv.txt |optargs= > > > */* No output now since i completely removed the line */*should be: > > root@arm:~# cat /media/boot/uEnv.txt |grep optargs= > root@arm:~# > Still no output though, as again the line has been completely removed from > the first uEnv.txt file > > > On Mon, Sep 8, 2014 at 3:40 AM, William Hermans <yyrk...@gmail.com> wrote: > >> Ok, silly me, was editing the wrong file. I was editing the file on the >> NFS rootfs, when I am actually loading my second stage uEnv.txt file from >> the sdcard. >> >> root@arm:~# mount /dev/mmcblk0p1 /media/boot/ >> root@arm:~# mkdir /media/rootfs >> root@arm:~# mount /dev/mmcblk0p2 /media/rootfs/ >> root@arm:~# cat /media/boot/uEnv.txt |optargs= >> */* No output now since i completely removed the line */* >> root@arm:~# cat /media/rootfs/boot/uEnv.txt >> uname_r=3.8.13-bone64.1 >> cmdline=quiet init=/lib/systemd/systemd consoleblank=0 >> cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN >> root@arm:~# cat /sys/module/kernel/parameters/consoleblank >> 0 >> >> Moscowbob, if you're familiar with C I can link you to the header file >> that pretty much determines how all this works. The netargs line I am >> talking about is something I have set in my own 1st stage uEnv.txt file, >> since this used to be the way it had to be done. Now, I use it still, >> because I boot custom compared to Roberts new way. I only load the root >> file system via NFS, and the kernel still gets loaded from the sdcard. >> >> Understanding all of this takes time. I first learned this around 14-15 >> months ago when the A5A was first released to the general public. I more >> than 2 weeks reading all the uEnv.txt files I could, and when I felt I >> understood things well enough, I asked Robert C Nelson a question ( I do >> not remember what offhand ), and he linked me to this file. >> http://git.denx.de/?p=u-boot.git;a=blob;f=include/configs/am335x_evm.h;hb=HEAD#l57 >> This was enough information for me to fully understand what I needed to do >> in order to get what I wanted to achieve done. >> >> Other than this, I do not know how else to explain to you it all works. >> Except, if you examine the 1st stage uEnv.txt file I pasted above closer >> towards the top, and examine the output of /proc/cmdline . . . It might all >> start making sense to you. >> >> >> On Mon, Sep 8, 2014 at 3:17 AM, William Hermans <yyrk...@gmail.com> >> wrote: >> >>> Moscowbob, you and I both now. Initially it worked, but now for some >>> reason it does not. There are a few things I can check and instead of me >>> doing a play by play and posting 500 lines more . . . let me see if i can >>> get to the bottom of it. >>> >>> On Mon, Sep 8, 2014 at 3:12 AM, Moscowbob <moscow...@gmail.com> wrote: >>> >>>> Sorry - there is a typo.. >>>> >>>> ".....the display is now not blanking, after adding the optargs to >>>> uEnv.txt in the fat boot partition but for learning sake, I would like to >>>> know how to achieve this in the /boot/uEnv.txt" >>>> >>>> >>>> On Monday, 8 September 2014 11:08:35 UTC+1, Moscowbob wrote: >>>>> >>>>> Thanks William, but the line in red is just commented out to indicate >>>>> it is not part of the working file. I did not work without the hash. >>>>> I have followed these instructions http://elinux. >>>>> org/Beagleboard:U-boot_partitioning_layout_2.0#nfs_support and there >>>>> is no mention of any netargs.. >>>>> >>>>> Apologies for my ignorance, but I am brand new to all this and having >>>>> a hard time following, would you please clarify how to achieve what you >>>>> mentioned. >>>>> >>>>> the display is now not balnking after adding the optargs to uEnv.txt >>>>> in the fat boot partition but for learning sake, I would like to know how >>>>> to achieve this in the /boot/uEnv.txt >>>>> >>>>> Thanks for the help. >>>>> >>>>> Rob >>>>> >>>>> >>>>> On Monday, 8 September 2014 10:12:14 UTC+1, William Hermans wrote: >>>>>> >>>>>> >>>>>> >>>>>> *#cmdline=quiet init=/lib/systemd/systemd consoleblank=0 <======= >>>>>> DOES NOT WORK* >>>>>>> >>>>>>> >>>>>>> That would be because you need to remove the comment . . .remove the >>>>>> hash mark or '#'. If that does not work, then your netargs do not contain >>>>>> ${cmdline} >>>>>> >>>>>> On Mon, Sep 8, 2014 at 1:20 AM, Moscowbob <mosc...@gmail.com> wrote: >>>>>> >>>>>>> Thank you all for you assistance the problem is resolved. just some >>>>>>> additional points. >>>>>>> >>>>>>> SD Card boot partition: >>>>>>> uEnv.txt >>>>>>> -------------------------------- >>>>>>> ##Rename as: uEnv.txt to boot via nfs >>>>>>> >>>>>>> ##https://www.kernel.org/doc/Documentation/filesystems/nfs/ >>>>>>> nfsroot.txt >>>>>>> >>>>>>> ##SERVER: sudo apt-get install tftpd-hpa >>>>>>> ##SERVER: TFTP_DIRECTORY defined in /etc/default/tftpd-hpa >>>>>>> ##SERVER: zImage/*.dtb need to be located here: >>>>>>> ##SERVER: TFTP_DIRECTORY/zImage >>>>>>> ##SERVER: TFTP_DIRECTORY/dtbs/*.dtb >>>>>>> >>>>>>> ##client_ip needs to be set for u-boot to try booting via nfs >>>>>>> >>>>>>> client_ip=192.168.1.17 >>>>>>> >>>>>>> #u-boot defaults: uncomment and override where needed >>>>>>> >>>>>>> server_ip=192.168.1.12 >>>>>>> gw_ip=192.168.1.1 >>>>>>> netmask=255.255.255.0 >>>>>>> #hostname= >>>>>>> device=eth0 >>>>>>> #autoconf=off >>>>>>> root_dir=/home/rob/beaglebone/rootfs >>>>>>> nfs_options=,vers=3 >>>>>>> nfsrootfstype=ext4 rootwait fixrtc >>>>>>> *optargs="consoleblank=0"* >>>>>>> >>>>>>> -------------------------------- >>>>>>> >>>>>>> rootfs/boot/ >>>>>>> uEnv.txt >>>>>>> ----------------------- >>>>>>> uname_r=3.15.10-bone8 >>>>>>> cmdline=quiet init=/lib/systemd/systemd >>>>>>> *#cmdline=quiet init=/lib/systemd/systemd consoleblank=0 <======= >>>>>>> DOES NOT WORK* >>>>>>> ------------------------ >>>>>>> >>>>>>> Thanks >>>>>>> Rob >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Monday, 8 September 2014 01:15:14 UTC+1, Moscowbob wrote: >>>>>>>> >>>>>>>> >>>>>>>> BBB boot from tftp and nfs - >>>>>>>> kernel: 3.15.10-bone8 >>>>>>>> rootfs: debian-jessie-console-armhf-2014-08-13 >>>>>>>> >>>>>>>> Hardware: >>>>>>>> BBB A5C >>>>>>>> Circuitco LCD4 cape >>>>>>>> Circuitco RS232 cape >>>>>>>> >>>>>>>> /home/rob/rootfs/boot/uEnv.txt >>>>>>>> >>>>>>>> uname_r=3.15.10-bone8 >>>>>>>> cmdline=quiet init=/lib/systemd/systemd >>>>>>>> *optargs="consoleblank=0"*. >>>>>>>> >>>>>>>> I used this reference http://elinux.org/Be >>>>>>>> agleboard:BeagleBone_Black_FAQ >>>>>>>> <http://elinux.org/Beagleboard:BeagleBone_Black_FAQ#Is_there_a_way_to_prevent_my_HDMI_monitor_from_sleeping_while_using_my_BBB.3F> >>>>>>>> but >>>>>>>> the display is still blanking after 10 minutes. >>>>>>>> >>>>>>>> Would appreciate some guidance. >>>>>>>> >>>>>>>> Thanks >>>>>>>> Rob >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>> 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 beagleboard...@googlegroups.com. >>>>>>> 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 beagleboard+unsubscr...@googlegroups.com. >>>> 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
