From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005-hi6Y0CQ0nG0@public.gmane.org>
To: Jan Kasprzak <kas-0hYGf3jDe+XrBKCeMvbIDA@public.gmane.org>
Cc: acpi-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: S3 on Asus M6R
Date: Mon, 21 Mar 2005 17:29:20 +0100 [thread overview]
Message-ID: <423EF660.7010906@gmx.net> (raw)
In-Reply-To: <20050321135401.GC30293-0hYGf3jDe+XrBKCeMvbIDA@public.gmane.org>
[forgot the CC:]
Jan Kasprzak schrieb:
> Hi all,
>
> I have an Asus M6R laptop (http://www.fi.muni.cz/~kas/m6r/).
> I have tried to use ACPI S3 suspend-to-ram, but it does not work for me:
>
> - usually the system either immediately resumes and locks up
> after "echo 3 > /proc/acpi/sleep", or it or powers itself down
> and does a cold boot when I push the power button. I have found
> that the lm_sensors package is what causes the problem (altough
> I have no idea why).
>
> - without lm_sensors enabled (chkconfig lm_sensors off), I can suspend
> my system (the power LED starts blinking, which means the system
> is suspended to RAM). But I cannot resume it back - after hitting
> the power button the LEDs are on as when the laptop is normally
> running, but I get no output on the display, no response to ping, no
> response to CapsLock key, etc.
>
> I have read Documentation/power/video.txt, but neither using
> vbetool or boot-radeon utility make any difference for me.
>
> I have tried to use bash -x s3.sh >s3.log 2>s3.err, where s3.sh
> is as follows:
>
> #!/bin/bash
> chvt 1
> rmmod ohci-hcd
> rmmod ehci-hcd
> sync
> echo 3 > /proc/acpi/sleep
> sync
> /tmp/boot-radeon
> chvt 7
Can we see your kernel command line? Do you use any framebuffer? Does
it work if you boot with init=/bin/bash?
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
-------------------------------------------------------
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-21 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 13:54 S3 on Asus M6R Jan Kasprzak
[not found] ` <20050321135401.GC30293-0hYGf3jDe+XrBKCeMvbIDA@public.gmane.org>
2005-03-21 16:29 ` Carl-Daniel Hailfinger [this message]
[not found] ` <423EF660.7010906-hi6Y0CQ0nG0@public.gmane.org>
2005-03-21 17:03 ` Jan Kasprzak
[not found] ` <20050321170340.GK30293-0hYGf3jDe+XrBKCeMvbIDA@public.gmane.org>
2005-03-21 17:34 ` Carl-Daniel Hailfinger
[not found] ` <423F05A9.6050309-hi6Y0CQ0nG0@public.gmane.org>
2005-03-21 17:39 ` Jan Kasprzak
[not found] ` <20050321173912.GN30293-0hYGf3jDe+XrBKCeMvbIDA@public.gmane.org>
2005-03-21 19:56 ` Stefan Dösinger
[not found] ` <200503212056.20589.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2005-03-21 21:02 ` Jan Kasprzak
[not found] ` <20050321210217.GF14356-0hYGf3jDe+XrBKCeMvbIDA@public.gmane.org>
2005-03-21 21:56 ` Stefan Dösinger
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=423EF660.7010906@gmx.net \
--to=c-d.hailfinger.devel.2005-hi6y0cq0ng0@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=kas-0hYGf3jDe+XrBKCeMvbIDA@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