Bug 463118

Summary: Regression: X presents blank screen
Product: [Fedora] Fedora Reporter: W. Michael Petullo <mike>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: benja, bugzilla, kernel-maint, notverysmart, quintela, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: powerpc   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-11-13 23:30:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 469502    
Bug Blocks:    
Attachments:
Description Flags
Log of X starting -- result is blank screen, changing virtual terminals does not work
none
/var/log/messages with the kernel Oops none

Description W. Michael Petullo 2008-09-21 22:18:54 UTC
Description of problem:
X11 is broken for me on a PowerPC G4 iBook in recent versions of Rawhide. When I boot into X mode, my screen goes black. Switching to another (text) virtual console does not work -- i.e., the screen stays black. My graphics card is identified as an ATI Technologies Inc M9+ 5C63 [Radeon Mobility 9200 (AGP)] (rev 01). I have removed my xorg.conf, but things were working fine without it until the update. 

Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.5.0-6.fc10.ppc

How reproducible:
Every time

Steps to Reproduce:
Boot into X mode.
  
Actual results:
Blank screen, as noted above.

Expected results:
X should start.

Additional info:
The update that caused this regression happened sometime after bug #460721 was fixed.

Comment 1 W. Michael Petullo 2008-09-21 22:27:58 UTC
Created attachment 317330 [details]
Log of X starting -- result is blank screen, changing virtual terminals does not work

Comment 2 Benjamin Jacobs 2008-09-30 14:42:27 UTC
Same hardware (iBook G4/ati m9+ m5c63), same problem. However, I'm able to boot in runlevel 3 but the kernel drm/radeon driver is oopsing. So X won't start and I've the black screen in rc5. See the attached log.

Also, with those kernels, plymouth(?) displays some bright white kernel lines and then displays three mixed progress lines (blue, light blue and white) at the bottom of the screen with some more garbage. Sorry no camera but, thrust me, it doesn't look good.

Comment 3 Benjamin Jacobs 2008-09-30 14:45:28 UTC
Created attachment 318081 [details]
/var/log/messages with the kernel Oops

Comment 4 W. Michael Petullo 2008-10-02 00:44:14 UTC
In addition to my X problem, I see the same plymouth problems as Benjamin (comment #2). However, I would like to point out that I did at one point have X working even though plymouth didn't look quite right. So, these seem to be separate problems.

Comment 5 W. Michael Petullo 2008-10-02 22:48:47 UTC
I had hoped that my problem was the same as the one in the thread at https://www.redhat.com/archives/fedora-devel-list/2008-October/msg00088.html. However, an update to the newest Rawhide (including a libdrm resync) did not seem to fix the problem.

Comment 6 Steve 2008-10-16 09:15:02 UTC
I've the same issue since xorg-x11-drv-ati-6.9.0-25.fc10.i386. After graphical boot, the Monitor turns off.

Good: xorg-x11-drv-ati-6.9.0-21.fc10.i386

Bad : xorg-x11-drv-ati-6.9.0-25.fc10.i386
      xorg-x11-drv-ati-6.9.0-27.fc10.i386

Comment 7 Steve 2008-10-16 09:16:26 UTC
Sorry forgot to say: Graphic Card is "ATI Radeon HD 3850 AGP".

Comment 8 Steve 2008-10-21 07:45:08 UTC
xorg-x11-drv-ati-6.9.0-28.fc10.i386 is also broken!

Comment 9 Steve 2008-10-21 21:42:12 UTC
xorg-x11-drv-ati-6.9.0-29.fc10.i386 is also broken.

Comment 10 Steve 2008-10-21 22:23:42 UTC
I'va made a new bug-report for this bug, since it is not the same as in description:
https://bugzilla.redhat.com/show_bug.cgi?id=467966

Comment 11 Jonathan Matthew 2008-10-25 13:30:24 UTC
I'm also seeing this (or at least these symptoms) on a similar machine to the submitter's.  With the 2.6.25.11-97 kernel from F9, everything works.

Comment 12 W. Michael Petullo 2008-10-25 16:55:08 UTC
I downgraded my kernel to 2.6.26.6-79.fc9.ppc and the problem is fixed. Reassigned bug to kernel.

Comment 13 Jonathan Matthew 2008-11-12 11:34:37 UTC
The 2.6.27.5-94 f10 kernel also works for me.  As far as I recall, 2.6.27.4-79 didn't.

Comment 14 W. Michael Petullo 2008-11-13 23:30:15 UTC
Fixed in 2.6.27.5-94.fc10.ppc.