subject:"Re\: \[beagleboard\] optargs in kernel 3.15.10\-bone8"

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-09 Thread John Syn


On 9/9/14, 7:27 AM, "Robert Nelson"  wrote:

>On Tue, Sep 9, 2014 at 9:13 AM, Moscowbob  wrote:
>> @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
>
>"on the nfs" u-boot can't read /boot/uEnv.txt off the "nfs" (yet)...
>for the nfs case, it's got to be on the first partition /uEnv.txt
In the case where client_ip is defined, why not use TFTP to load uEnv.txt?

Regards,
John
>
>>
>> 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
>
>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.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-09 Thread William Hermans

loaduEnvtxt=load mmc 0:2 ${loadaddr} /boot/uEnv.txt ; env import -t
${loadaddr} ${filesize};

This works for me.

On Tue, Sep 9, 2014 at 9:06 AM, Moscowbob  wrote:

> Thanks Robert, that clears up things for me now
>
> On Tuesday, 9 September 2014 15:28:20 UTC+1, RobertCNelson wrote:
>
>> On Tue, Sep 9, 2014 at 9:13 AM, Moscowbob  wrote:
>> > @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
>>
>> "on the nfs" u-boot can't read /boot/uEnv.txt off the "nfs" (yet)...
>> for the nfs case, it's got to be on the first partition /uEnv.txt
>>
>> >
>> > 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
>>
>> 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.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-09 Thread Moscowbob

Thanks Robert, that clears up things for me now

On Tuesday, 9 September 2014 15:28:20 UTC+1, RobertCNelson wrote:
>
> On Tue, Sep 9, 2014 at 9:13 AM, Moscowbob > 
> wrote: 
> > @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 
>
> "on the nfs" u-boot can't read /boot/uEnv.txt off the "nfs" (yet)... 
> for the nfs case, it's got to be on the first partition /uEnv.txt 
>
> > 
> > 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 
>
> 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.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-09 Thread Robert Nelson

On Tue, Sep 9, 2014 at 9:13 AM, Moscowbob  wrote:
> @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

"on the nfs" u-boot can't read /boot/uEnv.txt off the "nfs" (yet)...
for the nfs case, it's got to be on the first partition /uEnv.txt

>
> 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

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.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-09 Thread Moscowbob

@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  > wrote:
>
>> On Mon, Sep 8, 2014 at 10:22 PM, Jason Lange > > wrote:
>> >
>> >
>> > On Sun, Sep 7, 2014 at 8:35 PM, William Hermans > > 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 .
>> 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.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-08 Thread Jason Lange

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  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  wrote:
>
>> ummn... new topic?
>>
>>
>> On Mon, Sep 8, 2014 at 9:59 PM, William Hermans 
>> 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  wrote:
>>>
 Too much fun!

 On Mon, Sep 8, 2014 at 9:32 PM, 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  > wrote:
>
>> On Mon, Sep 8, 2014 at 10:22 PM, Jason Lange 
>> wrote:
>> >
>> >
>> > On Sun, Sep 7, 2014 at 8:35 PM, William Hermans 
>> 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 g

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-08 Thread William Hermans

"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  wrote:

> ummn... new topic?
>
>
> On Mon, Sep 8, 2014 at 9:59 PM, William Hermans  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  wrote:
>>
>>> Too much fun!
>>>
>>> On Mon, Sep 8, 2014 at 9:32 PM, 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 
 wrote:

> On Mon, Sep 8, 2014 at 10:22 PM, Jason Lange 
> wrote:
> >
> >
> > On Sun, Sep 7, 2014 at 8:35 PM, William Hermans 
> 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 gr

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-08 Thread Jason Lange

ummn... new topic?


On Mon, Sep 8, 2014 at 9:59 PM, William Hermans  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  wrote:
>
>> Too much fun!
>>
>> On Mon, Sep 8, 2014 at 9:32 PM, 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 
>>> wrote:
>>>
 On Mon, Sep 8, 2014 at 10:22 PM, Jason Lange 
 wrote:
 >
 >
 > On Sun, Sep 7, 2014 at 8:35 PM, William Hermans 
 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 th

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-08 Thread William Hermans

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  wrote:

> Too much fun!
>
> On Mon, Sep 8, 2014 at 9:32 PM, 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 
>> wrote:
>>
>>> On Mon, Sep 8, 2014 at 10:22 PM, Jason Lange 
>>> wrote:
>>> >
>>> >
>>> > On Sun, Sep 7, 2014 at 8:35 PM, William Hermans 
>>> 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.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-08 Thread Jason Lange

Too much fun!

On Mon, Sep 8, 2014 at 9:32 PM, 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 
> wrote:
>
>> On Mon, Sep 8, 2014 at 10:22 PM, Jason Lange  wrote:
>> >
>> >
>> > On Sun, Sep 7, 2014 at 8:35 PM, William Hermans 
>> 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.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-08 Thread William Hermans

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 
wrote:

> On Mon, Sep 8, 2014 at 10:22 PM, Jason Lange  wrote:
> >
> >
> > On Sun, Sep 7, 2014 at 8:35 PM, William Hermans 
> 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.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-08 Thread Robert Nelson

On Mon, Sep 8, 2014 at 10:22 PM, Jason Lange  wrote:
>
>
> On Sun, Sep 7, 2014 at 8:35 PM, William Hermans  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.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-08 Thread Jason Lange

On Sun, Sep 7, 2014 at 8:35 PM, William Hermans  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.txt*s*.  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?

And if that is so, what is the simplest way for someone to know which of
the two situations they are dealing with?

-- 
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.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-08 Thread Robert Nelson

On Mon, Sep 8, 2014 at 7:40 AM, Moscowbob  wrote:
> Sorry typo...
> "Is there any reason I should not continue with 3.15 kernel and revert to
> 3.14? "

Well, 3.15 is eol, and we are planning to make the 3.14 the "new"
stable... Otherwise the same setup will work on the v3.16.x/v3.17.x
branches of bb-kernel.

Do i give too many options. ;)

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.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-08 Thread Moscowbob

Sorry typo...
"Is there any reason I should not continue with 3.15 kernel and revert to 
3.14? "

On Monday, 8 September 2014 13:39:16 UTC+1, Moscowbob wrote:
>
> Robert, I did the changes in the 
> bb-kernel/KERNEL/arch/arm/boot/dts/am335x-boneblack.dts and lcd and rs232 
> capes both work fine. Is there any reason I should not continue with 3.15 
> kernel and revert to 3.13 ?
>
> Thanks
>
> Rob 
>
> On Monday, 8 September 2014 12:34:10 UTC+1, RobertCNelson wrote:
>>
>> On Sun, Sep 7, 2014 at 7:15 PM, 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 
>>
>> So to achieve this with a kernel (not v3.8.x) 
>>
>> http://elinux.org/Beagleboard:Capes_3.8_to_3.14 
>>
>> sudo apt-get update 
>> sudo apt-get install linux-image-3.14.17-ti-r17 
>>
>> (reboot) 
>>
>> git clone -b 3.14-ti https://github.com/RobertCNelson/dtb-rebuilder.git 
>> cd dtb-rebuilder/ 
>>
>> nano ./src/arm/am335x-boneblack.dts 
>>
>> Disable hdmi: 
>> #include "am335x-boneblack-nxp-hdmi-audio.dtsi" -> /* #include 
>> "am335x-boneblack-nxp-hdmi-audio.dtsi" */ 
>>
>> Disable proto cape: 
>> #include "am335x-bone-basic-proto-cape.dtsi" -> /* #include 
>> "am335x-bone-basic-proto-cape.dtsi" */ 
>>
>> Enable lcd 4: 
>> /* #include "am335x-bone-lcd4-01-00a1.dtsi" */ -> #include 
>> "am335x-bone-lcd4-01-00a1.dtsi" 
>>
>> Enable uart (there's 3 options: uart1/uart2/uart4) 
>>
>> For uart 1: 
>> /* #include "am335x-bone-ttyO1.dtsi" */ -> #include 
>> "am335x-bone-ttyO1.dtsi" 
>>
>> make 
>> sudo make install 
>>
>> (reboot) 
>>
>> lcd and serial should work with a non v3.8.x capemgr kernel.. 
>>
>> (i'm hoping someone comes out with an html5 gui for the above ^^) 
>>
>> 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.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-08 Thread Moscowbob

Robert, I did the changes in the 
bb-kernel/KERNEL/arch/arm/boot/dts/am335x-boneblack.dts and lcd and rs232 
capes both work fine. Is there any reason I should not continue with 3.15 
kernel and revert to 3.13 ?

Thanks

Rob 

On Monday, 8 September 2014 12:34:10 UTC+1, RobertCNelson wrote:
>
> On Sun, Sep 7, 2014 at 7:15 PM, 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 
>
> So to achieve this with a kernel (not v3.8.x) 
>
> http://elinux.org/Beagleboard:Capes_3.8_to_3.14 
>
> sudo apt-get update 
> sudo apt-get install linux-image-3.14.17-ti-r17 
>
> (reboot) 
>
> git clone -b 3.14-ti https://github.com/RobertCNelson/dtb-rebuilder.git 
> cd dtb-rebuilder/ 
>
> nano ./src/arm/am335x-boneblack.dts 
>
> Disable hdmi: 
> #include "am335x-boneblack-nxp-hdmi-audio.dtsi" -> /* #include 
> "am335x-boneblack-nxp-hdmi-audio.dtsi" */ 
>
> Disable proto cape: 
> #include "am335x-bone-basic-proto-cape.dtsi" -> /* #include 
> "am335x-bone-basic-proto-cape.dtsi" */ 
>
> Enable lcd 4: 
> /* #include "am335x-bone-lcd4-01-00a1.dtsi" */ -> #include 
> "am335x-bone-lcd4-01-00a1.dtsi" 
>
> Enable uart (there's 3 options: uart1/uart2/uart4) 
>
> For uart 1: 
> /* #include "am335x-bone-ttyO1.dtsi" */ -> #include 
> "am335x-bone-ttyO1.dtsi" 
>
> make 
> sudo make install 
>
> (reboot) 
>
> lcd and serial should work with a non v3.8.x capemgr kernel.. 
>
> (i'm hoping someone comes out with an html5 gui for the above ^^) 
>
> 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.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-08 Thread Robert Nelson

On Sun, Sep 7, 2014 at 7:15 PM, 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

So to achieve this with a kernel (not v3.8.x)

http://elinux.org/Beagleboard:Capes_3.8_to_3.14

sudo apt-get update
sudo apt-get install linux-image-3.14.17-ti-r17

(reboot)

git clone -b 3.14-ti https://github.com/RobertCNelson/dtb-rebuilder.git
cd dtb-rebuilder/

nano ./src/arm/am335x-boneblack.dts

Disable hdmi:
#include "am335x-boneblack-nxp-hdmi-audio.dtsi" -> /* #include
"am335x-boneblack-nxp-hdmi-audio.dtsi" */

Disable proto cape:
#include "am335x-bone-basic-proto-cape.dtsi" -> /* #include
"am335x-bone-basic-proto-cape.dtsi" */

Enable lcd 4:
/* #include "am335x-bone-lcd4-01-00a1.dtsi" */ -> #include
"am335x-bone-lcd4-01-00a1.dtsi"

Enable uart (there's 3 options: uart1/uart2/uart4)

For uart 1:
/* #include "am335x-bone-ttyO1.dtsi" */ -> #include "am335x-bone-ttyO1.dtsi"

make
sudo make install

(reboot)

lcd and serial should work with a non v3.8.x capemgr kernel..

(i'm hoping someone comes out with an html5 gui for the above ^^)

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.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-07 Thread Jason Lange

I think if they are built in and not loaded as an overlay they never
disappear from the listing I think that L comes and goes to show there
status.

On Sun, Sep 7, 2014 at 9:02 PM, William Hermans  wrote:

> Err actually, they are not loaded, been a while since ive played with
> *slots* heh.
>
> On Sun, Sep 7, 2014 at 8:53 PM, William Hermans  wrote:
>
>> On Sun, Sep 7, 2014 at 8:30 PM, Jason Lange  wrote:
>>
>>> I don't know if capemanager is functional for these new fangled
>>> kernels.  optargs will happily pass non functional arguments (like my
>>> fauxarg above).  Maybe optargs was passing your capemgr.disable argument
>>> and it was something else that was broken?
>>>
>>
>> Yes, capemgr always works with 3.8.x, however it is different. optargs
>> does not seem to work as it did previously.
>>
>> root@arm:~# cat /sys/devices/bone_capemgr.9/slots
>>  0: 54:PF---
>>  1: 55:PF---
>>  2: 56:PF---
>>  3: 57:PF---
>>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>>  5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>>  6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
>>
>> root@arm:~# mount /dev/mmcblk0p1 /media/boot/
>> root@arm:~# cat /media/boot/uEnv.txt |grep optargs=
>> optargs=consoleblank=0
>> capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
>>
>>
>>
>>> But if you can make it work why isn't it working for MoscowBob ??
>>>
>>> On Sun, Sep 7, 2014 at 8:20 PM, William Hermans 
>>> wrote:
>>>
>>>> For the record. in that cmdline *consoleblank=0* is declared in
>>>> $optargs  and *init=/lib/systemd/systemd *is declared in* $cmdline. *
>>>>
>>>> Previously I had tried disabling hdmi via optargs, so maybe that is now
>>>> different. Either way
>>>> *optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN*
>>>>
>>>> was not working for me
>>>>
>>>>
>>>>
>>>> On Sun, Sep 7, 2014 at 8:08 PM, William Hermans 
>>>> wrote:
>>>>
>>>>> Jason, odd, it seems to be working for me now too. Previously the
>>>>> cmdline env variable was overriding my optargs statements.
>>>>>
>>>>> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
>>>>>> *0*
>>>>>> *root@arm:~# cat /proc/cmdline*
>>>>>> *console=ttyO0,115200n8 consoleblank=0 root=/dev/nfs
>>>>>> nfsroot=192.168.2xxx.xxx:/home/william/rootfs-testing,rsize=32768,wsize=32768,vers=3
>>>>>> rw ip=192.168.xxx.xxx:192.168.xxx.xxx:192.168.xxx.xxx:255.255.255.0:arm
>>>>>> quiet init=/lib/systemd/systemd*
>>>>>>
>>>>>
>>>>>
>>>>> On Sun, Sep 7, 2014 at 7:55 PM, Jason Lange 
>>>>> wrote:
>>>>>
>>>>>> just added fauxarg to my optargs like this:
>>>>>>
>>>>>> optargs="spidev.bufsiz=16384" fauxarg
>>>>>>
>>>>>> and rebooted.  Now cat /proc/cmdline shows this:
>>>>>>
>>>>>> console=tty0 console=ttyO0,115200n8 spidev.bufsiz=16384 *fauxarg*
>>>>>> root=/dev/mmcblk0p1 rootfstype=ext4 rootwait fixrtc quiet
>>>>>> init=/lib/systemd/systemd
>>>>>>
>>>>>> On Sun, Sep 7, 2014 at 7:51 PM, William Hermans 
>>>>>> wrote:
>>>>>>
>>>>>>> Since both of you seem convinced that optargs is not broken, why
>>>>>>> dont you actually go make changes to your own uEnv.txt and test if what 
>>>>>>> you
>>>>>>> think will work, actually works. What I did works, as I tested it 
>>>>>>> myself.
>>>>>>>
>>>>>>> On Sun, Sep 7, 2014 at 7:50 PM, Jason Lange 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> try:
>>>>>>>> cat /proc/cmdline
>>>>>>>>
>>>>>>>> to see if optargs show there
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sun, Sep 7, 2014 at 7:46 PM, John Syn 
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> From: William Hermans 
>>>>>

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-07 Thread Jason Lange

Does the "L" that is there in the listing for slot 4, but not 5 and 6,
indicate that it is loaded.  If you echo in the HDMI capes again do they
then show a "L" as well?

By "new fangled" I mean 3.14 and above -- when I ls /sys/devices there is
no bone_capemgr


On Sun, Sep 7, 2014 at 8:53 PM, William Hermans  wrote:

> On Sun, Sep 7, 2014 at 8:30 PM, Jason Lange  wrote:
>
>> I don't know if capemanager is functional for these new fangled kernels.
>> optargs will happily pass non functional arguments (like my fauxarg
>> above).  Maybe optargs was passing your capemgr.disable argument and it was
>> something else that was broken?
>>
>
> Yes, capemgr always works with 3.8.x, however it is different. optargs
> does not seem to work as it did previously.
>
> root@arm:~# cat /sys/devices/bone_capemgr.9/slots
>  0: 54:PF---
>  1: 55:PF---
>  2: 56:PF---
>  3: 57:PF---
>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>  5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>  6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
>
> root@arm:~# mount /dev/mmcblk0p1 /media/boot/
> root@arm:~# cat /media/boot/uEnv.txt |grep optargs=
> optargs=consoleblank=0
> capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
>
>
>
>> But if you can make it work why isn't it working for MoscowBob ??
>>
>> On Sun, Sep 7, 2014 at 8:20 PM, William Hermans 
>> wrote:
>>
>>> For the record. in that cmdline *consoleblank=0* is declared in
>>> $optargs  and *init=/lib/systemd/systemd *is declared in* $cmdline. *
>>>
>>> Previously I had tried disabling hdmi via optargs, so maybe that is now
>>> different. Either way
>>> *optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN*
>>>
>>> was not working for me
>>>
>>>
>>>
>>> On Sun, Sep 7, 2014 at 8:08 PM, William Hermans 
>>> wrote:
>>>
>>>> Jason, odd, it seems to be working for me now too. Previously the
>>>> cmdline env variable was overriding my optargs statements.
>>>>
>>>> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
>>>>> *0*
>>>>> *root@arm:~# cat /proc/cmdline*
>>>>> *console=ttyO0,115200n8 consoleblank=0 root=/dev/nfs
>>>>> nfsroot=192.168.2xxx.xxx:/home/william/rootfs-testing,rsize=32768,wsize=32768,vers=3
>>>>> rw ip=192.168.xxx.xxx:192.168.xxx.xxx:192.168.xxx.xxx:255.255.255.0:arm
>>>>> quiet init=/lib/systemd/systemd*
>>>>>
>>>>
>>>>
>>>> On Sun, Sep 7, 2014 at 7:55 PM, Jason Lange 
>>>> wrote:
>>>>
>>>>> just added fauxarg to my optargs like this:
>>>>>
>>>>> optargs="spidev.bufsiz=16384" fauxarg
>>>>>
>>>>> and rebooted.  Now cat /proc/cmdline shows this:
>>>>>
>>>>> console=tty0 console=ttyO0,115200n8 spidev.bufsiz=16384 *fauxarg*
>>>>> root=/dev/mmcblk0p1 rootfstype=ext4 rootwait fixrtc quiet
>>>>> init=/lib/systemd/systemd
>>>>>
>>>>> On Sun, Sep 7, 2014 at 7:51 PM, William Hermans 
>>>>> wrote:
>>>>>
>>>>>> Since both of you seem convinced that optargs is not broken, why dont
>>>>>> you actually go make changes to your own uEnv.txt and test if what you
>>>>>> think will work, actually works. What I did works, as I tested it myself.
>>>>>>
>>>>>> On Sun, Sep 7, 2014 at 7:50 PM, Jason Lange 
>>>>>> wrote:
>>>>>>
>>>>>>> try:
>>>>>>> cat /proc/cmdline
>>>>>>>
>>>>>>> to see if optargs show there
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Sep 7, 2014 at 7:46 PM, John Syn  wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> From: William Hermans 
>>>>>>>> Reply-To: "beagleboard@googlegroups.com" <
>>>>>>>> beagleboard@googlegroups.com>
>>>>>>>> Date: Sunday, September 7, 2014 at 7:43 PM
>>>>>>>> To: "beagleboard@googlegroups.com" 
>>>>>>>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>>>>>>>
>>>>>>>> Ok, so rather coming in and sniping

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-07 Thread William Hermans

Err actually, they are not loaded, been a while since ive played with
*slots* heh.

On Sun, Sep 7, 2014 at 8:53 PM, William Hermans  wrote:

> On Sun, Sep 7, 2014 at 8:30 PM, Jason Lange  wrote:
>
>> I don't know if capemanager is functional for these new fangled kernels.
>> optargs will happily pass non functional arguments (like my fauxarg
>> above).  Maybe optargs was passing your capemgr.disable argument and it was
>> something else that was broken?
>>
>
> Yes, capemgr always works with 3.8.x, however it is different. optargs
> does not seem to work as it did previously.
>
> root@arm:~# cat /sys/devices/bone_capemgr.9/slots
>  0: 54:PF---
>  1: 55:PF---
>  2: 56:PF---
>  3: 57:PF---
>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>  5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>  6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
>
> root@arm:~# mount /dev/mmcblk0p1 /media/boot/
> root@arm:~# cat /media/boot/uEnv.txt |grep optargs=
> optargs=consoleblank=0
> capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
>
>
>
>> But if you can make it work why isn't it working for MoscowBob ??
>>
>> On Sun, Sep 7, 2014 at 8:20 PM, William Hermans 
>> wrote:
>>
>>> For the record. in that cmdline *consoleblank=0* is declared in
>>> $optargs  and *init=/lib/systemd/systemd *is declared in* $cmdline. *
>>>
>>> Previously I had tried disabling hdmi via optargs, so maybe that is now
>>> different. Either way
>>> *optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN*
>>>
>>> was not working for me
>>>
>>>
>>>
>>> On Sun, Sep 7, 2014 at 8:08 PM, William Hermans 
>>> wrote:
>>>
>>>> Jason, odd, it seems to be working for me now too. Previously the
>>>> cmdline env variable was overriding my optargs statements.
>>>>
>>>> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
>>>>> *0*
>>>>> *root@arm:~# cat /proc/cmdline*
>>>>> *console=ttyO0,115200n8 consoleblank=0 root=/dev/nfs
>>>>> nfsroot=192.168.2xxx.xxx:/home/william/rootfs-testing,rsize=32768,wsize=32768,vers=3
>>>>> rw ip=192.168.xxx.xxx:192.168.xxx.xxx:192.168.xxx.xxx:255.255.255.0:arm
>>>>> quiet init=/lib/systemd/systemd*
>>>>>
>>>>
>>>>
>>>> On Sun, Sep 7, 2014 at 7:55 PM, Jason Lange 
>>>> wrote:
>>>>
>>>>> just added fauxarg to my optargs like this:
>>>>>
>>>>> optargs="spidev.bufsiz=16384" fauxarg
>>>>>
>>>>> and rebooted.  Now cat /proc/cmdline shows this:
>>>>>
>>>>> console=tty0 console=ttyO0,115200n8 spidev.bufsiz=16384 *fauxarg*
>>>>> root=/dev/mmcblk0p1 rootfstype=ext4 rootwait fixrtc quiet
>>>>> init=/lib/systemd/systemd
>>>>>
>>>>> On Sun, Sep 7, 2014 at 7:51 PM, William Hermans 
>>>>> wrote:
>>>>>
>>>>>> Since both of you seem convinced that optargs is not broken, why dont
>>>>>> you actually go make changes to your own uEnv.txt and test if what you
>>>>>> think will work, actually works. What I did works, as I tested it myself.
>>>>>>
>>>>>> On Sun, Sep 7, 2014 at 7:50 PM, Jason Lange 
>>>>>> wrote:
>>>>>>
>>>>>>> try:
>>>>>>> cat /proc/cmdline
>>>>>>>
>>>>>>> to see if optargs show there
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Sep 7, 2014 at 7:46 PM, John Syn  wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> From: William Hermans 
>>>>>>>> Reply-To: "beagleboard@googlegroups.com" <
>>>>>>>> beagleboard@googlegroups.com>
>>>>>>>> Date: Sunday, September 7, 2014 at 7:43 PM
>>>>>>>> To: "beagleboard@googlegroups.com" 
>>>>>>>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>>>>>>>
>>>>>>>> Ok, so rather coming in and sniping a comment Jjohn, why dont you
>>>>>>>> try and set an optargs env variable in the initial uEnv.txt file and 
>>>>>>>> see
>>>>>>>> what happens

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-07 Thread William Hermans

On Sun, Sep 7, 2014 at 8:30 PM, Jason Lange  wrote:

> I don't know if capemanager is functional for these new fangled kernels.
> optargs will happily pass non functional arguments (like my fauxarg
> above).  Maybe optargs was passing your capemgr.disable argument and it was
> something else that was broken?
>

Yes, capemgr always works with 3.8.x, however it is different. optargs does
not seem to work as it did previously.

root@arm:~# cat /sys/devices/bone_capemgr.9/slots
 0: 54:PF---
 1: 55:PF---
 2: 56:PF---
 3: 57:PF---
 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
 6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN

root@arm:~# mount /dev/mmcblk0p1 /media/boot/
root@arm:~# cat /media/boot/uEnv.txt |grep optargs=
optargs=consoleblank=0 capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN



> But if you can make it work why isn't it working for MoscowBob ??
>
> On Sun, Sep 7, 2014 at 8:20 PM, William Hermans  wrote:
>
>> For the record. in that cmdline *consoleblank=0* is declared in
>> $optargs  and *init=/lib/systemd/systemd *is declared in* $cmdline. *
>>
>> Previously I had tried disabling hdmi via optargs, so maybe that is now
>> different. Either way
>> *optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN*
>>
>> was not working for me
>>
>>
>>
>> On Sun, Sep 7, 2014 at 8:08 PM, William Hermans 
>> wrote:
>>
>>> Jason, odd, it seems to be working for me now too. Previously the
>>> cmdline env variable was overriding my optargs statements.
>>>
>>> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
>>>> *0*
>>>> *root@arm:~# cat /proc/cmdline*
>>>> *console=ttyO0,115200n8 consoleblank=0 root=/dev/nfs
>>>> nfsroot=192.168.2xxx.xxx:/home/william/rootfs-testing,rsize=32768,wsize=32768,vers=3
>>>> rw ip=192.168.xxx.xxx:192.168.xxx.xxx:192.168.xxx.xxx:255.255.255.0:arm
>>>> quiet init=/lib/systemd/systemd*
>>>>
>>>
>>>
>>> On Sun, Sep 7, 2014 at 7:55 PM, Jason Lange  wrote:
>>>
>>>> just added fauxarg to my optargs like this:
>>>>
>>>> optargs="spidev.bufsiz=16384" fauxarg
>>>>
>>>> and rebooted.  Now cat /proc/cmdline shows this:
>>>>
>>>> console=tty0 console=ttyO0,115200n8 spidev.bufsiz=16384 *fauxarg*
>>>> root=/dev/mmcblk0p1 rootfstype=ext4 rootwait fixrtc quiet
>>>> init=/lib/systemd/systemd
>>>>
>>>> On Sun, Sep 7, 2014 at 7:51 PM, William Hermans 
>>>> wrote:
>>>>
>>>>> Since both of you seem convinced that optargs is not broken, why dont
>>>>> you actually go make changes to your own uEnv.txt and test if what you
>>>>> think will work, actually works. What I did works, as I tested it myself.
>>>>>
>>>>> On Sun, Sep 7, 2014 at 7:50 PM, Jason Lange 
>>>>> wrote:
>>>>>
>>>>>> try:
>>>>>> cat /proc/cmdline
>>>>>>
>>>>>> to see if optargs show there
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Sep 7, 2014 at 7:46 PM, John Syn  wrote:
>>>>>>
>>>>>>>
>>>>>>> From: William Hermans 
>>>>>>> Reply-To: "beagleboard@googlegroups.com" <
>>>>>>> beagleboard@googlegroups.com>
>>>>>>> Date: Sunday, September 7, 2014 at 7:43 PM
>>>>>>> To: "beagleboard@googlegroups.com" 
>>>>>>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>>>>>>
>>>>>>> Ok, so rather coming in and sniping a comment Jjohn, why dont you
>>>>>>> try and set an optargs env variable in the initial uEnv.txt file and see
>>>>>>> what happens.
>>>>>>>
>>>>>>> If you're using the same uboot we're using, it wont work. Now, feel
>>>>>>> free to find yourself trolling a different post.
>>>>>>>
>>>>>>> Wow, that was so unnecessary. I was just trying to be helpful.
>>>>>>>
>>>>>>> Regards,
>>>>>>> John
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Sep 7, 2014 at 7:36 PM

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-07 Thread William Hermans

This should be that $optargs works in the initial uEnv.txt file loaded at
boot, but not the second stage uEnv.txt file which is pulled in by the
stage 1 file.

False alarm ( again ).

On Sun, Sep 7, 2014 at 6:37 PM, William Hermans  wrote:

> @Robert
>
> I'll have you know that you've broken $optargs in the initial stage
> uEnv.txt.
>
> In case you did not know already . . .
>
> On Sun, Sep 7, 2014 at 6:32 PM, William Hermans  wrote:
>
>> hmm so actual that did not work for me either, which I do not know is a
>> bug or what so here is what I had to do.
>>
>> First check output of:
>>
>> *$ cat /sys/module/kernel/parameters/consoleblank*
>> *600*
>>
>> It'll probably be 600 as above, which is ten minutes( 600 seconds ).
>>
>> So . . .
>>
>> *nano /boot/uEnv.txt*
>> and uncomment this line:
>> *#cmdline=quiet init=/lib/systemd/systemd*
>> then add at the end  *consoleblank=0*
>> Which gives you
>>
>>
>> *cmdline=quiet init=/lib/systemd/systemd consoleblank=0*
>> reboot the beaglebone and when it comes back up.
>>
>> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
>>> *0*
>>>
>>
>>
>> On Sun, Sep 7, 2014 at 6:07 PM, William Hermans 
>> wrote:
>>
>>> errr sorry, that should only be *setterm -blank 0*

>>>
>>> On Sun, Sep 7, 2014 at 6:03 PM, William Hermans 
>>> wrote:
>>>
 $ setterm -powersave off -blank 0

 On Sun, Sep 7, 2014 at 5:15 PM, 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
> 
>  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+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.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-07 Thread William Hermans

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.


On Sun, Sep 7, 2014 at 8:30 PM, Jason Lange  wrote:

> I don't know if capemanager is functional for these new fangled kernels.
> optargs will happily pass non functional arguments (like my fauxarg
> above).  Maybe optargs was passing your capemgr.disable argument and it was
> something else that was broken?
>
> But if you can make it work why isn't it working for MoscowBob ??
>
> On Sun, Sep 7, 2014 at 8:20 PM, William Hermans  wrote:
>
>> For the record. in that cmdline *consoleblank=0* is declared in
>> $optargs  and *init=/lib/systemd/systemd *is declared in* $cmdline. *
>>
>> Previously I had tried disabling hdmi via optargs, so maybe that is now
>> different. Either way
>> *optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN*
>>
>> was not working for me
>>
>>
>>
>> On Sun, Sep 7, 2014 at 8:08 PM, William Hermans 
>> wrote:
>>
>>> Jason, odd, it seems to be working for me now too. Previously the
>>> cmdline env variable was overriding my optargs statements.
>>>
>>> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
>>>> *0*
>>>> *root@arm:~# cat /proc/cmdline*
>>>> *console=ttyO0,115200n8 consoleblank=0 root=/dev/nfs
>>>> nfsroot=192.168.2xxx.xxx:/home/william/rootfs-testing,rsize=32768,wsize=32768,vers=3
>>>> rw ip=192.168.xxx.xxx:192.168.xxx.xxx:192.168.xxx.xxx:255.255.255.0:arm
>>>> quiet init=/lib/systemd/systemd*
>>>>
>>>
>>>
>>> On Sun, Sep 7, 2014 at 7:55 PM, Jason Lange  wrote:
>>>
>>>> just added fauxarg to my optargs like this:
>>>>
>>>> optargs="spidev.bufsiz=16384" fauxarg
>>>>
>>>> and rebooted.  Now cat /proc/cmdline shows this:
>>>>
>>>> console=tty0 console=ttyO0,115200n8 spidev.bufsiz=16384 *fauxarg*
>>>> root=/dev/mmcblk0p1 rootfstype=ext4 rootwait fixrtc quiet
>>>> init=/lib/systemd/systemd
>>>>
>>>> On Sun, Sep 7, 2014 at 7:51 PM, William Hermans 
>>>> wrote:
>>>>
>>>>> Since both of you seem convinced that optargs is not broken, why dont
>>>>> you actually go make changes to your own uEnv.txt and test if what you
>>>>> think will work, actually works. What I did works, as I tested it myself.
>>>>>
>>>>> On Sun, Sep 7, 2014 at 7:50 PM, Jason Lange 
>>>>> wrote:
>>>>>
>>>>>> try:
>>>>>> cat /proc/cmdline
>>>>>>
>>>>>> to see if optargs show there
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Sep 7, 2014 at 7:46 PM, John Syn  wrote:
>>>>>>
>>>>>>>
>>>>>>> From: William Hermans 
>>>>>>> Reply-To: "beagleboard@googlegroups.com" <
>>>>>>> beagleboard@googlegroups.com>
>>>>>>> Date: Sunday, September 7, 2014 at 7:43 PM
>>>>>>> To: "beagleboard@googlegroups.com" 
>>>>>>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>>>>>>
>>>>>>> Ok, so rather coming in and sniping a comment Jjohn, why dont you
>>>>>>> try and set an optargs env variable in the initial uEnv.txt file and see
>>>>>>> what happens.
>>>>>>>
>>>>>>> If you're using the same uboot we're using, it wont work. Now, feel
>>>>>>> free to find yourself trolling a different post.
>>>>>>>
>>>>>>> Wow, that was so unnecessary. I was just trying to be helpful.
>>>>>>>
>>>>>>> Regards,
>>>>>>> John
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Sep 7, 2014 at 7:36 PM, John Syn  wrote:
>>>>>>>
>>>>>>>

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-07 Thread Jason Lange

I don't know if capemanager is functional for these new fangled kernels.
optargs will happily pass non functional arguments (like my fauxarg
above).  Maybe optargs was passing your capemgr.disable argument and it was
something else that was broken?

But if you can make it work why isn't it working for MoscowBob ??

On Sun, Sep 7, 2014 at 8:20 PM, William Hermans  wrote:

> For the record. in that cmdline *consoleblank=0* is declared in $optargs
> and *init=/lib/systemd/systemd *is declared in* $cmdline. *
>
> Previously I had tried disabling hdmi via optargs, so maybe that is now
> different. Either way
> *optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN*
>
> was not working for me
>
>
>
> On Sun, Sep 7, 2014 at 8:08 PM, William Hermans  wrote:
>
>> Jason, odd, it seems to be working for me now too. Previously the cmdline
>> env variable was overriding my optargs statements.
>>
>> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
>>> *0*
>>> *root@arm:~# cat /proc/cmdline*
>>> *console=ttyO0,115200n8 consoleblank=0 root=/dev/nfs
>>> nfsroot=192.168.2xxx.xxx:/home/william/rootfs-testing,rsize=32768,wsize=32768,vers=3
>>> rw ip=192.168.xxx.xxx:192.168.xxx.xxx:192.168.xxx.xxx:255.255.255.0:arm
>>> quiet init=/lib/systemd/systemd*
>>>
>>
>>
>> On Sun, Sep 7, 2014 at 7:55 PM, Jason Lange  wrote:
>>
>>> just added fauxarg to my optargs like this:
>>>
>>> optargs="spidev.bufsiz=16384" fauxarg
>>>
>>> and rebooted.  Now cat /proc/cmdline shows this:
>>>
>>> console=tty0 console=ttyO0,115200n8 spidev.bufsiz=16384 *fauxarg*
>>> root=/dev/mmcblk0p1 rootfstype=ext4 rootwait fixrtc quiet
>>> init=/lib/systemd/systemd
>>>
>>> On Sun, Sep 7, 2014 at 7:51 PM, William Hermans 
>>> wrote:
>>>
>>>> Since both of you seem convinced that optargs is not broken, why dont
>>>> you actually go make changes to your own uEnv.txt and test if what you
>>>> think will work, actually works. What I did works, as I tested it myself.
>>>>
>>>> On Sun, Sep 7, 2014 at 7:50 PM, Jason Lange 
>>>> wrote:
>>>>
>>>>> try:
>>>>> cat /proc/cmdline
>>>>>
>>>>> to see if optargs show there
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Sep 7, 2014 at 7:46 PM, John Syn  wrote:
>>>>>
>>>>>>
>>>>>> From: William Hermans 
>>>>>> Reply-To: "beagleboard@googlegroups.com" <
>>>>>> beagleboard@googlegroups.com>
>>>>>> Date: Sunday, September 7, 2014 at 7:43 PM
>>>>>> To: "beagleboard@googlegroups.com" 
>>>>>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>>>>>
>>>>>> Ok, so rather coming in and sniping a comment Jjohn, why dont you try
>>>>>> and set an optargs env variable in the initial uEnv.txt file and see what
>>>>>> happens.
>>>>>>
>>>>>> If you're using the same uboot we're using, it wont work. Now, feel
>>>>>> free to find yourself trolling a different post.
>>>>>>
>>>>>> Wow, that was so unnecessary. I was just trying to be helpful.
>>>>>>
>>>>>> Regards,
>>>>>> John
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Sep 7, 2014 at 7:36 PM, John Syn  wrote:
>>>>>>
>>>>>>>
>>>>>>> From: William Hermans 
>>>>>>> Reply-To: "beagleboard@googlegroups.com" <
>>>>>>> beagleboard@googlegroups.com>
>>>>>>> Date: Sunday, September 7, 2014 at 7:26 PM
>>>>>>> To: "beagleboard@googlegroups.com" 
>>>>>>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>>>>>>
>>>>>>> optargs does not work in the latest uboot file setup. I've noticed
>>>>>>> this myself in othe situations. you have to use Robert new cmdline env
>>>>>>> variable
>>>>>>>
>>>>>>>
>>>>>>> https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
>>>>>>>
>>>>>>> Looking at the u-boot patch it l

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-07 Thread William Hermans

For the record. in that cmdline *consoleblank=0* is declared in $optargs
and *init=/lib/systemd/systemd *is declared in* $cmdline. *

Previously I had tried disabling hdmi via optargs, so maybe that is now
different. Either way
*optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN*

was not working for me



On Sun, Sep 7, 2014 at 8:08 PM, William Hermans  wrote:

> Jason, odd, it seems to be working for me now too. Previously the cmdline
> env variable was overriding my optargs statements.
>
> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
>> *0*
>> *root@arm:~# cat /proc/cmdline*
>> *console=ttyO0,115200n8 consoleblank=0 root=/dev/nfs
>> nfsroot=192.168.2xxx.xxx:/home/william/rootfs-testing,rsize=32768,wsize=32768,vers=3
>> rw ip=192.168.xxx.xxx:192.168.xxx.xxx:192.168.xxx.xxx:255.255.255.0:arm
>> quiet init=/lib/systemd/systemd*
>>
>
>
> On Sun, Sep 7, 2014 at 7:55 PM, Jason Lange  wrote:
>
>> just added fauxarg to my optargs like this:
>>
>> optargs="spidev.bufsiz=16384" fauxarg
>>
>> and rebooted.  Now cat /proc/cmdline shows this:
>>
>> console=tty0 console=ttyO0,115200n8 spidev.bufsiz=16384 *fauxarg*
>> root=/dev/mmcblk0p1 rootfstype=ext4 rootwait fixrtc quiet
>> init=/lib/systemd/systemd
>>
>> On Sun, Sep 7, 2014 at 7:51 PM, William Hermans 
>> wrote:
>>
>>> Since both of you seem convinced that optargs is not broken, why dont
>>> you actually go make changes to your own uEnv.txt and test if what you
>>> think will work, actually works. What I did works, as I tested it myself.
>>>
>>> On Sun, Sep 7, 2014 at 7:50 PM, Jason Lange  wrote:
>>>
>>>> try:
>>>> cat /proc/cmdline
>>>>
>>>> to see if optargs show there
>>>>
>>>>
>>>>
>>>>
>>>> On Sun, Sep 7, 2014 at 7:46 PM, John Syn  wrote:
>>>>
>>>>>
>>>>> From: William Hermans 
>>>>> Reply-To: "beagleboard@googlegroups.com" >>>> >
>>>>> Date: Sunday, September 7, 2014 at 7:43 PM
>>>>> To: "beagleboard@googlegroups.com" 
>>>>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>>>>
>>>>> Ok, so rather coming in and sniping a comment Jjohn, why dont you try
>>>>> and set an optargs env variable in the initial uEnv.txt file and see what
>>>>> happens.
>>>>>
>>>>> If you're using the same uboot we're using, it wont work. Now, feel
>>>>> free to find yourself trolling a different post.
>>>>>
>>>>> Wow, that was so unnecessary. I was just trying to be helpful.
>>>>>
>>>>> Regards,
>>>>> John
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Sep 7, 2014 at 7:36 PM, John Syn  wrote:
>>>>>
>>>>>>
>>>>>> From: William Hermans 
>>>>>> Reply-To: "beagleboard@googlegroups.com" <
>>>>>> beagleboard@googlegroups.com>
>>>>>> Date: Sunday, September 7, 2014 at 7:26 PM
>>>>>> To: "beagleboard@googlegroups.com" 
>>>>>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>>>>>
>>>>>> optargs does not work in the latest uboot file setup. I've noticed
>>>>>> this myself in othe situations. you have to use Robert new cmdline env
>>>>>> variable
>>>>>>
>>>>>>
>>>>>> https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
>>>>>>
>>>>>> Looking at the u-boot patch it looks like optargs is used with both
>>>>>> mmcargs and nfsargs.
>>>>>>
>>>>>> Regards,
>>>>>> John
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange 
>>>>>> wrote:
>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> I'm wondering if it would help if you changed from:
>>>>>>>
>>>>>>> optargs="consoleblank=0"
>>>>>>>
>>>>>>> to:
>>>>>>>
>>>>>>> optargs=consoleblank=0
>>>>>>>
>>>>>>> I use *optargs

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-07 Thread William Hermans

Jason, odd, it seems to be working for me now too. Previously the cmdline
env variable was overriding my optargs statements.

*root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
> *0*
> *root@arm:~# cat /proc/cmdline*
> *console=ttyO0,115200n8 consoleblank=0 root=/dev/nfs
> nfsroot=192.168.2xxx.xxx:/home/william/rootfs-testing,rsize=32768,wsize=32768,vers=3
> rw ip=192.168.xxx.xxx:192.168.xxx.xxx:192.168.xxx.xxx:255.255.255.0:arm
> quiet init=/lib/systemd/systemd*
>


On Sun, Sep 7, 2014 at 7:55 PM, Jason Lange  wrote:

> just added fauxarg to my optargs like this:
>
> optargs="spidev.bufsiz=16384" fauxarg
>
> and rebooted.  Now cat /proc/cmdline shows this:
>
> console=tty0 console=ttyO0,115200n8 spidev.bufsiz=16384 *fauxarg*
> root=/dev/mmcblk0p1 rootfstype=ext4 rootwait fixrtc quiet
> init=/lib/systemd/systemd
>
> On Sun, Sep 7, 2014 at 7:51 PM, William Hermans  wrote:
>
>> Since both of you seem convinced that optargs is not broken, why dont you
>> actually go make changes to your own uEnv.txt and test if what you think
>> will work, actually works. What I did works, as I tested it myself.
>>
>> On Sun, Sep 7, 2014 at 7:50 PM, Jason Lange  wrote:
>>
>>> try:
>>> cat /proc/cmdline
>>>
>>> to see if optargs show there
>>>
>>>
>>>
>>>
>>> On Sun, Sep 7, 2014 at 7:46 PM, John Syn  wrote:
>>>
>>>>
>>>> From: William Hermans 
>>>> Reply-To: "beagleboard@googlegroups.com" 
>>>> Date: Sunday, September 7, 2014 at 7:43 PM
>>>> To: "beagleboard@googlegroups.com" 
>>>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>>>
>>>> Ok, so rather coming in and sniping a comment Jjohn, why dont you try
>>>> and set an optargs env variable in the initial uEnv.txt file and see what
>>>> happens.
>>>>
>>>> If you're using the same uboot we're using, it wont work. Now, feel
>>>> free to find yourself trolling a different post.
>>>>
>>>> Wow, that was so unnecessary. I was just trying to be helpful.
>>>>
>>>> Regards,
>>>> John
>>>>
>>>>
>>>>
>>>> On Sun, Sep 7, 2014 at 7:36 PM, John Syn  wrote:
>>>>
>>>>>
>>>>> From: William Hermans 
>>>>> Reply-To: "beagleboard@googlegroups.com" >>>> >
>>>>> Date: Sunday, September 7, 2014 at 7:26 PM
>>>>> To: "beagleboard@googlegroups.com" 
>>>>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>>>>
>>>>> optargs does not work in the latest uboot file setup. I've noticed
>>>>> this myself in othe situations. you have to use Robert new cmdline env
>>>>> variable
>>>>>
>>>>>
>>>>> https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
>>>>>
>>>>> Looking at the u-boot patch it looks like optargs is used with both
>>>>> mmcargs and nfsargs.
>>>>>
>>>>> Regards,
>>>>> John
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange 
>>>>> wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I'm wondering if it would help if you changed from:
>>>>>>
>>>>>> optargs="consoleblank=0"
>>>>>>
>>>>>> to:
>>>>>>
>>>>>> optargs=consoleblank=0
>>>>>>
>>>>>> I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone
>>>>>> Debian Image 2014-09-04 running 3.14.17-ti-r17
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Sep 7, 2014 at 6:37 PM, William Hermans 
>>>>>> wrote:
>>>>>>
>>>>>>> @Robert
>>>>>>>
>>>>>>> I'll have you know that you've broken $optargs in the initial stage
>>>>>>> uEnv.txt.
>>>>>>>
>>>>>>> In case you did not know already . . .
>>>>>>>
>>>>>>> On Sun, Sep 7, 2014 at 6:32 PM, William Hermans 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> hmm so actual t

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-07 Thread Jason Lange

 just added fauxarg to my optargs like this:

optargs="spidev.bufsiz=16384" fauxarg

and rebooted.  Now cat /proc/cmdline shows this:

console=tty0 console=ttyO0,115200n8 spidev.bufsiz=16384 *fauxarg*
root=/dev/mmcblk0p1 rootfstype=ext4 rootwait fixrtc quiet
init=/lib/systemd/systemd

On Sun, Sep 7, 2014 at 7:51 PM, William Hermans  wrote:

> Since both of you seem convinced that optargs is not broken, why dont you
> actually go make changes to your own uEnv.txt and test if what you think
> will work, actually works. What I did works, as I tested it myself.
>
> On Sun, Sep 7, 2014 at 7:50 PM, Jason Lange  wrote:
>
>> try:
>> cat /proc/cmdline
>>
>> to see if optargs show there
>>
>>
>>
>>
>> On Sun, Sep 7, 2014 at 7:46 PM, John Syn  wrote:
>>
>>>
>>> From: William Hermans 
>>> Reply-To: "beagleboard@googlegroups.com" 
>>> Date: Sunday, September 7, 2014 at 7:43 PM
>>> To: "beagleboard@googlegroups.com" 
>>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>>
>>> Ok, so rather coming in and sniping a comment Jjohn, why dont you try
>>> and set an optargs env variable in the initial uEnv.txt file and see what
>>> happens.
>>>
>>> If you're using the same uboot we're using, it wont work. Now, feel free
>>> to find yourself trolling a different post.
>>>
>>> Wow, that was so unnecessary. I was just trying to be helpful.
>>>
>>> Regards,
>>> John
>>>
>>>
>>>
>>> On Sun, Sep 7, 2014 at 7:36 PM, John Syn  wrote:
>>>
>>>>
>>>> From: William Hermans 
>>>> Reply-To: "beagleboard@googlegroups.com" 
>>>> Date: Sunday, September 7, 2014 at 7:26 PM
>>>> To: "beagleboard@googlegroups.com" 
>>>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>>>
>>>> optargs does not work in the latest uboot file setup. I've noticed this
>>>> myself in othe situations. you have to use Robert new cmdline env variable
>>>>
>>>>
>>>> https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
>>>>
>>>> Looking at the u-boot patch it looks like optargs is used with both
>>>> mmcargs and nfsargs.
>>>>
>>>> Regards,
>>>> John
>>>>
>>>>
>>>>
>>>> On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange 
>>>> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> I'm wondering if it would help if you changed from:
>>>>>
>>>>> optargs="consoleblank=0"
>>>>>
>>>>> to:
>>>>>
>>>>> optargs=consoleblank=0
>>>>>
>>>>> I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone
>>>>> Debian Image 2014-09-04 running 3.14.17-ti-r17
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Sep 7, 2014 at 6:37 PM, William Hermans 
>>>>> wrote:
>>>>>
>>>>>> @Robert
>>>>>>
>>>>>> I'll have you know that you've broken $optargs in the initial stage
>>>>>> uEnv.txt.
>>>>>>
>>>>>> In case you did not know already . . .
>>>>>>
>>>>>> On Sun, Sep 7, 2014 at 6:32 PM, William Hermans 
>>>>>> wrote:
>>>>>>
>>>>>>> hmm so actual that did not work for me either, which I do not know
>>>>>>> is a bug or what so here is what I had to do.
>>>>>>>
>>>>>>> First check output of:
>>>>>>>
>>>>>>> *$ cat /sys/module/kernel/parameters/consoleblank*
>>>>>>> *600*
>>>>>>>
>>>>>>> It'll probably be 600 as above, which is ten minutes( 600 seconds ).
>>>>>>>
>>>>>>> So . . .
>>>>>>>
>>>>>>> *nano /boot/uEnv.txt*
>>>>>>> and uncomment this line:
>>>>>>> *#cmdline=quiet init=/lib/systemd/systemd*
>>>>>>> then add at the end  *consoleblank=0*
>>>>>>> Which gives you
>>>>>>>
>>>>>>>
>>>>>>> *cmdline=quiet init=/lib/systemd/systemd consoleblank=0*
>>

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-07 Thread William Hermans

Since both of you seem convinced that optargs is not broken, why dont you
actually go make changes to your own uEnv.txt and test if what you think
will work, actually works. What I did works, as I tested it myself.

On Sun, Sep 7, 2014 at 7:50 PM, Jason Lange  wrote:

> try:
> cat /proc/cmdline
>
> to see if optargs show there
>
>
>
>
> On Sun, Sep 7, 2014 at 7:46 PM, John Syn  wrote:
>
>>
>> From: William Hermans 
>> Reply-To: "beagleboard@googlegroups.com" 
>> Date: Sunday, September 7, 2014 at 7:43 PM
>> To: "beagleboard@googlegroups.com" 
>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>
>> Ok, so rather coming in and sniping a comment Jjohn, why dont you try and
>> set an optargs env variable in the initial uEnv.txt file and see what
>> happens.
>>
>> If you're using the same uboot we're using, it wont work. Now, feel free
>> to find yourself trolling a different post.
>>
>> Wow, that was so unnecessary. I was just trying to be helpful.
>>
>> Regards,
>> John
>>
>>
>>
>> On Sun, Sep 7, 2014 at 7:36 PM, John Syn  wrote:
>>
>>>
>>> From: William Hermans 
>>> Reply-To: "beagleboard@googlegroups.com" 
>>> Date: Sunday, September 7, 2014 at 7:26 PM
>>> To: "beagleboard@googlegroups.com" 
>>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>>
>>> optargs does not work in the latest uboot file setup. I've noticed this
>>> myself in othe situations. you have to use Robert new cmdline env variable
>>>
>>>
>>> https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
>>>
>>> Looking at the u-boot patch it looks like optargs is used with both
>>> mmcargs and nfsargs.
>>>
>>> Regards,
>>> John
>>>
>>>
>>>
>>> On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange  wrote:
>>>
>>>> Hello,
>>>>
>>>> I'm wondering if it would help if you changed from:
>>>>
>>>> optargs="consoleblank=0"
>>>>
>>>> to:
>>>>
>>>> optargs=consoleblank=0
>>>>
>>>> I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone
>>>> Debian Image 2014-09-04 running 3.14.17-ti-r17
>>>>
>>>>
>>>>
>>>> On Sun, Sep 7, 2014 at 6:37 PM, William Hermans 
>>>> wrote:
>>>>
>>>>> @Robert
>>>>>
>>>>> I'll have you know that you've broken $optargs in the initial stage
>>>>> uEnv.txt.
>>>>>
>>>>> In case you did not know already . . .
>>>>>
>>>>> On Sun, Sep 7, 2014 at 6:32 PM, William Hermans 
>>>>> wrote:
>>>>>
>>>>>> hmm so actual that did not work for me either, which I do not know is
>>>>>> a bug or what so here is what I had to do.
>>>>>>
>>>>>> First check output of:
>>>>>>
>>>>>> *$ cat /sys/module/kernel/parameters/consoleblank*
>>>>>> *600*
>>>>>>
>>>>>> It'll probably be 600 as above, which is ten minutes( 600 seconds ).
>>>>>>
>>>>>> So . . .
>>>>>>
>>>>>> *nano /boot/uEnv.txt*
>>>>>> and uncomment this line:
>>>>>> *#cmdline=quiet init=/lib/systemd/systemd*
>>>>>> then add at the end  *consoleblank=0*
>>>>>> Which gives you
>>>>>>
>>>>>>
>>>>>> *cmdline=quiet init=/lib/systemd/systemd consoleblank=0*
>>>>>> reboot the beaglebone and when it comes back up.
>>>>>>
>>>>>> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
>>>>>>> *0*
>>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Sep 7, 2014 at 6:07 PM, William Hermans 
>>>>>> wrote:
>>>>>>
>>>>>>> errr sorry, that should only be *setterm -blank 0*
>>>>>>>>
>>>>>>>
>>>>>>> On Sun, Sep 7, 2014 at 6:03 PM, William Hermans 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> $ setterm -powersave off -blank 0
>>>>>>>>
>&g

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-07 Thread Jason Lange

try:
cat /proc/cmdline

to see if optargs show there




On Sun, Sep 7, 2014 at 7:46 PM, John Syn  wrote:

>
> From: William Hermans 
> Reply-To: "beagleboard@googlegroups.com" 
> Date: Sunday, September 7, 2014 at 7:43 PM
> To: "beagleboard@googlegroups.com" 
> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>
> Ok, so rather coming in and sniping a comment Jjohn, why dont you try and
> set an optargs env variable in the initial uEnv.txt file and see what
> happens.
>
> If you're using the same uboot we're using, it wont work. Now, feel free
> to find yourself trolling a different post.
>
> Wow, that was so unnecessary. I was just trying to be helpful.
>
> Regards,
> John
>
>
>
> On Sun, Sep 7, 2014 at 7:36 PM, John Syn  wrote:
>
>>
>> From: William Hermans 
>> Reply-To: "beagleboard@googlegroups.com" 
>> Date: Sunday, September 7, 2014 at 7:26 PM
>> To: "beagleboard@googlegroups.com" 
>> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>>
>> optargs does not work in the latest uboot file setup. I've noticed this
>> myself in othe situations. you have to use Robert new cmdline env variable
>>
>>
>> https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
>>
>> Looking at the u-boot patch it looks like optargs is used with both
>> mmcargs and nfsargs.
>>
>> Regards,
>> John
>>
>>
>>
>> On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange  wrote:
>>
>>> Hello,
>>>
>>> I'm wondering if it would help if you changed from:
>>>
>>> optargs="consoleblank=0"
>>>
>>> to:
>>>
>>> optargs=consoleblank=0
>>>
>>> I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone
>>> Debian Image 2014-09-04 running 3.14.17-ti-r17
>>>
>>>
>>>
>>> On Sun, Sep 7, 2014 at 6:37 PM, William Hermans 
>>> wrote:
>>>
>>>> @Robert
>>>>
>>>> I'll have you know that you've broken $optargs in the initial stage
>>>> uEnv.txt.
>>>>
>>>> In case you did not know already . . .
>>>>
>>>> On Sun, Sep 7, 2014 at 6:32 PM, William Hermans 
>>>> wrote:
>>>>
>>>>> hmm so actual that did not work for me either, which I do not know is
>>>>> a bug or what so here is what I had to do.
>>>>>
>>>>> First check output of:
>>>>>
>>>>> *$ cat /sys/module/kernel/parameters/consoleblank*
>>>>> *600*
>>>>>
>>>>> It'll probably be 600 as above, which is ten minutes( 600 seconds ).
>>>>>
>>>>> So . . .
>>>>>
>>>>> *nano /boot/uEnv.txt*
>>>>> and uncomment this line:
>>>>> *#cmdline=quiet init=/lib/systemd/systemd*
>>>>> then add at the end  *consoleblank=0*
>>>>> Which gives you
>>>>>
>>>>>
>>>>> *cmdline=quiet init=/lib/systemd/systemd consoleblank=0*
>>>>> reboot the beaglebone and when it comes back up.
>>>>>
>>>>> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
>>>>>> *0*
>>>>>>
>>>>>
>>>>>
>>>>> On Sun, Sep 7, 2014 at 6:07 PM, William Hermans 
>>>>> wrote:
>>>>>
>>>>>> errr sorry, that should only be *setterm -blank 0*
>>>>>>>
>>>>>>
>>>>>> On Sun, Sep 7, 2014 at 6:03 PM, William Hermans 
>>>>>> wrote:
>>>>>>
>>>>>>> $ setterm -powersave off -blank 0
>>>>>>>
>>>>>>> On Sun, Sep 7, 2014 at 5:15 PM, 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-

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-07 Thread John Syn


From:  William Hermans 
Reply-To:  "beagleboard@googlegroups.com" 
Date:  Sunday, September 7, 2014 at 7:43 PM
To:  "beagleboard@googlegroups.com" 
Subject:  Re: [beagleboard] optargs in kernel 3.15.10-bone8

> Ok, so rather coming in and sniping a comment Jjohn, why dont you try and set
> an optargs env variable in the initial uEnv.txt file and see what happens.
> 
> If you're using the same uboot we're using, it wont work. Now, feel free to
> find yourself trolling a different post.
Wow, that was so unnecessary. I was just trying to be helpful.

Regards,
John
> 
> 
> On Sun, Sep 7, 2014 at 7:36 PM, John Syn  wrote:
>> 
>> From:  William Hermans 
>> Reply-To:  "beagleboard@googlegroups.com" 
>> Date:  Sunday, September 7, 2014 at 7:26 PM
>> To:  "beagleboard@googlegroups.com" 
>> Subject:  Re: [beagleboard] optargs in kernel 3.15.10-bone8
>> 
>>> optargs does not work in the latest uboot file setup. I've noticed this
>>> myself in othe situations. you have to use Robert new cmdline env variable
>> https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm
>> -uEnv.txt-bootz-n-fixes.patch
>> 
>> Looking at the u-boot patch it looks like optargs is used with both mmcargs
>> and nfsargs.
>> 
>> Regards,
>> John
>>> 
>>> 
>>> On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange  wrote:
>>>> Hello,
>>>> 
>>>> I'm wondering if it would help if you changed from:
>>>> 
>>>> optargs="consoleblank=0"
>>>> 
>>>> to:
>>>> 
>>>> optargs=consoleblank=0
>>>> 
>>>> I use optargs=spidev.bufsiz=16382 without a hitch on BeagleBone Debian
>>>> Image 2014-09-04 running 3.14.17-ti-r17
>>>> 
>>>> 
>>>> 
>>>> On Sun, Sep 7, 2014 at 6:37 PM, William Hermans  wrote:
>>>>> @Robert
>>>>> 
>>>>> I'll have you know that you've broken $optargs in the initial stage
>>>>> uEnv.txt.
>>>>> 
>>>>> In case you did not know already . . .
>>>>> 
>>>>> On Sun, Sep 7, 2014 at 6:32 PM, William Hermans  wrote:
>>>>>> hmm so actual that did not work for me either, which I do not know is a
>>>>>> bug or what so here is what I had to do.
>>>>>> 
>>>>>> First check output of:
>>>>>>> $ cat /sys/module/kernel/parameters/consoleblank
>>>>>>> 600
>>>>>> It'll probably be 600 as above, which is ten minutes( 600 seconds ).
>>>>>> 
>>>>>> So . . .
>>>>>> nano /boot/uEnv.txt
>>>>>> and uncomment this line:
>>>>>> #cmdline=quiet init=/lib/systemd/systemd
>>>>>> then add at the end  consoleblank=0
>>>>>> Which gives you
>>>>>> cmdline=quiet init=/lib/systemd/systemd consoleblank=0
>>>>>> 
>>>>>> reboot the beaglebone and when it comes back up.
>>>>>> 
>>>>>>> root@arm:~# cat /sys/module/kernel/parameters/consoleblank
>>>>>>> 0
>>>>>> 
>>>>>> 
>>>>>> On Sun, Sep 7, 2014 at 6:07 PM, William Hermans 
>>>>>> wrote:
>>>>>>> errr sorry, that should only be setterm -blank 0
>>>>>>> 
>>>>>>> On Sun, Sep 7, 2014 at 6:03 PM, William Hermans 
>>>>>>> wrote:
>>>>>>> $ setterm -powersave off -blank 0
>>>>>>> 
>>>>>>> On Sun, Sep 7, 2014 at 5:15 PM, 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
>>>&g

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-07 Thread Jason Lange

Hi again,

I just tried wrapping my optarg in quotes and it didn't make a lick of
difference, so that's not it.

It's seems that I should have the latest uboot since I'm running an image
from 3 days ago.
My optargs aren't broken.

On Sun, Sep 7, 2014 at 7:36 PM, John Syn  wrote:

>
> From: William Hermans 
> Reply-To: "beagleboard@googlegroups.com" 
> Date: Sunday, September 7, 2014 at 7:26 PM
> To: "beagleboard@googlegroups.com" 
> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>
> optargs does not work in the latest uboot file setup. I've noticed this
> myself in othe situations. you have to use Robert new cmdline env variable
>
>
> https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
>
> Looking at the u-boot patch it looks like optargs is used with both
> mmcargs and nfsargs.
>
> Regards,
> John
>
>
>
> On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange  wrote:
>
>> Hello,
>>
>> I'm wondering if it would help if you changed from:
>>
>> optargs="consoleblank=0"
>>
>> to:
>>
>> optargs=consoleblank=0
>>
>> I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone Debian
>> Image 2014-09-04 running 3.14.17-ti-r17
>>
>>
>>
>> On Sun, Sep 7, 2014 at 6:37 PM, William Hermans 
>> wrote:
>>
>>> @Robert
>>>
>>> I'll have you know that you've broken $optargs in the initial stage
>>> uEnv.txt.
>>>
>>> In case you did not know already . . .
>>>
>>> On Sun, Sep 7, 2014 at 6:32 PM, William Hermans 
>>> wrote:
>>>
>>>> hmm so actual that did not work for me either, which I do not know is a
>>>> bug or what so here is what I had to do.
>>>>
>>>> First check output of:
>>>>
>>>> *$ cat /sys/module/kernel/parameters/consoleblank*
>>>> *600*
>>>>
>>>> It'll probably be 600 as above, which is ten minutes( 600 seconds ).
>>>>
>>>> So . . .
>>>>
>>>> *nano /boot/uEnv.txt*
>>>> and uncomment this line:
>>>> *#cmdline=quiet init=/lib/systemd/systemd*
>>>> then add at the end  *consoleblank=0*
>>>> Which gives you
>>>>
>>>>
>>>> *cmdline=quiet init=/lib/systemd/systemd consoleblank=0*
>>>> reboot the beaglebone and when it comes back up.
>>>>
>>>> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
>>>>> *0*
>>>>>
>>>>
>>>>
>>>> On Sun, Sep 7, 2014 at 6:07 PM, William Hermans 
>>>> wrote:
>>>>
>>>>> errr sorry, that should only be *setterm -blank 0*
>>>>>>
>>>>>
>>>>> On Sun, Sep 7, 2014 at 6:03 PM, William Hermans 
>>>>> wrote:
>>>>>
>>>>>> $ setterm -powersave off -blank 0
>>>>>>
>>>>>> On Sun, Sep 7, 2014 at 5:15 PM, 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
>>>>>>

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-07 Thread William Hermans

Ok, so rather coming in and sniping a comment Jjohn, why dont you try and
set an optargs env variable in the initial uEnv.txt file and see what
happens.

If you're using the same uboot we're using, it wont work. Now, feel free to
find yourself trolling a different post.

On Sun, Sep 7, 2014 at 7:36 PM, John Syn  wrote:

>
> From: William Hermans 
> Reply-To: "beagleboard@googlegroups.com" 
> Date: Sunday, September 7, 2014 at 7:26 PM
> To: "beagleboard@googlegroups.com" 
> Subject: Re: [beagleboard] optargs in kernel 3.15.10-bone8
>
> optargs does not work in the latest uboot file setup. I've noticed this
> myself in othe situations. you have to use Robert new cmdline env variable
>
>
> https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
>
> Looking at the u-boot patch it looks like optargs is used with both
> mmcargs and nfsargs.
>
> Regards,
> John
>
>
>
> On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange  wrote:
>
>> Hello,
>>
>> I'm wondering if it would help if you changed from:
>>
>> optargs="consoleblank=0"
>>
>> to:
>>
>> optargs=consoleblank=0
>>
>> I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone Debian
>> Image 2014-09-04 running 3.14.17-ti-r17
>>
>>
>>
>> On Sun, Sep 7, 2014 at 6:37 PM, William Hermans 
>> wrote:
>>
>>> @Robert
>>>
>>> I'll have you know that you've broken $optargs in the initial stage
>>> uEnv.txt.
>>>
>>> In case you did not know already . . .
>>>
>>> On Sun, Sep 7, 2014 at 6:32 PM, William Hermans 
>>> wrote:
>>>
>>>> hmm so actual that did not work for me either, which I do not know is a
>>>> bug or what so here is what I had to do.
>>>>
>>>> First check output of:
>>>>
>>>> *$ cat /sys/module/kernel/parameters/consoleblank*
>>>> *600*
>>>>
>>>> It'll probably be 600 as above, which is ten minutes( 600 seconds ).
>>>>
>>>> So . . .
>>>>
>>>> *nano /boot/uEnv.txt*
>>>> and uncomment this line:
>>>> *#cmdline=quiet init=/lib/systemd/systemd*
>>>> then add at the end  *consoleblank=0*
>>>> Which gives you
>>>>
>>>>
>>>> *cmdline=quiet init=/lib/systemd/systemd consoleblank=0*
>>>> reboot the beaglebone and when it comes back up.
>>>>
>>>> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
>>>>> *0*
>>>>>
>>>>
>>>>
>>>> On Sun, Sep 7, 2014 at 6:07 PM, William Hermans 
>>>> wrote:
>>>>
>>>>> errr sorry, that should only be *setterm -blank 0*
>>>>>>
>>>>>
>>>>> On Sun, Sep 7, 2014 at 6:03 PM, William Hermans 
>>>>> wrote:
>>>>>
>>>>>> $ setterm -powersave off -blank 0
>>>>>>
>>>>>> On Sun, Sep 7, 2014 at 5:15 PM, 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://beagleboar

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-07 Thread John Syn


From:  William Hermans 
Reply-To:  "beagleboard@googlegroups.com" 
Date:  Sunday, September 7, 2014 at 7:26 PM
To:  "beagleboard@googlegroups.com" 
Subject:  Re: [beagleboard] optargs in kernel 3.15.10-bone8

> optargs does not work in the latest uboot file setup. I've noticed this myself
> in othe situations. you have to use Robert new cmdline env variable
https://github.com/eewiki/u-boot-patches/blob/master/v2014.07/0001-am335x_ev
m-uEnv.txt-bootz-n-fixes.patch

Looking at the u-boot patch it looks like optargs is used with both mmcargs
and nfsargs.

Regards,
John
> 
> 
> On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange  wrote:
>> Hello,
>> 
>> I'm wondering if it would help if you changed from:
>> 
>> optargs="consoleblank=0"
>> 
>> to:
>> 
>> optargs=consoleblank=0
>> 
>> I use optargs=spidev.bufsiz=16382 without a hitch on BeagleBone Debian Image
>> 2014-09-04 running 3.14.17-ti-r17
>> 
>> 
>> 
>> On Sun, Sep 7, 2014 at 6:37 PM, William Hermans  wrote:
>>> @Robert
>>> 
>>> I'll have you know that you've broken $optargs in the initial stage
>>> uEnv.txt.
>>> 
>>> In case you did not know already . . .
>>> 
>>> On Sun, Sep 7, 2014 at 6:32 PM, William Hermans  wrote:
>>>> hmm so actual that did not work for me either, which I do not know is a bug
>>>> or what so here is what I had to do.
>>>> 
>>>> First check output of:
>>>>> $ cat /sys/module/kernel/parameters/consoleblank
>>>>> 600
>>>> It'll probably be 600 as above, which is ten minutes( 600 seconds ).
>>>> 
>>>> So . . .
>>>> nano /boot/uEnv.txt
>>>> and uncomment this line:
>>>> #cmdline=quiet init=/lib/systemd/systemd
>>>> then add at the end  consoleblank=0
>>>> Which gives you
>>>> cmdline=quiet init=/lib/systemd/systemd consoleblank=0
>>>> 
>>>> reboot the beaglebone and when it comes back up.
>>>> 
>>>>> root@arm:~# cat /sys/module/kernel/parameters/consoleblank
>>>>> 0
>>>> 
>>>> 
>>>> On Sun, Sep 7, 2014 at 6:07 PM, William Hermans  wrote:
>>>>>> errr sorry, that should only be setterm -blank 0
>>>>> 
>>>>> On Sun, Sep 7, 2014 at 6:03 PM, William Hermans  wrote:
>>>>>> $ setterm -powersave off -blank 0
>>>>>> 
>>>>>> On Sun, Sep 7, 2014 at 5:15 PM, 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_pr
>>>>>>> event_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+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.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-07 Thread William Hermans

optargs does not work in the latest uboot file setup. I've noticed this
myself in othe situations. you have to use Robert new cmdline env variable

On Sun, Sep 7, 2014 at 7:19 PM, Jason Lange  wrote:

> Hello,
>
> I'm wondering if it would help if you changed from:
>
> optargs="consoleblank=0"
>
> to:
>
> optargs=consoleblank=0
>
> I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone Debian
> Image 2014-09-04 running 3.14.17-ti-r17
>
>
>
> On Sun, Sep 7, 2014 at 6:37 PM, William Hermans  wrote:
>
>> @Robert
>>
>> I'll have you know that you've broken $optargs in the initial stage
>> uEnv.txt.
>>
>> In case you did not know already . . .
>>
>> On Sun, Sep 7, 2014 at 6:32 PM, William Hermans 
>> wrote:
>>
>>> hmm so actual that did not work for me either, which I do not know is a
>>> bug or what so here is what I had to do.
>>>
>>> First check output of:
>>>
>>> *$ cat /sys/module/kernel/parameters/consoleblank*
>>> *600*
>>>
>>> It'll probably be 600 as above, which is ten minutes( 600 seconds ).
>>>
>>> So . . .
>>>
>>> *nano /boot/uEnv.txt*
>>> and uncomment this line:
>>> *#cmdline=quiet init=/lib/systemd/systemd*
>>> then add at the end  *consoleblank=0*
>>> Which gives you
>>>
>>>
>>> *cmdline=quiet init=/lib/systemd/systemd consoleblank=0*
>>> reboot the beaglebone and when it comes back up.
>>>
>>> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
 *0*

>>>
>>>
>>> On Sun, Sep 7, 2014 at 6:07 PM, William Hermans 
>>> wrote:
>>>
 errr sorry, that should only be *setterm -blank 0*
>

 On Sun, Sep 7, 2014 at 6:03 PM, William Hermans 
 wrote:

> $ setterm -powersave off -blank 0
>
> On Sun, Sep 7, 2014 at 5:15 PM, 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
>> 
>>  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+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.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-07 Thread Jason Lange

Hello,

I'm wondering if it would help if you changed from:

optargs="consoleblank=0"

to:

optargs=consoleblank=0

I use *optargs=spidev.bufsiz=16382 *without a hitch on BeagleBone Debian
Image 2014-09-04 running 3.14.17-ti-r17



On Sun, Sep 7, 2014 at 6:37 PM, William Hermans  wrote:

> @Robert
>
> I'll have you know that you've broken $optargs in the initial stage
> uEnv.txt.
>
> In case you did not know already . . .
>
> On Sun, Sep 7, 2014 at 6:32 PM, William Hermans  wrote:
>
>> hmm so actual that did not work for me either, which I do not know is a
>> bug or what so here is what I had to do.
>>
>> First check output of:
>>
>> *$ cat /sys/module/kernel/parameters/consoleblank*
>> *600*
>>
>> It'll probably be 600 as above, which is ten minutes( 600 seconds ).
>>
>> So . . .
>>
>> *nano /boot/uEnv.txt*
>> and uncomment this line:
>> *#cmdline=quiet init=/lib/systemd/systemd*
>> then add at the end  *consoleblank=0*
>> Which gives you
>>
>>
>> *cmdline=quiet init=/lib/systemd/systemd consoleblank=0*
>> reboot the beaglebone and when it comes back up.
>>
>> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
>>> *0*
>>>
>>
>>
>> On Sun, Sep 7, 2014 at 6:07 PM, William Hermans 
>> wrote:
>>
>>> errr sorry, that should only be *setterm -blank 0*

>>>
>>> On Sun, Sep 7, 2014 at 6:03 PM, William Hermans 
>>> wrote:
>>>
 $ setterm -powersave off -blank 0

 On Sun, Sep 7, 2014 at 5:15 PM, 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
> 
>  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+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.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-07 Thread William Hermans

@Robert

I'll have you know that you've broken $optargs in the initial stage
uEnv.txt.

In case you did not know already . . .

On Sun, Sep 7, 2014 at 6:32 PM, William Hermans  wrote:

> hmm so actual that did not work for me either, which I do not know is a
> bug or what so here is what I had to do.
>
> First check output of:
>
> *$ cat /sys/module/kernel/parameters/consoleblank*
> *600*
>
> It'll probably be 600 as above, which is ten minutes( 600 seconds ).
>
> So . . .
>
> *nano /boot/uEnv.txt*
> and uncomment this line:
> *#cmdline=quiet init=/lib/systemd/systemd*
> then add at the end  *consoleblank=0*
> Which gives you
>
>
> *cmdline=quiet init=/lib/systemd/systemd consoleblank=0*
> reboot the beaglebone and when it comes back up.
>
> *root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
>> *0*
>>
>
>
> On Sun, Sep 7, 2014 at 6:07 PM, William Hermans  wrote:
>
>> errr sorry, that should only be *setterm -blank 0*
>>>
>>
>> On Sun, Sep 7, 2014 at 6:03 PM, William Hermans 
>> wrote:
>>
>>> $ setterm -powersave off -blank 0
>>>
>>> On Sun, Sep 7, 2014 at 5:15 PM, 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
 
  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+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.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-07 Thread William Hermans

hmm so actual that did not work for me either, which I do not know is a bug
or what so here is what I had to do.

First check output of:

*$ cat /sys/module/kernel/parameters/consoleblank*
*600*

It'll probably be 600 as above, which is ten minutes( 600 seconds ).

So . . .

*nano /boot/uEnv.txt*
and uncomment this line:
*#cmdline=quiet init=/lib/systemd/systemd*
then add at the end  *consoleblank=0*
Which gives you


*cmdline=quiet init=/lib/systemd/systemd consoleblank=0*
reboot the beaglebone and when it comes back up.

*root@arm:~# cat /sys/module/kernel/parameters/consoleblank*
> *0*
>


On Sun, Sep 7, 2014 at 6:07 PM, William Hermans  wrote:

> errr sorry, that should only be *setterm -blank 0*
>>
>
> On Sun, Sep 7, 2014 at 6:03 PM, William Hermans  wrote:
>
>> $ setterm -powersave off -blank 0
>>
>> On Sun, Sep 7, 2014 at 5:15 PM, 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
>>> 
>>>  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+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.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-07 Thread William Hermans

>
> errr sorry, that should only be *setterm -blank 0*
>

On Sun, Sep 7, 2014 at 6:03 PM, William Hermans  wrote:

> $ setterm -powersave off -blank 0
>
> On Sun, Sep 7, 2014 at 5:15 PM, 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
>> 
>>  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+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.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

2014-09-07 Thread William Hermans

$ setterm -powersave off -blank 0

On Sun, Sep 7, 2014 at 5:15 PM, 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
> 
>  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+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.

39 matches

Mail list logo