From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 43829] Resuming my AMD A4-3300 based laptop leaves the screen black
Date: Thu, 03 Apr 2014 06:16:27 +0000 [thread overview]
Message-ID: <bug-43829-502-MiWVi5FEfR@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-43829-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 817 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=43829
--- Comment #50 from Helge Bahmann <hcb@chaoticmind.net> ---
(In reply to comment #49)
> I have a similar issue with a samsumg series 3 laptop with "VGA compatible
> controller: Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD
> 6620G]" and "VGA compatible controller: Advanced Micro Devices, Inc.
> [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series]". after resume an external
> monitor show the system is still responsive.
>
> BUT I can make the screen turn on after suspend with the next command:
> sudo pm-suspend --quirk-test --quirk-s3-bios
whoa, that worked as well for me! I'll try to dissect unless someone else jumps
to it, and then make good on my promise above :)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1726 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-04-03 6:16 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 15:27 [Bug 43829] New: Resuming my AMD A4-300 based laptop leaves the screen black bugzilla-daemon
2012-01-06 1:21 ` [Bug 43829] " bugzilla-daemon
2012-01-06 1:22 ` [Bug 43829] Resuming my AMD A4-3300 " bugzilla-daemon
2012-01-08 19:02 ` bugzilla-daemon
2012-01-11 22:16 ` bugzilla-daemon
2012-01-11 22:21 ` bugzilla-daemon
2012-01-12 22:32 ` bugzilla-daemon
2012-01-15 3:14 ` bugzilla-daemon
2012-04-30 12:26 ` bugzilla-daemon
2012-08-17 21:08 ` bugzilla-daemon
2012-09-14 21:12 ` bugzilla-daemon
2012-09-16 16:00 ` bugzilla-daemon
2012-09-16 16:10 ` bugzilla-daemon
2012-09-16 17:23 ` bugzilla-daemon
2012-09-16 23:11 ` bugzilla-daemon
2012-09-24 20:19 ` bugzilla-daemon
2012-10-15 20:52 ` bugzilla-daemon
2012-10-16 12:46 ` bugzilla-daemon
2012-12-28 11:25 ` bugzilla-daemon
2013-01-18 8:02 ` bugzilla-daemon
2013-01-18 8:05 ` bugzilla-daemon
2013-01-18 8:06 ` bugzilla-daemon
2013-01-18 8:09 ` bugzilla-daemon
2013-02-28 19:16 ` bugzilla-daemon
2013-05-03 15:42 ` bugzilla-daemon
2013-05-03 16:01 ` bugzilla-daemon
2013-07-11 20:49 ` bugzilla-daemon
2013-07-11 20:52 ` bugzilla-daemon
2013-07-12 10:38 ` bugzilla-daemon
2013-07-13 4:33 ` bugzilla-daemon
2013-08-11 14:29 ` bugzilla-daemon
2013-08-19 17:21 ` bugzilla-daemon
2013-08-19 17:21 ` bugzilla-daemon
2013-08-19 23:07 ` bugzilla-daemon
2013-09-12 6:29 ` bugzilla-daemon
2013-09-14 20:52 ` bugzilla-daemon
2013-09-14 20:56 ` bugzilla-daemon
2013-09-14 21:00 ` bugzilla-daemon
2013-09-17 23:24 ` bugzilla-daemon
2013-09-27 9:18 ` bugzilla-daemon
2013-10-24 4:10 ` bugzilla-daemon
2013-10-27 20:07 ` bugzilla-daemon
2013-10-27 20:16 ` bugzilla-daemon
2013-11-19 4:53 ` bugzilla-daemon
2013-12-28 11:14 ` bugzilla-daemon
2014-01-19 10:20 ` bugzilla-daemon
2014-03-29 22:31 ` bugzilla-daemon
2014-03-30 22:09 ` bugzilla-daemon
2014-03-31 2:18 ` bugzilla-daemon
2014-04-02 4:18 ` bugzilla-daemon
2014-04-03 2:18 ` bugzilla-daemon
2014-04-03 6:16 ` bugzilla-daemon [this message]
2014-04-03 7:44 ` bugzilla-daemon
2014-04-03 7:50 ` bugzilla-daemon
2014-04-03 8:19 ` bugzilla-daemon
2014-04-03 9:04 ` bugzilla-daemon
2014-04-03 11:03 ` bugzilla-daemon
2014-04-03 17:02 ` bugzilla-daemon
2014-04-03 17:58 ` bugzilla-daemon
2014-04-03 18:12 ` bugzilla-daemon
2014-04-03 19:45 ` bugzilla-daemon
2014-04-03 20:01 ` 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=bug-43829-502-MiWVi5FEfR@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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 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.