From: Jason Dagit <dagit-LP0vGzdgvNwj5TC/SZClsA@public.gmane.org>
To: nicdev05 nic <nicdev05-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Driver Testing
Date: Wed, 16 Mar 2005 22:27:20 -0800 [thread overview]
Message-ID: <87br9iwzw7.fsf@www.codersbase.com> (raw)
In-Reply-To: <20050317024304.95595.qmail-oqthl4G0bEevuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org> (nicdev05-/E1597aS9LQAvxtiuMwx3w@public.gmane.org's message of "Wed, 16 Mar 2005 18:43:04 -0800 (PST)")
nicdev05 nic <nicdev05-/E1597aS9LQAvxtiuMwx3w@public.gmane.org> writes:
> So, any idea as what the resume command should be? I
> a Fedora Core-2 system.
Unfortunately I don't have the answer to this questions, but perhaps
others on the list do. I'm a debian zealot (okay, perhaps satisfied
user is more accurate :) and I'm not (yet) very versed in the ways of
acpi.
> Outside of resume, the suspend process works fine
> (by writing to /sys/power/state). If I press the power
> button the system seems to resume but then follows
> with a reboot...
If you reboot on resume you may be experiencing this bug:
http://bugme.osdl.org/show_bug.cgi?id=3691
Does that sound like your problem? I'm anxiously awaiting advice from
others on this list about how to solve that bug. I have a laptop
which I currently use swsuspend2 on, but would much, much rather
suspend to ram, at least most of the time.
Jason
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-03-17 6:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 2:43 Driver Testing nicdev05 nic
[not found] ` <20050317024304.95595.qmail-oqthl4G0bEevuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2005-03-17 6:27 ` Jason Dagit [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-18 17:57 nicdev05 nic
[not found] ` <20050318175743.66629.qmail-0gFffodynuCvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2005-03-18 18:55 ` Jason Dagit
2005-03-17 1:21 nicdev05 nic
[not found] ` <20050317012151.36290.qmail-0gFffodynuCvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2005-03-17 1:45 ` Jason Dagit, Jason Dagit
2005-03-17 13:02 ` Matthew Garrett
2005-03-24 10:29 ` 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=87br9iwzw7.fsf@www.codersbase.com \
--to=dagit-lp0vgzdgvnwj5tc/szclsa@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=nicdev05-/E1597aS9LQAvxtiuMwx3w@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.