Bug 548721

Summary: Blank screen from Xorg on RadeonHD/HDMI
Product: [Fedora] Fedora Reporter: Jan ONDREJ <ondrejj>
Component: xorg-x11-drv-radeonhdAssignee: Hans Ulrich Niedermann <rhbugs>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: rh, rhbugs, soeren.grunewald
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: 2010-12-04 01:30:08 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
without nomodeset
none
with nomodeset none

Description Jan ONDREJ 2009-12-18 11:25:39 UTC
Created attachment 379190 [details]
without nomodeset

Description of problem:
When booting Fedora 12 on my system without "nomodeset", Xorg starts, but there is no video on my display.

Version-Release number of selected component (if applicable):
kernel-PAE-2.6.31.6-166.fc12.i686
xorg-x11-drv-radeonhd-1.3.0-3.15.20091112git.fc12.i686
xorg-x11-server-Xorg-1.7.3-3.fc12.i686

Same problem with older F12 kernels too.

How reproducible:
Always

Steps to Reproduce:
1. boot F12 on my hardware configuration

Actual results:
blank screen (may be monitor is OFF)

Expected results:
functional X desktop

Additional info:
I will attach 2 Xorg.logs, one without nomodeset, one with. You can see some differences. I see at least this curious change:

-(II) RADEONHD(0): Found radeon drm 1.31.0.
+(II) RADEONHD(0): Found radeon drm 2.0.0.

Comment 1 Jan ONDREJ 2009-12-18 11:26:20 UTC
Created attachment 379191 [details]
with nomodeset

Comment 2 Soeren Grunewald 2009-12-18 13:50:07 UTC
this might belong together with
https://bugzilla.redhat.com/show_bug.cgi?id=540556

Comment 3 Hans Ulrich Niedermann 2009-12-18 14:56:28 UTC
radeonhd can only work if the kernel is booted with "nomodeset" (older kernels) or "radeon.modeset=0" (newer kernels). (I am not certain what kernel version marks the border between "old" and "new" here.)

Starting with xorg-x11-drv-radeonhd-1.3.0-3.15.20091112git, radeonhd can detect whether KMS is enabled and abort cleanly if it is.

Do you get a working X display when you use Fedora's default driver for your card radeon(4) from the xorg-x11-drv-ati package?

Comment 4 Jarmo 2010-01-03 08:46:49 UTC
I had similar issues with Mobility Radeon HD 3470 (RV620) on Fedora 12.
My experience so far:

Default driver xorg-x11-drv-ati works (even with KMS) when xorg.conf is manually created and configured.

xorg-x11-drv-radeonhd works when the kernel is booted with "nomodeset" or
radeon.modeset=0" (so no KMS) and xorg.conf is manually created and configured.
If xorg.conf is not configured, then xorg-x11-drv-radeonhd set driver to "VESA" and the screen resolution is too low (wrong).

I don't know what is the benefit or difference to use xorg-x11-drv-radeonhd instead of xorg-x11-drv-ati as xorg-x11-drv-ati seems to work better currently (set the driver correct and also may work with KMS)?

Comment 5 Hans Ulrich Niedermann 2010-01-03 12:19:37 UTC
(In reply to comment #4)
> I had similar issues with Mobility Radeon HD 3470 (RV620) on Fedora 12.
> My experience so far:
> 
> Default driver xorg-x11-drv-ati works (even with KMS) when xorg.conf is
> manually created and configured.

I am glad to hear that. It is even supposed to work with no xorg.conf file at all.

> xorg-x11-drv-radeonhd works when the kernel is booted with "nomodeset" or
> radeon.modeset=0" (so no KMS) and xorg.conf is manually created and configured.

Also glad to hear about that.

> If xorg.conf is not configured, then xorg-x11-drv-radeonhd set driver to "VESA"
> and the screen resolution is too low (wrong).

Xorg will pick a driver, and in the absense of the -ati package (with the radeon driver), will load the default vesa driver instead.

> I don't know what is the benefit or difference to use xorg-x11-drv-radeonhd
> instead of xorg-x11-drv-ati as xorg-x11-drv-ati seems to work better currently
> (set the driver correct and also may work with KMS)?  

In Fedora, radeonhd exists only for the (increasingly rare) cases where something does not quite work as intended with -ati and the user still want a working display. That is why it needs manual installation, manual xorg.conf editing, etc., while the -ati radeon driver will work without any manual interaction.

Comment 6 Jarmo 2010-01-03 17:17:20 UTC
(In reply to comment #5)
> 
> In Fedora, radeonhd exists only for the (increasingly rare) cases where
> something does not quite work as intended with -ati and the user still want a
> working display. That is why it needs manual installation, manual xorg.conf
> editing, etc., while the -ati radeon driver will work without any manual
> interaction.  

Excellent, sufficient answer - thanks!

I also found reason why I needed manual xorg.conf.
I had (and have) an external display with my laptop. Although the  external display is switch off (no power), it's connected to VGA port. Xorg found/see it and set the screen resolution based on external display which is wrong for laptop display (too big resolution).

Comment 7 Bug Zapper 2010-11-04 03:02:34 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Jan ONDREJ 2010-11-04 07:40:00 UTC
Problem still persist in F13, but it's look to be fixed in F14. Can we change version to 14 and close as "works for me"?

Comment 9 Bug Zapper 2010-12-04 01:30:08 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.