From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 66963] r600: linux v3.11.0-RC isn't booting with radeon.dpm=1 option in grub Date: Mon, 30 Sep 2013 05:44:17 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0193992207==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id C03FCE6166 for ; Sun, 29 Sep 2013 22:44:17 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0193992207== Content-Type: multipart/alternative; boundary="1380519857.A3fF16.5477"; charset="us-ascii" --1380519857.A3fF16.5477 Date: Mon, 30 Sep 2013 05:44:17 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=66963 --- Comment #136 from Alex Deucher --- (In reply to comment #135) > Created attachment 86825 [details] > dmesg when under works due to setting .debug=1 > > I tried again with the latest rc3 build and it still doesn't work; I had > left changes from comment 94 intact. Trying to get more information I tried > booting with radeon.modeset=0 radeon.debug=1. Once I re-loaded the module > with dpm, now it works! So it works correctly if you set it to debug mode, > otherwise I can't get any logs of the event. > There is no radeon.debug parameter: [ 34.991462] radeon: unknown parameter 'debug' ignored Seems like you just got lucky this time. Does it work reliably if you disable radeon and boot into a non-X runlevel, then manually load radeon? E.g., boot with: radeon.modeset=0 1 on the kernel command line in grub to boot into single user mode. then at the command prompt: modprobe -r radeon modprobe radeon modeset=1 dpm=1 > This is the dmesg from when it worked (with debug on). I noticed there are > some HDMI errors; I only have DVI actually hooked up. You can ignore those. -- You are receiving this mail because: You are the assignee for the bug. --1380519857.A3fF16.5477 Date: Mon, 30 Sep 2013 05:44:17 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 136 on bug 66963 from 
(In reply to comment #135)
> Created attachment 86825 [details]
> dmesg when under works due to setting .debug=1
> 
> I tried again with the latest rc3 build and it still doesn't work; I had
> left changes from comment 94 intact.  Trying to get more information I tried
> booting with radeon.modeset=0 radeon.debug=1.  Once I re-loaded the module
> with dpm, now it works!  So it works correctly if you set it to debug mode,
> otherwise I can't get any logs of the event.  
> 

There is no radeon.debug parameter:
[   34.991462] radeon: unknown parameter 'debug' ignored

Seems like you just got lucky this time. Does it work reliably if you disable
radeon and boot into a non-X runlevel, then manually load radeon?  E.g., boot
with:
radeon.modeset=0 1
on the kernel command line in grub to boot into single user mode.  then at the
command prompt:
modprobe -r radeon
modprobe radeon modeset=1 dpm=1

> This is the dmesg from when it worked (with debug on).  I noticed there are
> some HDMI errors; I only have DVI actually hooked up.

You can ignore those.

You are receiving this mail because:
  • You are the assignee for the bug.
--1380519857.A3fF16.5477-- --===============0193992207== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============0193992207==--