From: Pierre Ossman <pierre-list@ossman.eu>
To: linux-pm@lists.linux-foundation.org
Subject: Re: Resume hanging on MSI motherboard
Date: Fri, 23 Jul 2010 12:40:23 +0200 [thread overview]
Message-ID: <20100723124023.75e53814@mjolnir.ossman.eu> (raw)
In-Reply-To: <200912082343.30195.rjw@sisk.pl>
[-- Attachment #1.1: Type: text/plain, Size: 1619 bytes --]
I decided to resume (hah) this old project and this time I actually
made some immediate progress.
The issue used to be that the machine failed to resume properly,
hanging somewhere during the startup process. In Windows, it suspended
and resumes properly, but left most of the machine running.
The above is now solved. I found "ACPI Suspend mode" in the BIOS, which
had a large effect on the behaviour. It was previously set to S1 (which
I guess was what Windows successfully ended up in, hence the high power
usage). Setting it to S3 makes Windows work perfectly (suspend wise at
least). Linux works a lot better, but has two issues remaining:
1. Graphics gets screwed up with v2.6.34-rc5-10802-g733029f. Works fine
with 2.6.33.5-112.fc13.x86_64 though. Should probably test latest
tree...
2. Machine fails to wake properly using the IR remote. This works fine
in Windows, but not in Linux. As this is a HTPC, this is pretty crucial
for everything to come together. :/
The IR receiver itself seems to be put in somewhat proper mode as it
lights up when the machine is suspended and it gets the power signal
from the remote. The machine doesn't react though. It does wake up on
activity from the USB connected keyboard, so triggering resume from USB
seems to be working.
Any ideas on things to mess with when it comes to USB triggered resume?
Rgds
--
-- Pierre Ossman
WARNING: This correspondence is being monitored by FRA, a
Swedish intelligence agency. Make sure your server uses
encryption for SMTP traffic and consider using PGP for
end-to-end encryption.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 230 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2010-07-23 10:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 7:17 Resume hanging on MSI motherboard Pierre Ossman
2009-12-08 8:03 ` Pierre Ossman
2009-12-08 12:38 ` Rafael J. Wysocki
2009-12-08 22:35 ` Pierre Ossman
2009-12-08 22:43 ` Rafael J. Wysocki
2010-07-23 10:40 ` Pierre Ossman [this message]
2010-07-23 11:58 ` Pierre Ossman
2009-12-27 10:20 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2009-12-03 20:46 Pierre Ossman
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=20100723124023.75e53814@mjolnir.ossman.eu \
--to=pierre-list@ossman.eu \
--cc=linux-pm@lists.linux-foundation.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