public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Gertjan Hofman <gertjan-nuBT7F/NYkeO3qShyYWIeA@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: No S3/S4 response on Toshiba A70 (FC3)
Date: Fri, 11 Feb 2005 12:29:09 +0100	[thread overview]
Message-ID: <20050211112909.GA1976@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.33.0502102209230.27152-100000-nuBT7F/NYkeO3qShyYWIeA@public.gmane.org>

Hi!

> Thanks for the response and pointing me to the doc file. I quickly tried
> the standard FC3 non-smp kernel and now S3 goes into suspend but never
> comes back. Not huge surprise. Using a vanilla kernel is a project for the
> weekend. Three questions comes to mind - you point me to the swsusp.txt -
> is this implying S3 will never work ? Secondly, your video.txt doc makes
> it sound like very few video cards can recover from S3. Is this still true
> ?  Lastly, why is a vanilla kernel better than FC3 kernels ? Feel free to
> point me to more documentation.

1) S3 is more tricky than swsusp.

2) actually the list is not so short, but tricks are different for
each card.

3) I do not know about fedora kernel. If you want support on
mainstream mailing lists, you should better use vanilla kernels.

								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

      parent reply	other threads:[~2005-02-11 11:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-10  5:41 No S3/S4 response on Toshiba A70 (FC3) Gertjan Hofman
     [not found] ` <Pine.LNX.4.33.0502092114410.8615-100000-nuBT7F/NYkeO3qShyYWIeA@public.gmane.org>
2005-02-10 18:17   ` Pavel Machek
     [not found]     ` <20050210181723.GA1577-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-02-11  6:14       ` Gertjan Hofman
     [not found]         ` <Pine.LNX.4.33.0502102209230.27152-100000-nuBT7F/NYkeO3qShyYWIeA@public.gmane.org>
2005-02-11 11:29           ` Pavel Machek [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=20050211112909.GA1976@elf.ucw.cz \
    --to=pavel-+zi9xunit7i@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=gertjan-nuBT7F/NYkeO3qShyYWIeA@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