public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Lukas <christoph.lukas-hi6Y0CQ0nG0@public.gmane.org>
To: "Rockefeller, Harry" <harryr-qMhjF6E6u3VBDgjK7y7TUQ@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI S3 wake howto was: RE: [BKPATCH] ACPI for 2.6
Date: Wed, 31 Mar 2004 08:02:14 +0200	[thread overview]
Message-ID: <1080712934.8580.31.camel@beja> (raw)
In-Reply-To: <7105F2BD9451D7479B4B3A99A2B72FAC062C08C7-Lp/cVzEoVyYIbgCsDWxlK60bRtRcJeJQ@public.gmane.org>

Am Die, den 30.03.2004 schrieb Rockefeller, Harry um 19:33:
> As a user, I'm stuck at first base.  With kernel 2.6.4
> S3 is supposedly supported.  Entering S3 appears to work.
> Exiting S3 (waking up?) the LCD screen comes back when a key is
> depressed, but *nothing* brings my machine back to life.
> The full few-seconds power-button reboot is all that works.
> 
> I admit that there may be a simple one-line web-link answer
> pointing to some ACPI FAQ or How-to.  If that is the case 
> just point me there and I'll read that.

I spent several hours trying to set up S3 on my notebook. The problem
with S3 seems to be that the drivers have to take care for saving /
restoring PCI states and reinitializing hardware components.

The mayor problem for me was that the video card (Nvidia GForce) had to
be reinitialized. I solved that with using the original XFree nv driver
instead of the nvidia one and applying an XFree hack from:

http://www.loria.fr/~thome/d600/

This made S3 working for me from within X. On the same page you can find
a patch for the ATI Radeon M9.

The second problem was that some drivers had to be unloaded before
suspend and reloaded after resume (usb).

The third problem was that I did not get alsa to work after resume. A
similar problem is described here:

http://sourceforge.net/mailarchive/message.php?msg_id=7591163

Using those hints I wrote a small _shell_ script to save the PCI config
space of my alsa and network driver before suspend and to restore it
after resume.

That finally made S3 working for me. :-)

As a recipe I would suggest:
- Start with mostly all drivers unloaded
- Always umount all unnecessary partitions as it is likely that your
system will crash until you find the correct way to deal with your
drivers
- Boot your system with acpi_irq_balance acpi_irq_pci=3,4,5,..
- Get your video card working with S3
- Try one driver after another to deal with S3
- If it does not survive suspend / resume try:
-- unloading / reloading
-- keeping the driver loaded and saving / restoring PCI config space

As the alsa drivers were the worst ones to get working, I tried to
contact the alsa-devel list for some help, but there did not seem to be
any interest in getting S3 working with alsa. No responses so far. :-(

Regards,
Christoph



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

  parent reply	other threads:[~2004-03-31  6:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-30 17:33 ACPI S3 wake howto was: RE: [BKPATCH] ACPI for 2.6 Rockefeller, Harry
     [not found] ` <7105F2BD9451D7479B4B3A99A2B72FAC062C08C7-Lp/cVzEoVyYIbgCsDWxlK60bRtRcJeJQ@public.gmane.org>
2004-03-31  4:51   ` S3/S4 doesn't work, no-one cares, it's a mess " Huw Rogers
     [not found]     ` <20040330233155.463A.COUNT0-tC47gz4GrgtWk0Htik3J/w@public.gmane.org>
2004-03-31  4:58       ` Tomasz Ciolek
     [not found]         ` <20040331045844.GA28355-+XVqjN4+fIJfbCVcMT5z6Ydd74u8MsAO@public.gmane.org>
2004-03-31  5:00           ` Huw Rogers
2004-03-31  5:40       ` Michael Frank
     [not found]         ` <opr5poqe0z4evsfm-TBR8pM7LtsqkE96DxU8f+dAkNl5+tjhE@public.gmane.org>
2004-04-01  0:34           ` Micha Feigin
     [not found]             ` <20040401003403.GA9382-4cxDFgrrBECgSpxsJD1C4w@public.gmane.org>
2004-04-01  5:12               ` Michael Frank
2004-03-31  9:09       ` Cam
2004-03-31 10:58       ` Micha Feigin
     [not found]         ` <20040331105851.GA11223-i54C7/sJn21wdIlnA33utQ@public.gmane.org>
2004-03-31 12:30           ` Luca Capello
     [not found]             ` <406AB9DA.7020805-wlebWZzHoyE@public.gmane.org>
2004-04-01  0:38               ` Micha Feigin
     [not found]                 ` <20040401003823.GB9382-4cxDFgrrBECgSpxsJD1C4w@public.gmane.org>
2004-04-01 13:46                   ` Stefan Seyfried
2004-04-02 20:34           ` Pavel Machek
2004-03-31 11:26       ` Nils Faerber
     [not found]         ` <1080732363.4883.964.camel-bi+AKbBUZKZeoWH0uzbU5w@public.gmane.org>
2004-03-31 11:50           ` Eric Valette
2004-03-31 12:51           ` Andi Kleen
2004-04-02 20:37           ` Pavel Machek
2004-04-01  6:15       ` Nigel Cunningham
2004-04-02 20:40       ` Pavel Machek
2004-03-31  6:02   ` Christoph Lukas [this message]
2004-04-02 20:27   ` Pavel Machek

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=1080712934.8580.31.camel@beja \
    --to=christoph.lukas-hi6y0cq0ng0@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=harryr-qMhjF6E6u3VBDgjK7y7TUQ@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