I had a look at uswsusp suspend command (called from within initrd) and saw that it do interact with the framebuffer and makes some splash-related initialization. Would'nt that be messing up with splashy? Shouldn't its code get reviewed? Or you are sure the issue is splashy related only?
---- Fabio Pugliese Ornellas E-Mail: [EMAIL PROTECTED] gTalk: [EMAIL PROTECTED] ICQ: 6516089 MSN: [EMAIL PROTECTED] WWW: http://ornellas.apanela.com/ On Fri, Aug 1, 2008 at 10:46, Luis Mondesi <[EMAIL PROTECTED]> wrote: > > On Aug 1, 2008, at 12:47 AM, "Fabio Pugliese Ornellas" < > [EMAIL PROTECTED]> wrote: > > Hello, >> >> I have just tested the newer 0.3.11 version asn my Asus EEE PC 900 still >> "freezes" if I use uswsusp + splashy, the bug still exists. >> >> If I find time on the following days, I'll post here my findings on the >> topic. >> >> > Yeah we are working on a quick release of 0.3.12 to address this and other > pesky bugs. > Sit tight. > So far it looks like removing chvt 8 from initramfs and Splashy fixes a few > of this issues. Exiting when $resume is set proved not to be the right > solution. >
