From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73053] HD6850 cannot boot with dpm
Date: Fri, 27 Dec 2013 00:42:02 +0000 [thread overview]
Message-ID: <bug-73053-502-0V71L7BjkE@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-73053-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 830 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=73053
--- Comment #1 from Alex Deucher <agd5f@yahoo.com> ---
(In reply to comment #0)
> The monitor goes blank, and the system becomes totally unresponsive as soon
> as the radeon module is loaded, if I boot 3.12.4 with radeon.dpm=1 or I boot
> 3.13-rc5 without radeon.dpm=0.
Did dpm ever work on your board? Just to clarify, does 3.13-rc5 fail to boot
even with radeon.dpm=0? Please attach a copy of your dmesg output, Xorg log,
and vbios. To get a copy of your vbios:
(as root)
(use lspci to get the bus id)
cd /sys/bus/pci/devices/<pci bus id>
echo 1 > rom
cat rom > /tmp/vbios.rom
echo 0 > rom
>
> Bug #66963 might be related.
Unrelated. That bug is about rv6xx asics. Your chip is a BTC part.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1805 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-12-27 0:42 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-26 23:16 [Bug 73053] New: HD6850 cannot boot with dpm bugzilla-daemon
2013-12-27 0:42 ` bugzilla-daemon [this message]
2013-12-27 11:14 ` [Bug 73053] " bugzilla-daemon
2013-12-27 20:17 ` bugzilla-daemon
2013-12-27 20:18 ` bugzilla-daemon
2014-01-07 18:44 ` bugzilla-daemon
2014-01-08 22:18 ` bugzilla-daemon
2014-01-08 22:19 ` bugzilla-daemon
2014-01-08 22:21 ` bugzilla-daemon
2014-01-08 22:21 ` bugzilla-daemon
2014-01-08 22:45 ` bugzilla-daemon
2014-01-08 23:52 ` bugzilla-daemon
2014-01-09 3:00 ` bugzilla-daemon
2014-01-09 5:29 ` bugzilla-daemon
2014-01-09 16:44 ` bugzilla-daemon
2014-01-09 16:45 ` bugzilla-daemon
2014-01-09 16:46 ` bugzilla-daemon
2014-01-09 16:46 ` bugzilla-daemon
2014-01-11 15:58 ` bugzilla-daemon
2014-01-12 9:12 ` bugzilla-daemon
2014-01-12 9:13 ` bugzilla-daemon
2014-01-12 9:24 ` bugzilla-daemon
2014-01-12 18:17 ` bugzilla-daemon
2014-01-14 13:52 ` bugzilla-daemon
2014-01-14 13:52 ` [Bug 73053] dpm hangs with BTC parts bugzilla-daemon
2014-01-15 21:14 ` bugzilla-daemon
2014-01-17 15:11 ` bugzilla-daemon
2014-01-17 15:55 ` bugzilla-daemon
2014-01-19 21:56 ` bugzilla-daemon
2014-03-06 21:15 ` bugzilla-daemon
2014-03-08 20:25 ` bugzilla-daemon
2014-03-09 16:36 ` bugzilla-daemon
2014-07-01 16:18 ` bugzilla-daemon
2014-07-01 21:11 ` bugzilla-daemon
2014-07-07 13:16 ` bugzilla-daemon
2014-07-10 8:45 ` bugzilla-daemon
2014-07-10 12:09 ` bugzilla-daemon
2014-07-10 12:54 ` bugzilla-daemon
2014-07-10 16:56 ` bugzilla-daemon
2014-07-11 22:32 ` bugzilla-daemon
2014-07-12 0:10 ` bugzilla-daemon
2014-07-12 0:35 ` bugzilla-daemon
2014-07-12 12:49 ` bugzilla-daemon
2014-07-12 12:52 ` bugzilla-daemon
2014-07-13 1:43 ` bugzilla-daemon
2014-07-13 10:29 ` bugzilla-daemon
2014-07-13 21:15 ` bugzilla-daemon
2014-07-14 13: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-73053-502-0V71L7BjkE@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;
as well as URLs for NNTP newsgroup(s).