From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Pavel Machek <pavel@suse.cz>
Cc: Luca <kronos@kronoz.cjb.net>, linux-kernel@vger.kernel.org
Subject: Re: Suspend to RAM: help with whitelist wanted
Date: Sun, 29 Jan 2006 07:12:39 +0000 [thread overview]
Message-ID: <20060129071239.GB23736@srcf.ucam.org> (raw)
In-Reply-To: <20060128084225.GC1605@elf.ucw.cz>
On Sat, Jan 28, 2006 at 09:42:25AM +0100, Pavel Machek wrote:
> Well, doing it at boot is slightly ugly; I'd like s2ram to just work,
> and not need boot-time-hooks. [If there's no other solution... what
> can I do, but I do not like it.]
Indeed. The symptoms are that X stops drawing the background to windows,
and it seems to be very strongly tied to saving the state while X is
running (even if X is not currently the foreground VT).
> Thanks for pointer! Anyway, AFAICT the list is not really adequate. It
> lists working machines, but does not really list all the switches
> neccessary to get the video working. (Well, it tries in some cases,
> *strange*, perhaps less switches are neccessary than I think?)
For machines where nothing is listed, we do POSTing and restore the VBE
state. These may not be necessary in all cases, but they don't seem to
be actively harmful except on the machines where they're explicitly
switched of.f
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2006-01-29 7:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 21:36 Suspend to RAM: help with whitelist wanted Pavel Machek
2006-01-27 17:04 ` Luca
2006-01-27 23:05 ` Pavel Machek
2006-01-28 1:05 ` Olivier Galibert
2006-01-28 8:12 ` Pavel Machek
2006-01-27 23:22 ` Pavel Machek
2006-01-28 1:31 ` Matthew Garrett
2006-01-28 8:42 ` Pavel Machek
2006-01-29 7:12 ` Matthew Garrett [this message]
2006-02-04 21:11 ` Pavel Machek
2006-01-28 15:58 ` Luca
2006-01-28 16:04 ` Jan De Luyck
2006-01-28 17:11 ` Luca
2006-01-28 16:27 ` Pavel Machek
2006-01-28 16:36 ` Pavel Machek
2006-01-29 14:42 ` Luca
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060129071239.GB23736@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=kronos@kronoz.cjb.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).