public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: ezra peisach <epeisach-AW32GngNFaTp5eoAjl1PXg@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: DELL inspiron 8200 fails to restore console after S1/S3
Date: Tue, 6 Jan 2004 16:10:43 -0500 (EST)	[thread overview]
Message-ID: <200401062110.QAA188725@med-xtal.bu.edu> (raw)


Testing w/ the 2.6.0 kernel and the 12/03 patches to acpi, the following
happens w/ the stock DSDT A10 on an inspiron 8200:

The display is a radeon 9000....

The following occurs if X is not running. (init run level 3)

If one moves to power state: S1 - the screen does not go blank (text
remains) When power is restored, the machine accepts keyboard input,
but the screen then goes blank.

If one move to power state S3 - screen goes blank. Power restoration
flashes the screen then remains blank.

When X is running - sometimes the screen is restored, sometimes
not. I.e. sometimes it comes out w/ garbage.

Based on the bugzilla.kernel.org - bug 605 - discusses backlight not
going off.  There is a comment that ACPI may not be responsible for
this - the gfx driver is.

When X is not running - there isn't a gfx driver - except the kernel.
Do we need an OS specific handler to receive notifications of 

\_SB.PCI0.AGP.VID

and do the right thing?

Perhaps the agp driver is the proper place.... I suspect it may be a radeon 
specific thing...

For the X case - maybe it needs to observe the acpi events - not just apm.

Anyone have any ideas?

Ezra



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click

             reply	other threads:[~2004-01-06 21:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-06 21:10 ezra peisach [this message]
     [not found] ` <200401062110.QAA188725-AW32GngNFaTp5eoAjl1PXg@public.gmane.org>
2004-01-18  8:37   ` DELL inspiron 8200 fails to restore console after S1/S3 Luca Capello
  -- strict thread matches above, loose matches on Subject: below --
2004-01-12  6:48 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720CB2-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-12 13:22   ` ezra peisach
2004-01-13 16:24   ` Brian Perkins
2004-01-18  2:45 Yu, Luming

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=200401062110.QAA188725@med-xtal.bu.edu \
    --to=epeisach-aw32gngnfatp5eoajl1pxg@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