Bug 47064

Summary: no VGA output on Radeon HD6550D when 2 monitors are connected
Product: xorg Reporter: diego.abelenda
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED DUPLICATE QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
DRI/radeon related part of dmesg
none
xrandr output
none
DRM/radeon related part of dmesg none

Description diego.abelenda 2012-03-07 09:52:20 UTC 
Created attachment 58130 [details]
DRI/radeon related part of dmesg

I just bought an AMD system and when I tried and connected my dual screen. When The uEFI initializes them both display the same thing, but once radeon loads I get only the DVI-connected one displaying anything.
I have some DisplayPort related errors in my kernel log so maybe this is an initialization problem of KMS.

xrandr says both monitors are up and at the same resolution (1920x1080@60) but obviously it doesn't talk about the same screen as me.

The fun fact was that the exact same setup worked with an nvidia card and nouveau.
Second Fun fact is that on windows7 with the latest version of Catalyst the VGA monitor gets an unsupported mode when trying to set it into 1920x1080@60Hz the only way to get an image is reducing resolution to 1680x1050 (or less).
Comment 1 diego.abelenda 2012-03-07 09:53:20 UTC 
Created attachment 58131 [details]
xrandr output
Comment 2 diego.abelenda 2012-03-07 12:12:43 UTC 
Created attachment 58139 [details]
DRM/radeon related part of dmesg

Proper output... the previous one was with a nvidia card plugged and only the DVI monitor connected to the Radeon not the VGA one (this is why there is no error in the log, the error is there only when a VGA monitor is connected during boot).
Comment 3 Alex Deucher 2012-03-12 06:43:07 UTC 

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

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.