@William - After reading RCN explanation that different locations are
searched, this crossed my mind and I deleted all uEnv.txt files everywhere
except for the sd card fat partition, but this still does not work if I add
either
cmdline=quiet init=/lib/systemd/systemd consoleblank=0
OR
cmdline=quiet init=/lib/systemd/systemd
optarg="consoleblank=0"
to the /boot/uEnv.txt on the nfs
My next step was to just use a fat formatted sd card with MLO, uimage and
uEnv.txt and no ext4 partition and still the same - the consoleblank does
not work for my configuration if added to /boot/uEnv.txt
Thanks
Rob
On Tuesday, 9 September 2014 05:33:10 UTC+1, William Hermans wrote:
>
> Jason, he was using a console testing image, and using the built in env
> variables for tftp + nfs. These images came with two uEnv.txt files, and
> since he was having problems with uboot env variables I'm betting he
> actually had 3 uEnv.txt files.
>
> 1) fat / boot part
> 2) ext4 footfs on sdcard
> 3) ext4 rootfs on nfs share host.
>
> uboot was probably pulling in the uEnv.txt which he was not editing. Which
> again, I'm betting was on partition 2 ( ext4 ) of the sdcard. e.g. he was
> editing the uEnv.txt file on the nfs share as I suggested.
>
> On Mon, Sep 8, 2014 at 9:04 PM, Robert Nelson <robert...@gmail.com
> <javascript:>> wrote:
>
>> On Mon, Sep 8, 2014 at 10:22 PM, Jason Lange <j.b....@gmail.com
>> <javascript:>> wrote:
>> >
>> >
>> > On Sun, Sep 7, 2014 at 8:35 PM, William Hermans <yyr...@gmail.com
>> <javascript:>> wrote:
>> >>
>> >> Jason, hah ! I see why now. Can you see the problem ?
>> >>
>> >>> uname_r=3.15.10-bone8
>> >>> cmdline=quiet init=/lib/systemd/systemd
>> >>> optargs="consoleblank=0".
>> >>
>> >>
>> >> This is actually in the wrong file. For this to work in the file he's
>> >> using there it needs to be as i said above. Which is:
>> >>
>> >> cmdline=quiet init=/lib/systemd/systemd consoleblank=0
>> >>
>> >> This is because the file he's using is the second stage uEnv.txt file
>> and
>> >> not the one loaded at boot. Which now that I think about it could have
>> very
>> >> well been my problem too.
>> >
>> >
>> > Well I finally understand what your saying here -- I didn't know that
>> there
>> > are/were two functional uEnv.txts. This looks like the file that I set
>> my
>> > optargs in (that is, it starts with the uname_r variable being set),
>> but I
>> > am running the new set up with only one uEnv.txt being functional.
>> >
>> > @Robert again for clarity:
>> >
>> > In a setup that only uses one uEnv.txt (that being /boot/uEnv.txt) that
>> is
>> > the place to set your optargs but in the two functional uEnv.txt setup
>> the
>> > place to set optargs is /uEnv.txt?
>>
>> Just edit:
>>
>> /boot/uEnv.txt
>>
>> /uEnv.txt is just a shim..
>>
>> > And if that is so, what is the simplest way for someone to know which
>> of the
>> > two situations they are dealing with?
>>
>> "/uEnv.txt" will set your bootargs like so:
>>
>> setenv bootargs console=tty0 console=\${console} \${optargs}
>> \${cape_disable} \${cape_enable} root=/dev/mmcblk0p1
>> rootfstype=\${mmcrootfstype} \${cmdline}
>>
>> So override any of those "\${var}" by defining them in /boot/uEnv.txt
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> http://www.rcn-ee.com/
>>
>> --
>> 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 <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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
