On Tue, Mar 29, 2011 at 3:08 AM, Jason Kridner <
jkri...@beagleboard.org> wrote:
> On Monday, March 28, 2011 4:21:08 PM UTC-4, Jason Kridner wrote:
>>
>> Gerald,
>>
>> I understand you are having an issue with the screen going blank and are
>> looking for a way to configure the kernel to keep the display. I believe
>> you can try adding this line to uEnv.txt:
>>
>> optargs="consoleblank=0"
>
> My uEnv.txt looks like:
> dvimode=hd720
> console="ttyS2,115200n8 console=tty0"
> optargs="consoleblank=0"
>
> I've let it sit for a while and the screen hasn't gone blank on me, but I
> can't confirm it won't yet. What I can confirm is that the quotes above
> seem to be working. The resulting kernel command line I get is:
>
> root@beagleboard:~# cat /proc/cmdline
> console=ttyS2,115200n8 console=tty0 consoleblank=0 mpurate=auto buddy=none
> camera=lbcm3m1 vram=12M omapfb.mode=dvi:hd720 omapdss.def_disp=dvi
> root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
>
> Having the "console=tty0" helps quite a bit by showing the boot activity.
> Clearly you want the "ttyS2,115200n8" as the new u-boot will now default to
> "ttyO2,115200n8" and the 2.6.32 kernel won't spit anything out there. I
> think shipping with a uEnv.txt that sets things to hd720 probably makes
> sense as connecting to an HDTV is probably one of the easiest options for a
> display. I don't have an opinion on the consoleblank.
>