From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 67107] Xorg starts and crashes with DPM enable
Date: Wed, 02 Oct 2013 02:51:32 +0000 [thread overview]
Message-ID: <bug-67107-502-MokyMc9ZAL@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-67107-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1295 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=67107
--- Comment #13 from Adam Honse <calcprogrammer1@gmail.com> ---
To follow up with my previous comment, I tried disabling the discrete GPU. In
my case I disable it AFTER the radeon module is loaded (because doing it the
other way around causes errors that lag the machine to an unusable state). The
machine has no means of disabling it in the BIOS so I use the acpi_call kernel
module with the turn_off_gpu script from here:
https://github.com/mkottman/acpi_call/
What I did was start the laptop with dpm=1 and gdm set to not start
automatically so I'd boot to a text console. Radeon module loads at boot and
KMS sets the console to the appropriate resolution. Then I insmod the
acpi_call.ko and run the turn-off-gpu script which turns off the discrete GPU.
Then I started gdm, logged in, and ran glxgears to confirm that the integrated
GPU was working (ran fine) and looked at Xorg.0.log to confirm radeon.dpm=1 (it
did). This was on battery power, haven't tested plugged in. I'm downloading
Open Arena now to see if gaming performance is improved. Using xrandr
--listproviders confirms that only one GPU is active and available which is the
integrated one.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2150 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:[~2013-10-02 2:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-20 4:33 [Bug 67107] New: Xorg starts and crashes with DPM enable bugzilla-daemon
2013-07-20 16:36 ` [Bug 67107] " bugzilla-daemon
2013-07-20 19:47 ` bugzilla-daemon
2013-07-29 18:56 ` bugzilla-daemon
2013-08-26 19:52 ` bugzilla-daemon
2013-08-26 20:01 ` bugzilla-daemon
2013-08-26 20:01 ` bugzilla-daemon
2013-08-27 22:07 ` bugzilla-daemon
2013-08-27 22:08 ` bugzilla-daemon
2013-09-17 2:01 ` bugzilla-daemon
2013-09-17 2:43 ` bugzilla-daemon
2013-09-17 17:57 ` bugzilla-daemon
2013-09-26 0:06 ` bugzilla-daemon
2013-10-02 2:51 ` bugzilla-daemon [this message]
2013-10-10 22:41 ` bugzilla-daemon
2013-10-10 23:06 ` bugzilla-daemon
2013-10-10 23:20 ` bugzilla-daemon
2013-10-11 22:43 ` bugzilla-daemon
2013-10-12 1:08 ` 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-67107-502-MokyMc9ZAL@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox