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 <[email protected]> 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 <[email protected]> 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 <[email protected]> wrote: >> >>> try: >>> cat /proc/cmdline >>> >>> to see if optargs show there >>> >>> >>> >>> >>> On Sun, Sep 7, 2014 at 7:46 PM, John Syn <[email protected]> wrote: >>> >>>> >>>> From: William Hermans <[email protected]> >>>> Reply-To: "[email protected]" <[email protected]> >>>> Date: Sunday, September 7, 2014 at 7:43 PM >>>> To: "[email protected]" <[email protected]> >>>> 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 <[email protected]> wrote: >>>> >>>>> >>>>> From: William Hermans <[email protected]> >>>>> Reply-To: "[email protected]" <[email protected] >>>>> > >>>>> Date: Sunday, September 7, 2014 at 7:26 PM >>>>> To: "[email protected]" <[email protected]> >>>>> 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 <[email protected]> >>>>> 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 <[email protected]> >>>>>> 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 <[email protected]> >>>>>>> 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 <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> errr sorry, that should only be *setterm -blank 0* >>>>>>>>>> >>>>>>>>> >>>>>>>>> On Sun, Sep 7, 2014 at 6:03 PM, William Hermans <[email protected] >>>>>>>>> > wrote: >>>>>>>>> >>>>>>>>>> $ setterm -powersave off -blank 0 >>>>>>>>>> >>>>>>>>>> On Sun, Sep 7, 2014 at 5:15 PM, Moscowbob <[email protected]> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> BBB boot from tftp and nfs - >>>>>>>>>>> kernel: 3.15.10-bone8 >>>>>>>>>>> rootfs: debian-jessie-console-armhf-2014-08-13 >>>>>>>>>>> >>>>>>>>>>> Hardware: >>>>>>>>>>> BBB A5C >>>>>>>>>>> Circuitco LCD4 cape >>>>>>>>>>> Circuitco RS232 cape >>>>>>>>>>> >>>>>>>>>>> /home/rob/rootfs/boot/uEnv.txt >>>>>>>>>>> >>>>>>>>>>> uname_r=3.15.10-bone8 >>>>>>>>>>> cmdline=quiet init=/lib/systemd/systemd >>>>>>>>>>> *optargs="consoleblank=0"*. >>>>>>>>>>> >>>>>>>>>>> I used this reference >>>>>>>>>>> http://elinux.org/Beagleboard:BeagleBone_Black_FAQ >>>>>>>>>>> <http://elinux.org/Beagleboard:BeagleBone_Black_FAQ#Is_there_a_way_to_prevent_my_HDMI_monitor_from_sleeping_while_using_my_BBB.3F> >>>>>>>>>>> but >>>>>>>>>>> the display is still blanking after 10 minutes. >>>>>>>>>>> >>>>>>>>>>> Would appreciate some guidance. >>>>>>>>>>> >>>>>>>>>>> Thanks >>>>>>>>>>> Rob >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> For more options, visit http://beagleboard.org/discuss >>>>>>>>>>> --- >>>>>>>>>>> You received this message because you are subscribed to the >>>>>>>>>>> Google Groups "BeagleBoard" group. >>>>>>>>>>> To unsubscribe from this group and stop receiving emails from >>>>>>>>>>> it, send an email to [email protected]. >>>>>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> -- >>>>>>> For more options, visit http://beagleboard.org/discuss >>>>>>> --- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "BeagleBoard" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>> send an email to [email protected]. >>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>> >>>>>> >>>>>> -- >>>>>> For more options, visit http://beagleboard.org/discuss >>>>>> --- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "BeagleBoard" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to [email protected]. >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> >>>>> -- >>>>> For more options, visit http://beagleboard.org/discuss >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "BeagleBoard" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>>> -- >>>>> For more options, visit http://beagleboard.org/discuss >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "BeagleBoard" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >>>> For more options, visit http://beagleboard.org/discuss >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "BeagleBoard" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>>> -- >>>> For more options, visit http://beagleboard.org/discuss >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "BeagleBoard" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "BeagleBoard" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
