Sorry, I don't want to shut you down. It just seemed like a natural break
in a long thread. (If there was a sideband I wouldn't be tacking this on.)
Cheers William.
On Mon, Sep 8, 2014 at 10:05 PM, William Hermans <yyrk...@gmail.com> wrote:
> "um" If you posts on this subject are valid so are mine. A/B conversation
> as well.
>
> On Mon, Sep 8, 2014 at 10:01 PM, Jason Lange <j.b.la...@gmail.com> wrote:
>
>> ummn... new topic?
>>
>>
>> On Mon, Sep 8, 2014 at 9:59 PM, William Hermans <yyrk...@gmail.com>
>> wrote:
>>
>>> Robert, using your build instructions and compiling the kernel from
>>> source ( 3.8.13-bone64.1 ) it is somehow loading omap_rng module at boot.
>>> IS this normal, or did i somehow screw up in menuconfig ?
>>>
>>> As it is, I have the module blacklisted, but I'd rather it did not exist
>>> at all on my own system.
>>>
>>> Also, I'm looking into building that html5 web app you say you're
>>> waiting for. Anything specific you want ? Or just so long as it executes
>>> the commands mentioned above ?
>>>
>>> On Mon, Sep 8, 2014 at 9:42 PM, Jason Lange <j.b.la...@gmail.com> wrote:
>>>
>>>> Too much fun!
>>>>
>>>> On Mon, Sep 8, 2014 at 9:32 PM, William Hermans <yyrk...@gmail.com>
>>>> 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 <robertcnel...@gmail.com
>>>>> > wrote:
>>>>>
>>>>>> On Mon, Sep 8, 2014 at 10:22 PM, Jason Lange <j.b.la...@gmail.com>
>>>>>> wrote:
>>>>>> >
>>>>>> >
>>>>>> > On Sun, Sep 7, 2014 at 8:35 PM, William Hermans <yyrk...@gmail.com>
>>>>>> 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+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.
>>>>>
>>>>
>>>> --
>>>> 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.
>>>
>>
>> --
>> 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.
>
--
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.
