All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: Ilya Bagrak <reason-ss4n/k5RZhaUArH+D2fLrA@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: radeon display is blank after resume from S3
Date: Sun, 22 Feb 2004 02:38:31 +0100	[thread overview]
Message-ID: <20040222013831.GA29988@hell.org.pl> (raw)
In-Reply-To: <34137.68.19.7.134.1077396635.squirrel-2RFepEojUI2yzif+TlFmFpQCsf4PZ8us@public.gmane.org>

Thus wrote Ilya Bagrak:
> Linux 2.6.3-mm2 on Fujitsu E7110 laptop w/
> 1. radeon mobility 7500 card
> 2. intel 845 pci bridge (i think)

ASUS L3800C, rest pretty much the same.

> The basic problem is that after resuming from S3, the screen remains
> completely blank.  All other devices seem to return to normal, and I can
> communicate with the laptop over the network.  I have experienced this
> same problem since early 2.6.0 test kernels, and I've been actively
> looking for a solution ever since.

In my case, acpi_sleep=s3_bios is enough. If that doesn't work, you may try
the new radeonfb driver from 2.6.3 -- on my box it *at least* manages to
get the backlight on without having to pass acpi_sleep, but then it screws
up some other things so the laptop gets locked anyway.
Best regards,

-- 
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

      parent reply	other threads:[~2004-02-22  1:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-21 20:50 radeon display is blank after resume from S3 Ilya Bagrak
     [not found] ` <34137.68.19.7.134.1077396635.squirrel-2RFepEojUI2yzif+TlFmFpQCsf4PZ8us@public.gmane.org>
2004-02-22  1:38   ` Karol Kozimor [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=20040222013831.GA29988@hell.org.pl \
    --to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=reason-ss4n/k5RZhaUArH+D2fLrA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.