From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 16140] [RADEON:KMS:RV250:RESUME] suspend to RAM resume broken
Date: Thu, 9 Feb 2012 04:08:56 GMT [thread overview]
Message-ID: <201202090408.q1948uqg020808@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-16140-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=16140
soren121 <doodle62@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |doodle62@gmail.com
--- Comment #45 from soren121 <doodle62@gmail.com> 2012-02-09 04:08:53 ---
No fix in sight, but there is a workaround: set a primary password in the BIOS.
The BIOS will initialize the video card on wake-up and allow Linux to resume
normally. Inconvenient? Yes, but it's better than bottlenecking your already
out-of-date graphics card. I posted this workaround on the Canonical Launchpad
bug report some time ago; I guess it hasn't been shared outside as of yet.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2012-02-09 4:08 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-16140-2300@https.bugzilla.kernel.org/>
2010-06-23 17:09 ` [Bug 16140] Suspend To RAM/ Resume broken - Radeon KMS on RV250 bugzilla-daemon
2010-06-23 17:20 ` bugzilla-daemon
2010-06-23 21:02 ` bugzilla-daemon
2010-06-23 21:14 ` bugzilla-daemon
2010-06-23 21:17 ` bugzilla-daemon
2010-06-24 17:20 ` bugzilla-daemon
2010-08-13 9:43 ` bugzilla-daemon
2010-08-13 9:48 ` bugzilla-daemon
2010-08-28 12:35 ` bugzilla-daemon
2010-08-28 12:36 ` bugzilla-daemon
2010-08-28 12:43 ` bugzilla-daemon
2010-09-17 11:30 ` bugzilla-daemon
2010-09-17 11:34 ` bugzilla-daemon
2010-09-17 11:35 ` bugzilla-daemon
2010-09-17 11:36 ` bugzilla-daemon
2010-09-17 15:58 ` bugzilla-daemon
2010-09-20 19:45 ` bugzilla-daemon
2010-10-07 21:28 ` bugzilla-daemon
2010-10-07 21:28 ` bugzilla-daemon
2010-10-07 21:29 ` bugzilla-daemon
2010-10-07 21:30 ` bugzilla-daemon
2010-10-07 21:31 ` bugzilla-daemon
2010-10-07 21:32 ` bugzilla-daemon
2010-10-07 21:38 ` bugzilla-daemon
2010-10-07 22:31 ` bugzilla-daemon
2010-10-07 22:32 ` bugzilla-daemon
2010-10-08 9:00 ` bugzilla-daemon
2010-10-08 9:01 ` bugzilla-daemon
2010-10-08 9:02 ` bugzilla-daemon
2010-10-08 11:52 ` bugzilla-daemon
2010-10-08 11:56 ` bugzilla-daemon
2010-10-08 11:59 ` bugzilla-daemon
2010-10-08 12:00 ` bugzilla-daemon
2010-10-08 17:49 ` bugzilla-daemon
2010-10-08 17:52 ` bugzilla-daemon
2010-10-10 13:41 ` bugzilla-daemon
2010-10-10 23:16 ` bugzilla-daemon
2010-10-29 18:00 ` bugzilla-daemon
2010-11-16 22:55 ` bugzilla-daemon
2010-12-04 16:22 ` bugzilla-daemon
2010-12-13 5:27 ` bugzilla-daemon
2011-03-07 18:49 ` [Bug 16140] [RADEON:KMS:RV250:RESUME] suspend to RAM resume broken bugzilla-daemon
2011-03-07 20:09 ` bugzilla-daemon
2011-03-07 20:24 ` bugzilla-daemon
2011-03-08 18:32 ` bugzilla-daemon
2011-03-08 18:34 ` bugzilla-daemon
2011-03-22 8:38 ` bugzilla-daemon
2011-08-29 3:45 ` bugzilla-daemon
2012-02-09 4:08 ` bugzilla-daemon [this message]
2012-02-09 13:54 ` bugzilla-daemon
2012-02-09 16:12 ` bugzilla-daemon
2012-02-09 16:42 ` bugzilla-daemon
2012-11-23 18:33 ` bugzilla-daemon
2013-12-10 21:43 ` bugzilla-daemon
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=201202090408.q1948uqg020808@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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