Bug 511930

Summary: AddScreen/ScreenInit failed for ATI Radeon X800
Product: [Fedora] Fedora Reporter: Joachim Frieben <jfrieben>
Component: xorg-x11-drv-atiAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: rderooy, xgl-maint, zaitcev
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-07-23 08:12:03 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:
Attachments:
Description Flags
Xorg.0.log for ATI Radeon X800 none

Description Joachim Frieben 2009-07-15 17:58:15 UTC
Created attachment 353861 [details]
Xorg.0.log for ATI Radeon X800

Description of problem:
X fails to launch for an ATI Technologies Inc Radeon X800 SE (R430) (PCIE) rev 0. The last lines of Xorg.0.log say

  "failed to add fb"

  "Fatal server error:"
  "AddScreen/ScreenInit failed for driver 0"

Version-Release number of selected component (if applicable):
xorg-x11-drv-ati-6.12.2-19.fc12.1.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Start X.
  
Actual results:
After several attempts to launch the X server, the system drops back to the framebuffer.

Expected results:
X is launched successfully, and the GDM login panel appears on the screen.

Additional info:
- Installed packages include
  * xorg-x11-drv-ati-6.12.2-19.fc12.1.x86_64
  * xorg-x11-server-Xorg-1.6.99-13.20090715.fc12.x86_64
  * kernel-2.6.31-0.68.rc3.fc12.x86_64

Comment 1 Pete Zaitcev 2009-07-22 14:08:12 UTC
Is there a message like this in dmesg?

[drm:radeon_cp_init_kms] *ERROR* invalid ioctl with kms radeon_cp_init_kms

Maybe bug 512757 is a dup of this.

Comment 2 Joachim Frieben 2009-07-22 17:57:40 UTC
(In reply to comment #1)
Right, that's exactly the message that fills dmesg.

Comment 3 Robert de Rooy 2009-07-23 08:12:03 UTC

*** This bug has been marked as a duplicate of bug 512757 ***