Bug 522238

Summary: KMS:RV280:9200Pro DVI/VGA encoder conflict lead to DVI off
Product: [Fedora] Fedora Reporter: Martin Decky <martin>
Component: xorg-x11-drv-atiAssignee: Jérôme Glisse <jglisse>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 12CC: airlied, awilliam, jglisse, leifer, mcepl, xgl-maint
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: card_R200
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-12-01 00:31:33 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
dmesg output
none
X.org log none

Description Martin Decky 2009-09-09 20:30:03 UTC
Created attachment 360335 [details]
dmesg output

Description of problem:
My Radeon card has three outputs: D-Sub, DVI and S-video. There is an LCD connected to both the D-Sub and the DVI output, the S-video output is disconnected. The KMS driver discovers all outputs, but turns the DVI output off (the LCD displays "No signal" and goes to sleep) despite there is a monitor connected. In X11, the displayed portion of the framebuffer is apparently enlarged to cover both heads, despite the DVI output stays off (a part of the desktop is not visible).

Version-Release number of selected component (if applicable):
Test Day:2009-09-09 Radeon LiveCD for i686

How reproducible:
Always

Expected results:
The DVI output should stay on, because there is a monitor connected and since the S-video output is disconnected, there are enough CRTs for both outputs.

Additional info:
ATI Technologies Inc RV280 [Radeon 9200 PRO] (rev 01) [1002:5960]

In Fedora 11 with xorg-x11-drv-ati-6.12.2-16.fc11.i586 both D-Sub and DVI stay on since the initial KMS screen setup.

Comment 1 Martin Decky 2009-09-09 20:30:24 UTC
Created attachment 360336 [details]
X.org log

Comment 2 Adam Williamson 2009-09-16 18:34:35 UTC
(II) RADEON(0): Output DVI-0 using initial mode 1920x1080 +1920+0

is that the right mode?

What happens if you boot with only the DVI monitor connected - not the d-sub one?

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 3 Martin Decky 2009-10-05 22:42:29 UTC
(In reply to comment #2)

Yes, mode 1920x1080 +1920+0 is correct for the DVI output.

I have retested it with desktop-i386.20091002.15.iso snapshot and the results are the same as previously. With both outputs connected DVI-0 stays off again and the output of dmesg and X.org log is essentially the same as previously, only these lines in dmesg are interesting:

[drm] 2: conflicting encoders switching off SVIDEO-1
[drm] in favor of DVI-I-1

Nevertheless, DVI output stays off.

With VGA output disconnected and only the DVI output connected during boot the single monitor is detected and turned on. Again, nothing interesting to be found in the logs. After reconnecting the VGA output and redetecting the displays DVI output is turned of (despite the connected monitor being correctly detected).

Comment 4 Jérôme Glisse 2009-11-03 20:07:24 UTC
Does the lcd connected on the dvi goes through a dvi->vga adapter ? According to log it doesn't, but just want to make sure:
1 LCD connected to VGA
1 LCD connected to DVI-I with a DVI-I cable

Both LCD has 1920x1080 resolution.

Comment 5 Martin Decky 2009-11-04 01:31:12 UTC
No, there are no adapters what so ever. So just to recapitulate:

1 LCD (BenQ G2220HD 1920x1080) from VGA output to VGA input using VGA cable
1 LCD (BenQ G2220HD 1920x1080) from DVI-I output to DVI-D input using DVI cable

Comment 6 Matěj Cepl 2009-11-05 17:15:28 UTC
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages (at least F12Beta, but even better if the very latest versions).

Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]

Comment 7 Bug Zapper 2009-11-16 12:08:47 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Leif Gruenwoldt 2009-11-25 04:47:46 UTC
This looks like a duplicate of bug #484992

Comment 9 Adam Williamson 2009-11-25 19:12:44 UTC
different hardware, and that's reported against F10. Dave?

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 10 Leif Gruenwoldt 2009-11-25 19:34:32 UTC
(In reply to comment #9)
> different hardware, and that's reported against F10. Dave?

The commonality between several of these bugs appears to be KMS causing a secondary DVI display to not light up.

@Martin, in my configuration switching to a VGA cable for the secondary display caused it to light up. Is this the case for you?

Comment 11 Martin Decky 2009-11-26 12:44:03 UTC
(In reply to comment #10)
> The commonality between several of these bugs appears to be KMS causing a
> secondary DVI display to not light up.

I believe there is at least one major difference between this bug and bug #484992. In the bug #484992 the DVI output is not even detected (if I am not mistaken), while in this bug the DVI output gets detected fine and the size of the framebuffer gets enlarged accordingly, but the display does not light up (it indicates "no signal").

Sure, there might be some relations between these two bugs, but it is probably not an obvious one.

> @Martin, in my configuration switching to a VGA cable for the secondary display
> caused it to light up. Is this the case for you?  

No, in my case using a VGA cable does not help. However, I have had no chance to give it a try since 2009-11-03, thus it might be already fixed somehow in F12 release. I hope to have some spare time to test it again soon.

Comment 12 Dave Airlie 2009-12-01 00:14:03 UTC
awaiting reported retest. I think we fixed this already for F12 GA.

Comment 13 Martin Decky 2009-12-01 00:28:07 UTC
Yes, it works again in kernel-PAE-2.6.31.5-127.fc12.i686. Thanks for the cooperation. I suggest closing this bug.