On Sat, 2007-04-14 at 02:38 +0200, Adrian Bunk wrote:
quoted text
> This email lists some known regressions in Linus' tree compared to 2.6.20.
> 
> If you find your name in the Cc header, you are either submitter of one
> of the bugs, maintainer of an affectected subsystem or driver, a patch
> of you caused a breakage or I'm considering you in any other way
> possibly involved with one or more of these issues.
> 
> Due to the huge amount of recipients, please trim the Cc when answering.
> 
> 
> Subject    : resume from RAM corrupts vesafb console
> References : http://lkml.org/lkml/2007/3/26/76
> Submitter  : Marcus Better <marcus@better.se>
> Handled-By : Pavel Machek <pavel@ucw.cz>
> Status     : problem is being debugged
> 
> 
Hi Marcus,

A screen with blinking green blocks implies that your display is in text
mode, not in graphics mode.  I don't know what options you are using,
but have you tried using:

acpi_sleep=s3_mode

If the above does not work, also try

acpi_sleep=s3_bios,s3_mode

If it is still not working, you can add this to your suspend script:

vbetool vbemode set <VESA mode ID>

where VESA mode ID = "vga=" value - 512 (0x200)

Tony

PS: If your BIOS setup has an option to re-POST the graphics card on
resume, that is a big help.

Tony


-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/