Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC
I've verified that I provided the correct dmesg. But, my knowledge of how this is supposed to work is lacking, so I don't know how to debug this. If you could answer some questions, that would help me figure out what to do next. I'd also really like to learn whatever you can tell me about it:
1. Will the kernel choose one of the drivers (radeonfb or radeon) if they're both present or do I need to completely block one of them to get it to work right?
2. Is radeonfb really supposed to be compiled into the kernel as it is, or should it have been built as a module? Why do you think they compiled it into the kernel?
3. If the kernel is activating radeonfb as we can see in dmesg, why would it also load the drm/radeon driver?
4. The login screen comes up and is functional because I can blindly type in my user id and password, but none of the components of the login screen are actually visible except for the mouse. Which component is failing in this scenario (Xorg, radeon(fb), gtk, etc) ?
Thanks for your help!
--------------------------------------------
On Thu, 9/18/14, Michel Dänzer <michel@daenzer.net> wrote:
Subject: Re: Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC
To: "Bill Chatfield" <bill_chatfield@yahoo.com>
Cc: 762047@bugs.debian.org
Date: Thursday, September 18, 2014, 2:24 AM
On 18.09.2014 13:23, Bill Chatfield
wrote:
> [ 0.997986] radeonfb 0000:00:10.0:
enabling device (0006 -> 0007)
> [ 1.193788] radeonfb 0000:00:10.0: Invalid
ROM contents
> [ 1.193813] radeonfb (0000:00:10.0):
Invalid ROM signature 303 should be 0xaa55
> [ 1.193823] radeonfb: Retrieved PLL infos
from Open Firmware
> [ 1.193842] radeonfb: Reference=27.00 MHz
(RefDiv=12) Memory=203.00 Mhz, System=392.00 MHz
> [ 1.193864] radeonfb: PLL min 12000 max
35000
> [ 1.289994] i2c i2c-2: unable to read EDID
block.
> [ 1.441986] i2c i2c-2: unable to read EDID
block.
> [ 1.593986] i2c i2c-2: unable to read EDID
block.
> [ 1.949865] radeonfb: Monitor 1 type LCD
found
> [ 1.949881] radeonfb: EDID probed
> [ 1.949893] radeonfb: Monitor 2 type no
found
> [ 1.949915] radeonfb: Using Firmware
dividers 0x0002008e from PPLL 0
> [ 1.949981] radeonfb: Dynamic Clock Power
Management enabled
> [ 1.982573] Console: switching to colour
frame buffer device 160x53
> [ 2.004457] radeonfb: Backlight
initialized (radeonbl0)
> [ 2.004635] radeonfb (0000:00:10.0): ATI
Radeon 4e50 "NP"
This shows that radeonfb is still enabled, so it doesn't
provide the
information corresponding to the bug.
--
Earthling Michel Dänzer
|
http://www.amd.com
Libre software enthusiast
|
Mesa and X developer
Reply to: