From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 73530] Asus U38N: Black screen with Radeon driver in Linux Date: Mon, 17 Nov 2014 19:03:51 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0438579415==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 54ACE6E232 for ; Mon, 17 Nov 2014 11:03:51 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0438579415== Content-Type: multipart/alternative; boundary="1416251031.fCE5E1.26648"; charset="UTF-8" --1416251031.fCE5E1.26648 Date: Mon, 17 Nov 2014 19:03:51 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=73530 --- Comment #71 from Nicolas Werner --- Created attachment 109638 --> https://bugs.freedesktop.org/attachment.cgi?id=109638&action=edit dmesg with drm/radeon: add locking around atombios scratch space usage (In reply to Alex Deucher from comment #70) > (In reply to Nicolas Werner from comment #69) > > > > I also have the same problem. (same notebook, so not surprising) > > > > I tried everything you recommended (in comment #65), in order, nothing > > helps. Any more suggestions? > > Does this patch help? > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/ > ?id=1c9498425453bb65ef339a57705c5ef59fe1541d > Well, not enough, to get something other than a black screen or some flickering before between white and black before it decides to stay black. :/ dmesg with debug attached > > > > Btw, I'm using OpenSUSE, so Kernel 3.16.6. > > > > Also xrandr output is much shorter than the ones posted here, is that normal > > when you use modeset=0? > > Yes. When you set modeset=0 you are effectively disabling the radeon driver > so you end up with vesa or efifb or some other platform driver rather than > the native driver. Makes sense, thanks! -- You are receiving this mail because: You are the assignee for the bug. --1416251031.fCE5E1.26648 Date: Mon, 17 Nov 2014 19:03:51 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 71 on bug 73530 from 
Created attachment 109638 [details]
dmesg with drm/radeon: add locking around atombios scratch space usage

(In reply to Alex Deucher from comment #70)
> (In reply to Nicolas Werner from comment #69)
> > 
> > I also have the same problem. (same notebook, so not surprising)
> > 
> > I tried everything you recommended (in comment #65), in order, nothing
> > helps. Any more suggestions?
> 
> Does this patch help?
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/
> ?id=1c9498425453bb65ef339a57705c5ef59fe1541d
> 
Well, not enough, to get something other than a black screen or some flickering
before between white and black before it decides to stay black. :/
dmesg with debug attached

> > 
> > Btw, I'm using OpenSUSE, so Kernel 3.16.6.
> > 
> > Also xrandr output is much shorter than the ones posted here, is that normal
> > when you use modeset=0?
> 
> Yes.  When you set modeset=0 you are effectively disabling the radeon driver
> so you end up with vesa or efifb or some other platform driver rather than
> the native driver.

Makes sense, thanks!

You are receiving this mail because:
  • You are the assignee for the bug.
--1416251031.fCE5E1.26648-- --===============0438579415== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============0438579415==--