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 <[email protected]> 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/Beagleboard: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 [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.

Reply via email to