public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Dösinger" <stefandoesinger-RbZlAiThDcE@public.gmane.org>
To: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Luca Capello <luca-wlebWZzHoyE@public.gmane.org>,
	Giridhar Pemmasani
	<giri-IxWJ8JVbGpr5NRxSJurNR4dd74u8MsAO@public.gmane.org>
Subject: Re: Resume from suspend-to-ram (radeon)
Date: Fri, 23 Apr 2004 12:08:36 +0000	[thread overview]
Message-ID: <200404231208.36032.stefandoesinger@gmx.at> (raw)
In-Reply-To: <20040420101720.GA2314-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>

Hi,

> > The radeonfb resume does not crash, but when fbcon is loaded something
> > fails. Compile radeonfb(original version, 2.6.4 kernel) and frame buffer
> > console as modules, disable video mode selection support and load only
> > radeonfb(NOT fbcon) and the system will resume with backlight on and a
> > black screen. At least my device does in single user mode.
> >
> > I use plain text console and X with int10 POST patch. This gives me the
> > console back when resuming(X has to soft-boot the V-Bios).
>
> Perhaps some hints how to do this should be added to
> Documentation/power/video.txt?
>
> 									Pavel
Patching X11 or that radeonfb crashes on resume?
I wrote a howto about S3 on the Acer TM 800 which covers the radeon problem:
http://www.doesi.gmxhome.de/linux/tm800s3/s3.html

/Stefan


-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297

      parent reply	other threads:[~2004-04-23 12:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-20 20:46 Resume from suspend-to-ram Giridhar Pemmasani
2004-02-23  7:00 ` Resume from suspend-to-ram (radeon) Len Brown
     [not found]   ` <1077519609.12675.63.camel-D2Zvc0uNKG8@public.gmane.org>
2004-02-23  7:42     ` Giridhar Pemmasani
     [not found]       ` <20040223074227.80AE57831D-Yo/1PYb2HdawRS80dfYGFoIJIQD0bWaD@public.gmane.org>
2004-03-31 12:44         ` Luca Capello
     [not found]           ` <406ABD4A.10408-wlebWZzHoyE@public.gmane.org>
2004-04-01  1:10             ` Nigel Cunningham
     [not found]               ` <1080781821.3066.5.camel-632l8fqo88ezhJTzJkPP2xCuuivNXqWP@public.gmane.org>
2004-04-01  4:04                 ` Giridhar Pemmasani
     [not found]                   ` <20040401040507.0AAC477A2B-Yo/1PYb2HdawRS80dfYGFoIJIQD0bWaD@public.gmane.org>
2004-04-01  6:03                     ` Nigel Cunningham
2004-04-02 15:24             ` Stefan Dösinger
     [not found]               ` <200404021524.46611.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2004-04-20 10:17                 ` Pavel Machek
     [not found]                   ` <20040420101720.GA2314-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-04-23 12:08                     ` Stefan Dösinger [this message]

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=200404231208.36032.stefandoesinger@gmx.at \
    --to=stefandoesinger-rbzlaithdce@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=giri-IxWJ8JVbGpr5NRxSJurNR4dd74u8MsAO@public.gmane.org \
    --cc=luca-wlebWZzHoyE@public.gmane.org \
    --cc=pavel-+ZI9xUNit7I@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