From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 61891] Cannot switch off Radeon 6400M with vgaswitcheroo
Date: Fri, 27 Dec 2013 09:49:46 +0000 [thread overview]
Message-ID: <bug-61891-2300-nK3fVMMpgw@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-61891-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=61891
--- Comment #13 from madcatx@atlas.cz ---
"acpiphp.disable=1" in the kernel bootline fixes the problem for me. The Radeon
is reported as off in vgaswitcheroo and the laptop draws less power. The DIS
even powers up and down correctly with DRI_PRIME.
Acpidump provided
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-12-27 9:49 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-22 14:36 [Bug 61891] New: Cannot switch off Radeon 6400M with vgaswitcheroo bugzilla-daemon
2013-09-22 14:38 ` [Bug 61891] " bugzilla-daemon
2013-09-22 14:38 ` bugzilla-daemon
2013-09-22 21:07 ` bugzilla-daemon
2013-09-22 23:44 ` bugzilla-daemon
2013-09-22 23:46 ` bugzilla-daemon
2013-09-26 1:09 ` bugzilla-daemon
2013-11-05 20:27 ` bugzilla-daemon
2013-11-05 20:28 ` bugzilla-daemon
2013-11-05 21:01 ` bugzilla-daemon
2013-11-23 13:29 ` bugzilla-daemon
2013-12-13 14:32 ` bugzilla-daemon
2013-12-15 23:38 ` bugzilla-daemon
2013-12-24 19:48 ` bugzilla-daemon
2013-12-27 9:49 ` bugzilla-daemon [this message]
2013-12-27 9:50 ` bugzilla-daemon
2013-12-27 22:59 ` bugzilla-daemon
2013-12-27 23:07 ` bugzilla-daemon
2013-12-27 23:15 ` bugzilla-daemon
2013-12-27 23:17 ` bugzilla-daemon
2013-12-27 23:23 ` bugzilla-daemon
2013-12-27 23:25 ` bugzilla-daemon
2013-12-27 23:26 ` bugzilla-daemon
2013-12-27 23:27 ` bugzilla-daemon
2013-12-27 23:41 ` bugzilla-daemon
2013-12-27 23:43 ` bugzilla-daemon
2013-12-27 23:47 ` bugzilla-daemon
2013-12-28 0:01 ` bugzilla-daemon
2013-12-28 0:45 ` bugzilla-daemon
2013-12-28 0:45 ` bugzilla-daemon
2013-12-28 1:00 ` bugzilla-daemon
2013-12-28 1:31 ` bugzilla-daemon
2013-12-28 1:36 ` bugzilla-daemon
2013-12-28 2:10 ` bugzilla-daemon
2013-12-28 2:22 ` bugzilla-daemon
2013-12-28 2:57 ` bugzilla-daemon
2013-12-28 10:36 ` bugzilla-daemon
2013-12-28 12:14 ` bugzilla-daemon
2013-12-28 12:18 ` bugzilla-daemon
2013-12-28 12:21 ` bugzilla-daemon
2013-12-28 12:22 ` bugzilla-daemon
2013-12-28 12:40 ` bugzilla-daemon
2013-12-28 12:45 ` bugzilla-daemon
2013-12-28 12:53 ` bugzilla-daemon
2013-12-28 12:55 ` bugzilla-daemon
2013-12-28 13:03 ` bugzilla-daemon
2013-12-28 13:24 ` bugzilla-daemon
2013-12-28 13:28 ` bugzilla-daemon
2013-12-28 13:29 ` bugzilla-daemon
2013-12-28 13:30 ` bugzilla-daemon
2013-12-28 13:35 ` bugzilla-daemon
2013-12-28 13:39 ` bugzilla-daemon
2013-12-28 13:40 ` bugzilla-daemon
2013-12-28 14:01 ` bugzilla-daemon
2013-12-28 14:03 ` bugzilla-daemon
2013-12-28 14:20 ` bugzilla-daemon
2013-12-28 14:26 ` bugzilla-daemon
2013-12-28 14:59 ` bugzilla-daemon
2013-12-28 15:08 ` bugzilla-daemon
2013-12-28 15:32 ` bugzilla-daemon
2013-12-28 15:59 ` bugzilla-daemon
2013-12-28 16:36 ` bugzilla-daemon
2013-12-28 17:22 ` bugzilla-daemon
2013-12-28 17:25 ` bugzilla-daemon
2013-12-28 17:26 ` bugzilla-daemon
2013-12-28 17:31 ` bugzilla-daemon
2013-12-28 21:00 ` 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-61891-2300-nK3fVMMpgw@https.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;
as well as URLs for NNTP newsgroup(s).