public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Dösinger" <stefandoesinger-RbZlAiThDcE@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Questions about vbestate
Date: Wed, 19 Jan 2005 11:18:18 +0100	[thread overview]
Message-ID: <200501191118.19164.stefandoesinger@gmx.at> (raw)
In-Reply-To: <1106096142.7368.32.camel@tyrosine>

Am Mittwoch, 19. Januar 2005 01:55 schrieb Matthew Garrett:
> On Tue, 2005-01-18 at 19:12 +0100, Stefan Dösinger wrote:
> > *If I save the card's state with vbesate before calling the post-routine
> > and restoring the state afterwards makes switching back to X work again.
>
> I'd recommend saving the vbe state on boot, and not on every suspend.
> I'm not sure why, but there certainly seems to be some amount of
> information that's lost otherwise. Saving on suspend seems to make a
> large amount of hardware unhappy - I've only found one machine that
> complains about it on boot.
I tried this and it didn't work. I've also found out why. It's because the dri 
part of fglrx crashes after resume.

fglrx and suspend works fine if I disable DRI in xorg.conf. With dri enabled 
I've found no way to resume a started X session :-(

I suppose that vbestate doesn't touch the radeon specific settings set by 
fglrx and fglrx doesn't restore them carefully enought. If I start a secound 
X server after S3 I can't revive the original session too because the 2nd 
server doesn't initialize dri.

I've written a bug report to ATI yesterday and I'm waiting for a reply.

Stefan


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

  reply	other threads:[~2005-01-19 10:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-18 18:12 Questions about vbestate Stefan Dösinger
     [not found] ` <200501181912.19644.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2005-01-19  0:55   ` Matthew Garrett
2005-01-19 10:18     ` Stefan Dösinger [this message]
2005-01-22 11:05     ` Stefan Dösinger
     [not found]       ` <200501221205.40179.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2005-01-22 13:10         ` Matthew Garrett
2005-01-22 15:11           ` Stefan Dösinger

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=200501191118.19164.stefandoesinger@gmx.at \
    --to=stefandoesinger-rbzlaithdce@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /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