You are just talking about your logo disappearing (usually tux)? It has been this way for years if not forever on all Linux systems.
A long while back in 2.4 this bothered me enough that I did fix it in a MV kernel. This is in effect of the console layer not saving its logo settings. It is not all that hard to fix. For a development system having the logo is kind of a nice thing even an advertising tool. However, probably no one ships a system with it on. You might send a patch in to console people to fix it. When I sent a patch to MV long back it was discarded. I didn't send it to the proper maintainer which could have stuck then. Regards, Richard W. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:linux-omap- > [EMAIL PROTECTED] On Behalf Of arun c > Sent: Monday, May 19, 2008 1:49 AM > To: [email protected] > Subject: Power management behavior of linux-2.6.14-omap2-v5 > > Hi all, > > I am using linux-2.6.14-omap2-v5 to test PM on 2430SDP. > > I did > > a) cat myimg > /dev/fb0 > I can see "myimg" displayed on the lcd > > b) cat /dev/fb0 > myimg_before_sleep > > c) echo "mem" > /sys/power/state > Board goes to sleep state. > > d) After a key press the board awakes and lcd > becomes blue "myimg" is disappeared from > the screen. > > e) cat /dev/fb0 > myimg_after_wakeup > > The two binary files "myimg_before_sleep" and > "myimg_after_wakeup" differs each other. > > Can somebody explain me why such a behavior? > Why the lcd fails to display the same image > before and after sleeping? > > Regards, > Arun C > -- > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
