Red Hat Bugzilla – Bug 484992
xorg-x11-drv-ati 6.10 with KMS does not detect the secondary DVI port
Last modified: 2009-12-18 02:53:18 EST
Created attachment 331501 [details]
dmesg with KMS
Description of problem:
xorg-x11-drv-ati 6.10 cannot detect the secondary DVI port when modesetting is enabled. My TFT monitor being connected to the secondary DVI, I then have no usable screen and Xorg crashes :
(WW) RADEON(0): No outputs definitely connected, trying again...
(EE) RADEON(0): No modes.
(EE) Screen(s) found, but none have a usable configuration.
Version-Release number of selected component (if applicable):
A user mentioned on bodhi that xorg-x11-drv-ati-6.10.0-1.fc10 exhibited a similar problem, see https://admin.fedoraproject.org/updates/xorg-x11-drv-ati-6.10.0-2.fc10 .
Steps to Reproduce:
1. Boot without nomodeset with secondary DVI port hooked to monitor
2. If the primary DVI port is connected, Xorg may start normally, else no Xorg
Xorg crashes if the primary DVI port is not connected.
Xorg launches itself.
With nomodeset this does not happen.
This did not happen with the 6.9.x driver either.
Created attachment 331502 [details]
dmesg with nomodeset
Created attachment 331503 [details]
Xorg log with KMS
Created attachment 331504 [details]
Xorg log with nomodeset
Do you still have this issue with fedora 12 (you can test livecd from http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/) ?
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. 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 '10'.
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 10'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 10 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:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.