On Tue, Apr 8, 2008 at 2:39 PM, Soeren Sonnenburg <kernel@nn7.de> wrote:
quoted text
> On Tue, 2008-04-08 at 14:35 +0200, Romano Giannetti wrote:
>  >
>  > On Tue, 2008-04-08 at 10:58 +0200, Tino Keitel wrote:
>  > > With 2.6.25-rc, the text console is fine after resume, due to the
>  > > recent changes to the Intel i915 DRM driver. Maybe those people who
>  > > used to use vbetool prior to 2.6.25 should check if this is still
>  > > needed.
>  >
>  > Yep, the problem is just that: in 2.6.24 vbetool hacks (in my case,
>  > using s2ram -p -m options) was needed to resume graphics. Now they are
>  > not needed anymore, and using them _break_ resume.
>  >
>  > So, people with a working suspend-to-ram setup (even using the whitelist
>  > in s2ram, I mean, simply calling s2ram) will discover that 2.6.25 break
>  > their machine. Removing the s2ram package and suspending with
>  > kernel-only machinery will work, but... well, it's not user-friendly.
>
>  The above holds only if you have an intel graphics adapter. For me
>  (radeon) it really breaks (as in echo mem >/sys/power/state leaves me a
>  black screen on resume and manually typing vbetool post or vbetool
>  vgamode simply hangs the machine).
>

For me (radeon X700) using binary fglrx xorg driver without the binary
kernel module (which does not compile under .25rc for me)
resume-from-ram works using s2ram.

Lightly tested with -rc8.

My laptop is in whitelist as VBE_POST|VBE_SAVE|NOFB .

quoted text
>  Soeren

Fabio
--
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/